linux-kernel - Re: buffer io error on device sr0?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AD51D3F.2030603@gmail.com>
Date:	Tue, 13 Oct 2009 18:37:19 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	tfjellstrom@...w.ca
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: buffer io error on device sr0?

On 10/13/2009 03:43 AM, Thomas Fjellstrom wrote:
> I'm not sure which version it started, but it seems at least 2.6.32-rc3-git2
> has issues with detecting blank DVDR disks.
>
> [220595.198654] cdrom: This disc doesn't have any tracks I recognize!
> [220595.298488] sr 3:0:0:0: [sr0] Unhandled sense code
> [220595.298492] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [220595.298496] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
> [220595.298501] sr 3:0:0:0: [sr0] Add. Sense: No additional sense information
> [220595.298505] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
> [220595.298514] end_request: I/O error, dev sr0, sector 0
> [220595.298518] Buffer I/O error on device sr0, logical block 0
> [220595.304554] sr 3:0:0:0: [sr0] Unhandled sense code
> [220595.304562] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [220595.304570] sr 3:0:0:0: [sr0] Sense Key : Blank Check [current]
> [220595.304579] sr 3:0:0:0: [sr0] Add. Sense: No additional sense information
> [220595.304588] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
> [220595.304609] end_request: I/O error, dev sr0, sector 0
> [220595.304616] Buffer I/O error on device sr0, logical block 0
>
> Unless its supposed to be this way. Although I didn't receive any kind of
> notification when inserting the disk, as I used to (could be a hal/kde error,
> but the logs in dmesg seem to hint otherwise).

Something tried to read off the disk and the drive reported "no way, 
it's blank". That's all this indicates. Most likely HAL or something is 
doing the read..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/