From: Michael Buesch <fsdeveloper@yahoo.de>
To: linux-kernel@vger.kernel.org
Subject: 2.4.x Problem with cd writing
Date: Wed, 16 Apr 2003 19:19:08 +0200 [thread overview]
Message-ID: <200304161919.08615.fsdeveloper@yahoo.de> (raw)
Hi.
I've problems with CD-writing since about a half year on various
2.4 kernels (2.4.18 (maybe, I don't remember exactly), 2.4.19, 2.4.2x)
While my writer writes TOC or fixes CD (doesn't write real data-stream),
the whole ide-disk interface of the system is frozen. Kernel ist still
working and all programs run correctly, until they need harddisk
access. No harddisk or CD-ROM access is possible.
After the writer finishes TOC or fixating, the ide-disk interface
defrosts.
mb@lfs:~> cdrecord -scanbus
Cdrecord 1.11a40 (i686-pc-linux-gnu) Copyright (C) 1995-2002 Jörg Schilling
Linux sg driver version: 3.1.24
Using libscg version 'schily-0.7'
scsibus0:
0,0,0 0) 'LG ' 'DVD-ROM DRD8160B' '1.01' Removable CD-ROM
0,1,0 1) 'TEAC ' 'CD-W54E ' '1.0Y' Removable CD-ROM << (my writer)
0,2,0 2) *
0,3,0 3) *
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
(I've tried various versions of cdrecord and it occurs in cdrdao, too)
root@lfs:/proc> hdparm /dev/hdd
/dev/hdd:
HDIO_GET_MULTCOUNT failed: Invalid argument
IO_support = 1 (32-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
BLKRAGET failed: Invalid argument
HDIO_GETGEO failed: Invalid argument
root@lfs:/proc> cat /proc/version
Linux version 2.4.21-pre6 (root@lfs) (gcc version 3.2.2) #3 Sam Apr 5 20:23:37 CEST 2003
--
Regards Michael Buesch.
http://www.8ung.at/tuxsoft
$ cat /dev/zero > /dev/null
/dev/null: That's *not* funny! :(
next reply other threads:[~2003-04-16 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 17:19 Michael Buesch [this message]
2003-04-16 17:30 ` 2.4.x Problem with cd writing Michael Buesch
2003-04-16 17:43 ` Valdis.Kletnieks
2003-04-16 17:52 ` Michael Buesch
2003-04-16 18:10 ` Steffen Moser
2003-04-16 18:58 ` Michael Buesch
2003-04-16 19:56 ` Steffen Moser
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=200304161919.08615.fsdeveloper@yahoo.de \
--to=fsdeveloper@yahoo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.