Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#62644 - [nvidia-340xx] Crashes after update to kernel 5.1.2.arch1-1

Attached to Project: Arch Linux
Opened by silvrax (silvrax) - Wednesday, 15 May 2019, 22:44 GMT
Last edited by Jan Alexander Steffens (heftig) - Thursday, 16 May 2019, 21:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:

After updating the kernel to 5.1.2.arch1-1 graphics system is broken.

Additional info:
* package version(s) linux-5.1.2.arch1-1 and nvidia-340xx-340.107-82

* config and/or log files etc.

May 15 22:56:10 arch kernel: nvidia: module license 'NVIDIA' taints kernel.
May 15 22:56:10 arch kernel: Disabling lock debugging due to kernel taint
May 15 22:56:10 arch kernel: hidraw: raw HID events driver (C) Jiri Kosina
May 15 22:56:10 arch kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
May 15 22:56:10 arch kernel: WARNING: CPU: 7 PID: 391 at drivers/gpu/drm/drm_pci.c:299 drm_legacy_pci_init+0xb9/0xd0 [drm]
May 15 22:56:10 arch kernel: Modules linked in: snd_usbmidi_lib hid nvidia(POE+) snd_rawmidi snd_seq_device intel_powerclamp coretemp kvm_intel iTCO_wdt gpio_ich iTCO_vendor_support mxm_wmi snd_hda_codec_realtek kvm snd_hda>
May 15 22:56:10 arch kernel: CPU: 7 PID: 391 Comm: systemd-udevd Tainted: P OE 5.1.2-arch1-1-ARCH #1
May 15 22:56:10 arch kernel: Hardware name: MICRO-STAR INTERNATIONAL CO.,LTD MS-7583/P55-GD65 (MS-7583) , BIOS V1.6 12/28/2009
May 15 22:56:10 arch kernel: RIP: 0010:drm_legacy_pci_init+0xb9/0xd0 [drm]
May 15 22:56:10 arch kernel: Code: de e8 db fd ff ff 8b 3b eb bd 41 83 c4 01 49 63 dc 48 c1 e3 05 49 03 5d 18 8b 3b 85 ff 75 a5 5b 31 c0 5d 41 5c 41 5d 41 5e c3 <0f> 0b b8 ea ff ff ff 5b 5d 41 5c 41 5d 41 5e c3 0f 1f 80 00 >
May 15 22:56:10 arch kernel: RSP: 0018:ffffb2f9814f7c28 EFLAGS: 00010246
May 15 22:56:10 arch kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00000000000a9007
May 15 22:56:10 arch kernel: RDX: 00000000000a8e07 RSI: ffffffffc072ee25 RDI: 0000000000000001
May 15 22:56:10 arch kernel: RBP: ffffffffc1533de0 R08: 00000000000271a0 R09: ffffffffa10743e6
May 15 22:56:10 arch kernel: R10: fffff6240883fc00 R11: 0000000000000000 R12: 0000000000000001
May 15 22:56:10 arch kernel: R13: ffffffffc1533c00 R14: ffffb2f9814f7e88 R15: ffffffffc1534a00
May 15 22:56:10 arch kernel: FS: 00007f120b996840(0000) GS:ffff8e0967bc0000(0000) knlGS:0000000000000000
May 15 22:56:10 arch kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 15 22:56:10 arch kernel: CR2: 00007f1209ee7000 CR3: 00000002257b2000 CR4: 00000000000006e0
May 15 22:56:10 arch kernel: Call Trace:
May 15 22:56:10 arch kernel: nvidia_init_module+0x2ed/0x758 [nvidia]
May 15 22:56:10 arch kernel: ? _raw_spin_unlock+0x16/0x30
May 15 22:56:10 arch kernel: ? nv_drm_init+0x14/0x14 [nvidia]
May 15 22:56:10 arch kernel: nvidia_frontend_init_module+0x4d/0x894 [nvidia]
May 15 22:56:10 arch kernel: do_one_initcall+0x46/0x1f5
May 15 22:56:10 arch kernel: ? kmem_cache_alloc_trace+0x169/0x1c0
May 15 22:56:10 arch kernel: ? do_init_module+0x22/0x210
May 15 22:56:10 arch kernel: do_init_module+0x5a/0x210
May 15 22:56:10 arch kernel: load_module+0x202c/0x22c0
May 15 22:56:10 arch kernel: ? vmap_page_range_noflush+0x23f/0x350
May 15 22:56:10 arch kernel: ? __se_sys_init_module+0x10a/0x170
May 15 22:56:10 arch kernel: __se_sys_init_module+0x10a/0x170
May 15 22:56:10 arch kernel: do_syscall_64+0x5b/0x180
May 15 22:56:10 arch kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9
May 15 22:56:10 arch kernel: RIP: 0033:0x7f120d35d71e
May 15 22:56:10 arch kernel: Code: 48 8b 0d 45 37 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 12 37 0c 00 f7 d8 64 89 >
May 15 22:56:10 arch kernel: RSP: 002b:00007ffd629b4528 EFLAGS: 00000246 ORIG_RAX: 00000000000000af
May 15 22:56:10 arch kernel: RAX: ffffffffffffffda RBX: 0000562809c51d10 RCX: 00007f120d35d71e
May 15 22:56:10 arch kernel: RDX: 00007f120cfc684d RSI: 0000000000dd54f8 RDI: 00007f1209112010
May 15 22:56:10 arch kernel: RBP: 00007f120cfc684d R08: 0000000000000008 R09: 0000000000000046
May 15 22:56:10 arch kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007f1209112010
May 15 22:56:10 arch kernel: R13: 0000562809c4a910 R14: 0000000000020000 R15: 0000562809c51d10
May 15 22:56:10 arch kernel: ---[ end trace 12e753b8e7969885 ]---
May 15 22:56:10 arch kernel: NVRM: DRM init failed

* link to upstream bug report, if any

https://devtalk.nvidia.com/default/topic/1051609/linux/any-love-for-340-y-410-y-and-5-1-/

Steps to reproduce:

* Apply these updates:
linux 5.0.13.arch1-1 -> 5.1.2.arch1-1
linux-headers 5.0.13.arch1-1 -> 5.1.2.arch1-1
nvidia-340xx 340.107-80 -> 340.107-82
* Reboot and try to start lightdm
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Thursday, 16 May 2019, 21:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  patch updated in 340.107-83; thanks.
Comment by John Bug (johnbug) - Wednesday, 15 May 2019, 22:59 GMT
Confirmed.
Comment by loqs (loqs) - Wednesday, 15 May 2019, 23:32 GMT
https://github.com/torvalds/linux/commit/0e2a933b02c972919f7478364177eb76cd4ae00d DRIVER_LERGACY is no longer defined
updated kernel-5.1.patch
Edit:
added src.tar.gz for easier build testing
Comment by Serge (Viterzgir) - Thursday, 16 May 2019, 16:16 GMT
Yep also have this issue with latest kernel 5.1.2.arch1-1.
Comment by Krisztián Hordósi (hordosikrisztian) - Thursday, 16 May 2019, 16:22 GMT
I'm also experiencing the same issue with the above kernel version and nvidia-340 package.
Comment by loqs (loqs) - Thursday, 16 May 2019, 16:50 GMT
Is the issue still present with the proposed solution from https://bugs.archlinux.org/task/62644#comment179283 ?
Comment by Roman Brusentsov (Gavcheg) - Thursday, 16 May 2019, 18:05 GMT
I use patches from "https://git.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/nvidia-340xx" and then apply another one:

--- kernel/nv-drm.c 2018-05-25 06:16:20.000000000 +0200
+++ kernel/nv-drm.c 2019-05-09 20:51:33.364278935 +0200
@@ -146,11 +146,7 @@
};

static struct drm_driver nv_drm_driver = {
-#if defined(DRIVER_LEGACY)
.driver_features = DRIVER_GEM | DRIVER_PRIME | DRIVER_LEGACY,
-#else
- .driver_features = DRIVER_GEM | DRIVER_PRIME,
-#endif
.load = nv_drm_load,
.unload = nv_drm_unload,
.fops = &nv_drm_fops,

After that, driver build and work fine.

Loading...