From: Dylan Griffiths <Dylan_G@bigfoot.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel BUG in inode.c line 486 in 2.4.5
Date: Sat, 23 Jun 2001 04:44:16 -0600 [thread overview]
Message-ID: <3B347300.FEFF00D@bigfoot.com> (raw)
In-Reply-To: <3B34711A.F25ED753@bigfoot.com>
I should mention, there are also NFS3 mounts on the system..
Dylan Griffiths wrote:
> -=-
>
> kernel BUG at inode.c:486!
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c0141e43>]
> EFLAGS: 00013286
> eax: 0000001b ebx: c726a2c0 ecx: 00000001 edx: c022a068
> esi: c022cee0 edi: d489c9c0 ebp: d501dfa4 esp: d501deec
> ds: 0018 es: 0018 ss: 0018
> Process gmc (pid: 169, stackpage=d501d000)
> Stack: c01f602c c01f608b 000001e6 c726a2c0 c0142887 c726a2c0 d4221a40
> c726a2c0
> c015a66d c726a2c0 c01402f6 d4221a40 c726a2c0 d4221a40 00000000
> c0138d18
> d4221a40 d501df68 c013945a d489c9c0 d501df68 00000000 cc51b000
> 00000000
> Call Trace: [<c0142887>] [<c015a66d>] [<c01402f6>] [<c0138d18>] [<c013945a>]
> [<c0139a8c>] [<c01368a6>]
> [<c0106b9b>]
>
> Code: 0f 0b 83 c4 0c f6 83 f4 00 00 00 10 75 1f 68 e8 01 00 00 68
>
--
www.kuro5hin.org -- technology and culture, from the trenches.
prev parent reply other threads:[~2001-06-23 10:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 10:36 Kernel BUG in inode.c line 486 in 2.4.5 Dylan Griffiths
2001-06-23 10:44 ` Dylan Griffiths [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=3B347300.FEFF00D@bigfoot.com \
--to=dylan_g@bigfoot.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