From: Dave Jones <davej@redhat.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk,
davej@codemonkey.org.uk, airlied@linux.ie
Subject: Re: 2.6.15-mm1 - locks solid when starting KDE (EDAC errors)
Date: Fri, 6 Jan 2006 19:28:33 -0500 [thread overview]
Message-ID: <20060107002833.GB9402@redhat.com> (raw)
In-Reply-To: <9a8748490601061625q14d0ac04ica527821cf246427@mail.gmail.com>
On Sat, Jan 07, 2006 at 01:25:22AM +0100, Jesper Juhl wrote:
> On 1/6/06, Andrew Morton <akpm@osdl.org> wrote:
> > Jesper Juhl <jesper.juhl@gmail.com> wrote:
> >
> > > Reverted that one patch, then rebuild/reinstalled the kernel
> > > (with the same .config) and booted it - no change. It still locks up
> > > in the exact same spot.
> > > X starts & runs fine (sort of) since I can play around at the kdm
> > > login screen all I want, it's only once I actually login and KDE
> > > proper starts that it locks up.
> >
> > Oh bugger. No serial console/netconsole or such?
> >
> > Or are you able log in and then quickly do the alt-ctrl-F1 thing, see if we
> > get an oops?
> >
> I switched to tty1 right after logging in, and after a few seconds
> (corresponding pretty well with the time it takes to hit the same spot
> where it crashed all previous times) I got a lot of nice crash info
> scrolling by.
> Actually a *lot* scrolled by, a rough guestimate says some 4-6 (maybe
> more) screens scrolled by, and since the box locks up solid I couldn't
> scroll up to get at the initial parts :( So all I have for you is the
> final block - hand copied from the screen using pen and paper
> ...
> It never makes it to the logs, and as mentioned previously I don't
> have another machine to capture on via netconsole or serial, so if you
> have any good ideas as to how to capture it all, then I'm all ears.
If only someone did a patch to pause the text output after the first oops..
Oh wait! Someone did!
Dave
next prev parent reply other threads:[~2006-01-07 0:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 23:52 2.6.15-mm1 - locks solid when starting KDE (EDAC errors) Jesper Juhl
2006-01-05 23:56 ` Jesper Juhl
2006-01-06 0:27 ` Andrew Morton
2006-01-06 0:40 ` Jesper Juhl
2006-01-06 0:59 ` Andrew Morton
2006-01-06 1:04 ` Jesper Juhl
2006-01-07 0:25 ` Jesper Juhl
2006-01-07 0:28 ` Dave Jones [this message]
2006-01-07 0:40 ` Andrew Morton
2006-01-07 0:57 ` Dave Jones
2006-01-07 1:20 ` Jesper Juhl
2006-01-07 1:28 ` Jesper Juhl
2006-01-07 1:53 ` Grant Coady
2006-01-07 2:51 ` Jesper Juhl
2006-01-07 3:13 ` Andrew Morton
2006-01-07 3:19 ` Jesper Juhl
2006-01-07 3:53 ` Dave Jones
2006-01-06 13:46 ` Alan Cox
2006-01-07 1:12 ` Jesper Juhl
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=20060107002833.GB9402@redhat.com \
--to=davej@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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