046d:c508 Logitech Optical Trackman resets
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
My mouse doesn't work and I keep getting the following message:
[ 1227.610132] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1229.510131] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1231.420138] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1233.170132] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1234.940134] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1236.700138] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1238.540162] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1240.380148] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1242.180122] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1243.940234] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1245.780141] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1247.590128] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1249.540164] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1251.400122] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1253.270135] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1255.010133] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1256.730079] usb 4-1: reset low speed USB device using ohci_hcd and address 2
[ 1258.520062] usb 4-1: reset low speed USB device using ohci_hcd and address 2
after I disconnect and reconnect the mouse, everything works fine
[ 1260.330180] usb 4-1: USB disconnect, address 2
[ 1261.080139] usb 4-1: new low speed USB device using ohci_hcd and address 3
[ 1261.275125] usb 4-1: configuration #1 chosen from 1 choice
[ 1261.288050] input: Logitech USB Receiver as /devices/
[ 1261.290406] generic-usb 0003:046D:
this happens in 30% of boots and it also prevents logging into the machine using ssh (ssh user@machine <command> still works, I guess the tty allocation is blocked only)
k@ubuntu:~$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: k 2090 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Audigy2'/'SB Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0xe800, irq 21'
Mixer name : 'SigmaTel STAC9750,51'
Components : 'AC97a:83847650'
Controls : 202
Simple ctrls : 37
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Frequency: Once every few days.
HibernationDevice: RESUME=
IwConfig:
lo no wireless extensions.
eth1 no wireless extensions.
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7576
NonfreeKernelMo
Package: linux (not installed)
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
ProcVersionSign
Regression: No
RelatedPackageV
Reproducible: No
RfKill:
Tags: lucid needs-upstream-
Uname: Linux 2.6.32-22-generic x86_64
UserGroups: adm admin cdrom dialout fuse lp lpadmin plugdev sambashare vboxusers
dmi.bios.date: 05/08/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.3
dmi.board.
dmi.board.name: 790GX-G65 (MS-7576)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7576
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
Changed in linux (Ubuntu): | |
status: | Incomplete → New |
tags: | added: kj-triage |
tags: | added: acpi |
tags: | added: acpi-bad-address |
tags: | added: acpi-no-handler |
tags: | added: acpi-parse-exec-fail |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it without more information.
Please run the following command which will attach necessary information:
apport-collect 592804
Bear in mind that when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.
If you cannot use apport please at least add the following information (pay attention to lspci's additional options): signature > version.log
First run the following commands:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_
then attach the files separately to the bug report (not pasted into comments or tar/zip-ed).
For your reference, the full description of procedures for kernel-related bug reports is available at https:/ /wiki.ubuntu. com/KernelTeam/ KernelTeamBugPo licies. Thanks in advance!