INFO: task hung in console_device

Status: upstream: reported on 2026/10/28 13:00
Reported-by: syzbot+3642aec634e6ee454731@syzkaller.appspotmail.com
First crash: 21d, last: 21d
▶ ▼ Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-44 INFO: task hung in console_device 1 syz, C 11 2637d 2775d 0/2 public: reported C repro on 2019/04/14 00:00
upstream INFO: task hung in console_device kernel 1 13 565d 733d 0/29 auto-obsoleted due to no activity on 2025/07/31 12:18
android-414 INFO: task hung in console_device 1 14 2919d 2776d 0/1 auto-closed as invalid on 2019/05/20 06:11
android-414 INFO: task hung in console_device (2) 1 1 2566d 2566d 0/1 auto-closed as invalid on 2020/03/08 16:40
android-49 INFO: task hung in console_device 1 syz, C 150 2572d 2778d 0/3 public: reported C repro on 2019/04/11 08:44

Sample crash report:
INFO: task syz.3.1242:8282 blocked for more than 143 seconds.
      Not tainted syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.1242      state:D stack:27856 pid: 8282 ppid:  4190 flags:0x00004004
Call Trace:
 <TASK>
 context_switch kernel/sched/core.c:5049 [inline]
 __schedule+0x11c3/0x4350 kernel/sched/core.c:6395
 schedule+0x11b/0x1e0 kernel/sched/core.c:6478
 schedule_timeout+0xbd/0x2d0 kernel/time/timer.c:2093
 __down_common+0x289/0x3b0 kernel/locking/semaphore.c:228
 down+0x7e/0xd0 kernel/locking/semaphore.c:63
 console_lock kernel/printk/printk.c:2557 [inline]
 console_device+0x33/0x120 kernel/printk/printk.c:2843
 tty_lookup_driver+0xfa/0x480 drivers/tty/tty_io.c:1948
 tty_open_by_driver drivers/tty/tty_io.c:2065 [inline]
 tty_open+0x21d/0xcd0 drivers/tty/tty_io.c:2148
 chrdev_open+0x585/0x5f0 fs/char_dev.c:414
 do_dentry_open+0x7f7/0xf90 fs/open.c:826
 do_open fs/namei.c:3659 [inline]
 path_openat+0x2718/0x2fb0 fs/namei.c:3793
 do_filp_open+0x1df/0x400 fs/namei.c:3820
 do_sys_openat2+0x14b/0x500 fs/open.c:1255
 do_sys_open fs/open.c:1271 [inline]
 __do_sys_openat fs/open.c:1287 [inline]
 __se_sys_openat fs/open.c:1282 [inline]
 __x64_sys_openat+0x135/0x160 fs/open.c:1282
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f694b35b559
RSP: 002b:00007f69495b2028 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f694b5e1fa0 RCX: 00007f694b35b559
RDX: 0000000000000001 RSI: 00002000000000c0 RDI: ffffffffffffff9c
RBP: 00007f694b3f2b20 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f694b5e2038 R14: 00007f694b5e1fa0 R15: 00007ffee45c6aa8
 </TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
 #0: ffffffff8d11efa0 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:4/1325:
2 locks held by getty/3949:
 #0: ffff88814d19d098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
 #1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x594/0x1a50 drivers/tty/n_tty.c:2158
3 locks held by kworker/u4:5/4278:
2 locks held by kworker/u4:7/5115:
 #0: ffff888017879138 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000306fd00 ((work_completion)(&sub_info->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
5 locks held by syz.5.1201/8069:
1 lock held by syz.3.1242/8282:
 #0: ffffffff8d7f6648 (tty_mutex){+.+.}-{3:3}, at: tty_open_by_driver drivers/tty/tty_io.c:2064 [inline]
 #0: ffffffff8d7f6648 (tty_mutex){+.+.}-{3:3}, at: tty_open+0x20a/0xcd0 drivers/tty/tty_io.c:2148
3 locks held by kworker/0:28/9471:
3 locks held by kworker/0:35/10087:
 #0: ffff88814ccc7938 ((wq_completion)ipv6_addrconf){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000472fd00 ((work_completion)(&(&ifa->dad_work)->work)){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8e26bd48 (rtnl_mutex){+.+.}-{3:3}, at: addrconf_dad_work+0xc4/0x1530 net/ipv6/addrconf.c:4128
3 locks held by kworker/0:36/10088:
 #0: ffff888017870938 ((wq_completion)events){+.+.}-{0:0}, at: process_one_work+0x75c/0xff0 kernel/workqueue.c:-1
 #1: ffffc9000473fd00 (deferred_process_work){+.+.}-{0:0}, at: process_one_work+0x79e/0xff0 kernel/workqueue.c:2285
 #2: ffffffff8e26bd48 (rtnl_mutex){+.+.}-{3:3}, at: switchdev_deferred_process_work+0xa/0x20 net/switchdev/switchdev.c:74
1 lock held by syz-executor/10647:
 #0: ffffffff8e26bd48 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8e26bd48 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x79f/0xf10 net/core/rtnetlink.c:5695
1 lock held by syz-executor/10710:
 #0: ffffffff8e26bd48 (rtnl_mutex){+.+.}-{3:3}, at: rtnl_lock net/core/rtnetlink.c:72 [inline]
 #0: ffffffff8e26bd48 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x79f/0xf10 net/core/rtnetlink.c:5695
1 lock held by syz-executor/10720:
2 locks held by modprobe/10724:
1 lock held by sed/10726:

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/07/2026
Call Trace:
 <TASK>
 dump_stack_lvl+0x188/0x250 lib/dump_stack.c:106
 nmi_cpu_backtrace+0x3a2/0x3d0 lib/nmi_backtrace.c:111
 nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
 trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
 check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
 watchdog+0xe1b/0xe60 kernel/hung_task.c:369
 kthread+0x42e/0x520 kernel/kthread.c:334
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
 </TASK>

Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/10/28 13:00 linux-5.15.y 792fbe1537d8 858db2ec .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan INFO: task hung in console_device
* Struck through repros no longer work on HEAD.