From: Andi Kleen <ak@suse.de>
To: lepton <lepton@sina.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]linux-2.4.24 with k8 numa support panic when init scsi
Date: Tue, 10 Feb 2004 14:32:08 +0100 [thread overview]
Message-ID: <20040210143208.7b1d9940.ak@suse.de> (raw)
In-Reply-To: <20040209035356.GA27697@lepton.goldenhope.com.cn>
On Mon, 9 Feb 2004 11:53:56 +0800
lepton <lepton@sina.com> wrote:
> If I disabled "Node Memory Interleave" setting in BIOS. The kernel will
> boot. It saids It could't find numa configuration.But the scsi disk is
> unusable after boot.File system on scsi disk can not be mounted. The kernel
> complain about some file system error.
>
> If I set "Node Memoey Interleave" to "Auto",the kernel will panic in the
> init process of scsi.
And it boots with numa=off ?
> Another problem perhaps has no relation with this problem is that the
> system won't reboot automatic after panic although I have set panic=1
> in boot.
Try reboot=bios or reboot=triple
> The scsi card I am using is a Adaptec SCSI Card 29160LP.
>
> I have tested linux kernel-2.6.1/2.6.2, all of them has no such problem.
Compiled with NUMA on I suppose?
> Others has use United Linux in the server serveral moths ago.I know the
> kernel comes with the distrbution (2.4.19) works fine too.
The original UnitedLinux install didn't default to NUMA, unless
you installed the special k_numa kernel. Later SPs did.
If you used an NUMA kernel can you please check which kernel
revision (between 2.4.20 and 2.4.24) broke it?
>
> Bootdata ok (command line is ro root=/dev/hda2 console=ttyS0,19200 panic=1)
> Linux version 2.4.24 (root@amd64.ytht.net) (gcc version 3.3.2 20030908 (Debian prerelease)) #1 SMP Mon Feb 9 02:01:47 UTC 2004
I'm a bit suspicious of this compiler. Any chance you could try it with a gcc 3.2 too?
[...]
The boot output for the NUMA scanning looks ok, I cannot see what's wrong with it.
-Andi
next prev parent reply other threads:[~2004-02-09 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040208143740.GA25010@lepton.goldenhope.com.cn.suse.lists.linux.kernel>
[not found] ` <p73y8rdk3ng.fsf@verdi.suse.de>
2004-02-09 3:53 ` [BUG]linux-2.4.24 with k8 numa support panic when init scsi lepton
2004-02-10 13:32 ` Andi Kleen [this message]
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
2004-02-08 14:37 lepton
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=20040210143208.7b1d9940.ak@suse.de \
--to=ak@suse.de \
--cc=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