Ubuntu
linux package

USB devices occasionally stop working

Bug #923666 reported by Julian Edwards
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
High
Unassigned
Quantal
Invalid
High
Unassigned
Raring
Fix Released
High
Unassigned

Bug Description

I can't report this with ubuntu bug because:

$ ubuntu-bug
Segmentation fault (core dumped)

so here's my best description:

Sometimes, within a few minutes of boot, my usb-connected mouse and keyboard still stop working. For the mouse, it just stops but for the keyboard it breaks after a key down event which leaves whatever key you pressed repeating for ever (which makes it quite hard to reboot!).

Quite often I will know this is about to happen because the media keys and scroll wheel on the keyboard fail to work for a while before the eventual failure.

I see this in the syslog:
Jan 30 09:04:36 beast kernel: [ 240.576040] INFO: task modprobe:370 blocked for more than 120 seconds.
Jan 30 09:04:36 beast kernel: [ 240.576046] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 30 09:04:36 beast kernel: [ 240.576051] modprobe D ffffffff81806240 0 370 153 0x00000004
Jan 30 09:04:36 beast kernel: [ 240.576059] ffff880121c3fb68 0000000000000086 ffff880121c3fb18 ffffffff81309787
Jan 30 09:04:36 beast kernel: [ 240.576067] ffff880121c3ffd8 ffff880121c3ffd8 ffff880121c3ffd8 0000000000013780
Jan 30 09:04:36 beast kernel: [ 240.576073] ffffffff81c0d020 ffff880125162e20 ffff880121c3fb78 ffff8801251b96c0
Jan 30 09:04:36 beast kernel: [ 240.576079] Call Trace:
Jan 30 09:04:36 beast kernel: [ 240.576091] [<ffffffff81309787>] ? kobject_put+0x27/0x60
Jan 30 09:04:36 beast kernel: [ 240.576100] [<ffffffff81653bbf>] schedule+0x3f/0x60
Jan 30 09:04:36 beast kernel: [ 240.576106] [<ffffffff81491ced>] usb_kill_urb.part.4+0x5d/0xa0
Jan 30 09:04:36 beast kernel: [ 240.576112] [<ffffffff81089e50>] ? add_wait_queue+0x60/0x60
Jan 30 09:04:36 beast kernel: [ 240.576117] [<ffffffff81491d61>] usb_kill_urb+0x31/0x40
Jan 30 09:04:36 beast kernel: [ 240.576141] [<ffffffffa0082941>] usbhid_init_reports+0xc1/0x120 [usbhid]
Jan 30 09:04:36 beast kernel: [ 240.576151] [<ffffffffa0082e31>] usbhid_start+0x491/0x570 [usbhid]
Jan 30 09:04:36 beast kernel: [ 240.576162] [<ffffffffa008d274>] lg_probe+0x84/0x2c0 [hid_logitech]
Jan 30 09:04:36 beast kernel: [ 240.576170] [<ffffffff8103cbb9>] ? default_spin_lock_flags+0x9/0x10
Jan 30 09:04:36 beast kernel: [ 240.576184] [<ffffffffa004eba4>] hid_device_probe+0xb4/0x140 [hid]
Jan 30 09:04:36 beast kernel: [ 240.576190] [<ffffffff811ed043>] ? sysfs_create_link+0x13/0x20
Jan 30 09:04:36 beast kernel: [ 240.576199] [<ffffffff813f2f38>] really_probe+0x68/0x190
Jan 30 09:04:36 beast kernel: [ 240.576205] [<ffffffff813f31c5>] driver_probe_device+0x45/0x70
Jan 30 09:04:36 beast kernel: [ 240.576213] [<ffffffff813f329b>] __driver_attach+0xab/0xb0
Jan 30 09:04:36 beast kernel: [ 240.576217] [<ffffffff813f31f0>] ? driver_probe_device+0x70/0x70
Jan 30 09:04:36 beast kernel: [ 240.576222] [<ffffffff813f31f0>] ? driver_probe_device+0x70/0x70
Jan 30 09:04:36 beast kernel: [ 240.576229] [<ffffffff813f202c>] bus_for_each_dev+0x5c/0x90
Jan 30 09:04:36 beast kernel: [ 240.576237] [<ffffffff813f2cfe>] driver_attach+0x1e/0x20
Jan 30 09:04:36 beast kernel: [ 240.576244] [<ffffffff813f2950>] bus_add_driver+0x1a0/0x270
Jan 30 09:04:36 beast kernel: [ 240.576258] [<ffffffffa0095000>] ? 0xffffffffa0094fff
Jan 30 09:04:36 beast kernel: [ 240.576262] [<ffffffff813f3806>] driver_register+0x76/0x140
Jan 30 09:04:36 beast kernel: [ 240.576272] [<ffffffffa0095000>] ? 0xffffffffa0094fff
Jan 30 09:04:36 beast kernel: [ 240.576285] [<ffffffffa004fb53>] __hid_register_driver+0x53/0x90 [hid]
Jan 30 09:04:36 beast kernel: [ 240.576293] [<ffffffff810417e3>] ? set_memory_nx+0x43/0x50
Jan 30 09:04:36 beast kernel: [ 240.576306] [<ffffffffa009501e>] lg_init+0x1e/0x1000 [hid_logitech]
Jan 30 09:04:36 beast kernel: [ 240.576314] [<ffffffff81002040>] do_one_initcall+0x40/0x180
Jan 30 09:04:36 beast kernel: [ 240.576322] [<ffffffff810a782e>] sys_init_module+0xbe/0x230
Jan 30 09:04:36 beast kernel: [ 240.576328] [<ffffffff8165e002>] system_call_fastpath+0x16/0x1b

2 mins later:

Jan 30 09:06:36 beast kernel: [ 360.576038] INFO: task modprobe:370 blocked for more than 120 seconds.
Jan 30 09:06:36 beast kernel: [ 360.576044] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 30 09:06:36 beast kernel: [ 360.576049] modprobe D ffffffff81806240 0 370 153 0x00000004
Jan 30 09:06:36 beast kernel: [ 360.576057] ffff880121c3fb68 0000000000000086 ffff880121c3fb18 ffffffff81309787
Jan 30 09:06:36 beast kernel: [ 360.576064] ffff880121c3ffd8 ffff880121c3ffd8 ffff880121c3ffd8 0000000000013780
Jan 30 09:06:36 beast kernel: [ 360.576071] ffffffff81c0d020 ffff880125162e20 ffff880121c3fb78 ffff8801251b96c0
Jan 30 09:06:36 beast kernel: [ 360.576077] Call Trace:
Jan 30 09:06:36 beast kernel: [ 360.576089] [<ffffffff81309787>] ? kobject_put+0x27/0x60
Jan 30 09:06:36 beast kernel: [ 360.576097] [<ffffffff81653bbf>] schedule+0x3f/0x60
Jan 30 09:06:36 beast kernel: [ 360.576104] [<ffffffff81491ced>] usb_kill_urb.part.4+0x5d/0xa0
Jan 30 09:06:36 beast kernel: [ 360.576110] [<ffffffff81089e50>] ? add_wait_queue+0x60/0x60
Jan 30 09:06:36 beast kernel: [ 360.576115] [<ffffffff81491d61>] usb_kill_urb+0x31/0x40
Jan 30 09:06:36 beast kernel: [ 360.576139] [<ffffffffa0082941>] usbhid_init_reports+0xc1/0x120 [usbhid]
Jan 30 09:06:36 beast kernel: [ 360.576154] [<ffffffffa0082e31>] usbhid_start+0x491/0x570 [usbhid]
Jan 30 09:06:36 beast kernel: [ 360.576165] [<ffffffffa008d274>] lg_probe+0x84/0x2c0 [hid_logitech]
Jan 30 09:06:36 beast kernel: [ 360.576172] [<ffffffff8103cbb9>] ? default_spin_lock_flags+0x9/0x10
Jan 30 09:06:36 beast kernel: [ 360.576186] [<ffffffffa004eba4>] hid_device_probe+0xb4/0x140 [hid]
Jan 30 09:06:36 beast kernel: [ 360.576193] [<ffffffff811ed043>] ? sysfs_create_link+0x13/0x20
Jan 30 09:06:36 beast kernel: [ 360.576203] [<ffffffff813f2f38>] really_probe+0x68/0x190
Jan 30 09:06:36 beast kernel: [ 360.576209] [<ffffffff813f31c5>] driver_probe_device+0x45/0x70
Jan 30 09:06:36 beast kernel: [ 360.576219] [<ffffffff813f329b>] __driver_attach+0xab/0xb0
Jan 30 09:06:36 beast kernel: [ 360.576223] [<ffffffff813f31f0>] ? driver_probe_device+0x70/0x70
Jan 30 09:06:36 beast kernel: [ 360.576232] [<ffffffff813f31f0>] ? driver_probe_device+0x70/0x70
Jan 30 09:06:36 beast kernel: [ 360.576240] [<ffffffff813f202c>] bus_for_each_dev+0x5c/0x90
Jan 30 09:06:36 beast kernel: [ 360.576252] [<ffffffff813f2cfe>] driver_attach+0x1e/0x20
Jan 30 09:06:36 beast kernel: [ 360.576258] [<ffffffff813f2950>] bus_add_driver+0x1a0/0x270
Jan 30 09:06:36 beast kernel: [ 360.576272] [<ffffffffa0095000>] ? 0xffffffffa0094fff
Jan 30 09:06:36 beast kernel: [ 360.576276] [<ffffffff813f3806>] driver_register+0x76/0x140
Jan 30 09:06:36 beast kernel: [ 360.576285] [<ffffffffa0095000>] ? 0xffffffffa0094fff
Jan 30 09:06:36 beast kernel: [ 360.576300] [<ffffffffa004fb53>] __hid_register_driver+0x53/0x90 [hid]
Jan 30 09:06:36 beast kernel: [ 360.576305] [<ffffffff810417e3>] ? set_memory_nx+0x43/0x50
Jan 30 09:06:36 beast kernel: [ 360.576315] [<ffffffffa009501e>] lg_init+0x1e/0x1000 [hid_logitech]
Jan 30 09:06:36 beast kernel: [ 360.576321] [<ffffffff81002040>] do_one_initcall+0x40/0x180
Jan 30 09:06:36 beast kernel: [ 360.576329] [<ffffffff810a782e>] sys_init_module+0xbe/0x230
Jan 30 09:06:36 beast kernel: [ 360.576336] [<ffffffff8165e002>] system_call_fastpath+0x16/0x1b

The same sort of messages repeat every 2 minutes until I rebooted it.

cat /proc/version_signature:
Ubuntu 3.2.0-10.18-generic 3.2.1
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ed 2678 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe020000 irq 21'
   Mixer name : 'Nvidia MCP77/78 HDMI'
   Components : 'HDA:10ec0888,10438321,00100101 HDA:10de0002,10de0101,00100000'
   Controls : 45
   Simple ctrls : 24
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=73dd7b46-df18-4ae4-9a16-7e635959e1b1
IwConfig:
 lo no wireless extensions.

 virbr0 no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=
 LC_TIME=en_GB.utf8
 TERM=xterm
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=38c98076-521e-408e-af6a-2e8e00de0f05 ro
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic N/A
 linux-backports-modules-3.2.0-23-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
Tags: precise precise
Uname: Linux 3.2.0-23-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-01-16 (90 days ago)
UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare
dmi.bios.date: 05/28/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M3N72-D ACPI BIOS Revision 0202
dmi.board.name: M3N72-D
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N72-DACPIBIOSRevision0202:bd05/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N72-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

See original description
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 923666

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: precise
Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [precise] USB devices occasionally stop working

apport-collect is also segfaulting.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-12.20)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-12.20
Julian Edwards (julian-edwards)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: [precise] USB devices occasionally stop working

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.3-rc1 fixed the issue, the tag would be: 'kernel-fixed-upstream-v3.3-rc1'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. If you believe this bug does not require upstream testing, please add the tag: 'kernel-upstream-testing-not-needed'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc1-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Julian Edwards (julian-edwards)
tags: added: kernel-unable-to-test-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Brad Figg (brad-figg) wrote : Test with newer development kernel (3.2.0-15.24)

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-request-3.2.0-15.24
Julian Edwards (julian-edwards)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bot-stop-nagging
Revision history for this message
Herton R. Krzesinski (herton) wrote : Re: [precise] USB devices occasionally stop working

From the kernel stack trace, it seems the probe function of hid_logitech is stuck, and probably is what makes everything hid related later to freeze (mouse/keyboard).

Some questions:
- Do you still get the problem with latest Precise kernel? If yes can you paste the trace again with it?
- Are any of you usb devices a hid/logitech one? Please attach the output of "sudo lsusb -v", and please try to run again apport-collect 923666 to attach all the logs to the bug.
- In case latest Precise kernel still has the issue, if you remove/move or blacklist hid-logitech module, does the problem still happens?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 923666] Re: [precise] USB devices occasionally stop working

On Monday 27 Feb 2012 20:29:50 you wrote:
> >From the kernel stack trace, it seems the probe function of hid_logitech
>
> is stuck, and probably is what makes everything hid related later to
> freeze (mouse/keyboard).
>
> Some questions:
> - Do you still get the problem with latest Precise kernel? If yes can you
> paste the trace again with it? - Are any of you usb devices a hid/logitech
> one? Please attach the output of "sudo lsusb -v", and please try to run
> again apport-collect 923666 to attach all the logs to the bug. - In case
> latest Precise kernel still has the issue, if you remove/move or blacklist
> hid-logitech module, does the problem still happens?
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete

I'll do this in about a week's time - the PC with this problem is getting
shipped around the world at the moment. I'll post back here ASAP.

FWIW none of the USB devices are Logitech; it's a Microsoft keyboard and
mouse. Also, this has been happening for a long time (2 years or more) so I
remain sceptical that it's fixed in the latest kernel :)

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [precise] USB devices occasionally stop working

Yes, my keyboard is a Logitech one.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Sorry for saying it was a MS keyboard, I had a brain fart :(

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I haven't seen the problem with the latest kernel. That's not to say it's cured because the problem is extremely intermittent and I am yet to find a reliable way of re-creating it. I am guessing there's a race condition somewhere.

tags: added: apport-collected
description: updated
Revision history for this message
Julian Edwards (julian-edwards) wrote : AcpiTables.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : AlsaDevices.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : AplayDevices.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : ArecordDevices.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : BootDmesg.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : Card0.Amixer.values.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : Card0.Codecs.codec.0.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : Card0.Codecs.codec.3.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : Lspci.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : Lsusb.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : PciMultimedia.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : ProcModules.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : PulseList.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : UdevDb.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : UdevLog.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : WifiSyslog.txt

apport information

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [quantal] USB devices occasionally stop working

This had stopped with the precise kernel. However it is happening again with quantal's.

summary: - [precise] USB devices occasionally stop working
+ [quantal] USB devices occasionally stop working
Revision history for this message
Julian Edwards (julian-edwards) wrote :

This is still a problem in raring, and in fact has got worse. This happens about 70% of the time about 5 minutes after each boot.

summary: - [quantal] USB devices occasionally stop working
+ USB devices occasionally stop working
Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu):
importance: Medium → High
tags: added: kernel-key kernel-stable-key
removed: kernel-unable-to-test-upstream needs-upstream-testing
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Hi Julian,

Would it be possible for you to test a couple of kernels. The first test would be the latest 3.2 stable kernel[0], to ensure the bug still doesn't exist there. The second test would be with the latest 3.10 kernel[1] to see if this is fixed in the mainline kernel.

If the bug is still fixed in the latest 3.2 kernel, I can perform a kernel bisect to identify the commit that introduced this bug in Quantal and Raring. If the bug is fixed in the latest 3.10 mainline kernel, I can perform a "Reverse" bisect to identify the commit that fixes it. If the bug still exists in 3.10, we can work with upstream to have this issue looked at, in parallel with me performing a bisect against 3.2 stable.

Thanks in advance!

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.44-precise/
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc1-saucy/

Joseph Salisbury (jsalisbury)
Changed in linux (Ubuntu Quantal):
importance: Undecided → High
Changed in linux (Ubuntu Raring):
importance: Undecided → High
Changed in linux (Ubuntu Quantal):
status: New → Incomplete
Changed in linux (Ubuntu Raring):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Also, testing the 3.10 kernel will help identify if this bug will also exist in Saucy.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Ok I'll give 3.10 a go. I am not sure when this bug was introduced as I've had it as long as I can remember, so bisecting might not be useful.

Also, in raring there's no mention of any USB errors in syslog. The device just suddenly stops working. Interestingly, it is always the mouse first (but the keyboard will usually follow some time later). Unplugging and replugging the mouse does not work, there has to be a reboot.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Ok I can't use 3.10 as the nvidia module won't compile. I will attach its build log, I hope you can suggest a work around.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

/var/lib/dkms/nvidia-304/304.88/build/make.log

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for attempting to test 3.10-rc1. It might be difficult to debug the Nvidia compile error without the source. An alternative might be to use the Nouveau driver.

However, it's probably better to confirm that the bug still does not happen in the 3.2 kernel. Did you have a chance to test the 3.2.44[0] kernel?

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.44-precise/

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 923666] Re: USB devices occasionally stop working

On 15/05/13 02:37, Joseph Salisbury wrote:
> However, it's probably better to confirm that the bug still does not
> happen in the 3.2 kernel. Did you have a chance to test the 3.2.44[0]
> kernel?

I am using it right now. The bug has not occurred yet after 42 minutes
of uptime, but I'll keep an eye on it as it could still fail.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

The 3.2.44 kernel has not caused the problem in 2 days of running with it. Today I am back on the default raring kernel to see if it re-occurs. So far it has not :/

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Hi Julian,

Have you seen this issue happen again since you started using the Raring kernel again?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On 22/05/13 01:36, Joseph Salisbury wrote:
> Hi Julian,
>
> Have you seen this issue happen again since you started using the Raring
> kernel again?
>

Hi

Yes, it happened twice yesterday but oddly only after ~6 hours usage. I
am back on the precise kernel today to see if it happens again, but it
certainly looks so far like precise does not have the bug.

Cheers.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Still not seeing the bug in the precise kernel, but when booting to the current raring one it happens sooner or later.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Can you test the latest 3.8 stable kernel, which is 3.8.13:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13-raring/

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On 31/05/13 02:49, Joseph Salisbury wrote:
> Can you test the latest 3.8 stable kernel, which is 3.8.13:
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.13-raring/
>

I'm testing it now, let's see how it goes ...

Revision history for this message
Julian Edwards (julian-edwards) wrote :

3.8.13-030813-generic seems to have been pretty stable! At least so far ...

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

The upstream 3.8.13 updates have been applied to the Ubuntu 3.8.0-24.35 kernel. The Ubuntu 3.8.0-25.37 kernel is now available in the updates repository. Can you apply the latest updates and see if this bug is resolved?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On 18/06/13 01:55, Joseph Salisbury wrote:
> The upstream 3.8.13 updates have been applied to the Ubuntu 3.8.0-24.35
> kernel. The Ubuntu 3.8.0-25.37 kernel is now available in the updates
> repository. Can you apply the latest updates and see if this bug is
> resolved?
>

I *think* it's resolved with
Linux beast 3.8.0-25-generic #37-Ubuntu SMP Thu Jun 6 20:47:07 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

At least I've not seen the problem since using it for the last few days.

\o/

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Thanks for the update, Julian. I'll mark Raring as Fix Released for now. If you see the bug again, just change the status back to confirmed and we can investigate further.

At some point, it would also be great if you could test the latest Quantal kernel to see if it also resolves the bug.

Thanks again

Changed in linux (Ubuntu Raring):
status: Incomplete → Fix Released
tags: added: kernel-da-key
removed: kernel-key
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Thanks a bunch for helping with this. Life without frequent reboots is
much nicer.

Revision history for this message
penalvch (penalvch) wrote :

As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/923666/comments/48 .

tags: added: bios-outdated-1510 needs-upstream-testing
removed: kernel-request-3.2.0-12.20 kernel-request-3.2.0-15.24
Changed in linux (Ubuntu Quantal):
status: Incomplete → Invalid
Changed in linux (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.