From: Hans-Peter Jansen <hpj@urpla.net>
To: Jason Lunz <j@falooley.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: new aic7xxx bug, 2.4.13/6.2.4
Date: Mon, 12 Nov 2001 19:45:31 +0100 [thread overview]
Message-ID: <20011112184533.1DE6A1027@shrek.lisa.de> (raw)
In-Reply-To: <20011101222455.A5885@orr.falooley.org> <200111021443.fA2EhRY46335@aslan.scsiguy.com> <20011102143545.A30381@trellisinc.com>
In-Reply-To: <20011102143545.A30381@trellisinc.com>
On Friday, 2. November 2001 20:35, Jason Lunz wrote:
> In mlist.linux-kernel, you wrote:
[...]
> > But the mid-layer has already decided that it can't recover this device,
> > so it calls it dead and refuses to allow I/O to it anymore.
>
> This is definitely wrong. The drive won't do anything now without a
> reboot (or maybe removing and reinserting all scsi modules; I could do
> that but I haven't tried it).
>
> > Have you recently changed your version of cdrdao? Perhaps that program
> > is issuing a command that this particular drive simply will not accept?
>
> This is the same drive and version of cdrdao that have ripped more than
> 100 CDs. It's just this particular CD that breaks in this way at the
> same spot every time.
>
> If the DVD-ROM can't handle that CD then that's fine, but it would be
> nice if such a broken CD didn't result in not being able to use that
> drive at all anymore.
FYI: I've found a similar result under totally different conditions:
2.4.13-ac7
Vendor: TOSHIBA Model: DVD-ROM SD-M1502 Rev: 1012
Type: CD-ROM ANSI SCSI revision: 02
via ide-scsi
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 :)
Maybe you're barking up the wrong tree.
Hans-Peter
> thanks for your help,
>
> Jason
next prev parent reply other threads:[~2001-11-12 18:46 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 [this message]
2001-11-12 22:00 ` Jason Lunz
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=20011112184533.1DE6A1027@shrek.lisa.de \
--to=hpj@urpla.net \
--cc=j@falooley.org \
--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®