From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Olaf Hering <olaf@aepfle.de>, Linus Torvalds <torvalds@osdl.org>,
linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.18-rc6
Date: Wed, 06 Sep 2006 10:47:33 +1000 [thread overview]
Message-ID: <1157503653.22705.156.camel@localhost.localdomain> (raw)
In-Reply-To: <1157498567.3463.91.camel@mulgrave.il.steeleye.com>
On Tue, 2006-09-05 at 18:22 -0500, James Bottomley wrote:
> On Wed, 2006-09-06 at 08:20 +1000, Benjamin Herrenschmidt wrote:
> > Yes, it's a PCI error.
>
> Thanks, and the cat of /proc/scsi_host/host<n>/signalling?
>
> My suspicion is the register doesn't actually exist on this card so it
> doesn't actually respond on the bus. However, on my equivalent
> everything works; largely I think because the only PC's I have don't
> know how to signal a PCI error.
Olaf will tell us (I don't have the hardware) but it's indeed a typical
thing .... From my experience, Adaptec tend to very easily throw PCI
aborts at you if it doesn't like something in a register access (which
isn't necessarily a bad thing btw, other vendors are more lenient tho),
and Macs are well known to Machine Check the box when getting a PCI
error while most x86 boxes silently ignore them...
Ben.
next prev parent reply other threads:[~2006-09-06 0:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0609031939100.27779@g5.osdl.org>
2006-09-05 12:26 ` Linux 2.6.18-rc6 Olaf Hering
2006-09-05 21:01 ` James Bottomley
2006-09-05 22:20 ` Benjamin Herrenschmidt
2006-09-05 23:22 ` James Bottomley
2006-09-06 0:47 ` Benjamin Herrenschmidt [this message]
2006-09-06 12:09 ` Olaf Hering
2006-09-06 11:01 ` Olaf Hering
2006-09-06 14:04 ` James Bottomley
2006-09-07 9:15 ` Olaf Hering
2006-09-07 14:04 ` James Bottomley
2006-09-16 3:47 ` Doug Ledford
2006-09-16 8:44 ` Olaf Hering
2006-09-17 5:38 ` Olaf Hering
2006-09-17 14:05 ` James Bottomley
2006-09-17 18:17 ` Doug Ledford
2006-09-17 18:20 ` 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=1157503653.22705.156.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=torvalds@osdl.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