From: j-nomura@ce.jp.nec.com
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] CD-ROM I/O error
Date: Mon, 10 Jun 2002 10:18:34 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905659@msgid-missing> (raw)
Hello,
when I do 'cat /dev/cdrom > disc.iso' on my Itanium box,
I/O error happens on CD-ROM.
| hda: cdrom_decode_status: status=0x51 { DriveReady SeekComplete Error }
| hda: cdrom_decode_status: error=0x30
| hda: ATAPI reset complete
| end_request: I/O error, dev 03:00 (hda), sector 1322520
| hda: irq timeout: status=0xd0 { Busy }
| hda: ATAPI reset complete
With the same CD, I/O error does not happen on my Pentium machine.
I'm trying 2.4.17 and 2.4.18. Both results in same error.
Has anyone experienced a problem like this?
Best regards.
--
NOMURA, Jun'ichi <j-nomura@ce.jp.nec.com, nomura@hpc.bs1.fc.nec.co.jp>
HPC Operating System Group, 1st Computers Software Division,
Computers Software Operations Unit, NEC Solutions.
next reply other threads:[~2002-06-10 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 10:18 j-nomura [this message]
2002-06-10 15:56 ` [Linux-ia64] CD-ROM I/O error Matt_Domsch
2002-06-11 7:55 ` j-nomura
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=marc-linux-ia64-105590701905659@msgid-missing \
--to=j-nomura@ce.jp.nec.com \
--cc=linux-ia64@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