From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Gary Wolfe <gpwolfe@cableone.net>, linux-kernel@vger.kernel.org
Subject: Re: [crash/panic] Linux-2.6.0-test9
Date: Mon, 03 Nov 2003 19:07:34 +0100 [thread overview]
Message-ID: <3FA69966.1090001@colorfullife.com> (raw)
In-Reply-To: <20031103005218.6dc72800.akpm@osdl.org>
Andrew Morton wrote:
>Gary Wolfe <gpwolfe@cableone.net> wrote:
>
>
>>Greetings,
>>
>>I have:
>>
>>Asus P4C800 Deluxe w/2.4GHz P4 (no HT and not 800Mhz bus)
>>
>>Tried test8 and, now, test9 and both exhibit same problem.
>>
>>The issue seems to be related to the PnPBIOS support under the Plug and
>>Play Kconfig category. When enabled I get a crash of the form:
>>
>>Linux Plug and Play Support v0.97 (c) Adam Belay
>>PnPBIOS: Scanning system for PnP BIOS support...
>>PnPBIOS: Found PnP BIOS installation structure at 0xc00f5350
>>PnPBIOS: PnP BIOS version 1.0, entry 0xf0000:0x5f3a, dseg 0xf0000
>>general protection fault: 0000 [#1]
>>CPU: 0
>>EIP: 0098:[<00002b60>] Not tainted
>>EFLAGS: 00010083
>>EIP is at 0x2b60
>>eax: 000023d6 ebx: 0000007a ecx: 00010000 edx: 00000001
>>esi: dfed244e edi: 0000006d ebp: dfed0000 esp: dfed9eda
>>
>>
>
>Your stack pointer became misaligned. I thought Manfred fixed that?
>You don't have nmi_watchdog enabled on the kernel boot command line
>do you?
>
>
I fixed the double-oops caused by misaligned stack pointers, and the
oops if kmem_cache_alloc is called with an misaligned stack pointer.
In this case it seem to be an oops in the bios itself.
Gary: did it work with 2.4? Are there any bios upgrades you could try?
My guess is that the bios is just buggy.
--
Manfred
next prev parent reply other threads:[~2003-11-03 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 7:12 [crash/panic] Linux-2.6.0-test9 Gary Wolfe
2003-11-03 8:52 ` Andrew Morton
2003-11-03 14:53 ` Gary Wolfe
2003-11-03 18:07 ` Manfred Spraul [this message]
2003-11-03 16:37 ` Linus Torvalds
2003-11-03 23:25 ` Adam Belay
2003-11-08 19:04 ` Gary Wolfe
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=3FA69966.1090001@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=gpwolfe@cableone.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.