You are not logged in.

#1 2018-10-27 19:00:54

engelmarkus
Member
Registered: 2018-10-27
Posts: 2

Oops with linux 4.19 and nvidia-dkms

Hi,
I've installed

linux-4.19.arch1-1
linux-headers-4.19.arch1-1
nvidia-390xx-dkms-390.87-9

from testing and I've noticed that when the kernel command line contains "nvidia-drm.modeset=1", starting xfwm4 will trigger a kernel oops:

kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000080
kernel: PGD 0 P4D 0
kernel: Oops: 0000 [#1] PREEMPT SMP PTI
kernel: CPU: 2 PID: 1390 Comm: xfwm4 Tainted: P        W  OE     4.19.0-arch1-1-ARCH #1
kernel: Hardware name: System manufacturer System Product Name/P8P67 REV 3.1, BIOS 3602 11/01/2012
kernel: RIP: 0010:drm_lease_owner+0xd/0x20 [drm]
kernel: Code: 83 c4 18 5b 5d c3 b8 ea ff ff ff eb e2 b8 ed ff ff ff eb db e8 a4 b9 7b ce 0f 1f 40 00 66 66 66 66 90 48 89 f8 eb 03 48 89 d0 <48> 8b 90 80 00 00 00 48 85 d2 75 f1 c3 66 0f 1f 44 00 00 66 66 66
kernel: RSP: 0018:ffffb9df42dabbb0 EFLAGS: 00010202
kernel: RAX: 0000000000000000 RBX: ffff9dabd57e4200 RCX: ffff9dabd57e4288
kernel: RDX: ffff9dabd54a5ac0 RSI: 0000000000000000 RDI: 0000000000000000
kernel: RBP: ffff9dac0b6ae000 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: fffffc8c8b5193c0 R11: fffffc8c8b71a408 R12: ffff9dac0b6ae088
kernel: R13: 0000000000000000 R14: dead000000000200 R15: ffff9dabd57e42c8
kernel: FS:  00007f6572865040(0000) GS:ffff9dac12b00000(0000) knlGS:0000000000000000
kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 0000000000000080 CR3: 00000002d1f44001 CR4: 00000000000606e0
kernel: Call Trace:
kernel:  drm_is_current_master+0x1a/0x30 [drm]
kernel:  drm_master_release+0x3e/0x130 [drm]
kernel:  drm_file_free.part.0+0x2be/0x2d0 [drm]
kernel:  drm_open+0x1ba/0x1e0 [drm]
kernel:  drm_stub_open+0xaf/0xe0 [drm]
kernel:  chrdev_open+0xa3/0x1b0
kernel:  ? cdev_put.part.0+0x20/0x20
kernel:  do_dentry_open+0x132/0x340
kernel:  path_openat+0x2d1/0x14e0
kernel:  ? mem_cgroup_commit_charge+0x7a/0x520
kernel:  ? __switch_to_asm+0x34/0x70
kernel:  ? __switch_to_asm+0x40/0x70
kernel:  ? __switch_to_asm+0x34/0x70
kernel:  do_filp_open+0x93/0x100
kernel:  ? __check_object_size+0x102/0x189
kernel:  ? _raw_spin_unlock+0x16/0x30
kernel:  do_sys_open+0x186/0x210
kernel:  do_syscall_64+0x5b/0x170
kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
kernel: RIP: 0033:0x7f6575c388ef
kernel: Code: 52 89 f0 25 00 00 41 00 3d 00 00 41 00 74 44 8b 05 be e8 00 00 85 c0 75 65 89 f2 b8 01 01 00 00 48 89 fe bf 9c ff ff ff 0f 05 <48> 3d 00 f0 ff ff 0f 87 9d 00 00 00 48 8b 4c 24 28 64 48 33 0c 25
kernel: RSP: 002b:00007fff330a8a30 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
kernel: RAX: ffffffffffffffda RBX: 000056170fa9cb40 RCX: 00007f6575c388ef
kernel: RDX: 0000000000000002 RSI: 000056170e42069c RDI: 00000000ffffff9c
kernel: RBP: 0000000000000024 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000024
kernel: R13: 0000000000000012 R14: 000056170fa9a500 R15: 0000000000000012
kernel: Modules linked in: fuse bridge stp llc nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_log_ipv4 nf_log_common nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_log nft_counter lz4 lz4_compress nf_tables_set nf_tables nfnetlink nct6775 hwmon_vid snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi btusb btrtl btbcm btintel intel_rapl bluetooth x86_pkg_temp_thermal intel_powerclamp coretemp mousedev ext4 kvm_intel nls_iso8859_1 ecdh_generic mbcache nls_cp437 crc16 jbd2 vfat input_leds fscrypto fat kvm eeepc_wmi asus_wmi sparse_keymap rfkill gpio_ich wmi_bmof led_class iTCO_wdt iTCO_vendor_support irqbypass intel_cstate snd_hda_intel intel_uncore snd_hda_codec intel_rapl_perf pcspkr snd_hda_core realtek snd_hwdep r8169 snd_pcm i2c_i801 libphy snd_timer mei_me snd mei wmi lpc_ich
kernel:  soundcore evdev mac_hid pcc_cpufreq vboxnetflt(OE) vboxnetadp(OE) vboxpci(OE) vboxdrv(OE) sg crypto_user binder_linux(OE) ashmem_linux(OE) ip_tables x_tables btrfs libcrc32c crc32c_generic xor raid6_pq dm_crypt algif_skcipher af_alg hid_generic usbhid hid uas usb_storage dm_mod sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc ahci libahci libata aesni_intel firewire_ohci xhci_pci aes_x86_64 xhci_hcd crypto_simd firewire_core cryptd glue_helper scsi_mod crc_itu_t ehci_pci ehci_hcd nvidia_drm(POE) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm agpgart nvidia_uvm(POE) nvidia_modeset(POE) nvidia(POE) ipmi_devintf ipmi_msghandler
kernel: CR2: 0000000000000080
kernel: ---[ end trace bc802da8848412c9 ]---
kernel: RIP: 0010:drm_lease_owner+0xd/0x20 [drm]
kernel: Code: 83 c4 18 5b 5d c3 b8 ea ff ff ff eb e2 b8 ed ff ff ff eb db e8 a4 b9 7b ce 0f 1f 40 00 66 66 66 66 90 48 89 f8 eb 03 48 89 d0 <48> 8b 90 80 00 00 00 48 85 d2 75 f1 c3 66 0f 1f 44 00 00 66 66 66
kernel: RSP: 0018:ffffb9df42dabbb0 EFLAGS: 00010202
kernel: RAX: 0000000000000000 RBX: ffff9dabd57e4200 RCX: ffff9dabd57e4288
kernel: RDX: ffff9dabd54a5ac0 RSI: 0000000000000000 RDI: 0000000000000000
kernel: RBP: ffff9dac0b6ae000 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: fffffc8c8b5193c0 R11: fffffc8c8b71a408 R12: ffff9dac0b6ae088
kernel: R13: 0000000000000000 R14: dead000000000200 R15: ffff9dabd57e42c8
kernel: FS:  00007f6572865040(0000) GS:ffff9dac12b00000(0000) knlGS:0000000000000000
kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 0000000000000080 CR3: 00000002d1f44001 CR4: 00000000000606e0

When I omit this command line argument, everything works fine, so I think this version of the nvidia driver needs some more patches?

Markus

Offline

#2 2018-11-16 13:50:18

r3pek
Member
From: Beja, Portugal
Registered: 2013-06-08
Posts: 8
Website

Re: Oops with linux 4.19 and nvidia-dkms

Got the exact same thing on 410.73

Offline

#3 2018-11-16 14:54:30

pmatts
Member
Registered: 2015-02-23
Posts: 23

Re: Oops with linux 4.19 and nvidia-dkms

me too

linux 4.19.1.arch1-1
nvidia 410.73-2

I solved the problem by switching to LTS kernel. I hope it brings me a more peaceful life.

Last edited by pmatts (2018-11-16 15:25:42)

Offline

#4 2018-11-20 08:39:49

CjK
Member
Registered: 2008-10-17
Posts: 18

Re: Oops with linux 4.19 and nvidia-dkms

Same problem here, prevents machine from waking up after suspend and even from locked-screen (using lightdm).

So all we can do is wait for a kernel-upgrade, right?

Offline

#5 2018-11-22 10:43:32

qrwteyrutiyoup
Member
From: Canada
Registered: 2017-12-26
Posts: 16

Re: Oops with linux 4.19 and nvidia-dkms

I encountered this issue a few days ago and submitted a patch upstream that fixed it for me: https://lore.kernel.org/patchwork/patch/1015988/
For the ones with the same problem: perhaps you can build a kernel with it applied to see if it helps?

Offline

#6 2018-11-23 11:48:00

CjK
Member
Registered: 2008-10-17
Posts: 18

Re: Oops with linux 4.19 and nvidia-dkms

@qrwteyrutiyoup

Thanks for taking the time to submit a patch for this - much appreciated!

I'll wait for 4.19.3 ff for your patch to be included.

Offline

#7 2018-11-23 12:41:13

loqs
Member
Registered: 2014-03-06
Posts: 6,370

Re: Oops with linux 4.19 and nvidia-dkms

CjK wrote:

I'll wait for 4.19.3 ff for your patch to be included.

The patch is not in 4.19.3 or 4.19.4 due to it not yet having been merged into linux mainline.

Offline

#8 Yesterday 22:00:48

engelmarkus
Member
Registered: 2018-10-27
Posts: 2

Re: Oops with linux 4.19 and nvidia-dkms

The patch is included in "linux-4.19.8.arch1-1" and fixes the issue for me. Thank you, Sergio!

Offline

Board footer

Powered by FluxBB