From: Paul Dickson <dickson@permanentmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: My report on running 2.6.0-test2 on a Dell Inspiron 7000 (crash while shutting down)
Date: Wed, 6 Aug 2003 06:49:54 -0700 [thread overview]
Message-ID: <20030806064954.3e714af8.dickson@permanentmail.com> (raw)
In-Reply-To: <20030806021621.2da5a850.dickson@permanentmail.com>
On Wed, 6 Aug 2003 02:16:21 -0700, Paul Dickson wrote:
> But all is not perfect. I'll attach the problems I had as replies (so
> each has it's own message thread).
When I shutdown for a reboot, I getting the following oops (which I
recorded with a digital camera, an transcribe here):
--------------------------------------------------------------------------------
EIP: 0060:[<c0264054>] Not tainted
EFLAGS: 00010246
EIP is at device_shutdown+0x74/0xab
eax: 00000000 ebx: ffffffc4 ecx: 00000000 edx: 00000000
esi: cc950000 edi: fee1dead ebp: cc951ea0 esp: cc951e94
ds: 00tb es: 007b ss: 0068
Process reboot (pid: 2551, threadinfo=cc950000 task=cc94f940)
Stack: c034e09d 00000042 01234567 cc951fbc c012a4a6 c0446268 00000001 00000000
cc8fa2e0 cdfb0c60 cc125420 00000000 cf5df4a0 cc125420 420d1c20 cf5df4a0
cc951f04 00000246 00000246 cc770760 420d1c20 00000292 cc950000 cc951f04
Call Trace:
[<c012a4a6>] sys_reboot+0x126/0x310
[<c0153813>] invalidate_inod_buffers+0x13/0x80
[<c02c5ced>] sock_destroy_inode+0x1d/0x30
[<c016a296>] destroy_inode+0x36/0x60
[<c016b603>] iput+0x63/0x90
[<c0168440>] dput+0x30/0x220
[<c0152375>] __fput+0xc5/0x130
[<c01509db>] filp_close+04b/0x80
[<c0150a72>] sys_close+0x62/0xa0
[<c010b189>] sysenter_past_esp+0x52/0x71
Code: 8b 43 40 89 ca 89 c1 8d 74 26 00 81 fa c8 6e 3d c0 75 d9 b8
INIT: no more processes left in this runlevel
--------------------------------------------------------------------------------
Some of the 8s and 0s might be interchanges, especially near the end.
I think this had been mentioned before on LKML.
The feeling held in the edi is cute.
-Paul
prev parent reply other threads:[~2003-08-06 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 9:16 My report on running 2.6.0-test2 on a Dell Inspiron 7000 (PII, 300MHz with 256MB) Paul Dickson
2003-08-06 9:22 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (possible tty trouble) Paul Dickson
2003-08-06 11:42 ` Antonio Vargas
2003-08-06 13:09 ` Paul Dickson
2003-08-06 14:12 ` Havoc Pennington
2003-08-06 9:35 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (PII, 300MHz with 256MB) Paul Dickson
2003-08-06 10:03 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (lost USB mouse) Paul Dickson
2003-08-06 21:40 ` Greg KH
2003-08-06 10:58 ` My report on running 2.6.0-test2 on a Dell Inspiron 7000 (poor sound from crond) Paul Dickson
2003-08-06 13:49 ` Paul Dickson [this message]
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=20030806064954.3e714af8.dickson@permanentmail.com \
--to=dickson@permanentmail.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 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.