From: Eric Sandeen <sandeen@sandeen.net>
To: blacknred <leo1783@hotmail.co.uk>
Cc: xfs@oss.sgi.com
Subject: Re: kernel panic-xfs errors
Date: Thu, 09 Dec 2010 08:56:48 -0600 [thread overview]
Message-ID: <4D00EE30.2000408@sandeen.net> (raw)
In-Reply-To: <30416394.post@talk.nabble.com>
On 12/9/10 7:17 AM, blacknred wrote:
>
>> which is NOT a rhel 5.0 kernel, and it says x86_64.
>> But the addresses are all 32 bits?
>
> My apologies there, somehow it all got jumbled up, pasting it again:
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 00000098
> printing eip:
> *pde = 2c621001
> Oops: 0000 [#1]
> SMP
> CPU: 2
> EIP: 0060:[<c0619da1>] Tainted: GF VLI
> EFLAGS: 00010282 (2.6.18-164.11.1.el5PAE #1)
> EIP is at do_page_fault+0x205/0x607
> eax: ec6de000 ebx: 00000000 ecx: ec6de074 edx: 0000000d
> esi: 00014005 edi: ec6de0a4 ebp: 00000014 esp: ec6de054
> ds: 007b es: 007b ss: 0068
> Process bm (pid: 2910, ti=ec6dd000 task=ec6e3550 task.ti=ec6dd000)
> Stack: 00000000 00000000 ec6de0a4 00000014 00000098 f7180000 00000001
> 00000000
> ec6de0a4 c0639439 00000000 0000000e 0000000b 00000000 00000000
> 00000000
> 00014005 c0619b9c 00000014 c0405a89 00000000 ec6de0f8 0000000d
> 00014005
ok, same task.ti and esp though, so same massive stack overflow.
Is this really RHEL, or CentOS? RHEL doesn't ship xfs for i386,
and using the xfs-kmod is a very unsupported/unmaintained solution.
If it is "real RHEL" you could try requesting actual i386 support,
but these stack issues are one of the reasons it's unlikely.
CentOS would do well to ship the same xfs code as is in the x86_64
kernel and drop the kmod-xfs altogether. Some stack issues have
been resolved since then, but probably not as much as we see here.
I also am suspicious of whatever "moddw_ioctl" is in mod_dw;
I assume that's the proprietary kernel module. It may have a really
bad stack footprint, although the callchain below looks bad enough.
What does:
# objdump -d /path/to/mod_dw.ko | grep -A30 "<moddw_ioctl>:" | grep sub
say?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-09 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 15:42 kernel panic-xfs errors blacknred
2010-12-07 15:59 ` Emmanuel Florac
2010-12-07 17:20 ` blacknred
2010-12-07 18:00 ` Emmanuel Florac
2010-12-07 18:18 ` Stan Hoeppner
2010-12-07 21:52 ` Emmanuel Florac
2010-12-07 22:25 ` Dave Chinner
2010-12-08 9:39 ` blacknred
2010-12-08 10:57 ` Emmanuel Florac
2010-12-08 14:01 ` blacknred
2010-12-08 14:34 ` Emmanuel Florac
2010-12-09 0:59 ` Dave Chinner
2010-12-09 4:44 ` Eric Sandeen
2010-12-09 13:17 ` blacknred
2010-12-09 14:56 ` Eric Sandeen [this message]
2010-12-09 13:23 ` blacknred
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=4D00EE30.2000408@sandeen.net \
--to=sandeen@sandeen.net \
--cc=leo1783@hotmail.co.uk \
--cc=xfs@oss.sgi.com \
/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