Skip to contentSkip to conversation

New: usb subsystems hang

Bug 206779 [email protected] 2 participants 4 messages Mar 7, 2020 – Mar 12, 2020 USB

lore
Share & tools
lore

[email protected]

author
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=206779

            Bug ID: 206779
           Summary: usb subsystems hang
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.5.7
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Hi,

I observed issue with this version with one usb device.

My setup is:

Ubuntu 19.10 clean install
Kernel 5.5.7 vanilla, 5.5.7-vanilla

My issue is:

[  726.043665] INFO: task fastboot:1531 blocked for more than 120 seconds.
[  726.043716]       Not tainted 5.5.7-vanilla #1
[  726.043734] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  726.043753] fastboot        D    0  1531   1413 0x00000004
[  726.043755] Call Trace:
[  726.043778]  __schedule+0x28c/0x6e0
[  726.043779]  schedule+0x44/0xb0
[  726.043780]  schedule_timeout+0x1d3/0x2f0
[  726.043783]  ? ttwu_do_activate+0x5a/0x70
[  726.043784]  wait_for_completion_timeout+0xb3/0x140
[  726.043785]  ? wake_up_q+0xb0/0xb0
[  726.043787]  usb_start_wait_urb+0x8c/0x180
[  726.043788]  usb_bulk_msg+0xb8/0x160
[  726.043790]  proc_bulk+0x158/0x3a0
[  726.043791]  usbdev_ioctl+0xc08/0x1480
[  726.043794]  do_vfs_ioctl+0xa5/0x680
[  726.043796]  ? finish_task_switch+0x70/0x260
[  726.043798]  ? tomoyo_file_ioctl+0x19/0x20
[  726.043799]  ksys_ioctl+0x75/0x80
[  726.043801]  __x64_sys_ioctl+0x1a/0x20
[  726.043803]  do_syscall_64+0x57/0x1c0
[  726.043804]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  726.043810] RIP: 0033:0x7f1da431867b
[  726.043815] Code: Bad RIP value.
[  726.043816] RSP: 002b:00007ffdb4c22af8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[  726.043817] RAX: ffffffffffffffda RBX: 000055b82cb5c2a0 RCX:
00007f1da431867b
[  726.043818] RDX: 00007ffdb4c22b00 RSI: 00000000c0185502 RDI:
0000000000000004
[  726.043818] RBP: 0000000000000040 R08: 00000000000001ec R09:
00007ffdb4c22b40
[  726.043819] R10: 00007ffdb4c22b00 R11: 0000000000000246 R12:
0000000000000040
[  726.043819] R13: 00000006fc23abff R14: 0000000000000000 R15:
00007ffdb4c22c70
[  774.124057] usb 1-2: USB disconnect, device number 4

I had to restart the car so I could continue the process. My task is: writing a phone with adb and fastboot.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
author
#1 lore raw

[Bug 206779] usb subsystems hang

https://bugzilla.kernel.org/show_bug.cgi?id=206779

--- Comment #1 from sander44 ([email protected]) --- (In reply to sander44 from comment #0)

Quoted 51 lines

Hi,

I observed issue with this version with one usb device.

My setup is:

Ubuntu 19.10 clean install
Kernel 5.5.7 vanilla, 5.5.7-vanilla

My issue is:

[  726.043665] INFO: task fastboot:1531 blocked for more than 120 seconds.
[  726.043716]       Not tainted 5.5.7-vanilla #1
[  726.043734] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[  726.043753] fastboot        D    0  1531   1413 0x00000004
[  726.043755] Call Trace:
[  726.043778]  __schedule+0x28c/0x6e0
[  726.043779]  schedule+0x44/0xb0
[  726.043780]  schedule_timeout+0x1d3/0x2f0
[  726.043783]  ? ttwu_do_activate+0x5a/0x70
[  726.043784]  wait_for_completion_timeout+0xb3/0x140
[  726.043785]  ? wake_up_q+0xb0/0xb0
[  726.043787]  usb_start_wait_urb+0x8c/0x180
[  726.043788]  usb_bulk_msg+0xb8/0x160
[  726.043790]  proc_bulk+0x158/0x3a0
[  726.043791]  usbdev_ioctl+0xc08/0x1480
[  726.043794]  do_vfs_ioctl+0xa5/0x680
[  726.043796]  ? finish_task_switch+0x70/0x260
[  726.043798]  ? tomoyo_file_ioctl+0x19/0x20
[  726.043799]  ksys_ioctl+0x75/0x80
[  726.043801]  __x64_sys_ioctl+0x1a/0x20
[  726.043803]  do_syscall_64+0x57/0x1c0
[  726.043804]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  726.043810] RIP: 0033:0x7f1da431867b
[  726.043815] Code: Bad RIP value.
[  726.043816] RSP: 002b:00007ffdb4c22af8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[  726.043817] RAX: ffffffffffffffda RBX: 000055b82cb5c2a0 RCX:
00007f1da431867b
[  726.043818] RDX: 00007ffdb4c22b00 RSI: 00000000c0185502 RDI:
0000000000000004
[  726.043818] RBP: 0000000000000040 R08: 00000000000001ec R09:
00007ffdb4c22b40
[  726.043819] R10: 00007ffdb4c22b00 R11: 0000000000000246 R12:
0000000000000040
[  726.043819] R13: 00000006fc23abff R14: 0000000000000000 R15:
00007ffdb4c22c70
[  774.124057] usb 1-2: USB disconnect, device number 4

I had to restart the machine - vm so I could continue the process. My task is: writing a phone with adb and fastboot.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.
#2 lore raw

Re: [Bug 206779] usb subsystems hang

Quoted 56 lines · On 20-03-07 16:21:37, [email protected] wrote:

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D206779&data=02%7C01%7Cpeter.chen%40nxp.com%7C6362fa93c31249cccc1408d7c2b39d9a%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637191949021070621&sdata=td13UwZNZb0wRL9WjLJXP%2FUHoxSxVut7Xq11JJ1iozM%3D&reserved=0

--- Comment #1 from sander44 ([email protected]) --- (In reply to sander44 from comment #0)

Quoted 51 lines

Hi,

I observed issue with this version with one usb device.

My setup is:

Ubuntu 19.10 clean install
Kernel 5.5.7 vanilla, 5.5.7-vanilla

My issue is:

[  726.043665] INFO: task fastboot:1531 blocked for more than 120 seconds.
[  726.043716]       Not tainted 5.5.7-vanilla #1
[  726.043734] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[  726.043753] fastboot        D    0  1531   1413 0x00000004
[  726.043755] Call Trace:
[  726.043778]  __schedule+0x28c/0x6e0
[  726.043779]  schedule+0x44/0xb0
[  726.043780]  schedule_timeout+0x1d3/0x2f0
[  726.043783]  ? ttwu_do_activate+0x5a/0x70
[  726.043784]  wait_for_completion_timeout+0xb3/0x140
[  726.043785]  ? wake_up_q+0xb0/0xb0
[  726.043787]  usb_start_wait_urb+0x8c/0x180
[  726.043788]  usb_bulk_msg+0xb8/0x160
[  726.043790]  proc_bulk+0x158/0x3a0
[  726.043791]  usbdev_ioctl+0xc08/0x1480
[  726.043794]  do_vfs_ioctl+0xa5/0x680
[  726.043796]  ? finish_task_switch+0x70/0x260
[  726.043798]  ? tomoyo_file_ioctl+0x19/0x20
[  726.043799]  ksys_ioctl+0x75/0x80
[  726.043801]  __x64_sys_ioctl+0x1a/0x20
[  726.043803]  do_syscall_64+0x57/0x1c0
[  726.043804]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  726.043810] RIP: 0033:0x7f1da431867b
[  726.043815] Code: Bad RIP value.
[  726.043816] RSP: 002b:00007ffdb4c22af8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[  726.043817] RAX: ffffffffffffffda RBX: 000055b82cb5c2a0 RCX:
00007f1da431867b
[  726.043818] RDX: 00007ffdb4c22b00 RSI: 00000000c0185502 RDI:
0000000000000004
[  726.043818] RBP: 0000000000000040 R08: 00000000000001ec R09:
00007ffdb4c22b40
[  726.043819] R10: 00007ffdb4c22b00 R11: 0000000000000246 R12:
0000000000000040
[  726.043819] R13: 00000006fc23abff R14: 0000000000000000 R15:
00007ffdb4c22c70
[  774.124057] usb 1-2: USB disconnect, device number 4

I had to restart the machine - vm so I could continue the process. My task is: writing a phone with adb and fastboot.

The kernel is waiting the transfer has finished, but timeout value from the user app is unlimited (maybe 0). Try to add timeout value for this transfer to avoid process hang.

Signature · 2 lines
Thanks,
Peter Chen
author
#3 lore raw

[Bug 206779] usb subsystems hang

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=206779

--- Comment #2 from [email protected] ---

Quoted 57 lines · On 20-03-07 16:21:37, [email protected] wrote:

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D206779&data=02%7C01%7Cpeter.chen%40nxp.com%7C6362fa93c31249cccc1408d7c2b39d9a%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637191949021070621&sdata=td13UwZNZb0wRL9WjLJXP%2FUHoxSxVut7Xq11JJ1iozM%3D&reserved=0

--- Comment #1 from sander44 ([email protected]) --- (In reply to sander44 from comment #0)

Quoted 51 lines

Hi,

I observed issue with this version with one usb device.

My setup is:

Ubuntu 19.10 clean install
Kernel 5.5.7 vanilla, 5.5.7-vanilla

My issue is:

[  726.043665] INFO: task fastboot:1531 blocked for more than 120 seconds.
[  726.043716]       Not tainted 5.5.7-vanilla #1
[  726.043734] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[  726.043753] fastboot        D    0  1531   1413 0x00000004
[  726.043755] Call Trace:
[  726.043778]  __schedule+0x28c/0x6e0
[  726.043779]  schedule+0x44/0xb0
[  726.043780]  schedule_timeout+0x1d3/0x2f0
[  726.043783]  ? ttwu_do_activate+0x5a/0x70
[  726.043784]  wait_for_completion_timeout+0xb3/0x140
[  726.043785]  ? wake_up_q+0xb0/0xb0
[  726.043787]  usb_start_wait_urb+0x8c/0x180
[  726.043788]  usb_bulk_msg+0xb8/0x160
[  726.043790]  proc_bulk+0x158/0x3a0
[  726.043791]  usbdev_ioctl+0xc08/0x1480
[  726.043794]  do_vfs_ioctl+0xa5/0x680
[  726.043796]  ? finish_task_switch+0x70/0x260
[  726.043798]  ? tomoyo_file_ioctl+0x19/0x20
[  726.043799]  ksys_ioctl+0x75/0x80
[  726.043801]  __x64_sys_ioctl+0x1a/0x20
[  726.043803]  do_syscall_64+0x57/0x1c0
[  726.043804]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  726.043810] RIP: 0033:0x7f1da431867b
[  726.043815] Code: Bad RIP value.
[  726.043816] RSP: 002b:00007ffdb4c22af8 EFLAGS: 00000246 ORIG_RAX:
0000000000000010
[  726.043817] RAX: ffffffffffffffda RBX: 000055b82cb5c2a0 RCX:
00007f1da431867b
[  726.043818] RDX: 00007ffdb4c22b00 RSI: 00000000c0185502 RDI:
0000000000000004
[  726.043818] RBP: 0000000000000040 R08: 00000000000001ec R09:
00007ffdb4c22b40
[  726.043819] R10: 00007ffdb4c22b00 R11: 0000000000000246 R12:
0000000000000040
[  726.043819] R13: 00000006fc23abff R14: 0000000000000000 R15:
00007ffdb4c22c70
[  774.124057] usb 1-2: USB disconnect, device number 4

I had to restart the machine - vm so I could continue the process. My task is: writing a phone with adb and fastboot.

The kernel is waiting the transfer has finished, but timeout value from the user app is unlimited (maybe 0). Try to add timeout value for this transfer to avoid process hang.

Signature · 2 lines
You are receiving this mail because:
You are watching the assignee of the bug.