From: Matthew Wilcox <matthew@wil.cx>
To: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Cc: linux-scsi@vger.kernel.org, Matthew Wilcox <matthew@wil.cx>
Subject: Re: sym53c8xx parity errors on SuSE 9.1's hwscan?
Date: Thu, 23 Sep 2004 03:39:14 +0100 [thread overview]
Message-ID: <20040923023914.GV16153@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <m3y8j1q4gs.fsf@merlin.emma.line.org>
On Thu, Sep 23, 2004 at 01:16:51AM +0200, Matthias Andree wrote:
> SuSE Linux 9.1 (kernel 2.6.5 + SuSE patch set, but also 2.6.7 or a bit
> milder in 2.6.9-rc2-mm1) uses some SuSE-specific "hwprobe" or "hwinfo"
> tool to scan for hardware.
Does anyone have the source? I'd be interested to see what it's up to.
> I find it a bit intimidating that user-space (albeit with root
> permissions) causes "SCSI" parity errors, and given the 2.6.9 logging
> towards the end of the mail, I am wondering if SuSE's hwinfo stuff
> triggers some race condition or manages to bypass the SCSI phase state
> machine or if the probe confuses the chip. I haven't yet managed to
> isolate (with strace) the cause.
I have a suggestion. If the probe attempts to size the BARs of the
chip, this is a destructive process that could well cause the chip to
start spewing errors are require a reset to work again.
> Is there a useful debug setting for sym53c8xx that could shed some light
> on what the user-space has attempted that led to the SCSI parity error?
The trouble is that I suspect the probe is completely bypassing the driver.
It might be worth instrumenting drivers/pci/proc.c to see if it's writing
to any of the BARs (particularly the second memory BAR, the one that's 8k).
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2004-09-23 2:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 23:16 sym53c8xx parity errors on SuSE 9.1's hwscan? Matthias Andree
2004-09-23 2:39 ` Matthew Wilcox [this message]
2004-09-23 7:42 ` Olaf Hering
2004-09-23 8:51 ` Matthias Andree
2004-09-23 8:45 ` Matthias Andree
2004-10-25 8:16 ` Matthias Andree
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=20040923023914.GV16153@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=linux-scsi@vger.kernel.org \
--cc=ma@dt.e-technik.uni-dortmund.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.