From: Jason Lunz <j@falooley.org>
To: Hans-Peter Jansen <hpj@urpla.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new aic7xxx bug, 2.4.13/6.2.4
Date: Mon, 12 Nov 2001 17:00:59 -0500 [thread overview]
Message-ID: <20011112170059.A23809@orr.falooley.org> (raw)
In-Reply-To: <20011101222455.A5885@orr.falooley.org> <200111021443.fA2EhRY46335@aslan.scsiguy.com> <20011102143545.A30381@trellisinc.com> <20011112184533.1DE6A1027@shrek.lisa.de>
In-Reply-To: <20011112184533.1DE6A1027@shrek.lisa.de>
On Mon, Nov 12, 2001 at 7:45PM +0100, Hans-Peter Jansen wrote:
> cdrdao read-cd --device /dev/sr0 --driver generic-mmc --buffers 80 -n
> --eject --paranoia-mode 0 toc
> [...]
> ?: Input/output error. : scsi sendcmd: retryable error
> CDB: BE 00 00 04 2C 67 00 00 1A F8 01 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 20.101s timeout 20s
> ?: Input/output error. : scsi sendcmd: retryable error
> CDB: BE 00 00 04 2E 43 00 00 1A F8 01 00
> status: 0x0 (GOOD STATUS)
> cmd finished after 20.101s timeout 20s
> [...]
> killed with ^c
>
> locked the drive completely. Need to reboot to eject the cd...
> I suspect some bad interference between DVD firmware, kernel
> SCSI error handling and cdrdao. A plextor reader finally
> succeeded on this job (wink :)
I agree it's the same effect, but I disagree about the cause. It's the
fault of the scsi mid-layer; it marks the device as dead when a command
times out and won't allow further accesses to it. The fact that it
happens to both of us with different drives and different scsi drivers
(you don't even have scsi, but ide-scsi emulation) shows that the scsi
midlayer is broken in both cases.
And as Justin Gibbs suggested, I'd bet that raising the timeout on the
failing scsi command in cdrdao would probably fix this for both of us,
but I haven't had time to try it. If so, it's not a userspace bug
because it allows any user with cdrom access to disable a cdrom until
reboot.
Jason
prev parent reply other threads:[~2001-11-12 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 3:24 Jason Lunz
2001-11-02 14:03 ` Krzysztof Halasa
2001-11-02 14:55 ` Justin T. Gibbs
2001-11-02 14:43 ` Justin T. Gibbs
2001-11-02 19:35 ` Jason Lunz
2001-11-02 20:03 ` Justin T. Gibbs
2001-11-02 20:17 ` Richard B. Johnson
2001-11-12 18:45 ` Hans-Peter Jansen
2001-11-12 22:00 ` Jason Lunz [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=20011112170059.A23809@orr.falooley.org \
--to=j@falooley.org \
--cc=hpj@urpla.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®