linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207887] New: USB devices connected to Thinkpad Dock hangs after a while
Date: Mon, 25 May 2020 16:28:29 +0000	[thread overview]
Message-ID: <bug-207887-208809@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 207887
           Summary: USB devices connected to Thinkpad Dock hangs after a
                    while
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.0.0 -> master
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: mail@3v1n0.net
        Regression: No

Created attachment 289275
  --> https://bugzilla.kernel.org/attachment.cgi?id=289275&action=edit
DMesg of the hang with kernel-5.4.26-050426

Since I've moved from kernel 4.15 to kernel 5, the USB hub managed of my
Thinkpad Dock doesn't seem to work well after some usage (unfortunately is
quite hard to find a reproducer, as it "just happens", normally while writing).

This seems to be mostly triggered by the usage of an USB keyboard, as when the
USB traffic is limited to other devices, it doesn't seem to happen.

[  +0,136020] Freezing of tasks failed after 20.006 seconds (2 tasks refusing
to freeze, wq_busy=0):
[  +0,000387] device poll     D    0 22575   4818 0x00000004
[  +0,000006] Call Trace:
[  +0,000014]  __schedule+0x2e3/0x740
[  +0,000005]  ? __switch_to_asm+0x40/0x70
[  +0,000003]  ? __switch_to_asm+0x34/0x70
[  +0,000006]  schedule+0x42/0xb0
[  +0,000005]  schedule_preempt_disabled+0xe/0x10
[  +0,000005]  __mutex_lock.isra.0+0x182/0x4f0
[  +0,000008]  ? device_match_of_node+0x20/0x20
[  +0,000005]  __mutex_lock_slowpath+0x13/0x20
[  +0,000005]  mutex_lock+0x2e/0x40
[  +0,000007]  usbdev_open+0xd9/0x240
[  +0,000007]  chrdev_open+0xd3/0x1c0
[  +0,000006]  ? cdev_default_release+0x20/0x20
[  +0,000006]  do_dentry_open+0x143/0x3a0
[  +0,000006]  vfs_open+0x2d/0x30
[  +0,000005]  do_last+0x194/0x900
[  +0,000006]  path_openat+0x8d/0x290
[  +0,000006]  do_filp_open+0x91/0x100
[  +0,000006]  ? __alloc_fd+0x46/0x150
[  +0,000006]  do_sys_open+0x17f/0x230
[  +0,000007]  __x64_sys_openat+0x20/0x30
[  +0,000006]  do_syscall_64+0x57/0x190
[  +0,000004]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  +0,000005] RIP: 0033:0x7f9942175d19
[  +0,000010] Code: Bad RIP value.
[  +0,000003] RSP: 002b:00007f9940d2dab0 EFLAGS: 00000293 ORIG_RAX:
0000000000000101
[  +0,000005] RAX: ffffffffffffffda RBX: 00007f9930000bab RCX: 00007f9942175d19
[  +0,000002] RDX: 0000000000080000 RSI: 00007f9930010bf0 RDI: 00000000ffffff9c
[  +0,000002] RBP: 0000000000080000 R08: 0000000000000000 R09: 0000000000000000
[  +0,000002] R10: 0000000000000000 R11: 0000000000000293 R12: 00007f9930010bf0
[  +0,000002] R13: 00007f9930010bf0 R14: 00007f9930000b20 R15: 000055ed68c60c60
[  +0,000094] colord-sane     D    0  4630   3097 0x00000004
[  +0,000005] Call Trace:
[  +0,000006]  __schedule+0x2e3/0x740
[  +0,000004]  ? __switch_to_asm+0x40/0x70
[  +0,000003]  ? __switch_to_asm+0x34/0x70
[  +0,000005]  schedule+0x42/0xb0
[  +0,000005]  schedule_preempt_disabled+0xe/0x10
[  +0,000005]  __mutex_lock.isra.0+0x182/0x4f0
[  +0,000006]  ? device_match_of_node+0x20/0x20
[  +0,000006]  __mutex_lock_slowpath+0x13/0x20
[  +0,000005]  mutex_lock+0x2e/0x40
[  +0,000005]  usbdev_open+0xd9/0x240
[  +0,000006]  chrdev_open+0xd3/0x1c0
[  +0,000006]  ? cdev_default_release+0x20/0x20
[  +0,000005]  do_dentry_open+0x143/0x3a0
[  +0,000006]  vfs_open+0x2d/0x30
[  +0,000004]  do_last+0x194/0x900
[  +0,000006]  path_openat+0x8d/0x290
[  +0,000005]  ? do_anonymous_page+0x2e6/0x650
[  +0,000005]  do_filp_open+0x91/0x100
[  +0,000005]  ? __alloc_fd+0x46/0x150
[  +0,000006]  do_sys_open+0x17f/0x230
[  +0,000006]  __x64_sys_openat+0x20/0x30
[  +0,000006]  do_syscall_64+0x57/0x190
[  +0,000004]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  +0,000002] RIP: 0033:0x7f9e090a1dae
[  +0,000006] Code: Bad RIP value.
[  +0,000002] RSP: 002b:00007ffd77440af0 EFLAGS: 00000293 ORIG_RAX:
0000000000000101
[  +0,000004] RAX: ffffffffffffffda RBX: 00005608306a3450 RCX: 00007f9e090a1dae
[  +0,000002] RDX: 0000000000000000 RSI: 00007ffd77441c10 RDI: 00000000ffffff9c
[  +0,000002] RBP: 00000000ffffffff R08: 0000000000000000 R09: 000056083069373b
[  +0,000002] R10: 0000000000000000 R11: 0000000000000293 R12: 00007f9df790a110
[  +0,000002] R13: 00005608306a3460 R14: 0000000000000000 R15: 00007ffd77441c10
[  +0,000010] OOM killer enabled.
[  +0,000001] Restarting tasks ... done.
[  +0,030746] thermal thermal_zone3: failed to read out thermal zone (-61)
[  +0,059657] PM: suspend exit
[  +0,000065] PM: suspend entry (s2idle)
[  +0,014476] Filesystems sync: 0.014 seconds
[  +0,000348] Freezing user space processes ... 
[  +0,397649] usb 2-4.2: reset SuperSpeed Gen 1 USB device number 13 using
xhci_hcd

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2020-05-25 16:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 16:28 bugzilla-daemon [this message]
2020-05-25 16:29 ` [Bug 207887] USB devices connected to Thinkpad Dock hangs after a while bugzilla-daemon
2020-09-02 12:34 ` bugzilla-daemon
2020-09-02 12:36 ` [Bug 207887] USB keyboard (and other devices) " bugzilla-daemon
2020-09-02 17:26 ` bugzilla-daemon
2020-09-03 16:17 ` bugzilla-daemon
2021-03-18 11:48 ` bugzilla-daemon
2021-03-18 11:55 ` bugzilla-daemon
2021-03-18 15:19 ` bugzilla-daemon
2021-04-08 19:30 ` bugzilla-daemon
2021-08-25 16:36 ` bugzilla-daemon
2021-08-25 16:41 ` bugzilla-daemon
2021-08-25 16:46 ` bugzilla-daemon
2021-08-26  2:52 ` bugzilla-daemon
2021-08-26 13:54 ` bugzilla-daemon
2021-08-26 15:52 ` bugzilla-daemon
2021-08-29 20:09 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-207887-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).