Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 643512 - sys-kernel/gentoo-sources-4.14.11-r2: Freeze on shutdown/reboot
Summary: sys-kernel/gentoo-sources-4.14.11-r2: Freeze on shutdown/reboot
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-05 09:15 UTC by teefax
Modified: 2018-06-08 22:42 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
kernel config (config,106.74 KB, text/plain)
2018-01-05 09:15 UTC, teefax
Details

Note You need to log in before you can comment on or make changes to this bug.
Description teefax 2018-01-05 09:15:15 UTC
Created attachment 513382 [details]
kernel config

My system freezes most of the time on shutdown/reboot with the latest 4.14 kernel. The problem doesn't occur with previous kernels (4.12 / 4.9).

The following error shows up in the kernel messages each time this happens:

Jan 05 09:29:16 triton kernel: retire_capture_urb: 2490 callbacks suppressed
Jan 05 09:29:21 triton kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
Jan 05 09:29:21 triton kernel: IP: snd_ctl_notify.part.9+0xb4/0x190
Jan 05 09:29:21 triton kernel: PGD 0 P4D 0 
Jan 05 09:29:21 triton kernel: Oops: 0000 [#1] SMP NOPTI
Jan 05 09:29:21 triton kernel: Modules linked in: nvidia_drm(PO) snd_usb_audio snd_usbmidi_lib snd_rawmidi nvidia_modeset(PO) r8168(O) vboxpci(O) vboxnetflt(O) vboxnetadp(O) vboxdrv(O) nvidia(PO) zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O)
Jan 05 09:29:21 triton kernel: CPU: 0 PID: 3 Comm: kworker/0:0 Tainted: P           O    4.14.11-gentoo-r2 #1
Jan 05 09:29:21 triton kernel: Hardware name: Gigabyte Technology Co., Ltd. AB350-Gaming 3/AB350-Gaming 3-CF, BIOS F10 12/01/2017
Jan 05 09:29:21 triton kernel: Workqueue: events process_unsol_events
Jan 05 09:29:21 triton kernel: task: ffff9fb2ccda9b80 task.stack: ffffad4c018d4000
Jan 05 09:29:21 triton kernel: RIP: 0010:snd_ctl_notify.part.9+0xb4/0x190
Jan 05 09:29:21 triton kernel: RSP: 0018:ffffad4c018d7db0 EFLAGS: 00010086
Jan 05 09:29:21 triton kernel: RAX: ffff9fb2bd774f00 RBX: ffff9fb2c952a000 RCX: 0000000000000000
Jan 05 09:29:21 triton kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff9fb2bd774f60
Jan 05 09:29:21 triton kernel: RBP: ffff9fb2c952a4e0 R08: ffff9fb2dec1ef20 R09: ffff9fb2bd774f00
Jan 05 09:29:21 triton kernel: R10: 0000000000000001 R11: ffff9fb2ca000000 R12: ffff9fb2c8f175c0
Jan 05 09:29:21 triton kernel: R13: 0000000000000202 R14: 0000000000000010 R15: ffff9fb2c8f17580
Jan 05 09:29:21 triton kernel: FS:  0000000000000000(0000) GS:ffff9fb2dec00000(0000) knlGS:0000000000000000
Jan 05 09:29:21 triton kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 05 09:29:21 triton kernel: CR2: 0000000000000010 CR3: 0000000407b84000 CR4: 00000000003406f0
Jan 05 09:29:21 triton kernel: Call Trace:
Jan 05 09:29:21 triton kernel:  hdmi_present_sense+0x19f/0x740
Jan 05 09:29:21 triton kernel:  ? sched_clock_cpu+0xc/0xb0
Jan 05 09:29:21 triton kernel:  ? __switch_to+0x173/0x430
Jan 05 09:29:21 triton kernel:  check_presence_and_report+0x56/0x80
Jan 05 09:29:21 triton kernel:  process_unsol_events+0x59/0x70
Jan 05 09:29:21 triton kernel:  process_one_work+0x1d1/0x3c0
Jan 05 09:29:21 triton kernel:  worker_thread+0x26/0x3c0
Jan 05 09:29:21 triton kernel:  ? trace_event_raw_event_workqueue_execute_start+0x80/0x80
Jan 05 09:29:21 triton kernel:  kthread+0x112/0x130
Jan 05 09:29:21 triton kernel:  ? kthread_create_on_node+0x40/0x40
Jan 05 09:29:21 triton kernel:  ret_from_fork+0x1f/0x30
Jan 05 09:29:21 triton kernel: Code: 8b 00 48 39 c8 75 ef 48 8b 3d 91 d4 11 01 ba 58 00 00 00 be 20 80 08 01 48 89 4c 24 08 e8 f5 5b ac ff 48 85 c0 0f 84 c1 00 00 00 <49> 8b 16 8b 74 24 04 48 8b 4c 24 08 48 89 50 10 49 8b 56 08 89 
Jan 05 09:29:21 triton kernel: RIP: snd_ctl_notify.part.9+0xb4/0x190 RSP: ffffad4c018d7db0
Jan 05 09:29:21 triton kernel: CR2: 0000000000000010
Jan 05 09:29:21 triton kernel: ---[ end trace 0a92fa3d856a41e8 ]---
Comment 1 teefax 2018-01-05 14:06:06 UTC
No more freezes after I've disabled CONFIG_SND_HDA_CODEC_HDMI. I'll report back if they should reappear.
Comment 2 Tomáš Mózes 2018-01-05 15:46:09 UTC
Maybe it's a good candidate to report upstream if you can reproduce on vanilla sources.
Comment 3 teefax 2018-01-06 11:03:47 UTC
I could reproduce the problem with sys-kernel/vanilla-sources-4.14.11. This seems to be related to the nvidia drivers not working properly with the 4.14 kernel. With the x11-drivers/nvidia-drivers-387.22 the freeze occurs on shutdown/reboot. With nvidia-drivers-390.12 the freeze occurs directly after the login when pulseaudio is being started.

In both cases the problem can be avoided by disabling the HDMI sound codec support.
Comment 4 Arisu Tachibana Gentoo Infrastructure gentoo-dev 2018-01-06 18:58:27 UTC
can you try with gentoo-sources-4.14.12
Comment 5 Arisu Tachibana Gentoo Infrastructure gentoo-dev 2018-01-06 18:59:24 UTC
yes this is better to be reported upstream
Comment 6 Mike Pagano gentoo-dev 2018-06-08 22:42:36 UTC
As this concerns a proprietary closed-source upstream binary, it is not in the context of gentoo kernel support.