All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207887] USB keyboard (and other devices) connected to Thinkpad Dock hangs after a while
Date: Wed, 25 Aug 2021 16:41:37 +0000	[thread overview]
Message-ID: <bug-207887-208809-cxzsdWeqrT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207887-208809@https.bugzilla.kernel.org/>

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

--- Comment #12 from Johannes Wegener (catchall-kernelbug@blubbbla.de) ---
But at least the Call-Trace looks a bit more helpful (mentions hub_event) and
seems to hang in a mutex:


[ +43.245062] INFO: task kworker/0:1:19 blocked for more than 245 seconds.
[  +0.000014]       Tainted: P           OE     5.13.12-arch1-1 #1
[  +0.000005] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  +0.000004] task:kworker/0:1     state:D stack:    0 pid:   19 ppid:     2
flags:0x00004000
[  +0.000011] Workqueue: usb_hub_wq hub_event
[  +0.000015] Call Trace:
[  +0.000005]  __schedule+0x310/0x930
[  +0.000013]  schedule+0x5b/0xc0
[  +0.000007]  schedule_preempt_disabled+0x11/0x20
[  +0.000008]  __mutex_lock.constprop.0+0x2f8/0x4e0
[  +0.000011]  hub_event+0x1a8/0x17f0
[  +0.000011]  ? finish_task_switch.isra.0+0xaa/0x290
[  +0.000012]  process_one_work+0x1e3/0x3b0
[  +0.000010]  worker_thread+0x50/0x3b0
[  +0.000007]  ? process_one_work+0x3b0/0x3b0
[  +0.000007]  kthread+0x133/0x160
[  +0.000005]  ? set_kthread_struct+0x40/0x40
[  +0.000006]  ret_from_fork+0x22/0x30
[  +0.000022] INFO: task kworker/u8:2:84 blocked for more than 245 seconds.
[  +0.000006]       Tainted: P           OE     5.13.12-arch1-1 #1
[  +0.000004] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  +0.000003] task:kworker/u8:2    state:D stack:    0 pid:   84 ppid:     2
flags:0x00004000
[  +0.000007] Workqueue: scsi_tmf_8 scmd_eh_abort_handler
[  +0.000012] Call Trace:
[  +0.000003]  __schedule+0x310/0x930
[  +0.000008]  schedule+0x5b/0xc0
[  +0.000007]  schedule_timeout+0x11c/0x160
[  +0.000011]  wait_for_completion+0xa3/0x100
[  +0.000011]  command_abort+0x63/0x80 [usb_storage]
[  +0.000013]  scmd_eh_abort_handler+0x7e/0x230
[  +0.000009]  process_one_work+0x1e3/0x3b0
[  +0.000008]  worker_thread+0x50/0x3b0
[  +0.000007]  ? process_one_work+0x3b0/0x3b0
[  +0.000007]  kthread+0x133/0x160
[  +0.000005]  ? set_kthread_struct+0x40/0x40
[  +0.000005]  ret_from_fork+0x22/0x30
[  +0.000036] INFO: task udisksd:2185 blocked for more than 245 seconds.
[  +0.000005]       Tainted: P           OE     5.13.12-arch1-1 #1
[  +0.000004] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  +0.000003] task:udisksd         state:D stack:    0 pid: 2185 ppid:     1
flags:0x00000000
[  +0.000007] Call Trace:
[  +0.000003]  __schedule+0x310/0x930
[  +0.000008]  schedule+0x5b/0xc0
[  +0.000007]  schedule_timeout+0x11c/0x160
[  +0.000009]  wait_for_completion+0xa3/0x100
[  +0.000008]  __flush_work.isra.0+0x15b/0x210
[  +0.000008]  ? flush_workqueue_prep_pwqs+0x130/0x130
[  +0.000008]  __cancel_work_timer+0x12e/0x1c0
[  +0.000010]  disk_block_events+0x6f/0x90
[  +0.000007]  blkdev_get_by_dev+0xe5/0x220
[  +0.000008]  ? blkdev_get_by_dev+0x220/0x220
[  +0.000006]  blkdev_open+0x4c/0x90
[  +0.000006]  do_dentry_open+0x14b/0x380
[  +0.000013]  path_openat+0xb93/0x1000
[  +0.000010]  ? _copy_to_iter+0xdb/0x7b0
[  +0.000008]  do_filp_open+0xa5/0x150
[  +0.000014]  do_sys_openat2+0xb0/0x160
[  +0.000006]  __x64_sys_openat+0x53/0x90
[  +0.000006]  do_syscall_64+0x61/0x80
[  +0.000008]  ? exc_page_fault+0x78/0x180
[  +0.000009]  entry_SYSCALL_64_after_hwframe+0x44/0xae
[  +0.000012] RIP: 0033:0x7f7a234a5f04
[  +0.000006] RSP: 002b:00007ffc593edb50 EFLAGS: 00000293 ORIG_RAX:
0000000000000101
[  +0.000007] RAX: ffffffffffffffda RBX: 00007ffc593edc54 RCX: 00007f7a234a5f04
[  +0.000004] RDX: 0000000000000000 RSI: 000055a67b147e40 RDI: 00000000ffffff9c
[  +0.000005] RBP: 000055a67b147e40 R08: 0000000000000000 R09: 463801417d483af5
[  +0.000003] R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000000000
[  +0.000004] R13: 0000000000000000 R14: 000055a67b12b160 R15: 000055a67a59a828
[Aug25 18:36] INFO: task kworker/0:1:19 blocked for more than 368 seconds.
[  +0.000014]       Tainted: P           OE     5.13.12-arch1-1 #1
[  +0.000005] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  +0.000004] task:kworker/0:1     state:D stack:    0 pid:   19 ppid:     2
flags:0x00004000
[  +0.000011] Workqueue: usb_hub_wq hub_event
[  +0.000014] Call Trace:
[  +0.000006]  __schedule+0x310/0x930
[  +0.000012]  schedule+0x5b/0xc0
[  +0.000007]  schedule_preempt_disabled+0x11/0x20
[  +0.000007]  __mutex_lock.constprop.0+0x2f8/0x4e0
[  +0.000011]  hub_event+0x1a8/0x17f0
[  +0.000012]  ? finish_task_switch.isra.0+0xaa/0x290
[  +0.000012]  process_one_work+0x1e3/0x3b0
[  +0.000010]  worker_thread+0x50/0x3b0
[  +0.000007]  ? process_one_work+0x3b0/0x3b0
[  +0.000007]  kthread+0x133/0x160
[  +0.000005]  ? set_kthread_struct+0x40/0x40
[  +0.000006]  ret_from_fork+0x22/0x30
[  +0.000021] INFO: task kworker/u8:2:84 blocked for more than 368 seconds.
[  +0.000006]       Tainted: P           OE     5.13.12-arch1-1 #1
[  +0.000004] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[  +0.000003] task:kworker/u8:2    state:D stack:    0 pid:   84 ppid:     2
flags:0x00004000
[  +0.000007] Workqueue: scsi_tmf_8 scmd_eh_abort_handler
[  +0.000011] Call Trace:
[  +0.000004]  __schedule+0x310/0x930
[  +0.000008]  schedule+0x5b/0xc0
[  +0.000007]  schedule_timeout+0x11c/0x160
[  +0.000010]  wait_for_completion+0xa3/0x100
[  +0.000011]  command_abort+0x63/0x80 [usb_storage]
[  +0.000014]  scmd_eh_abort_handler+0x7e/0x230
[  +0.000009]  process_one_work+0x1e3/0x3b0
[  +0.000008]  worker_thread+0x50/0x3b0
[  +0.000006]  ? process_one_work+0x3b0/0x3b0
[  +0.000008]  kthread+0x133/0x160
[  +0.000004]  ? set_kthread_struct+0x40/0x40
[  +0.000006]  ret_from_fork+0x22/0x30

-- 
You may reply to this email to add a comment.

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

  parent reply	other threads:[~2021-08-25 16:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 16:28 [Bug 207887] New: USB devices connected to Thinkpad Dock hangs after a while bugzilla-daemon
2020-05-25 16:29 ` [Bug 207887] " 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 [this message]
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-cxzsdWeqrT@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.