On Tue, 18 Oct 2011 10:01:34 -0700
John Jason Jordan <[email protected]> wrote:
> It was dead again this morning. After restarting it and doing a
> few other morning tasks I looked at dmesg and var/log/messages.
>
> From dmesg:
>
> First, these messages are repeated over and over:
> [22976.956175] sr 3:0:0:0: [sr0] Add. Sense: Logical block
> address out of range [22976.956186] sr 3:0:0:0: [sr0] CDB:
> Read(10): 28 00 00 00 00 00 00 00 02 00
> [22976.956208] end_request: I/O error, dev sr0, sector 0
> [22976.959093] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> [22976.959103] sr 3:0:0:0: [sr0] Sense Key : Illegal Request
> [current] [22976.959114] Info fld=0x0
> [22976.959119] sr 3:0:0:0: [sr0] Add. Sense: Logical block
> address out of range
> [22976.959130] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00
> 00 00 00 02 00
> [22976.959152] end_request: I/O error, dev sr0, sector 0
>
> I don't think they are related, but I have no idea what Sense
> is. My hard disk passes Palimpsest Smart check and fsck. There
> is a USB hard disk attached, and there is also the optical
> drive. The USB disk has a couple torrent files on it that I
> have been seeding.
You're right, this isn't related to your bluetooth trouble.
/dev/sr0 is your CD/DVD drive. "Sense Key" is SCSI-spec jargon.
The host controller asks the SCSI peripheral for a status check,
and it returns a block of "sense data". The sense key is an error
code contained within that sense data.
(log messages snipped)
Hmm, looks to me like these messages are about establishing a
connection with the mouse. I had hoped to see some message
pertaining to DISconnecting it. That would give us a lead on why
it's being disconnected. You could try this: Check
/var/log/dmesg and /var/log/messages and see what's at the end of
each. Then let your system sit idle until the mouse disconnects.
Then, _without reconnecting the mouse,_ see what has changed in
those files. After that, reconnect the mouse and again see what
changed. A bit time-consuming, I know, but it would give you more
information to work with. Right now, I'm afraid that's all I can
come up with.
(I have the sneaking suspicion that Paul Heinlein's suggestion is
right: There's a kernel setting that's causing this. Not
necessarily a bug, _per se,_ but something mis-configured. There
may be a setting in /proc that could be changed, but I have no
idea what it might be.)
> I hope something in the above log entries flashes someone's
> synapses into more suggestions. I'll keep poking, and this
> evening I'll have time to try booting to a previous kernel.
Good luck!
--Dale
--
Kington's Law of Perforation:
If a straight line of holes is made in a piece of paper, such
as a sheet of stamps or a check, that line becomes the strongest
part of the paper.
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
