syzbot


INFO: task hung in hub_event (3)

Status: upstream: reported on 2023/01/14 20:19
Subsystems: usb
[Documentation on labels]
Reported-by: syzbot+a7edecbf389d11a369d4@syzkaller.appspotmail.com
First crash: 786d, last: 12d
Discussions (9)
Title Replies (including bot) Last reply
[syzbot] Monthly usb report (Apr 2024) 0 (1) 2024/04/08 12:51
[syzbot] Monthly usb report (Mar 2024) 0 (1) 2024/03/08 08:53
[syzbot] Monthly usb report (Feb 2024) 0 (1) 2024/02/05 20:59
[syzbot] Monthly usb report (Jan 2024) 0 (1) 2024/01/05 13:17
[syzbot] Monthly usb report (Dec 2023) 0 (1) 2023/12/05 09:53
[syzbot] Monthly usb report (Nov 2023) 0 (1) 2023/11/03 20:48
[syzbot] Monthly usb report (May 2023) 0 (1) 2023/05/31 12:38
[syzbot] Monthly usb report 12 (17) 2023/04/10 16:42
[syzbot] INFO: task hung in hub_event (3) 0 (1) 2023/01/14 20:19
Similar bugs (7)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream INFO: task hung in hub_event usb 19 1654d 1830d 0/26 auto-closed as invalid on 2020/01/02 20:34
linux-4.14 INFO: task hung in hub_event 5 826d 848d 0/1 auto-closed as invalid on 2022/05/10 10:19
linux-6.1 INFO: task hung in hub_event (2) 1 208d 208d 0/3 auto-obsoleted due to no activity on 2023/12/29 05:51
upstream INFO: task hung in hub_event (2) usb 27 825d 870d 0/26 closed as invalid on 2022/02/08 09:40
linux-5.15 INFO: task hung in hub_event (2) 1 114d 114d 0/3 auto-obsoleted due to no activity on 2024/04/01 17:35
linux-5.15 INFO: task hung in hub_event 3 225d 389d 0/3 auto-obsoleted due to no activity on 2023/12/12 00:26
linux-6.1 INFO: task hung in hub_event 2 371d 400d 0/3 auto-obsoleted due to no activity on 2023/08/08 09:24

Sample crash report:
INFO: task kworker/1:16:20830 blocked for more than 143 seconds.
      Not tainted 6.8.0-rc7-syzkaller-00238-g005f6f34bd47 #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/1:16    state:D stack:23472 pid:20830 tgid:20830 ppid:2      flags:0x00004000
Workqueue: usb_hub_wq hub_event
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5400 [inline]
 __schedule+0x17d1/0x49f0 kernel/sched/core.c:6727
 __schedule_loop kernel/sched/core.c:6802 [inline]
 schedule+0x149/0x260 kernel/sched/core.c:6817
 schedule_preempt_disabled+0x13/0x30 kernel/sched/core.c:6874
 __mutex_lock_common kernel/locking/mutex.c:684 [inline]
 __mutex_lock+0x6a3/0xd70 kernel/locking/mutex.c:752
 hub_port_connect drivers/usb/core/hub.c:5381 [inline]
 hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
 port_event drivers/usb/core/hub.c:5783 [inline]
 hub_event+0x259d/0x50f0 drivers/usb/core/hub.c:5865
 process_one_work kernel/workqueue.c:2633 [inline]
 process_scheduled_works+0x913/0x1420 kernel/workqueue.c:2706
 worker_thread+0xa5f/0x1000 kernel/workqueue.c:2787
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:243
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/29:
 #0: ffffffff8e130be0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire include/linux/rcupdate.h:298 [inline]
 #0: ffffffff8e130be0 (rcu_read_lock){....}-{1:2}, at: rcu_read_lock include/linux/rcupdate.h:750 [inline]
 #0: ffffffff8e130be0 (rcu_read_lock){....}-{1:2}, at: debug_show_all_locks+0x55/0x2a0 kernel/locking/lockdep.c:6614
2 locks held by getty/4821:
 #0: ffff88802a5b20a0 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:243
 #1: ffffc90002f062f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6b4/0x1e10 drivers/tty/n_tty.c:2201
2 locks held by syz-executor.3/5115:
 #0: ffff8880b943c958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:567
 #1: ffff8880b9528988 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x441/0x770 kernel/sched/psi.c:988
6 locks held by kworker/1:10/9108:
2 locks held by kworker/u4:24/22889:
4 locks held by syz-executor.4/19630:
5 locks held by kworker/1:16/20830:
 #0: ffff88801ca99538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2608 [inline]
 #0: ffff88801ca99538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2706
 #1: ffffc9000b3d7d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2608 [inline]
 #1: ffffc9000b3d7d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2706
 #2: ffff88802414f190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:990 [inline]
 #2: ffff88802414f190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x50f0 drivers/usb/core/hub.c:5811
 #3: ffff88802415a510 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3169 [inline]
 #3: ffff88802415a510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5380 [inline]
 #3: ffff88802415a510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
 #3: ffff88802415a510 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5783 [inline]
 #3: ffff88802415a510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x255f/0x50f0 drivers/usb/core/hub.c:5865
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5381 [inline]
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5783 [inline]
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x259d/0x50f0 drivers/usb/core/hub.c:5865
5 locks held by kworker/1:19/20832:
 #0: ffff88801ca99538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2608 [inline]
 #0: ffff88801ca99538 ((wq_completion)usb_hub_wq){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2706
 #1: ffffc9000b3f7d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_one_work kernel/workqueue.c:2608 [inline]
 #1: ffffc9000b3f7d20 ((work_completion)(&hub->events)){+.+.}-{0:0}, at: process_scheduled_works+0x825/0x1420 kernel/workqueue.c:2706
 #2: ffff8880240bc190 (&dev->mutex){....}-{3:3}, at: device_lock include/linux/device.h:990 [inline]
 #2: ffff8880240bc190 (&dev->mutex){....}-{3:3}, at: hub_event+0x1fe/0x50f0 drivers/usb/core/hub.c:5811
 #3: ffff8880240bf510 (&port_dev->status_lock){+.+.}-{3:3}, at: usb_lock_port drivers/usb/core/hub.c:3169 [inline]
 #3: ffff8880240bf510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5380 [inline]
 #3: ffff8880240bf510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
 #3: ffff8880240bf510 (&port_dev->status_lock){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5783 [inline]
 #3: ffff8880240bf510 (&port_dev->status_lock){+.+.}-{3:3}, at: hub_event+0x255f/0x50f0 drivers/usb/core/hub.c:5865
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect drivers/usb/core/hub.c:5381 [inline]
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_port_connect_change drivers/usb/core/hub.c:5623 [inline]
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: port_event drivers/usb/core/hub.c:5783 [inline]
 #4: ffff888023e75f68 (hcd->address0_mutex){+.+.}-{3:3}, at: hub_event+0x259d/0x50f0 drivers/usb/core/hub.c:5865
2 locks held by kworker/u4:7/22612:
 #0: ffff8880b943c958 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0xb0/0x140 kernel/sched/core.c:567
 #1: ffff8880b9428988 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x441/0x770 kernel/sched/psi.c:988
1 lock held by syz-executor.1/30721:

=============================================

NMI backtrace for cpu 1
CPU: 1 PID: 29 Comm: khungtaskd Not tainted 6.8.0-rc7-syzkaller-00238-g005f6f34bd47 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x49c/0x4d0 lib/nmi_backtrace.c:113
 nmi_trigger_cpumask_backtrace+0x198/0x320 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:160 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:222 [inline]
 watchdog+0xfaf/0xff0 kernel/hung_task.c:379
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:243
 </TASK>
Sending NMI from CPU 1 to CPUs 0:
NMI backtrace for cpu 0
CPU: 0 PID: 22612 Comm: kworker/u4:7 Not tainted 6.8.0-rc7-syzkaller-00238-g005f6f34bd47 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/29/2024
Workqueue: bat_events batadv_nc_worker
RIP: 0010:rcu_preempt_read_exit kernel/rcu/tree_plugin.h:384 [inline]
RIP: 0010:__rcu_read_unlock+0x2a/0x110 kernel/rcu/tree_plugin.h:423
Code: f3 0f 1e fa 55 41 57 41 56 41 55 41 54 53 49 bc 00 00 00 00 00 fc ff df 65 4c 8b 35 90 1a 88 7e 4d 8d ae 3c 04 00 00 4c 89 eb <48> c1 eb 03 42 0f b6 04 23 84 c0 75 6b 41 8b 6d 00 ff cd 42 0f b6
RSP: 0018:ffffc90013c47b60 EFLAGS: 00000293
RAX: ffffffff8b33cfd0 RBX: ffff8880a904a1fc RCX: ffff8880a9049dc0
RDX: 0000000000000000 RSI: ffffffff8bfe6d80 RDI: ffffffff8bfe6d40
RBP: 0000000000000000 R08: ffffffff8b33cfbe R09: 1ffffffff2591e84
R10: dffffc0000000000 R11: fffffbfff2591e85 R12: dffffc0000000000
R13: ffff8880a904a1fc R14: ffff8880a9049dc0 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880b9400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5d01ad66e4 CR3: 000000000df32000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <NMI>
 </NMI>
 <TASK>
 rcu_read_unlock include/linux/rcupdate.h:782 [inline]
 batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
 batadv_nc_worker+0x281/0x610 net/batman-adv/network-coding.c:719
 process_one_work kernel/workqueue.c:2633 [inline]
 process_scheduled_works+0x913/0x1420 kernel/workqueue.c:2706
 worker_thread+0xa5f/0x1000 kernel/workqueue.c:2787
 kthread+0x2ef/0x390 kernel/kthread.c:388
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1b/0x30 arch/x86/entry/entry_64.S:243
 </TASK>

Crashes (274):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/03/10 16:34 upstream 005f6f34bd47 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/03/09 18:12 upstream 09e5c48fea17 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in hub_event
2024/03/07 12:48 upstream 67be068d31d4 f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/03/01 08:50 upstream 87adedeba51a 352ab904 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in hub_event
2024/02/28 10:00 upstream cf1182944c7c d367cbe5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2024/02/27 16:18 upstream 45ec2f5f6ed3 05e69c83 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in hub_event
2024/02/26 19:15 upstream d206a76d7d27 edd6a5e9 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/02/17 23:59 upstream ced590523156 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/02/09 07:34 upstream 1f719a2f3fa6 7f07e9b0 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/02/02 14:49 upstream 021533194476 60bf9982 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2024/01/29 14:38 upstream 41bccc98fb79 991a98f4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/01/27 21:48 upstream 3a5879d495b2 cc4a4020 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2024/01/26 18:43 upstream ecb1b8288dc7 cc4a4020 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/01/25 13:47 upstream 6098d87eaf31 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/01/25 04:03 upstream 443b349019f2 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2024/01/06 20:39 upstream 95c8a35f1c01 d0304e9c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2023/12/21 20:33 upstream a4aebe936554 4f9530a3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2023/12/21 10:53 upstream 1a44b0073b92 4f9530a3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2023/12/20 03:53 upstream 55cb5f43689d 3ad490ea .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root INFO: task hung in hub_event
2023/12/12 06:51 upstream 26aff849438c 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-smack-root INFO: task hung in hub_event
2023/12/01 10:07 upstream e8f60209d6cf f819d6f7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2023/11/26 18:00 upstream 090472ed9c92 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-selinux-root INFO: task hung in hub_event
2024/03/10 19:45 upstream 137e0ec05aeb 6ee49f2e .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/03/07 02:02 upstream 67be068d31d4 f39a7eed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/03/02 14:50 upstream 5ad3cb0ed525 25905f5d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/03/01 03:51 upstream 805d849d7c3c 352ab904 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/02/20 23:42 upstream fca7526b7d89 3af7dd65 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/02/19 02:08 upstream b401b621758e 578f7538 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/02/13 20:36 upstream 7e90b5c295ec e66542d7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/02/12 00:41 upstream 2766f59ca44e 77b23aa1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/02/04 22:07 upstream 54be6c6c5ae8 a67b2c42 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/01/24 08:22 upstream 615d30064886 1e153dc8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/01/23 01:57 upstream 610347effc2e 1c0ecc51 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/01/20 21:06 upstream 125514880ddd 9bd8dcda .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2024/01/13 08:58 upstream 052d534373b7 551587c1 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/29 03:14 upstream 505e701c0b2c fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/26 02:03 upstream fbafc3e621c3 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/16 01:58 upstream 3bd7d7488169 3222d10c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/12 14:23 upstream 26aff849438c ebcad15c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/08 11:47 upstream 9ace34a8e446 28b24332 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/07 06:45 upstream bee0e7762ad2 e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/12/06 16:50 upstream bee0e7762ad2 e3299f55 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/11/29 13:49 upstream 18d46e76d7c2 6e78f9ce .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-386 INFO: task hung in hub_event
2023/01/14 13:26 upstream 97ec4d559d93 a63719e7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2023/01/10 20:10 upstream 40c18f363a08 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2022/12/31 00:37 upstream c8451c141e07 ab32d508 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce INFO: task hung in hub_event
2022/02/19 06:12 upstream 7993e65fdd0f 3cd800e4 .config console log report info ci-upstream-kasan-gce-root INFO: task hung in hub_event
2024/04/01 03:00 linux-next a6bd6c933339 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2024/03/31 21:36 linux-next a6bd6c933339 6baf5069 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2024/02/13 16:49 linux-next 46d4e2eb58e1 e66542d7 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2024/01/30 12:38 linux-next 596764183be8 991a98f4 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2023/12/23 08:49 linux-next 39676dfe5233 fb427a07 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root INFO: task hung in hub_event
2024/04/03 16:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 707081b61156 fed899ed .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in hub_event
2023/12/19 04:48 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 0bcda4cd6851 3ad490ea .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in hub_event
2023/11/12 09:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8de1e7afcc1c 6d6dbf8a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 INFO: task hung in hub_event
* Struck through repros no longer work on HEAD.