From: safemode <safemode@speakeasy.net>
To: linux-kernel@vger.kernel.org
Subject: cd writer problems with 2.4.5ac17
Date: Sat, 23 Jun 2001 21:03:22 -0400 [thread overview]
Message-ID: <20010624010433Z262618-17720+7036@vger.kernel.org> (raw)
I'm thinking that this is a kernel scsi emu problem rather than a CDR problem
due to the past scsi emulation mails i've seen about previous kernels. I've
been forced to move to 2.4.x because i want to use my promise ata66 ide
controller and the 2.2 promise drivers dont work for it. My CDR is detected
as Vendor: CREATIVE Model: CD-RW RW8438E Rev: FC03 by the ide-scsi
module. Now the problem is, cdrecord is very tempermental with it and it
shouldn't be. Often there are input output errors reading blank media before
writing, these lead to drive lockups that can only be recovered by power
cycling (rebooting). The cdrecord i'm using is version 1.11a04 and i'm
going to try an earlier release to see if it's a cdrecord issue in a bit but
i wanted to get responses from anyone else who may be having these problems
early if it isn't.
Errors: In dmesg this shows up.
scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 0, lun 0
Write (10) 00 00 00 00 00 00 00 1f 00
hde: irq timeout: status=0xd0 { Busy }
hde: ATAPI reset complete
I cant get the cdrecord actual error until i reboot, but then when i do it's
random when the error does occur, just that it does after a few uses of the
burner.
on a side note. the kernel really likes to hang up when writing to a cd.
This never used to happen a few kernel releases ago. it slows everything
else down but when the cdr does write a cd, it does so without losing any
fifo buffer.
Any more info needed i'd like to give to figure this out, the thing is,
everytime this happens i have to reboot to use the CDR again. It wont even
detect unless it's power cycled and just unplugging the power cord and
putting it back in doesn't really help because it causes one of my other
drives to flip out. (did that last night.)
next reply other threads:[~2001-06-24 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-24 1:03 safemode [this message]
2001-06-25 4:05 Pavel Roskin
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=20010624010433Z262618-17720+7036@vger.kernel.org \
--to=safemode@speakeasy.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®