public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Juergen Stohr <juergen.stohr@lpr.e-technik.tu-muenchen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]linux-2.4.26 Quad-Opteron: panic when init scsi
Date: Wed, 28 Apr 2004 20:13:20 -0300	[thread overview]
Message-ID: <20040428231320.GA16387@logos.cnet> (raw)
In-Reply-To: <20040427101720.GA27663@rcs.ei.tum.de>

On Tue, Apr 27, 2004 at 12:17:20PM +0200, Juergen Stohr wrote:
> Hi,
> 
> I have got a problem similar to the one discussed in the thread
> "[BUG]linux-2.4.24 with k8 numa support panic when init scsi": When 
> booting the 2.4.26 on a quad Opteron box, in most of the cases the 
> kernel crashes when initializing SCSI.
> It seems to me that this bug is caused by a race, as in a few
> cases the machine is able to boot.
> 
> The machine always boots if I set maxcpus=1.
> 
> If I append numa=off to the command line the kernel crashes with a
> "Machine Check Exception" (but is able to initialize SCSI; perhaps
> this is another bug?)
> 
> Does anybody know how to solve this problem or is anybody working on it?
> Can someone give me a hint where to start when debugging this race?
> 
> I will attach the config of my kernel, the syslogs and the output of
> ksymoops.

Andi,

Have you seen Juergen's ksymoops trace? 

It seems some BUG() (maybe BAD_RANGE()) is triggering at startup in 
__alloc_pages().


  reply	other threads:[~2004-04-28 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-27 10:17 [BUG]linux-2.4.26 Quad-Opteron: panic when init scsi Juergen Stohr
2004-04-28 23:13 ` Marcelo Tosatti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-29  9:24 Alexander v. Buelow

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=20040428231320.GA16387@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=juergen.stohr@lpr.e-technik.tu-muenchen.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