From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: dipankar@in.ibm.com, linux-scsi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: aic7xxx broken in 2.5.53/54 ?
Date: Fri, 03 Jan 2003 08:14:06 -0700 [thread overview]
Message-ID: <596830816.1041606846@aslan.scsiguy.com> (raw)
In-Reply-To: <20030103101618.GB8582@in.ibm.com>
> Looks like the aic7xxx driver in 2.5.53 and 54 are broken on my hardware.
It looks like the driver recovers fine.
...
> aic7xxx: PCI Device 0:1:0 failed memory mapped test. Using PIO.
> Uhhuh. NMI received for unknown reason 25 on CPU 0.
SERR must be enabled by your BIOS. I will change the driver so
that, should the memory mapped I/O test fail, an SERR (and thus an
NMI) is not generated.
...
> scsi0: PCI error Interrupt at seqaddr = 0x2
> scsi0: Signaled a Target Abort
These are left over from the failed memory mapped I/O test. They
should have been cleared by the test, but the behavior must be
different for the 7896/97. I'll review the documentation for this
chip and see if I can quiet up the failure.
Just out of curiosity, do you have any strange PCI options enabled
in your BIOS? I remeber seeing memory mapped I/O failures on this
ServerWorks chipset under FreeBSD in the past, but an updated BIOS
resolved the issue for the affected users. It seemed that the BIOS
incorrectly placed the Adaptec controller in a prefetchable region.
--
Justin
next prev parent reply other threads:[~2003-01-03 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 10:16 aic7xxx broken in 2.5.53/54 ? Dipankar Sarma
2003-01-03 15:14 ` Justin T. Gibbs [this message]
2003-01-06 7:32 ` Dipankar Sarma
2003-01-06 16:16 ` Justin T. Gibbs
2003-01-08 2:41 ` Tomas Szepe
2003-01-08 4:23 ` Justin T. Gibbs
2003-01-08 10:05 ` Tomas Szepe
2003-01-09 11:52 ` David Lang
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=596830816.1041606846@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=dipankar@in.ibm.com \
--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