I've started getting what I think are false warnings about my cd drive during boot. They are triggered by hald and acpi-support and are of this form:
ATAPI device hdc: Jan 7 10:32:44 corinthia kernel: Error: Not ready -- (Sense key=0x02) Jan 7 10:32:44 corinthia kernel: No reference position found (media may be upside down) -- (asc=0x06, ascq=0x00) Jan 7 10:32:44 corinthia kernel: The failed "Read 10" packet command was: Jan 7 10:32:44 corinthia kernel: "28 00 00 00 00 00 00 00 08 00 00 00 00 00 00 00 " Jan 7 10:32:44 corinthia kernel: end_request: I/O error, dev hdc, sector 0 Jan 7 10:32:44 corinthia kernel: Buffer I/O error on device hdc, logical block 0 Jan 7 10:32:44 corinthia kernel: Buffer I/O error on device hdc, logical block 1 Jan 7 10:32:44 corinthia kernel: Buffer I/O error on device hdc, logical block 2 Jan 7 10:32:44 corinthia kernel: Buffer I/O error on device hdc, logical block 3 Jan 7 10:32:45 corinthia kernel: Buffer I/O error on device hdc, logical block 4 Jan 7 10:32:45 corinthia kernel: Buffer I/O error on device hdc, logical block 5 Jan 7 10:32:45 corinthia kernel: Buffer I/O error on device hdc, logical block 6 Jan 7 10:32:45 corinthia kernel: Buffer I/O error on device hdc, logical block 7 Jan 7 10:32:45 corinthia kernel: hdc: tray open Then: The failed "Read 10" packet command was: Jan 7 10:19:29 corinthia kernel: "28 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 " Jan 7 10:19:29 corinthia kernel: end_request: I/O error, dev hdc, sector 0 Jan 7 10:19:29 corinthia kernel: hdc: tray open Jan 7 10:19:29 corinthia kernel: ATAPI device hdc: Jan 7 10:19:29 corinthia kernel: Error: Not ready -- (Sense key=0x02) Jan 7 10:19:29 corinthia kernel: No reference position found (media may be upside down This is repeated many times, and then I get: hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Er ror } Jan 7 10:32:50 corinthia kernel: hdc: drive_cmd: error=0x04 { AbortedCommand } Jan 7 10:32:50 corinthia kernel: ide: failed opcode was: 0xef After all this the system starts normally and the cd drive is usable. (The drive was empty while booting.) Oddly, I have a duplicate installation of Debian in a different partition which does not produce any of this stuff. Same kernel (2.6.18-4-686). Googling produced a few reports of a similar phenomenon on other systems (Ubuntu, Suse) but no clear indication of the cause -- just some speculation about the kernel being at fault. Anyone else seeing this? Anything to check? Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]