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,
airlied@linux.ie
Subject: Re: 2.6.15-mm1 - locks solid when starting KDE (EDAC errors)
Date: Fri, 6 Jan 2006 22:53:51 -0500 [thread overview]
Message-ID: <20060107035351.GH9402@redhat.com> (raw)
In-Reply-To: <9a8748490601061851p7ecfab9fua866fc2a79153b0@mail.gmail.com>
On Sat, Jan 07, 2006 at 03:51:48AM +0100, Jesper Juhl wrote:
> Ok, this is with a pristine 2.6.15-mm1 + Dave's oops-pausing-patch
> Captured by switching to tty1 just after logging in via kdm.
> A *lot* of info still scrolls down when the problem hits before Daves
> patch stops it at a BUG dump, it scrolls by too fast for me to see
> what it is, but I guess it must be warning/error messages other than
> Oops's or BUG()'s ???
>
> Anyway, here's the entire contents of my screen after Daves patch
> stops the output - again written down by hand and then typed in from
> my handwritten notes, so there may be typos, but I've tried to be
> accurate.
>
>
> 050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 090: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 0b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
My first thought was 'slab poison', but you don't have slab debugging turned on.
Randy's followup to my patch: http://lkml.org/lkml/2006/1/5/15
had another trick that may be useful. It'll slow down printk's
to a point where you might be able to see what happened.
another trick may be to just add a for (;;) into the BUG macro.
> ------------{ cut here ]------------
> kernel BUG at include/linux/list.h:166!
> invalid opcode: 0000 [#1]
> PREEMPT SMP
> Last sysfs file: /class/vc/vcsa2/dev
> Modules linked in: snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss
> snd_mixer_oss uhci_hcd usbcore snd_emu10k1 snd_rawmidi snd_ac97_codec
> snd_ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc
> snd_util_mem snd_hwdep snd agpgart
> CPU: 0
> EIP: 0060:[<c01475f5>] Tainted: G B VLI
Hmm, you had hit bad_page(), so that may be a more useful place
to add a pause.
Dave
next prev parent reply other threads:[~2006-01-07 3:54 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
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 [this message]
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=20060107035351.GH9402@redhat.com \
--to=davej@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.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