From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: blacknred <leo1783@hotmail.co.uk>, xfs@oss.sgi.com
Subject: Re: kernel panic-xfs errors
Date: Wed, 08 Dec 2010 22:44:09 -0600 [thread overview]
Message-ID: <4D005E99.2030400@sandeen.net> (raw)
In-Reply-To: <20101209005944.GD32766@dastard>
On 12/8/10 6:59 PM, Dave Chinner wrote:
> On Wed, Dec 08, 2010 at 01:39:10AM -0800, blacknred wrote:
>>
>>
>>> You've done a forced module load. No guarantee your kernel is in any
>>> sane shape if you've done that....
>>
>> Agree, but I'm reasonably convinced that module isn't the issue, because it
>> works fine with my other servers......
>>
>>> Strange failure. Hmmm - i386 arch and fedora - are you running with
>> 4k stacks? If so, maybe it blew the stack...
>>
>> i386 arch, rhel 5.0
>
> Yup, 4k stacks. This is definitely smelling like a stack blowout.
well, hang on. The oops said:
EIP: 0060:[<c0529da1>] Tainted: GF VLI
EFLAGS: 00010272 (2.6.33.3-85.fc13.x86_64 #1)
EIP is at do_page_fault+0x245/0x617
eax: ec5ee000 ebx: 00000000 ecx: eb5de084 edx: 0000000e
esi: 00013103 edi: ec5de0b3 ebp: 00000023 esp: ec5de024
ds: 008b es: 008b ss: 0078
which is NOT a rhel 5.0 kernel, and it says x86_64.
But the addresses are all 32 bits?
So what's going on here?
> esi: 00013103 edi: ec5de0b3 ebp: 00000023 esp: ec5de024
> ds: 008b es: 008b ss: 0078
> Process bm (pid: 3210, ti=ec622000 task=ec5e3450 task.ti=ec6ee000)
end of the stack is ec6ee000, stack grows up, esp is at ec5de024,
well past it (i.e. yes, overrun) if I remember my stack math
right... but that's a pretty huge difference so either I have it
wrong, or things are really a huge mess here.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-09 4:42 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 [this message]
2010-12-09 13:17 ` blacknred
2010-12-09 14:56 ` Eric Sandeen
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=4D005E99.2030400@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--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