From: Patrick Plattes <patrick@erdbeere.net>
To: linux-kernel@vger.kernel.org
Subject: cdrecord problem. (hdc: status error: status=0x50 { DriveReady SeekComplete })
Date: Wed, 1 Sep 2004 21:36:01 +0200 [thread overview]
Message-ID: <20040901193601.GA1344@erdbeere.net> (raw)
hello,
i have some trouble with cdrecord, but no idea where to search or where
to ask - i hope this is the right place.
mounting the cd or play audio tracks work just fine, but if i start to
use cdrecord i got this [1] messages on the screen and in the dmesg. the
first time i've seen the problem was with 2.6.8 and now i work with
2.6.9-rc1 - i thought this could be a known and fixed problem, but i
have the same problem.
tomorrow i will try it with an older kernel (maybe 2.6.2). if you have
any other idea how to find this problem, please send me an e-mail
thanks,
patrick
[1]
hdc: CHECK for good STATUS
hdc: status error: status=0x50 { DriveReady SeekComplete }
hdc: status error: error=0xd0LastFailedSense 0x0d
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: DMA disabled
hdc: drive not ready for command
hdc: ATAPI reset timed-out, status=0x80
ide1: reset: success
hdc: DMA interrupt recovery
hdc: lost interrupt
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x08 { DataRequest }
hdc: status error: error=0x01IllegalLengthIndication
hdc: drive not ready for command
hdc: status timeout: status=0xd0 { Busy }
hdc: status timeout: error=0xd0LastFailedSense 0x0d
hdc: drive not ready for command
[...]
reply other threads:[~2004-09-01 19:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040901193601.GA1344@erdbeere.net \
--to=patrick@erdbeere.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