From: Alexander Hoogerhuis <alexh@ihatent.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [OOPS] 2.5.69-mm6
Date: 18 May 2003 14:57:04 +0200 [thread overview]
Message-ID: <87wugoct0f.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <20030516191711.GX8978@holomorphy.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
William Lee Irwin III <wli@holomorphy.com> writes:
> On Fri, May 16, 2003 at 01:26:20PM +0200, Alexander Hoogerhuis wrote:
> >>> This one goes in -mm5 as well, machine runs fine for a while in X, but
> >>> trying to switch to a vty send the machine into the tall weeds...
>
> On Fri, May 16, 2003 at 11:08:48AM -0700, William Lee Irwin III wrote:
> >> Could you run with the radeon driver non-modular and kernel debugging
> >> on? Then when it oopses could you use addr2line(1) to resolve this to
> >> a line number?
> >> I'm at something of a loss with respect to dealing with DRM in general.
>
> On Fri, May 16, 2003 at 07:56:38PM +0100, Dave Jones wrote:
> > Not that I'm pointing fingers, but it could be that
> > reslabify-pgds-and-pmds.patch again ? Maybe it's still not quite right?
> > Might be worth backing out and retesting, just to rule it out.
>
> Yes, if he could try that too it would help. I got a private reply
> saying he'd be out of the picture for over 24 hours. I'm looking for
> someone with a radeon to fill in the gap until then.
>
I'm back in the picture now, the machine is chugging along, churning
out a new kernel. I'll get the details out in a few hours :)
>
> -- wli
mvh,
A
- --
Alexander Hoogerhuis | alexh@ihatent.com
CCNP - CCDP - MCNE - CCSE | +47 908 21 485
"You have zero privacy anyway. Get over it." --Scott McNealy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE+x4McCQ1pa+gRoggRAl0SAJ49l27s2cdi7pNNCE8xI6MtC2wrdQCgxotU
Nlqa0EFTAAZ/XoSi/HHi8Ng=
=XpPy
-----END PGP SIGNATURE-----
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-18 12:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 8:54 2.5.69-mm6 Andrew Morton
2003-05-16 11:26 ` [OOPS] 2.5.69-mm6 Alexander Hoogerhuis
2003-05-16 18:08 ` William Lee Irwin III
2003-05-16 18:56 ` Dave Jones
2003-05-16 19:17 ` William Lee Irwin III
2003-05-17 3:23 ` Zwane Mwaikambo
2003-05-17 14:16 ` Zwane Mwaikambo
2003-05-18 13:01 ` Alexander Hoogerhuis
2003-05-19 8:23 ` Alexander Hoogerhuis
2003-05-19 8:36 ` Zwane Mwaikambo
2003-05-19 8:45 ` Zwane Mwaikambo
2003-05-19 8:53 ` Alexander Hoogerhuis
2003-05-19 8:53 ` Zwane Mwaikambo
2003-05-19 9:23 ` Alexander Hoogerhuis
2003-05-19 10:18 ` Alexander Hoogerhuis
2003-05-19 11:03 ` Zwane Mwaikambo
2003-05-18 12:59 ` Alexander Hoogerhuis
2003-05-18 12:57 ` Alexander Hoogerhuis [this message]
2003-05-16 17:28 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 17:55 ` 2.5.69-mm6 Dave Jones
2003-05-16 18:10 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 18:30 ` 2.5.69-mm6 Dave Jones
2003-05-16 19:02 ` 2.5.69-mm6 Andreas Henriksson
2003-05-16 19:25 ` 2.5.69-mm6 Dave Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wugoct0f.fsf@lapper.ihatent.com \
--to=alexh@ihatent.com \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox