All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Hanna Linder <hannal@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	tmolina@cox.net, haveblue@us.ibm.com
Subject: Re: more aic7xxx boot failure
Date: 24 Oct 2002 16:20:38 -0700	[thread overview]
Message-ID: <87hefbxw3d.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <16660000.1035501142@w-hlinder>

Hanna Linder <hannal@us.ibm.com> writes:

> --On Thursday, October 24, 2002 15:46:56 -0700 Philippe Troin <phil@fifi.org> wrote:
> 
> > 
> > Have you tried booting with "noapic"?
> 
> 	Just did, That solves the problem too.
> 
>  
> > What error do you get on boot?
> 
> a kernel panic and scsi_abort error 0x2 (from what
> I remember flying by)
> 
> Would have to hookup with a serial cable to get all
> the data. Here is what I can see on the screen:
> 
> LASTPHASE = 0x1, SCSISIGI = 0x0, SXFRCTL0 = 0x0
> SSTAT0 = 0x0, SSTAT1 = 0x8
> STACK == 0x17, 0x0, 0x0, 0x0
> SCB count = 4
> Kernel NEXQSCB = 3
> Card NEXTQSCB = 0
> QINFIFO entries: 3 2
> a list of Waiting Queue entries 
> and a list of Disconnected Queue entries.
> QUOTFIFI entries:
> Sequencer Free SCB List: 0 to 31
> Pending list: 2
> Kernel Free SCB list: 1 0
> Untagged Q(0): 2
> DevQ(0:0:0):0 waiting
> qinpos = 0, SCB index = 3
> Kernel panic: Loop 1

Had the same problem.

Booted noapic, problem solved...

Now, if the driver could be fixed, that would be nicer...

Phil.

  reply	other threads:[~2002-10-24 23:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 22:25 more aic7xxx boot failure Hanna Linder
2002-10-24 22:46 ` Philippe Troin
2002-10-24 23:12   ` Hanna Linder
2002-10-24 23:20     ` Philippe Troin [this message]
2002-10-24 23:56       ` SL Baur
2002-10-25  0:39         ` Philippe Troin
2002-10-25  3:53       ` Doug Ledford

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=87hefbxw3d.fsf@ceramic.fifi.org \
    --to=phil@fifi.org \
    --cc=hannal@us.ibm.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=tmolina@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.