On Mon, 17 Oct 2011 23:59:42 -0700 Dale Snell <[email protected]> dijo:
>On Mon, 17 Oct 2011 22:08:47 -0700 >John Jason Jordan <[email protected]> wrote: >> The only other clue I have found is the following from >> Xorg.0.log, which appeared right after the last time I had to >> restart the Input Service: >I think all the X log file is telling you is that it's seen that >the mouse was connected, and X has recognized it. A better >source of information would be dmesg or the system log. Those >would be /var/log/dmesg and /var/log/messages, respectively. >You'll be wanting to look at the end of those files. >(/var/log/messages belongs to root, so you'll need to su to root, >or do a "sudo tail ..." to read it. These are the files that >should give you a clue as to what's going on. 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. The following appeared at the very end of dmesg: [25197.967557] input: Bluetooth Travel Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input11 [25197.967698] generic-bluetooth 0005:046D:B002.0006: input,hidraw2: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on 00:1C:26:E7:03:99 [53757.646178] input: Bluetooth Travel Mouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input12 [53757.646319] generic-bluetooth 0005:046D:B002.0007: input,hidraw2: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on 00:1C:26:E7:03:99 <snipped more identical entries ending at "input 17." It sure would be easier to understand dmesg if it gave a date and time when the event happened. >From /var/log/messages: Oct 17 21:40:05 Devil8 kernel: [102270.147543] input: Bluetooth TravelMouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input16 Oct 17 21:40:05 Devil8 kernel: [102270.147890] generic-bluetooth 0005:046D:B002.000B: input,hidraw2: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on 00:1C:26:E7:03:99 <It died last night and the following is when I reconnected it.> Oct 17 23:36:28 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:11 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:13 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:13 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:14 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:16 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:16 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:19 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 17 23:37:36 Devil8 kernel: [109321.378502] input:BluetoothTravelMouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input17 Oct 17 23:37:36 Devil8 kernel: [109321.378870] generic-bluetooth 0005:046D:B002.000C: input,hidraw2: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on 00:1C:26:E7:03:99 <snipped dhcp stuff as I printed homework this morning> <It was dead this morning and the following is when I reconnected it.> Oct 18 07:43:24 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 18 07:43:24 Devil8 bluetoothd[1673]: Refusing connection: setupinprogress Oct 18 07:43:47 Devil8 kernel: [138492.054316] input:BluetoothTravelMouse as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input18 Oct 18 07:43:47 Devil8 kernel: [138492.054462] generic-bluetooth 0005:046D:B002.000D: input,hidraw2: BLUETOOTH HID v48.09 Mouse [Bluetooth Travel Mouse] on 00:1C:26:E7:03:99 >You say this started after last week's upgrade, have you tried >booting to a prior kernel? If you've left your system stock, the >previous two kernels are still installed, all you have to do is >select one from the grub boot menu. I haven't tried this yet, but it's a good suggestion. >Hurrr... I just checked with RedHat's Bugzilla for Bluez bugs, >and there's one that matches your problem exactly, except that the >author is running F15, with blues-4.87. Since you're running F14, >I'm not sure that this isn't just a coincidence; still, it seems >odd. <https://bugzilla.redhat.com/show_bug.cgi?id=716479> It wouldn't surprise me if Fedora 14 and 15 are using the same kernel (assuming both are updated, as mine is). Fedora supports only the current and immediately previous versions; prior versions are cut off and there are no more updates for anything. Thanks for the link. I read the report and it does sound identical. I don't have an account and didn't want to create one just to add a "me too." However, if only two of us have the problem, that is weird. 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. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
