| View previous topic :: View next topic |
| Author |
Message |
IsLo
n00b
Joined: 11 Jul 2018
Posts: 4
|
 Posted: Wed Jul 11, 2018 7:39 pm Post subject: KDE-related kernel oops after kernel upgrade |
 |
|
Hello people!
I have a problem I am having difficulties solving. Googling around has not made me any wiser.
About 60% of the times when I do a poweroff or reboot, I get a kernel oops. The fact that it isn't entirely reproducible makes it extra tricky I think. This never happend with 4.9.95 (I am using gentoo-sources), but happens occasionaly after upgrading to 4.14.52. I also remember this happening on occasion with 4.14.11 for the short time that kernel version was stable. On the other hand, he 4.12.12 and 4.12.5 versions worked fine without ever crashing on poweroff or reboot. I am using KDE, and I have learned that this only ever happens when I am running it. If I don't fire up KDE and just stay with a terminal, I never have these crashes upon reboot/poweroff. If I am running KDE, switch to another virtual terminal and do
| Code: | | /etc/init.d/xdm stop |
I occasionally trigger the kernel oops.
This is what I got from syslog after the last time it happend:
| Code: |
7 Jul 11 00:20:34 HomeErik shutdown[4715]: shutting down for system halt
8 Jul 11 00:20:34 HomeErik init: Switching to runlevel: 0
9 Jul 11 00:20:35 HomeErik kernel: [ 6714.025218] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
10 Jul 11 00:20:35 HomeErik kernel: [ 6714.025224] IP: snd_ctl_notify.part.7+0xb5/0x190
11 Jul 11 00:20:35 HomeErik kernel: [ 6714.025225] PGD 0 P4D 0
12 Jul 11 00:20:35 HomeErik kernel: [ 6714.025226] Oops: 0000 [#1] SMP PTI
13 Jul 11 00:20:35 HomeErik kernel: [ 6714.025228] Modules linked in: nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) wmi x86_pkg_temp_thermal efivarfs
14 Jul 11 00:20:35 HomeErik kernel: [ 6714.025232] CPU: 5 PID: 66 Comm: kworker/5:1 Tainted: P O 4.14.52-gentoo #4
15 Jul 11 00:20:35 HomeErik kernel: [ 6714.025232] Hardware name: Exertis_CapTech MS-7998/Z170A-S02 (MS-7998), BIOS 3.40 03/25/2016
16 Jul 11 00:20:35 HomeErik kernel: [ 6714.025235] Workqueue: events process_unsol_events
17 Jul 11 00:20:35 HomeErik kernel: [ 6714.025235] task: ffff9db70ab61c00 task.stack: ffffbcc7033b4000
18 Jul 11 00:20:35 HomeErik kernel: [ 6714.025237] RIP: 0010:snd_ctl_notify.part.7+0xb5/0x190
19 Jul 11 00:20:35 HomeErik kernel: [ 6714.025237] RSP: 0018:ffffbcc7033b7de0 EFLAGS: 00010086
20 Jul 11 00:20:35 HomeErik kernel: [ 6714.025238] RAX: ffff9db70aa69cc0 RBX: ffff9db709019800 RCX: 0000000000000000
21 Jul 11 00:20:35 HomeErik kernel: [ 6714.025239] RDX: 0000000000000060 RSI: 0000000000000000 RDI: ffff9db70aa69d20
22 Jul 11 00:20:35 HomeErik kernel: [ 6714.025240] RBP: ffff9db709019c98 R08: ffff9db72ed63760 R09: ffff9db70aa69cc0
23 Jul 11 00:20:35 HomeErik kernel: [ 6714.025241] R10: ffffbcc7033b7cf0 R11: 00000000000003ce R12: ffff9db70aae15c0
24 Jul 11 00:20:35 HomeErik kernel: [ 6714.025241] R13: 0000000000000202 R14: 0000000000000010 R15: ffff9db70aae1580
25 Jul 11 00:20:35 HomeErik kernel: [ 6714.025243] FS: 0000000000000000(0000) GS:ffff9db72ed40000(0000) knlGS:0000000000000000
26 Jul 11 00:20:35 HomeErik kernel: [ 6714.025243] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
27 Jul 11 00:20:35 HomeErik kernel: [ 6714.025244] CR2: 0000000000000010 CR3: 00000003e8e0a002 CR4: 00000000003606e0
28 Jul 11 00:20:35 HomeErik kernel: [ 6714.025245] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
29 Jul 11 00:20:35 HomeErik kernel: [ 6714.025245] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
30 Jul 11 00:20:35 HomeErik kernel: [ 6714.025246] Call Trace:
31 Jul 11 00:20:35 HomeErik kernel: [ 6714.025249] hdmi_present_sense+0x198/0x330
32 Jul 11 00:20:35 HomeErik kernel: [ 6714.025250] check_presence_and_report+0x59/0x80
33 Jul 11 00:20:35 HomeErik kernel: [ 6714.025252] process_unsol_events+0x5d/0x70
34 Jul 11 00:20:35 HomeErik kernel: [ 6714.025254] process_one_work+0x1c9/0x3c0
35 Jul 11 00:20:35 HomeErik kernel: [ 6714.025255] worker_thread+0x26/0x3c0
36 Jul 11 00:20:35 HomeErik kernel: [ 6714.025257] ? trace_event_raw_event_workqueue_execute_start+0x80/0x80
37 Jul 11 00:20:35 HomeErik kernel: [ 6714.025258] kthread+0x114/0x130
38 Jul 11 00:20:35 HomeErik kernel: [ 6714.025259] ? kthread_create_on_node+0x40/0x40
39 Jul 11 00:20:35 HomeErik kernel: [ 6714.025261] ret_from_fork+0x35/0x40
40 Jul 11 00:20:35 HomeErik kernel: [ 6714.025262] Code: 8b 00 48 39 c8 75 ef ba 58 00 00 00 be 20 80 08 01 48 89 4c 24 08 48 8b 3d 61 f7 1f 01 e8 b4 19 b2 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
41 Jul 11 00:20:35 HomeErik kernel: [ 6714.025277] RIP: snd_ctl_notify.part.7+0xb5/0x190 RSP: ffffbcc7033b7de0
42 Jul 11 00:20:35 HomeErik kernel: [ 6714.025278] CR2: 0000000000000010
43 Jul 11 00:20:35 HomeErik kernel: [ 6714.025279] ---[ end trace b1627521fc2343c2 ]--- |
After the oops, everything freezes and the only way to accomplish the reboot/poweroff seems to be to do it the hard way.
Any ideas on how to fix this? I would be happy to provide any additional information/logs that might be necessary to find the culprit. |
|
| Back to top |
|
 |
Hazzerath
n00b
Joined: 10 Jan 2015
Posts: 3
|
| Posted: Sun Jul 15, 2018 7:44 am Post subject: Similar issues |
|
|
I'm running similar issues with the 4.14.52.
First time posting. Recently got sick with windows and setup on 4.9.95 now trying to upgrade to 4.14.52
sddm fails to run at boot, instead running startx shows its using the config and just freezes.
Usually i can control +C to kill but that doesn't seem to work under the new kernel.
Rebooting to use the older 4.9.95 kernel will fail because xdm won't stop due to an error which wont close the / drive.
It seems that the new updates add some basic thing, perhaps major changes:
- Spector patches upgrade
- Change to psyudo random numbers, now not using static inputs, so might take a lot longer to generate random numbers if too much is used. |
|
| Back to top |
|
|
TequilaTR
n00b
Joined: 01 Feb 2005
Posts: 68
|
| Posted: Wed Jul 18, 2018 8:52 pm Post subject: |
|
|
Hi,
very interesting. For me it is happening when upgrading from 4.16.13 to 4.17.6. Looks quite similar:
| Code: | BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
PGD 0 P4D 0
Oops: 0000 [#1] SMP PTI
Modules linked in: ebtable_filter x86_pkg_temp_thermal vxlan ip6_udp_tunnel udp_tunnel
CPU: 7 PID: 314 Comm: kworker/7:2 Not tainted 4.17.6-gentoo #1
Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./X99-UD3-CF, BIOS F2 08/18/2014
Workqueue: events process_unsol_events
RIP: 0010:snd_ctl_notify.part.8+0xb5/0x190
RSP: 0018:ffffc90001f9fdb8 EFLAGS: 00010086
RAX: ffff88044063f0c0 RBX: ffff880468b4a000 RCX: 0000000000000000
RDX: 0000000000000060 RSI: 0000000000000000 RDI: ffff88046f003680
RBP: ffff880468b4a4d0 R08: 0000000000000060 R09: ffff88044063f0c0
R10: ffff880469036b10 R11: 00000000000003d8 R12: ffff8804672c82c0
R13: 0000000000000202 R14: 0000000000000010 R15: ffff8804672c8280
FS: 0000000000000000(0000) GS:ffff88046f5c0000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000010 CR3: 000000000280a005 CR4: 00000000001606e0
Call Trace:
hdmi_present_sense+0x1d0/0x6b0
check_presence_and_report+0x59/0x80
process_unsol_events+0x5d/0x70
process_one_work+0x1b4/0x3e0
worker_thread+0x26/0x3c0
? trace_event_raw_event_workqueue_execute_start+0xa0/0xa0
kthread+0x10e/0x130
? kthread_create_worker_on_cpu+0x70/0x70
ret_from_fork+0x35/0x40
Code: 8b 00 48 39 c8 75 ef ba 58 00 00 00 be 20 80 08 01 48 89 4c 24 08 48 8b 3d 91 1c c7 00 e8 74 92 80 ff 48 8>
RIP: snd_ctl_notify.part.8+0xb5/0x190 RSP: ffffc90001f9fdb8
CR2: 0000000000000010
---[ end trace cda5826e881d39ac ]---
/usr/libexec/gdm-x-session[2362]: (EE) AMDGPU(0): failed to set mode: Permission denied
/usr/libexec/gdm-x-session[2362]: (II) systemd-logind: got pause for 13:77
|
gdm starts up, but when starting gnome3, the screen gets dark and i need a hard reset.
Can it be that we have a compiler issue here? Did you find out anything yet?
[Moderator edit: changed [quote] tags to [code] tags to preserve output layout. -Hu] |
|
| Back to top |
|
|
TequilaTR
n00b
Joined: 01 Feb 2005
Posts: 68
|
| Posted: Wed Jul 18, 2018 9:32 pm Post subject: |
|
|
Ok guys, I think i solved the one for me, maybe it helps you as well:
Seems like there was some regression introduced into the kernel somewhere for the alsa module. I stumbled upon:
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-February/131541.html
After making sure my kernel has
CONFIG_SND_DYNAMIC_MINORS=y
Then rebuild and the oops is going away for me. It feels a bit strange, because the cited regression commit is from 2017, and i am not sure it got comitted, or if it just was now re-introduced by accident... |
|
| Back to top |
|
|
IsLo
n00b
Joined: 11 Jul 2018
Posts: 4
|
| Posted: Tue Jul 24, 2018 12:11 pm Post subject: |
|
|
| TequilaTR wrote: | Ok guys, I think i solved the one for me, maybe it helps you as well:
Seems like there was some regression introduced into the kernel somewhere for the alsa module. I stumbled upon:
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-February/131541.html
After making sure my kernel has
CONFIG_SND_DYNAMIC_MINORS=y
Then rebuild and the oops is going away for me. It feels a bit strange, because the cited regression commit is from 2017, and i am not sure it got comitted, or if it just was now re-introduced by accident... |
After rebuilding my kernel with the above option the last 5 poweroffs have gone without a hitch. So I would say that indeed fixes things, and I need no more consider going back down to the older kernels. Thanks for the help! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
