From: Alexey Dobriyan <adobriyan@sw.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EIP is at device_shutdown+0x32/0x60
Date: Thu, 15 Nov 2007 12:59:28 +0300 [thread overview]
Message-ID: <20071115095928.GC6216@localhost.sw.ru> (raw)
In-Reply-To: <20071115014446.f943d835.akpm@linux-foundation.org>
On Thu, Nov 15, 2007 at 01:44:46AM -0800, Andrew Morton wrote:
> On Thu, 15 Nov 2007 12:11:58 +0300 Alexey Dobriyan <adobriyan@sw.ru> wrote:
>
> > Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
> > (1) and during 2.6.24 cycle (2):
> >
> > kernel_restart
> > sys_reboot
> > [garbage]
> > Code: 8b 88 a8 00 00 00 85 c9 74 04 89
> > EIP is at device_shutdown+0x32/0x60
>
> Yes, all my test boxes did that - it's what I referred to in the releaee
> notes. Greg is pondering the problem - seem he's the only person who
> cannot reproduce it ;)
>
> But what does "during 2.6.24 cycle (2)" mean? Some kernel other than
> 2.6.24-rc2-mm1 is crashing?
2.6.24-something also rarely crashes on reboot for me. In fact it can very
well be different crash. I never managed to catch oops message with mainline.
Netconsole doesn't show anything and replugging monitor cable also
doesn't help and bug dissapear if I try to catch it. :)
next prev parent reply other threads:[~2007-11-15 10:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 9:11 EIP is at device_shutdown+0x32/0x60 Alexey Dobriyan
2007-11-15 9:44 ` Andrew Morton
2007-11-15 9:59 ` Alexey Dobriyan [this message]
2007-11-15 12:55 ` Yasunori Goto
2007-11-15 13:15 ` Cornelia Huck
2007-11-15 16:34 ` Greg KH
2007-11-15 17:07 ` Mark Lord
2007-11-15 18:23 ` Greg KH
2007-11-15 18:29 ` Mark Lord
2007-11-15 18:48 ` Greg KH
2007-11-15 19:13 ` Mark Lord
2007-11-15 17:50 ` Kay Sievers
2007-11-15 18:18 ` Greg KH
2007-11-15 19:01 ` Greg KH
2007-11-16 1:13 ` Yasunori Goto
2007-11-16 1:22 ` Greg KH
2007-11-19 9:55 ` Cornelia Huck
2007-11-15 14:40 ` Jeff Dike
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=20071115095928.GC6216@localhost.sw.ru \
--to=adobriyan@sw.ru \
--cc=akpm@linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.