mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Dana Lacoste <dana.lacoste@peregrine.com>
Cc: linux-kernel@vger.kernel.org, aic7xxx@freebsd.org
Subject: Re: AIC7xxx in 2.4.19-pre8?
Date: Wed, 15 May 2002 08:54:22 -0600	[thread overview]
Message-ID: <200205151454.g4FEsM990428@aslan.scsiguy.com> (raw)
In-Reply-To: Your message of "15 May 2002 09:49:12 EDT." <1021470553.28001.37.camel@dlacoste.ottawa.loran.com>

>(Kernel version is 2.4.19-pre8.  Let me know if you want more info :)
>
>(Motherboard is Nexcom Peak 632 : 440BX with Adaptec 7890U2)
>
>I'm getting (over and over and over and over) the message from line
>1854 of drivers/scsi/aic7xxx/aic7xxx_pci.c :
>
>scsi0: PCI error Interrupt at seqaddr = 0x8
>scsi0: PCI error Interrupt at seqaddr = 0x9
>
>(0x9 is more common, no pattern detected between 0x8 and 0x9)
>
>It's interlaced with :
>scsi0: Received a Target Abort
>
>which means the status1 flag RTA was set, but I'm now officially out
>of my league :)

Hmm.  The aic7xxx chip could have botched a master transaction somehow,
but that's still hard to say.  Can you have the driver dump out its
chip state (call ahc_dump_card_state(ahc) from within the pci interrupt
handler) to get some additional information?

>This box was going fine till this morning (we upgraded from 2.4.18
>last night) and a second box we did the same thing to also had the
>same problem, so it looks like a kernel issue somehow, not just
>faulty hardware.  Retrograding to 2.4.18 caused the problem to go
>away.

How much memory is in the box?  What version of the aic7xxx driver
were you using under 2.4.18?

--
Justin

      reply	other threads:[~2002-05-15 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 13:49 Dana Lacoste
2002-05-15 14:54 ` Justin T. Gibbs [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=200205151454.g4FEsM990428@aslan.scsiguy.com \
    --to=gibbs@scsiguy.com \
    --cc=aic7xxx@freebsd.org \
    --cc=dana.lacoste@peregrine.com \
    --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

all inboxes | Powered by JetHome®