From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Panic from 2.4.19-pre9-aa2
Date: Thu, 06 Jun 2002 16:18:01 -0700 [thread overview]
Message-ID: <99570000.1023405481@flay> (raw)
In-Reply-To: <20020606212028.GA1004@dualathlon.random>
> not really sure what could be the problem, it would be interesting to
> see if you can reproduce it.
Yup, do 2 or 3 kernel compiles and it crashes again. Here's a slightly
different oops:
Unable to handle kernel NULL pointer dereference at virtual address 00000282
c0117feb
*pde = 00000000
Oops: 0000
CPU: 6
EIP: 0010:[<c0117feb>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010046
eax: c6369f6c ebx: 00000282 ecx: c029a488 edx: c4ff5b24
esi: c4ff5b20 edi: 00000282 ebp: c6227f70 esp: c6227f54
ds: 0018 es: 0018 ss: 0018
Process cpp (pid: 16679, stackpage=c6227000)
Stack: 00001000 c4ff5b20 c5773180 00000001 c4ff5b24 00000282 00000001 000526a9
c0148311 00000000 ffffffea c5eab160 000536a9 c6526000 c6226000 c57731ec
00001000 00001000 c013ead7 c5eab160 4011000c 000536a9 c5eab180 c6226000
Call Trace: [<c0148311>] [<c013ead7>] [<c0108a7b>]
Code: 8b 3b 0f 18 07 3b 5d f4 75 d0 c6 06 01 ff 75 f8 9d 8d 74 26
>>EIP; c0117fea <__wake_up+5a/7c> <=====
Trace; c0148310 <pipe_write+1bc/294>
Trace; c013ead6 <sys_write+8e/100>
Trace; c0108a7a <system_call+2e/34>
Code; c0117fea <__wake_up+5a/7c>
00000000 <_EIP>:
Code; c0117fea <__wake_up+5a/7c> <=====
0: 8b 3b mov (%ebx),%edi <=====
Code; c0117fec <__wake_up+5c/7c>
2: 0f 18 07 prefetchnta (%edi)
Code; c0117fee <__wake_up+5e/7c>
5: 3b 5d f4 cmp 0xfffffff4(%ebp),%ebx
Code; c0117ff2 <__wake_up+62/7c>
8: 75 d0 jne ffffffda <_EIP+0xffffffda> c0117fc4 <__
wake_up+34/7c>
Code; c0117ff4 <__wake_up+64/7c>
a: c6 06 01 movb $0x1,(%esi)
Code; c0117ff6 <__wake_up+66/7c>
d: ff 75 f8 pushl 0xfffffff8(%ebp)
Code; c0117ffa <__wake_up+6a/7c>
10: 9d popf
Code; c0117ffa <__wake_up+6a/7c>
11: 8d 74 26 00 lea 0x0(%esi,1),%esi
> Also if for example you enabled numa-q you
> may want to try to disable it and see if w/o discontigmem the problem
> goes away, if we could isolate it to a config option, it would help a lot.
OK, will see if I can do that - I'm out for a few days, so it may be next
Tuesday before I can do this
M.
next prev parent reply other threads:[~2002-06-06 23:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 20:44 Panic from 2.4.19-pre9-aa2 Martin J. Bligh
2002-06-06 21:20 ` Andrea Arcangeli
2002-06-06 21:53 ` Martin J. Bligh
2002-06-06 23:15 ` Andrea Arcangeli
2002-06-06 23:45 ` Martin J. Bligh
2002-06-06 23:53 ` Andrea Arcangeli
2002-06-06 23:31 ` Hugh Dickins
2002-06-07 1:33 ` Keith Owens
2002-06-06 23:18 ` Martin J. Bligh [this message]
2002-06-06 23:36 ` Andrea Arcangeli
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=99570000.1023405481@flay \
--to=martin.bligh@us.ibm.com \
--cc=andrea@suse.de \
--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