From: David Shepard <daveman@bellatlantic.net>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at inode.c:1034!
Date: Mon, 04 Nov 2002 23:33:42 -0500 [thread overview]
Message-ID: <3DC74A26.7050401@bellatlantic.net> (raw)
I am running kernel 2.4.19 plain and have been doing so successfully for
quite some time. In the past few days, I am seeing a repeatable BUG on
reboot/shutdown. Please let me know if there is any more information I
can provide.
--David Shepard
* Unmounting filesystems...
* Remounting remaining filesystems readonly...
kernel BUG at inode.c:1034!
invalid operand: 0000
CPU: 0
EIP: 0010:[<c0156d33>] Not tainted
EFLAGS: 00010246
eax: c56db150 ebx: c56db040 ecx: c56db150 edx: c56db040
esi: 00000000 edi: c7f42e00 ebp: c910a620 esp: c47f3f00
ds: 0018 es: 0018 ss:0018
Process umount (pid: 7961, stackpage=c47f3000
Stack: c11660c0 c56db040 00000296 c47f3f48 00000296 c11660c0 c56d6740
c56d6740
Stack: c0157ea4 c11660c0 c56d6740 00000001 c7f42e60 00000001 c01573ad
c7f42e00
Stack: c7f42ec4 c7f42e34 c910a620 c910468d c56db040 c7f42e00 c7f42e40
c0143207
Call Trace: [<c0157ea4>] [<c01573ad>] [<c910a620>] [<c910468d>]
[<c0143207>]
[<c015ad05>] [<c015add1>] [<c015ae67>] [<c01074a3>]
Code: 0f 0b 0a 04 9d bb 27 c0 e9 48 fa ff ff 55 57 56 53 83 ec 14
/sbin/rc: line 110: 7961 Segmentation fault umount -a -r -n -t
nodevfs,noproc,notmpfs >&/dev/null
next reply other threads:[~2002-11-05 4:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 4:33 David Shepard [this message]
2002-11-05 4:36 ` kernel BUG at inode.c:1034! William Lee Irwin III
2002-11-05 19:14 ` David Shepard
2002-11-06 2:43 ` David Shepard
2002-11-05 16:05 ` David Liana
-- strict thread matches above, loose matches on Subject: below --
2002-11-06 10:57 Wolfram Gloger
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=3DC74A26.7050401@bellatlantic.net \
--to=daveman@bellatlantic.net \
--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.