nvidia 346.35-2 breaks DRM (??)

Kilzool · 2015-01-19 01:01:47

Recently upgraded...[2015-01-18 19:23]

upgraded nvidia-utils (343.36-1 -> 346.35-2)
upgraded nvidia-libgl (343.36-1 -> 346.35-2)
upgraded libvdpau (0.8-1 -> 0.9-1)
upgraded nvidia (343.36-6 -> 346.35-2)

#> sudo journalctl -b

Jan 18 19:42:00 arch-1 kernel: ------------[ cut here ]------------
Jan 18 19:42:00 arch-1 kernel: WARNING: CPU: 0 PID: 371 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x185/0x190 [drm]()
Jan 18 19:42:00 arch-1 kernel: No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm
Jan 18 19:42:00 arch-1 kernel: Modules linked in:
Jan 18 19:42:00 arch-1 kernel:  ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype snd_hda
Jan 18 19:42:00 arch-1 kernel:  atkbd libps2 ata_piix ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common 
Jan 18 19:42:00 arch-1 kernel: CPU: 0 PID: 371 Comm: Xorg.bin Tainted: P        W  O   3.18.2-2-ARCH #1
Jan 18 19:42:00 arch-1 kernel: Hardware name: Dell Inc.                 Dell DXP051                  /0FJ030, BIOS A07 01/08/2007
Jan 18 19:42:00 arch-1 kernel:  00000000 f86ca031 00000000 f1b69dcc c1474f33 f1b69e10 f1b69e00 c10527f2
Jan 18 19:42:00 arch-1 kernel:  f8371258 f1b69e30 00000173 f836f150 0000008f f834c725 0000008f f834c725
Jan 18 19:42:00 arch-1 kernel:  f1b69e88 f3964c00 ffffffea f1b69e1c c105284e 00000009 f1b69e10 f8371258
Jan 18 19:42:00 arch-1 kernel: Call Trace:
Jan 18 19:42:00 arch-1 kernel:  [<c1474f33>] dump_stack+0x48/0x69
Jan 18 19:42:00 arch-1 kernel:  [<c10527f2>] warn_slowpath_common+0x82/0xa0
Jan 18 19:42:00 arch-1 kernel:  [<f834c725>] ? drm_setversion+0x185/0x190 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<f834c725>] ? drm_setversion+0x185/0x190 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<c105284e>] warn_slowpath_fmt+0x3e/0x60
Jan 18 19:42:00 arch-1 kernel:  [<f834c725>] drm_setversion+0x185/0x190 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<f834c5a0>] ? drm_noop+0x40/0x40 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<f834c23c>] drm_ioctl+0x2bc/0x560 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<f834c5a0>] ? drm_noop+0x40/0x40 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<c11b4d88>] ? fsnotify+0x3c8/0x5a0
Jan 18 19:42:00 arch-1 kernel:  [<c118a64d>] ? do_filp_open+0x3d/0xa0
Jan 18 19:42:00 arch-1 kernel:  [<f834bf80>] ? drm_copy_field+0x70/0x70 [drm]
Jan 18 19:42:00 arch-1 kernel:  [<c118cca2>] do_vfs_ioctl+0x302/0x4f0
Jan 18 19:42:00 arch-1 kernel:  [<c11965d8>] ? __alloc_fd+0x88/0x100
Jan 18 19:42:00 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:42:00 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:42:00 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:42:00 arch-1 kernel:  [<c117b114>] ? do_sys_open+0x1b4/0x240
Jan 18 19:42:00 arch-1 kernel:  [<c118cf10>] SyS_ioctl+0x80/0x90
Jan 18 19:42:00 arch-1 kernel:  [<c1479cd7>] sysenter_do_call+0x12/0x12
Jan 18 19:42:00 arch-1 kernel: ---[ end trace 22f22181de2f7fb7 ]---

Jan 18 19:41:59 arch-1 kernel: ------------[ cut here ]------------
Jan 18 19:41:59 arch-1 kernel: WARNING: CPU: 0 PID: 371 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x185/0x190 [drm]()
Jan 18 19:41:59 arch-1 kernel: No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm
Jan 18 19:41:59 arch-1 kernel: Modules linked in:
Jan 18 19:41:59 arch-1 kernel:  ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype snd_hda
Jan 18 19:41:59 arch-1 kernel:  atkbd libps2 ata_piix ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common 
Jan 18 19:41:59 arch-1 kernel: CPU: 0 PID: 371 Comm: Xorg.bin Tainted: P        W  O   3.18.2-2-ARCH #1
Jan 18 19:41:59 arch-1 kernel: Hardware name: Dell Inc.                 Dell DXP051                  /0FJ030, BIOS A07 01/08/2007
Jan 18 19:41:59 arch-1 kernel:  00000000 f86ca031 00000000 f1b69dcc c1474f33 f1b69e10 f1b69e00 c10527f2
Jan 18 19:41:59 arch-1 kernel:  f8371258 f1b69e30 00000173 f836f150 0000008f f834c725 0000008f f834c725
Jan 18 19:41:59 arch-1 kernel:  f1b69e88 f3964c00 ffffffea f1b69e1c c105284e 00000009 f1b69e10 f8371258
Jan 18 19:41:59 arch-1 kernel: Call Trace:
Jan 18 19:41:59 arch-1 kernel:  [<c1474f33>] dump_stack+0x48/0x69
Jan 18 19:41:59 arch-1 kernel:  [<c10527f2>] warn_slowpath_common+0x82/0xa0
Jan 18 19:41:59 arch-1 kernel:  [<f834c725>] ? drm_setversion+0x185/0x190 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c725>] ? drm_setversion+0x185/0x190 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<c105284e>] warn_slowpath_fmt+0x3e/0x60
Jan 18 19:41:59 arch-1 kernel:  [<f834c725>] drm_setversion+0x185/0x190 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c5a0>] ? drm_noop+0x40/0x40 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c23c>] drm_ioctl+0x2bc/0x560 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c5a0>] ? drm_noop+0x40/0x40 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<c118a64d>] ? do_filp_open+0x3d/0xa0
Jan 18 19:41:59 arch-1 kernel:  [<f834bf80>] ? drm_copy_field+0x70/0x70 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<c118cca2>] do_vfs_ioctl+0x302/0x4f0
Jan 18 19:41:59 arch-1 kernel:  [<c11965d8>] ? __alloc_fd+0x88/0x100
Jan 18 19:41:59 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:41:59 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:41:59 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:41:59 arch-1 kernel:  [<c117b114>] ? do_sys_open+0x1b4/0x240
Jan 18 19:41:59 arch-1 kernel:  [<c118cf10>] SyS_ioctl+0x80/0x90
Jan 18 19:41:59 arch-1 kernel:  [<c1479cd7>] sysenter_do_call+0x12/0x12
Jan 18 19:41:59 arch-1 kernel: ---[ end trace 22f22181de2f7fb5 ]---
Jan 18 19:41:59 arch-1 kernel: ------------[ cut here ]------------
Jan 18 19:41:59 arch-1 kernel: WARNING: CPU: 0 PID: 371 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x185/0x190 [drm]()
Jan 18 19:41:59 arch-1 kernel: No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm
Jan 18 19:41:59 arch-1 kernel: Modules linked in:
Jan 18 19:41:59 arch-1 kernel:  ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype snd_hda
Jan 18 19:41:59 arch-1 kernel:  atkbd libps2 ata_piix ahci libahci libata scsi_mod ehci_pci uhci_hcd ehci_hcd usbcore usb_common 
Jan 18 19:41:59 arch-1 kernel: CPU: 0 PID: 371 Comm: Xorg.bin Tainted: P        W  O   3.18.2-2-ARCH #1
Jan 18 19:41:59 arch-1 kernel: Hardware name: Dell Inc.                 Dell DXP051                  /0FJ030, BIOS A07 01/08/2007
Jan 18 19:41:59 arch-1 kernel:  00000000 f86ca031 00000000 f1b69dcc c1474f33 f1b69e10 f1b69e00 c10527f2
Jan 18 19:41:59 arch-1 kernel:  f8371258 f1b69e30 00000173 f836f150 0000008f f834c725 0000008f f834c725
Jan 18 19:41:59 arch-1 kernel:  f1b69e88 f3964c00 ffffffea f1b69e1c c105284e 00000009 f1b69e10 f8371258
Jan 18 19:41:59 arch-1 kernel: Call Trace:
Jan 18 19:41:59 arch-1 kernel:  [<c1474f33>] dump_stack+0x48/0x69
Jan 18 19:41:59 arch-1 kernel:  [<c10527f2>] warn_slowpath_common+0x82/0xa0
Jan 18 19:41:59 arch-1 kernel:  [<f834c725>] ? drm_setversion+0x185/0x190 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c725>] ? drm_setversion+0x185/0x190 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<c105284e>] warn_slowpath_fmt+0x3e/0x60
Jan 18 19:41:59 arch-1 kernel:  [<f834c725>] drm_setversion+0x185/0x190 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c5a0>] ? drm_noop+0x40/0x40 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c23c>] drm_ioctl+0x2bc/0x560 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<f834c5a0>] ? drm_noop+0x40/0x40 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<c118a64d>] ? do_filp_open+0x3d/0xa0
Jan 18 19:41:59 arch-1 kernel:  [<f834bf80>] ? drm_copy_field+0x70/0x70 [drm]
Jan 18 19:41:59 arch-1 kernel:  [<c118cca2>] do_vfs_ioctl+0x302/0x4f0
Jan 18 19:41:59 arch-1 kernel:  [<c11965d8>] ? __alloc_fd+0x88/0x100
Jan 18 19:41:59 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:41:59 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:41:59 arch-1 kernel:  [<c1189d6d>] ? final_putname+0x1d/0x40
Jan 18 19:41:59 arch-1 kernel:  [<c117b114>] ? do_sys_open+0x1b4/0x240
Jan 18 19:41:59 arch-1 kernel:  [<c118cf10>] SyS_ioctl+0x80/0x90
Jan 18 19:41:59 arch-1 kernel:  [<c1479cd7>] sysenter_do_call+0x12/0x12
Jan 18 19:41:59 arch-1 kernel: ---[ end trace 22f22181de2f7fb6 ]---
Jan 18 19:42:00 arch-1 acpid[352]: client connected from 371[0:0]
Jan 18 19:42:00 arch-1 acpid[352]: 1 client rule loaded
Jan 18 19:42:00 arch-1 kernel: ------------[ cut here ]------------

#> uname -a

Linux arch-1 3.18.2-2-ARCH #1 SMP PREEMPT Fri Jan 9 07:23:08 CET 2015 i686 GNU/Linux

Last edited by Kilzool (2015-01-19 06:42:16)

Zeroedout · 2015-01-19 09:44:00

Confirmed here with a gtx 760...

hickop · 2015-01-19 10:00:24

Cannot start X because of that it seams.
http://sprunge.us/MhLa

PS: Fixed for me with nvidia 346.35-3

Last edited by hickop (2015-01-19 10:31:56)

firekage · 2015-01-19 10:28:33

Hm...i think that something was wrong because i can't log into KDE. As soon as i type password, kde kicks me off from logging to login prompt again and again. GTX660.

Last edited by firekage (2015-01-19 10:29:17)

Zeroedout · 2015-01-19 10:49:40

Yay, glad to know it's been fixed! My mirrors haven't syncd yet so I found a workaround. It seems just adding a device section to xorg.conf fixes it,

Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection

worked for me.
Thank you reddit http://www.reddit.com/r/archlinux/comme … ens_found/

Last edited by Zeroedout (2015-01-19 10:50:21)

Foucault · 2015-01-19 10:55:37

I had the same errors in dmesg, X starts in vesa mode. Same errors again when I reload the nvidia module.

firekage wrote:

Hm...i think that something was wrong because i can't log into KDE. As soon as i type password, kde kicks me off from logging to login prompt again and again. GTX660.

Check dmesg for similar errors, we can't be sure it's the same issue otherwise.

Does this help anyone? I am not on my nvidia+arch computer so I can't test it now. Otherwise, if it is not a configuration issue a bug report must be opened with the gathered information from dmesg and Xorg.log. However at least for 1 GPU configuration manually entering the BusID should not be required, which means it's probably an upstream bug.

This seems to be the same BusID issue. You could also try the solution mentioned there.

firekage · 2015-01-19 12:46:39

Foucault wrote:

I had the same errors in dmesg, X starts in vesa mode. Same errors again when I reload the nvidia module.
firekage wrote:
Hm...i think that something was wrong because i can't log into KDE. As soon as i type password, kde kicks me off from logging to login prompt again and again. GTX660.
Check dmesg for similar errors, we can't be sure it's the same issue otherwise.
Does this help anyone? I am not on my nvidia+arch computer so I can't test it now. Otherwise, if it is not a configuration issue a bug report must be opened with the gathered information from dmesg and Xorg.log. However at least for 1 GPU configuration manually entering the BusID should not be required, which means it's probably an upstream bug.
This seems to be the same BusID issue. You could also try the solution mentioned there.

I checked several times of dmesg, journalctl and xorg.0.log. I think that there is no error related this problem. It happened after update.

This is the only "error" from xorg, when generate xorg.conf by typing nvidia-xconfig
http://imgur.com/gHar2vS

This is from dmesg
http://imgur.com/IP2I2Zg
-nvidia taints kernel so domething was disabled? System loads ok, i cant enter gui, cant log in to kde, it blink for a second, then kick me again to login prompt

This is something with nvidia and console, don't know it meaning
http://imgur.com/qCrFtNm
http://imgur.com/XiBbglR

I tried to move .kde4 to .kde4.bak than reboot. Nothing was solved, still can't log to kde. I even deleted krandrrc, the same thing happened, can't log. I created new user, and the same thing happened, can't log even to kde with this new created user.

Don't know how to fix it. I can't use machine, must sit on Windows...

Kilzool · 2015-01-20 17:21:07

Upgraded today...

[2015-01-20 12:07] [ALPM] upgraded nvidia (346.35-2 -> 346.35-3)

Now, the dmesg and journalctl do NOT show errors. So solved?

However, when running nvidia-settings from the console...
I get this warning:

** (nvidia-settings:742): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

After I get that warning in the console, I get a CORE DUMP.
Aborted (core dumped) (I have coredumps turned off)

NOTE: If I do "sudo nvidia-setttings" (from the console -- I DO NOT get the above warning, and I do not see a CORE DUMP message.

Last edited by Kilzool (2015-01-20 17:26:51)

Arch Linux

#1 2015-01-19 01:01:47

nvidia 346.35-2 breaks DRM (??)

#2 2015-01-19 09:44:00

Re: nvidia 346.35-2 breaks DRM (??)

#3 2015-01-19 10:00:24

Re: nvidia 346.35-2 breaks DRM (??)

#4 2015-01-19 10:28:33

Re: nvidia 346.35-2 breaks DRM (??)

#5 2015-01-19 10:49:40

Re: nvidia 346.35-2 breaks DRM (??)

#6 2015-01-19 10:55:37

Re: nvidia 346.35-2 breaks DRM (??)

#7 2015-01-19 12:46:39

Re: nvidia 346.35-2 breaks DRM (??)

#8 2015-01-20 17:21:07

Re: nvidia 346.35-2 breaks DRM (??)

Board footer