From: David Ford <david+challenge-response@blue-labs.org>
To: linux-kernel@vger.kernel.org
Cc: Jens Axboe <axboe@suse.de>, Mans Matulewicz <cybermans@xs4all.nl>
Subject: Re: ide-cdrom / atapi burning bug - 2.6.1
Date: Sat, 31 Jan 2004 13:17:06 -0500 [thread overview]
Message-ID: <401BF122.2090709@blue-labs.org> (raw)
In-Reply-To: <20040131093438.GS11683@suse.de>
I don't have an RW, but when my cdrom fixates, it stalls everything
while it's fixating. I have an nForce chipset. (2.6.x)
Jens Axboe wrote:
>On Sat, Jan 31 2004, Mans Matulewicz wrote:
>
>
>>Hi,
>>After replacing my 2.4.22 with a 2.6.1 kernel I tried ATAPI cd burning.
>>This totally fails. Most of the CD's are corrupt and my system totally
>>locks up when erasing an cdrw (reset button was the option I needed to
>>reboot my system) . k3b reports cd is completely burned but fails are
>>not identical or totally unreadable. I tried it both with an tainted
>>(nvidia) and an untainted (nv) kernel: same results. With ide-scsi
>>burning in 2.4.x I had no problems.
>>
>>
>
>Did you use DMA in 2.4 as well? Does 2.6 work if you turn it off? It's
>most likely an issue with your via adapter.
>
>
>
next prev parent reply other threads:[~2004-01-31 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 1:05 ide-cdrom / atapi burning bug - 2.6.1 Mans Matulewicz
2004-01-31 9:34 ` Jens Axboe
2004-01-31 10:10 ` Mans Matulewicz
2004-01-31 10:20 ` Jens Axboe
2004-01-31 10:27 ` Mans Matulewicz
2004-01-31 10:32 ` Jens Axboe
2004-01-31 16:45 ` Mans Matulewicz
2004-01-31 18:17 ` David Ford [this message]
2004-01-31 18:49 ` Jens Axboe
2004-02-01 0:00 ` Daniel Pittman
2004-02-01 15:25 ` Jens Axboe
2004-02-01 8:24 ` Alan
2004-02-01 15:27 ` Jens Axboe
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=401BF122.2090709@blue-labs.org \
--to=david+challenge-response@blue-labs.org \
--cc=axboe@suse.de \
--cc=cybermans@xs4all.nl \
--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