From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: thomas.schorpp@gmail.com
Cc: SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: aic7xxx: aic7892(B): possible regression in 2.6.26: intermittent unexpected busfrees
Date: Wed, 30 Jul 2008 15:26:16 -0500 [thread overview]
Message-ID: <1217449576.3335.42.camel@localhost.localdomain> (raw)
In-Reply-To: <4890B218.3030009@gmail.com>
On Wed, 2008-07-30 at 20:25 +0200, thomas schorpp wrote:
> thomas schorpp wrote:
> > hi,
> >
> > got dozens of intermittent bus-frees in few days with my Cheetah X15
> > since upgrading to vanilla release kernel 2.6.26.0
> >
> > -did not touch the hw
> > -fsck ok
> > -smart short/long selftest ok
> > -temperatures/voltages ok
> >
> > is this the hot weather, my old adaptec 19160 hba or the on disc
> > controller dying or have You guys done some "performance" changes in
> > aic7xxx released with 2.6.26 ?
>
> takeback. powerline voltage ribble by crappy REVOLTEC hdd fan cooler with broken
> fan bearings after 3 months on the same line as the Cheetah.
>
> greased, changed line and all fine again, sorry that is was not software ;)
It's a nice illustration of the problems hardware can cause on finicky
transmission lines that are SCSI buses.
Note, if the problems cause system failures (as in panics or causes
other problems ... well other problems than the usual ones caused when
the disk is lost or only intermittently accessible) then it would become
a software issue.
James
prev parent reply other threads:[~2008-07-30 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 13:19 aic7xxx: aic7892(B): possible regression in 2.6.26: intermittent unexpected busfrees thomas schorpp
2008-07-30 18:25 ` thomas schorpp
2008-07-30 20:26 ` James Bottomley [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=1217449576.3335.42.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=thomas.schorpp@gmail.com \
/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