public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ashok Raj <ashok.raj@intel.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andi Kleen <ak@muc.de>, Ashok Raj <ashok.raj@intel.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.13-rc5-mm1 doesnt boot on x86_64
Date: Mon, 8 Aug 2005 10:39:24 -0700	[thread overview]
Message-ID: <20050808103924.A18250@unix-os.sc.intel.com> (raw)
In-Reply-To: <1123522409.5019.0.camel@mulgrave>; from James.Bottomley@SteelEye.com on Mon, Aug 08, 2005 at 12:33:29PM -0500

On Mon, Aug 08, 2005 at 12:33:29PM -0500, James Bottomley wrote:
> On Mon, 2005-08-08 at 19:11 +0200, Andi Kleen wrote:
> > Looks like a SCSI problem. The machine has an Adaptec SCSI adapter, right?
> 
> The traceback looks pretty meaningless.
> 
> What was happening on the machine before this.  i.e. was it booting up,
> in which case can we have the prior dmesg file; or was the aic79xxx
> driver being removed?

I can get the trace again, but basically the system was booting. 

AIC_7XXX was defined in defconfig, but my system doesnt have it. Seems like
the senario was the driver tried to probe, found nothing, and tries
to de-reg resulting in the BUG().

I will try to get the recompile and entire dmesg log in the meantime.
> 
> James
> 
> 

-- 
Cheers,
Ashok Raj
- Open Source Technology Center

  reply	other threads:[~2005-08-08 17:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050808094818.A17579@unix-os.sc.intel.com>
2005-08-08 17:11 ` 2.6.13-rc5-mm1 doesnt boot on x86_64 Andi Kleen
2005-08-08 17:27   ` Ashok Raj
2005-08-08 17:33   ` James Bottomley
2005-08-08 17:39     ` Ashok Raj [this message]
2005-08-08 17:42     ` Andrew Morton
2005-08-09  0:06       ` James Bottomley
2005-08-09 18:12         ` Ashok Raj

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=20050808103924.A18250@unix-os.sc.intel.com \
    --to=ashok.raj@intel.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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