Andrew Morton wrote:
On Mon, 20 Apr 2009 18:52:34 -0700
Andy Isaacson <adi@xxxxxxxxxxxxx> wrote:
I'm running 2.6.30-rc2-00446-ga939b96 on a Dell E4300 with a
upgraded-to-Jaunty-mostly Ubuntu install. Using 2.6.28 and 2.6.29.1,
I've successfully burned a dozen CDRs, but since updating to .30-rc1
I've noticed intermittent failures to burn CDRs using wodim at the Gnome
desktop. (Switching back to .29.1 makes wodim reliable again.) There
have been a few different failure modes, but all of them seem to be
associated with these messages in dmesg, which I haven't seen before:
[ 360.740810] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 360.740816] sr 1:0:0:0: [sr0] Sense Key : Illegal Request [current]
[ 360.740820] sr 1:0:0:0: [sr0] Add. Sense: Logical block address out of range
[ 360.740826] end_request: I/O error, dev sr0, sector 0
[ 360.740830] Buffer I/O error on device sr0, logical block 0
...
Oh well, let's tentatively assume that we have a post-2.6.29 regression
in the libata ahci driver.
I tend to doubt it's a problem in ahci itself, I would guess it's higher
up the stack. Or could be that it's not a kernel bug, just some change
in timing that triggers the problem.
What's supposed to stop udev/hal from poking at the drive while wodim is
writing to the disc, anyway?
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
