From: Bradley Reed <bradreed1@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: CDR read problems with 2.6.11?
Date: Thu, 14 Apr 2005 01:36:19 +0200 [thread overview]
Message-ID: <20050414013619.342cea4e@galactus.localdomain> (raw)
I am running 2.6.11 with -ac4 and
realtime-preempt-2.6.11-final-V0.7.40-00 patches. Up to now, no
complaints, great job everyone.
Today I burnt two data backup CDs onto CD-R (I used k3b if it
matters) and the burn went 100% fine. No errors, I can read the
disks on other computers or on this one if I reboot into a different
kernel (2.4.28 for instance). Unfortunately I cannot read them from
the kernel I burned them with. [1]
mount yields:
root@galactus:~[1009]# mount /mnt/cdrom
mount: wrong fs type, bad option, bad superblock on /dev/cdrom,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
dmesg shows:
hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: DMA disabled
hda: ATAPI reset complete
hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: ATAPI reset complete
hda: tray open
end_request: I/O error, dev hda, sector 64
isofs_fill_super: bread failed, dev=hda, iso_blknum=16, block=16
hda: irq timeout: status=0xd0 { Busy }
ide: failed opcode was: unknown
hda: ATAPI reset complete
Obviously the tray is NOT open, but the other errors don't mean much
to me.
The drive is a NEC DVD+RW ND-5100A
Any suggestions on why I can't read (or burn correctly) the disks with 2.6.11?
Brad
[1] Actually although they mount and I can ls them under 2.4.28, not all the
files seem to be complete. The last few tarballs seem to be incomplete.
Earlier ones in the ls listing seem fine. Strange.
next reply other threads:[~2005-04-13 23:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 23:36 Bradley Reed [this message]
2005-04-14 0:03 ` Bernd Schubert
2005-04-14 0:16 ` Bradley Reed
2005-04-23 12:52 ` Jan Knutar
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=20050414013619.342cea4e@galactus.localdomain \
--to=bradreed1@gmail.com \
--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®