From: Andi Kleen <ak@muc.de>
To: lepton <lepton@mail.goldenhope.com.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]linux-2.4.24 with k8 numa support panic when init scsi
Date: Mon, 16 Feb 2004 05:28:03 +0100 [thread overview]
Message-ID: <m3znbjk5rg.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <1pI5B-23P-3@gated-at.bofh.it> (lepton@mail.goldenhope.com.cn's message of "Mon, 16 Feb 2004 05:00:19 +0100")
lepton <lepton@mail.goldenhope.com.cn> writes:
> I have do some test on weekend. The result is:
>
> 1. Compiling kernel with gcc 3.2:
> 2.4.20 2.4.21: can boot, can mount reiserfs filesystem
> 2.4.22: can boot, can mount reiserfs filesystem, but will panic
> when reboot. It is perhaps because of "reboot=triple" ?
Possible.
> 2.4.23: panic when init scsi, like before.
It could be a problem with the SCSI driver. I don't have any other reports
of this.
> 2.4.24: can boot, can mount reiserfs filesystem, but will panic when
> reboot.
> 2. Compiling kernel with gcc 3.3
> 2.4.20: can not compile....
> 2.4.21: can boot, can mount reiserfs filesystem
> 2.4.22: can boot, can mount reiserfs filesystem, but will panic when
> reboot.
> 2.4.23: panic when init scsi, like before
> 2.4.24: panic when init scsi, like before
>
> 3. when panic, reboot=bios or reboot=triple both can not work.
Of course they don't help for SCSI panics, just possible for reboot
problems.
> 2.4.24 changes a little from 2.4.23, so it is strange system will
> panic in 2.4.23 and don't panic in 2.4.24 when using gcc 3.2
> Perhaps there is some random error?
Yes, it looks very strange. I don't have a good explanation. Especially
since the behaviour changes with the compiler. It's probably some
random memory corruption somewhere.
I will look into the reboot crashes with non standard options.
Regarding the original reboot issues it seems to be related to C stepping
CPUs (we never had any with B stepping).
Anyways, the reboot problem is probably not fatal for you so I guess
you can just use 2.4.24 compiled with gcc 3.2 for now.
-Andi
next parent reply other threads:[~2004-02-16 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [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 ` [BUG]linux-2.4.24 with k8 numa support panic when init scsi 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 ` 吴涛
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=m3znbjk5rg.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=lepton@mail.goldenhope.com.cn \
--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