From: lepton <lepton@sina.com>
To: linux-kernel@vger.kernel.org
Subject: [BUG]linux-2.4.24 with k8 numa support panic when init scsi
Date: Sun, 8 Feb 2004 22:37:40 +0800 [thread overview]
Message-ID: <20040208143740.GA25010@lepton.goldenhope.com.cn> (raw)
Hi!
I've found if I enable k8-numa support in my dual amd64 boxes.
It will panic when init scsi.
Further investigation leads out it panics in
drivers/scsi/scsi_dma.c
when it __get_free_pages(GFP_ATOMIC | GFP_DMA, 0) in two
places.
Sometimes it will panic before found scsi disk (in scsi_init_minimal_dma_pool)
Sometimes it will panic after found scsi disk (in scsi_resize_dma_pool)
The following is my output of panic.
If you'd like any other information,I will provide as you
reguest.
scsi0:A:0:0: Tagged Queuing enabled. Depth 253
Unable to handle kernel NULL pointer dereference<1> at 0000000000000180
RIP: [<ffffffff80145ce0>]PML4 0
Oops: 0000
CPU 1
Pid: 1, comm: swapper Not tainted
RIP: 0010:[<ffffffff80145ce0>]
RSP: 0000:000001007ffe3da8 EFLAGS: 00010012
RAX: 0000000000000000 RBX: 0000010080000000 RCX: 0000000000000021
RDX: 0000010080000548 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 00000100fbf2b800 R11: 0000000000000800 R12: 0000000000000021
R13: 0000010080000000 R14: 0000000000000082 R15: 0000000000000021
FS: 0000000000000000(0000) GS:ffffffff803da800(0000)
knlGS:0000000000000000
CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
CR2: 0000000000000180 CR3: 000000007ffed000 CR4: 00000000000006e0
Process swapper (pid: 1, stackpage=1007ffe3000)
Stack: 000001007ffe3da8 0000000000000000 000000000000000f
0000000000000000
0000010080000548 000001007fffec80 0000010080000000
0000000000000000
0000000000000021 0000010080000000 0000000000000082
00000100fbf2f618
Call Trace: [<ffffffff801493bd>] [<ffffffff80145f7d>]
[<ffffffff8024f6ae>] [<ffffffff80244ed0>] [<ffffffff8010c122>]
[<ffffffff8010f1f0>] [<ffffffff8010c0c0>] [<ffffffff8010f1e8>]
Code: 48 2b 80 80 01 00 00 48 c1 f8 03 41 89 c6 41 89 f4 48 89 d3
RIP [<ffffffff80145ce0>] RSP <000001007ffe3da8>
CR2: 0000000000000180
<0>Kernel panic: Attempted to kill init!
next reply other threads:[~2004-02-08 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 14:37 lepton [this message]
[not found] <20040208143740.GA25010@lepton.goldenhope.com.cn.suse.lists.linux.kernel>
[not found] ` <p73y8rdk3ng.fsf@verdi.suse.de>
2004-02-09 3:53 ` lepton
2004-02-10 13:32 ` Andi Kleen
2004-02-09 7:30 ` lepton
2004-02-16 3:49 ` lepton
2004-02-16 5:22 ` Michael Frank
2004-02-16 6:41 ` 吴涛
[not found] <1ncMn-H9-7@gated-at.bofh.it>
[not found] ` <1ncMn-H9-9@gated-at.bofh.it>
[not found] ` <1ncMm-H9-5@gated-at.bofh.it>
[not found] ` <1ndIo-1yd-1@gated-at.bofh.it>
[not found] ` <1pI5B-23P-3@gated-at.bofh.it>
2004-02-16 4:28 ` Andi Kleen
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=20040208143740.GA25010@lepton.goldenhope.com.cn \
--to=lepton@sina.com \
--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
all inboxes | Powered by JetHome®