[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D
Made it a valid patch file (for Debian stable): amd64:/usr/src/linux-3.16.35# cd /usr/src/linux-3.16.35 amd64:/usr/src/linux-3.16.35# patch -p1 --dry-run https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557172/+attachment/4673143/+files/hid-core.c-3.16-to-4.5.diff ** Patch added: "Difference between Debian 3.16 and 4.5 hid-core.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557172/+attachment/4673144/+files/hid-core.c-3.16-to-4.5.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557172 Title: khubd/usbhid deadlock(?) creates processes in state D Status in linux package in Ubuntu: Incomplete Bug description: (Note that the attached logs are not a machine exhibiting the issue) I've observed this issue specifically on Dell's PowerEdge R410 with its DRAC. I manage quite a few other machines with DRACs and haven't seen this issue so it may be limited to the R410. I've seen cases of this both with the precise and trusty kernel. Basically, what happens is that things that read any info about the DRAC's usbhid device will block in an uninterruptible state. A quick way to do this is with "cat /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This means that commands like lspci will block as well. The thing is that it doesn't happen every time, but once it happens the first time all future reads on the device will block in state D too. This is also associated with the following from the kernel (first from a precise machine): [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197857.716899] usb 5-2: device descriptor read/64, error -71 [197857.944966] usb 5-2: device descriptor read/64, error -71 [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197858.285090] usb 5-2: device descriptor read/64, error -71 [197858.513108] usb 5-2: device descriptor read/64, error -71 [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.145214] usb 5-2: device not accepting address 2, error -71 [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.669322] usb 5-2: device not accepting address 2, error -71 [197859.675357] usb 5-2: USB disconnect, device number 2 [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds. [198047.537147] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.551792] khubd D 880803fe18a0 0 203 2 0x [198047.551803] 8810036b1c18 0046 88102fc53180 8810036b1fd8 [198047.551809] 00013180 00013180 881003f7c800 880804634800 [198047.551814] 8810036b1c38 8810020908e8 8810020908ec [198047.551819] Call Trace: [198047.551828] [] schedule+0x29/0x70 [198047.551833] [] schedule_preempt_disabled+0xe/0x10 [198047.551837] [] __mutex_lock_slowpath+0x114/0x1b0 [198047.551845] [] ? usb_alloc_urb+0x1e/0x50 [198047.551848] [] mutex_lock+0x23/0x37 [198047.551852] [] usb_disconnect+0x5a/0x210 [198047.551857] [] ? usb_control_msg+0xea/0x110 [198047.551860] [] hub_port_connect_change+0xcf/0x9c0 [198047.551864] [] ? hub_port_status+0xd5/0x120 [198047.551868] [] hub_events+0x464/0x8c0 [198047.551871] [] ? __schedule+0x38e/0x700 [198047.551875] [] hub_thread+0x35/0x150 [198047.551881] [] ? __wake_up_sync+0x20/0x20 [198047.551885] [] ? hub_events+0x8c0/0x8c0 [198047.551890] [] kthread+0xc9/0xe0 [198047.551893] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551898] [] ret_from_fork+0x58/0x90 [198047.551902] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds. [198047.558892] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.573524] kworker/9:1 D 880803fe18a0 0 246 2 0x [198047.573547] Workqueue: events hid_reset [usbhid] [198047.573550] 8808011f9788 0046 88080fc93180 8808011f9fd8 [198047.573555] 00013180 00013180 881003f94800 8808011f [198047.573559] 8808011f9798 8808011f98d8 7fff 7fff [198047.573564] Call Trace: [198047.573579] [] schedule+0x29/0x70 [198047.573582] [] schedule_timeout+0x1e5/0x250 [198047.573587] [] ? wake_affine+0x16d/0x2d0 [198047.573591] [] wait_for_completion+0xa7/0x160 [198047.573596] [] ? try_to_wake_up+0x210/0x210 [198047.573602] [] flush_work+0x29/0x40 [198047.573605] [] ? start_worker+0x40/0x40 [198047.573609] [] __cancel_work_timer+0x9c/0x1b0 [198047.573623] []
[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D
I'm running Debian stable with the 4.5 kernel for 8 days without restart, now. First I did some 5 suspend/resumes without any error. Then I used it as my desktop machine, doing at least one suspend/resume every day. I'm convinced the issue I had is fixed in the 4.5 kernel. Attached the difference between the Debian 3.16 and 4.5 hid-core.c (hid-core.c-3.16-to-4.5.diff). It's quite a bit more than a one-line fix. ** Patch added: "Difference between Debian 3.16 and 4.5 hid-core.c" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557172/+attachment/4673143/+files/hid-core.c-3.16-to-4.5.diff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557172 Title: khubd/usbhid deadlock(?) creates processes in state D Status in linux package in Ubuntu: Incomplete Bug description: (Note that the attached logs are not a machine exhibiting the issue) I've observed this issue specifically on Dell's PowerEdge R410 with its DRAC. I manage quite a few other machines with DRACs and haven't seen this issue so it may be limited to the R410. I've seen cases of this both with the precise and trusty kernel. Basically, what happens is that things that read any info about the DRAC's usbhid device will block in an uninterruptible state. A quick way to do this is with "cat /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This means that commands like lspci will block as well. The thing is that it doesn't happen every time, but once it happens the first time all future reads on the device will block in state D too. This is also associated with the following from the kernel (first from a precise machine): [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197857.716899] usb 5-2: device descriptor read/64, error -71 [197857.944966] usb 5-2: device descriptor read/64, error -71 [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197858.285090] usb 5-2: device descriptor read/64, error -71 [197858.513108] usb 5-2: device descriptor read/64, error -71 [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.145214] usb 5-2: device not accepting address 2, error -71 [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.669322] usb 5-2: device not accepting address 2, error -71 [197859.675357] usb 5-2: USB disconnect, device number 2 [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds. [198047.537147] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.551792] khubd D 880803fe18a0 0 203 2 0x [198047.551803] 8810036b1c18 0046 88102fc53180 8810036b1fd8 [198047.551809] 00013180 00013180 881003f7c800 880804634800 [198047.551814] 8810036b1c38 8810020908e8 8810020908ec [198047.551819] Call Trace: [198047.551828] [] schedule+0x29/0x70 [198047.551833] [] schedule_preempt_disabled+0xe/0x10 [198047.551837] [] __mutex_lock_slowpath+0x114/0x1b0 [198047.551845] [] ? usb_alloc_urb+0x1e/0x50 [198047.551848] [] mutex_lock+0x23/0x37 [198047.551852] [] usb_disconnect+0x5a/0x210 [198047.551857] [] ? usb_control_msg+0xea/0x110 [198047.551860] [] hub_port_connect_change+0xcf/0x9c0 [198047.551864] [] ? hub_port_status+0xd5/0x120 [198047.551868] [] hub_events+0x464/0x8c0 [198047.551871] [] ? __schedule+0x38e/0x700 [198047.551875] [] hub_thread+0x35/0x150 [198047.551881] [] ? __wake_up_sync+0x20/0x20 [198047.551885] [] ? hub_events+0x8c0/0x8c0 [198047.551890] [] kthread+0xc9/0xe0 [198047.551893] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551898] [] ret_from_fork+0x58/0x90 [198047.551902] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds. [198047.558892] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.573524] kworker/9:1 D 880803fe18a0 0 246 2 0x [198047.573547] Workqueue: events hid_reset [usbhid] [198047.573550] 8808011f9788 0046 88080fc93180 8808011f9fd8 [198047.573555] 00013180 00013180 881003f94800 8808011f [198047.573559] 8808011f9798 8808011f98d8 7fff 7fff [198047.573564] Call Trace: [198047.573579] [] schedule+0x29/0x70 [198047.573582] [] schedule_timeout+0x1e5/0x250 [198047.573587] [] ? wake_affine+0x16d/0x2d0 [198047.573591] [] wait_for_completion+0xa7/0x160 [198047.573596] [] ? try_to_wake_up+0x210/0x210 [198047.573602] []
[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D
Maybe this patch "HID: usbhid: fix recursive deadlock" fixes the Ubuntu problem: https://lists.ubuntu.com/archives/kernel- team/2016-February/071250.html But that fix is in my Debian kernel: https://tracker.debian.org/media/packages/l/linux/changelog-3.16.7-ckt25-2 Maybe it did not fix all or it enabled another path to the same dead- lock. On my machine I got the same dead-lock after a few suspends or hibernates. I'm running the Debian/testing kernel (4.5.4-1) now: linux-image-4.5.0-2-amd64 With the 3.16 kernel it happened quite often, every 3 to 5 suspends or hibernates. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557172 Title: khubd/usbhid deadlock(?) creates processes in state D Status in linux package in Ubuntu: Incomplete Bug description: (Note that the attached logs are not a machine exhibiting the issue) I've observed this issue specifically on Dell's PowerEdge R410 with its DRAC. I manage quite a few other machines with DRACs and haven't seen this issue so it may be limited to the R410. I've seen cases of this both with the precise and trusty kernel. Basically, what happens is that things that read any info about the DRAC's usbhid device will block in an uninterruptible state. A quick way to do this is with "cat /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This means that commands like lspci will block as well. The thing is that it doesn't happen every time, but once it happens the first time all future reads on the device will block in state D too. This is also associated with the following from the kernel (first from a precise machine): [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197857.716899] usb 5-2: device descriptor read/64, error -71 [197857.944966] usb 5-2: device descriptor read/64, error -71 [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197858.285090] usb 5-2: device descriptor read/64, error -71 [197858.513108] usb 5-2: device descriptor read/64, error -71 [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.145214] usb 5-2: device not accepting address 2, error -71 [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.669322] usb 5-2: device not accepting address 2, error -71 [197859.675357] usb 5-2: USB disconnect, device number 2 [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds. [198047.537147] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.551792] khubd D 880803fe18a0 0 203 2 0x [198047.551803] 8810036b1c18 0046 88102fc53180 8810036b1fd8 [198047.551809] 00013180 00013180 881003f7c800 880804634800 [198047.551814] 8810036b1c38 8810020908e8 8810020908ec [198047.551819] Call Trace: [198047.551828] [] schedule+0x29/0x70 [198047.551833] [] schedule_preempt_disabled+0xe/0x10 [198047.551837] [] __mutex_lock_slowpath+0x114/0x1b0 [198047.551845] [] ? usb_alloc_urb+0x1e/0x50 [198047.551848] [] mutex_lock+0x23/0x37 [198047.551852] [] usb_disconnect+0x5a/0x210 [198047.551857] [] ? usb_control_msg+0xea/0x110 [198047.551860] [] hub_port_connect_change+0xcf/0x9c0 [198047.551864] [] ? hub_port_status+0xd5/0x120 [198047.551868] [] hub_events+0x464/0x8c0 [198047.551871] [] ? __schedule+0x38e/0x700 [198047.551875] [] hub_thread+0x35/0x150 [198047.551881] [] ? __wake_up_sync+0x20/0x20 [198047.551885] [] ? hub_events+0x8c0/0x8c0 [198047.551890] [] kthread+0xc9/0xe0 [198047.551893] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551898] [] ret_from_fork+0x58/0x90 [198047.551902] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds. [198047.558892] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.573524] kworker/9:1 D 880803fe18a0 0 246 2 0x [198047.573547] Workqueue: events hid_reset [usbhid] [198047.573550] 8808011f9788 0046 88080fc93180 8808011f9fd8 [198047.573555] 00013180 00013180 881003f94800 8808011f [198047.573559] 8808011f9798 8808011f98d8 7fff 7fff [198047.573564] Call Trace: [198047.573579] [] schedule+0x29/0x70 [198047.573582] [] schedule_timeout+0x1e5/0x250 [198047.573587] [] ? wake_affine+0x16d/0x2d0 [198047.573591] [] wait_for_completion+0xa7/0x160 [198047.573596] [] ? try_to_wake_up+0x210/0x210 [198047.573602] [] flush_work+0x29/0x40
[Kernel-packages] [Bug 1557172] Re: khubd/usbhid deadlock(?) creates processes in state D
For a few weeks I have the same bug in Debian/stable: linux-image-3.16.0-4-amd64 That kernel image is from 9th March. I upgraded on April 4. dpkg log says 3.16.7-ckt20-1+deb8u4 3.16.7-ckt25-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1557172 Title: khubd/usbhid deadlock(?) creates processes in state D Status in linux package in Ubuntu: Incomplete Bug description: (Note that the attached logs are not a machine exhibiting the issue) I've observed this issue specifically on Dell's PowerEdge R410 with its DRAC. I manage quite a few other machines with DRACs and haven't seen this issue so it may be limited to the R410. I've seen cases of this both with the precise and trusty kernel. Basically, what happens is that things that read any info about the DRAC's usbhid device will block in an uninterruptible state. A quick way to do this is with "cat /sys/devices/pci:00/:00:1d.0/usb5/5-2/manufacturer". This means that commands like lspci will block as well. The thing is that it doesn't happen every time, but once it happens the first time all future reads on the device will block in state D too. This is also associated with the following from the kernel (first from a precise machine): [197852.595820] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197857.716899] usb 5-2: device descriptor read/64, error -71 [197857.944966] usb 5-2: device descriptor read/64, error -71 [197858.165020] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197858.285090] usb 5-2: device descriptor read/64, error -71 [197858.513108] usb 5-2: device descriptor read/64, error -71 [197858.733154] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.145214] usb 5-2: device not accepting address 2, error -71 [197859.261234] usb 5-2: reset full-speed USB device number 2 using uhci_hcd [197859.669322] usb 5-2: device not accepting address 2, error -71 [197859.675357] usb 5-2: USB disconnect, device number 2 [198047.530714] INFO: task khubd:203 blocked for more than 120 seconds. [198047.537147] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.543691] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.551792] khubd D 880803fe18a0 0 203 2 0x [198047.551803] 8810036b1c18 0046 88102fc53180 8810036b1fd8 [198047.551809] 00013180 00013180 881003f7c800 880804634800 [198047.551814] 8810036b1c38 8810020908e8 8810020908ec [198047.551819] Call Trace: [198047.551828] [] schedule+0x29/0x70 [198047.551833] [] schedule_preempt_disabled+0xe/0x10 [198047.551837] [] __mutex_lock_slowpath+0x114/0x1b0 [198047.551845] [] ? usb_alloc_urb+0x1e/0x50 [198047.551848] [] mutex_lock+0x23/0x37 [198047.551852] [] usb_disconnect+0x5a/0x210 [198047.551857] [] ? usb_control_msg+0xea/0x110 [198047.551860] [] hub_port_connect_change+0xcf/0x9c0 [198047.551864] [] ? hub_port_status+0xd5/0x120 [198047.551868] [] hub_events+0x464/0x8c0 [198047.551871] [] ? __schedule+0x38e/0x700 [198047.551875] [] hub_thread+0x35/0x150 [198047.551881] [] ? __wake_up_sync+0x20/0x20 [198047.551885] [] ? hub_events+0x8c0/0x8c0 [198047.551890] [] kthread+0xc9/0xe0 [198047.551893] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551898] [] ret_from_fork+0x58/0x90 [198047.551902] [] ? flush_kthread_worker+0xb0/0xb0 [198047.551908] INFO: task kworker/9:1:246 blocked for more than 120 seconds. [198047.558892] Not tainted 3.13.0-74-generic #118~precise1-Ubuntu [198047.565491] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [198047.573524] kworker/9:1 D 880803fe18a0 0 246 2 0x [198047.573547] Workqueue: events hid_reset [usbhid] [198047.573550] 8808011f9788 0046 88080fc93180 8808011f9fd8 [198047.573555] 00013180 00013180 881003f94800 8808011f [198047.573559] 8808011f9798 8808011f98d8 7fff 7fff [198047.573564] Call Trace: [198047.573579] [] schedule+0x29/0x70 [198047.573582] [] schedule_timeout+0x1e5/0x250 [198047.573587] [] ? wake_affine+0x16d/0x2d0 [198047.573591] [] wait_for_completion+0xa7/0x160 [198047.573596] [] ? try_to_wake_up+0x210/0x210 [198047.573602] [] flush_work+0x29/0x40 [198047.573605] [] ? start_worker+0x40/0x40 [198047.573609] [] __cancel_work_timer+0x9c/0x1b0 [198047.573623] [] cancel_work_sync+0x10/0x20 [198047.573632] [] hid_cancel_delayed_stuff+0x29/0x30 [usbhid] [198047.573640] [] usbhid_close+0xcc/0x110 [usbhid] [198047.573650] [] hidinput_close+0x22/0x30 [hid] [198047.573659] [] input_close_device+0x61/0x90 [198047.573663] []
