public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Wakko Warner <wakko@animx.eu.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Adaptec drivers and 2.6.x kernels
Date: Thu, 7 Oct 2004 15:49:27 -0700	[thread overview]
Message-ID: <20041007224927.GZ9106@holomorphy.com> (raw)
In-Reply-To: <20041007222709.GA24314@animx.eu.org>

On Thu, Oct 07, 2004 at 06:27:09PM -0400, Wakko Warner wrote:
> I've been irritated with this for some time now.  I've seen this with 2.6.7
> and 2.6.8.1 with both aic7xxx and aic79xx drivers.
> I have a bad CD (I burned it as fast as my burner could force.  I expected
> errors).  The scsi drivers do not handle errors very well.  I tried to read
> this bad cd on an ide cdrom (I have 2 one on hda and one on hdd), it just
> gives up with a read error.  If I do this on scd0 or scd1 (scd0 is an LG DVD
> multi burner using an acard u2w scsi to udma66 converter, scd1 is a plextor
> cdrw 40/12/40 narrow scsi), then the driver offlines the drive and I can't
> use it anymore.
> With this problem, the device recovered with scd1.  It was a simple:
> cd /proc/scsi
> echo "scsi remove-single-device 2 0 1 0" > scsi
> echo "scsi add-single-device 2 0 1 0" > scsi
> And it now works again.  Sometimes it doesn't.  scsi bus 0 and 1 are on the
> aic79xx [...]

I have boxen with aic7xxx and aic79xx that don't see issues of this
kind (granted, with bleeding edge -mm). Could you describe the systems
in more detail?


-- wli

  reply	other threads:[~2004-10-07 23:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07 22:27 Adaptec drivers and 2.6.x kernels Wakko Warner
2004-10-07 22:49 ` William Lee Irwin III [this message]
2004-10-08  0:06   ` Wakko Warner
2004-10-08 11:10     ` William Lee Irwin III
2004-10-08 11:19       ` Wakko Warner

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=20041007224927.GZ9106@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wakko@animx.eu.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