From: Mike Fedyk <mfedyk@matchmail.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: OOps! was: 2.6.0-test9-mm5
Date: Mon, 24 Nov 2003 21:10:18 -0800 [thread overview]
Message-ID: <20031125051018.GA1331@mis-mike-wstn.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0311242013270.1859@montezuma.fsmlabs.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On Mon, Nov 24, 2003 at 08:19:30PM -0500, Zwane Mwaikambo wrote:
> On Mon, 24 Nov 2003, Mike Fedyk wrote:
>
> > On Mon, Nov 24, 2003 at 03:58:07PM -0800, Mike Fedyk wrote:
> > > I just compiled witout preempt and it still gives an oops at the same spot.
> >
> > Just compiled vanilla 2.6.0-test9 and it doesn't oops.
> >
> > Let me know if you still want me to hand type that oops.
>
> Try disabling CONFIG_PNPBIOS and if that fixes it, try backing out one by
> one;
>
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test9/2.6.0-test9-mm5/broken-out/pnp-fix-[1234].patch
>
> But yes, the oops transcribed would be nice.
Here you go. All numbers are right justified, so what's not there starts
with zeros.
gpf f000 #1
preempt smp
cpu: 0
eip: 0098:[<000052fu>] not tainted VLI
eflags: 10046
eip is at 0f52f1
eax: 8000f000 ebx: 09004 ecx: a0000b edx: fce
esi: c1f5a31a edi: 0 ebp: c1f5be7c esp: c1f5be4a
ds: a0 es: a8 ss: 68
process: swapper (pid: 1 threadinfo-clf5a00 task=clf5aa80
stack: cfe dcf00a0 b00b af6easb5 aefd9cb3 0c810001 0 7b0001
9c66007b a000 beec0082 bc1f5 20090 2 100a8 a0
6750000 600023 20000 0 0 7b0000 7b0000 a00000000
Call trace:
:code: bad eip value
<0> kernel panic: attempted to kill init!
[-- Attachment #2: System.map-2.6.0-test9-mm5.bz2 --]
[-- Type: application/octet-stream, Size: 170165 bytes --]
next prev parent reply other threads:[~2003-11-25 5:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 20:11 2.6.0-test9-mm5 Andrew Morton
2003-11-21 21:01 ` 2.6.0-test9-mm5 Matt Mackall
2003-11-21 23:47 ` 2.6.0-test9-mm5 (compile stats) John Cherry
2003-11-24 22:55 ` OOps! was: 2.6.0-test9-mm5 Mike Fedyk
2003-11-24 23:41 ` Zwane Mwaikambo
2003-11-24 23:58 ` Mike Fedyk
2003-11-25 0:36 ` Mike Fedyk
2003-11-25 1:19 ` Zwane Mwaikambo
2003-11-25 5:10 ` Mike Fedyk [this message]
2003-11-25 5:33 ` Zwane Mwaikambo
2003-11-25 5:47 ` Mike Fedyk
2003-11-25 5:54 ` Zwane Mwaikambo
2003-11-25 6:36 ` Mike Fedyk
2003-11-25 7:54 ` Mike Fedyk
2003-11-25 8:05 ` Mike Fedyk
2003-11-25 8:47 ` Mike Fedyk
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=20031125051018.GA1331@mis-mike-wstn.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=zwane@arm.linux.org.uk \
/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