Description of problem: With my DVD writer (LG GSA-4167B, latest firmware DL13), when trying to write a DVD (DVD+R) with growisofs, it gets to some (single digit) percentage, then stops with the error message: :-[ WRITE@LBA=21320h failed with SK=3h/ASC=02h/ACQ=00h]: Input/output error builtin_dd: 135968*2KB out @ average 2.4x1385KBps :-( write failed: Input/output error /dev/dvd: flushing cache :-[ SYNCHRONOUS FLUSH CACHE failed with SK=3h/ASC=A0h/ACQ=80h]: Input/output error With the previous kernel-2.6.17-1.2174_FC5, everything works as expected. Version-Release number of selected component (if applicable): kernel-2.6.17-1.2187_FC5 dvd+rw-tools-5.21.4.10.8-6.2.1 How reproducible: Always (3 coasters so far) Steps to Reproduce: 1. pop blank DVD+R into drive 2. e.g. "growisofs -v -dvd-compat -Z /dev/dvd -dvd-video "/scratch/video/tmp/" -speed=8" Actual results: error above Expected results: DVD gets written entirely Additional info: works with previous kernel-2.6.17-1.2174_FC5
Created attachment 136798 [details] log of failed attempts to write DVD
*** Bug 207413 has been marked as a duplicate of this bug. ***
A new kernel update has been released (Version: 2.6.18-1.2200.fc5) based upon a new upstream kernel release. Please retest against this new kernel, as a large number of patches go into each upstream release, possibly including changes that may address this problem. This bug has been placed in NEEDINFO state. Due to the large volume of inactive bugs in bugzilla, if this bug is still in this state in two weeks time, it will be closed. Should this bug still be relevant after this period, the reporter can reopen the bug at any time. Any other users on the Cc: list of this bug can request that the bug be reopened by adding a comment to the bug. In the last few updates, some users upgrading from FC4->FC5 have reported that installing a kernel update has left their systems unbootable. If you have been affected by this problem please check you only have one version of device-mapper & lvm2 installed. See bug 207474 for further details. If this bug is a problem preventing you from installing the release this version is filed against, please see bug 169613. If this bug has been fixed, but you are now experiencing a different problem, please file a separate bug for the new problem. Thank you.
It has gotten better. I only saw this problem once and at some 95 odd percent, but as it is there still is something that is not quite right.
I'm currently on updated FC-6 and have since swapped my machine for an x86_64 one and I haven't seen this problem in quite a while. Closing as CURRENTRELEASE as I can't reproduce it anymore.