From: Dipankar Sarma <dipankar@in.ibm.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: aic7xxx broken in 2.5.53/54 ?
Date: Mon, 6 Jan 2003 13:02:04 +0530 [thread overview]
Message-ID: <20030106073204.GA1875@in.ibm.com> (raw)
In-Reply-To: <596830816.1041606846@aslan.scsiguy.com>
Hi Justin,
On Fri, Jan 03, 2003 at 08:14:06AM -0700, Justin T. Gibbs wrote:
> > Looks like the aic7xxx driver in 2.5.53 and 54 are broken on my hardware.
>
> It looks like the driver recovers fine.
Not for long. It dies shortly afterwards.
> > 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.
I guess having to use PIO with aic7xxx is bad. MMIO failure is
what we need to investigate.
>
> 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.
>
I didn't change anything in that box since it was delivered to me. FYI
it is an IBM x250. Would it help if I can get a PCI space dump and mtrr
dump ? FWIW, the older driver works fine. Does the older driver use
only PIO ?
Thanks
Dipankar
next prev parent reply other threads:[~2003-01-06 7:21 UTC|newest]
Thread overview: 11+ 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
2003-01-06 7:32 ` Dipankar Sarma [this message]
2003-01-06 16:16 ` Justin T. Gibbs
2003-01-06 16:36 ` uaca
2003-01-07 11:36 ` uaca
2003-01-08 2:41 ` Tomas Szepe
2003-01-08 4:23 ` Justin T. Gibbs
2003-01-08 10:05 ` Tomas Szepe
2003-01-08 15:39 ` uaca
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=20030106073204.GA1875@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=gibbs@scsiguy.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