Comment 7 for bug 113144

Hi,
this problem is solved in my system by using kernel 2.6.22-14-generic...
No help I know... :( sorry

Martin

Brezhonneg píše v Út 11. 12. 2007 v 11:47 +0100:
> Even though this bug report seems to get no attention, I am attaching
> yet another dmesg log. It confirms what I mentioned last time about the
> drive confused message:
>
> [ 1997.917839] hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
> [ 4052.407147] hda: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recover by ending request.
> [21695.426855] hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>
> Also, I noticed in this one (maybe in the previous one too) that the
> message happens to change at some point:
>
> [21699.361481] hda: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> [21699.361485] ide: failed opcode was: unknown
> [21699.361488] hda: drive not ready for command
> [21700.363396] hda: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
> [21700.363405] hda: status error: error=0x40 { LastFailedSense=0x04 }
> [21700.363409] ide: failed opcode was: unknown
> [21700.363413] hda: drive not ready for command
>
>
> ** Attachment added: "dmesg variation"
> http://launchpadlibrarian.net/10841087/dmesg.log
>
> ** Also affects: linux-source-2.6.22 (Ubuntu)
> Importance: Undecided
> Status: New
>