public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Wakko Warner <wakko@animx.eu.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-scsi@vger.kernel.org
Subject: Re: AIC7xxx on 2.6.18
Date: Sun, 4 Feb 2007 09:11:51 -0500	[thread overview]
Message-ID: <20070204141151.GA28726@animx.eu.org> (raw)
In-Reply-To: <1170558221.3860.3.camel@mulgrave.il.steeleye.com>

Keep me in CC, I'm not on the list.

James Bottomley wrote:
> On Fri, 2007-02-02 at 19:42 -0500, Wakko Warner wrote:
> > [   40.154122] ACPI: PCI Interrupt 0000:05:01.1[B] -> GSI 17 (level,
> > low) -> IRQ 22
> > [   40.158190] scsi4: PCI error Interrupt at seqaddr = 0x1bb
> > [   40.158261] scsi4: Signaled a Target Abort
> 
> Well, this is the source of the problem.  It means the driver detected
> an error in the PCI system.  I'm afraid I don't know what a PCI target
> error is, but I think it means something is wrong with the PCI bus in
> your system.  There's also a screaming interrupt, because the first 500
> interrupts will be ignored before it looks at the bus error register.

What I don't understand is that it works fine if I load the module first
then and exec init.  If the ID is 05:01.1, this is the 2nd channel provided
by the aha-2940u/uw card.  There's nothing attached to that channel.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???

      reply	other threads:[~2007-02-04 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070128194620.GA6358@animx.eu.org>
2007-01-29  0:24 ` AIC7xxx on 2.6.18 Andrew Morton
2007-01-29  1:05   ` James Bottomley
2007-01-30 12:18   ` Wakko Warner
2007-01-30 17:57     ` Andrew Morton
2007-01-31  1:30       ` Wakko Warner
2007-02-03  0:42   ` Wakko Warner
2007-02-03  5:12     ` Mark Rustad
2007-02-03  5:27       ` Sean Bruno
2007-02-04  1:29       ` Wakko Warner
2007-02-04  3:03     ` James Bottomley
2007-02-04 14:11       ` Wakko Warner [this message]

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=20070204141151.GA28726@animx.eu.org \
    --to=wakko@animx.eu.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.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