Hello, linux-ide@xxxxxxxxxxxxxxxxx wrote: > Hello, > I've tried the patch (thanks a lot for your help) and it works more or > less. > > More precisely: > when booting without a CD in the drive: > * no errors during the boot > * the drive is now active (that's a big plus) > * it can read about half the CDs that I insert (in a sample of ~7 audio > and data, burnt and pressed), I have tested no DVDs yet, and I haven't > burnt anything yet Hmmm... > * and the error log when a CD can't be read looks like this (dmesg tail) > [ 227.213893] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE,SUGGEST_OK > [ 227.213914] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] > [ 227.213926] Info fld=0x2e81 > [ 227.213930] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error > [ 227.213942] end_request: I/O error, dev sr0, sector 47616 > [ 227.213954] Buffer I/O error on device sr0, logical block 5952 > [ 234.227424] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE,SUGGEST_OK > [ 234.227446] sr 1:0:0:0: [sr0] Sense Key : Medium Error [current] > [ 234.227457] Info fld=0x2e81 > [ 234.227461] sr 1:0:0:0: [sr0] Add. Sense: L-EC uncorrectable error > [ 234.227473] end_request: I/O error, dev sr0, sector 47616 > [ 234.227484] Buffer I/O error on device sr0, logical block 5952 > [ 241.163142] sr 1:0:0:0: [sr0] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE,SUGGEST_OK ... > * When booting with a CD that doesn't work after an 'empty boot', I get > similar errors as before (and like the last pair of lines above), but > the CD can be read. When I insert another CD that didn't work after an > empty boot afterwards, it still doesn't work. Those errors shouldn't have much to do with how the transport is configured. These are the drive failing to read the media and these errors can be quite indetermininstic, so it's possible that the pattern really isn't a pattern but then again the drive doesn't seem to have much problem being peculiar. Can you please test more times and verify the pattern? > I guess that this is a state of things I can more or less live with > (unless you have a still better idea), I don't know whether the patch > should go in the trunk. Though it doesn't completely fix things, for me > it's better than before. Obviously, it would be best if the Pioneer > people fixed their broken firmware soon, which I hope they will. As the behavior is so peculiar, one thing I'm worried about is whether the problem is common to the model or is specific to the drive. If the former, it should go into mainline. Do you happen to know anyone who has the same model? > Anyway, thank you very much for your help. With other OSs it's probably > not so easy to get developer support ;-) Happy new year. :-) -- tejun -- 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
