Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 541184 - x11-drivers/nvidia-drivers-346.36 on kernel 3.18.7: No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly
Summary: x11-drivers/nvidia-drivers-346.36 on kernel 3.18.7: No drm_driver.set_busid()...
Status: RESOLVED DUPLICATE of bug 532082
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Jeroen Roovers (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-23 22:21 UTC by Paul McDermott
Modified: 2015-03-04 14:03 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul McDermott 2015-02-23 22:21:19 UTC 
x11-drivers/nvidia-drivers-346.35 complains "No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly." on boot, resulting in something crashing (nvidia driver still appears to load & works OK).

Full demsg mesage:

[  951.947444] ------------[ cut here ]------------
[  951.947453] WARNING: CPU: 1 PID: 3811 at drivers/gpu/drm/drm_ioctl.c:143 drm_setversion+0x159/0x160 [drm]()
[  951.947495] No drm_driver.set_busid() implementation provided by nvidia_frontend_exit_module [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.
[  951.947496] Modules linked in:
[  951.947497]  usbhid ath9k ath9k_common nvidia(PO) ath9k_hw ath i2c_i801 led_class drm
[  951.947502] CPU: 1 PID: 3811 Comm: Xorg Tainted: P        W  O   3.18.7-gentoo #1
[  951.947503] Hardware name: System manufacturer System Product Name/P6T SE, BIOS 0808    03/08/2010
[  951.947504]  00000009 c1520097 f2d19e34 c103a299 f81c1e60 f2d19e4c 00000ee3 f81c0811
[  951.947507]  0000008f f81a0c79 f81a0c79 f2d19e9c f1f72000 ffffffea f31fb440 c103a2e3
[  951.947509]  00000009 f2d19e34 f81c1e60 f2d19e4c f81a0c79 f81c0811 0000008f f81c1e60
[  951.947512] Call Trace:
[  951.947516]  [<c1520097>] ? dump_stack+0x45/0x65
[  951.947519]  [<c103a299>] ? warn_slowpath_common+0x79/0x90
[  951.947523]  [<f81a0c79>] ? drm_setversion+0x159/0x160 [drm]
[  951.947526]  [<f81a0c79>] ? drm_setversion+0x159/0x160 [drm]
[  951.947528]  [<c103a2e3>] ? warn_slowpath_fmt+0x33/0x40
[  951.947531]  [<f81a0c79>] ? drm_setversion+0x159/0x160 [drm]
[  951.947535]  [<f81a0b20>] ? drm_noop+0x30/0x30 [drm]
[  951.947538]  [<f81a0820>] ? drm_ioctl+0x260/0x4b0 [drm]
[  951.947541]  [<f81a0b20>] ? drm_noop+0x30/0x30 [drm]
[  951.947543]  [<c10e1d73>] ? path_openat+0xa3/0x590
[  951.947546]  [<c10ac686>] ? release_pages+0x156/0x1b0
[  951.947548]  [<c10e2ca7>] ? do_filp_open+0x27/0x70
[  951.947551]  [<f81a05c0>] ? drm_copy_field+0x50/0x50 [drm]
[  951.947553]  [<c10e4f87>] ? do_vfs_ioctl+0x327/0x530
[  951.947555]  [<c10ed8a1>] ? __alloc_fd+0x81/0xf0
[  951.947556]  [<c10ed954>] ? __fd_install+0x14/0x40
[  951.947559]  [<c10d51c7>] ? do_sys_open+0x197/0x210
[  951.947561]  [<c10ed38f>] ? __fget+0x4f/0x80
[  951.947562]  [<c10e51cc>] ? SyS_ioctl+0x3c/0x70
[  951.947565]  [<c1525735>] ? syscall_call+0x7/0x7
[  951.947566]  [<c1520000>] ? cipher_crypt_unaligned+0x2/0x52
[  951.947567] ---[ end trace 71f32390af0dcb39 ]---

A patch here:
https://devtalk.nvidia.com/default/topic/796559/linux/kernel-3-18-warning-no-drm_driver-set_busid-implementation-provided-by-nvidia_frontend_exit_modu/

suggests that this is an issue with the nvidia driver for 3.18 kernels.

NB See the note at the bottom for the 346.35 specific patch.
Comment 1 Max Klinger 2015-02-24 19:18:48 UTC 
I am having the same issue, but for me it isn't working OK after that. The Screen stays black, no change past this point. This was a bit suprising given that the kernel and the nvidia-drivers are both stable version now. I will give the patch a try.
Comment 2 Paul McDermott 2015-02-24 19:32:31 UTC 
It looks (to me) like it is the drm module that is crashing, but the drm module is loaded on my system...

[5008:~]$ lsmod
Module                  Size  Used by
usbhid                 16378  0 
ath9k                  84626  0 
ath9k_common           11766  1 ath9k
nvidia               7504748  26 
ath9k_hw              399859  2 ath9k_common,ath9k
ath                    16016  3 ath9k_common,ath9k,ath9k_hw
i2c_i801                8434  0 
led_class               2183  1 ath9k
drm                   188646  2 nvidia
Comment 3 Tomáš "tpruzina" Pružina (amd64 [ex]AT) 2015-03-01 22:28:29 UTC 
This is a bug only present in newer kernel versions, there is a simple patch on nvidia dev forums for it.
Apart from putting kernel into "tainted" state and producing bunch of warnings there is no other impact however.
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2015-03-04 14:03:18 UTC 
(In reply to Tomáš "tpruzina" Pružina (amd64 AT) from comment #3)
> This is a bug only present in newer kernel versions, there is a simple patch
> on nvidia dev forums for it.
> Apart from putting kernel into "tainted" state and producing bunch of
> warnings there is no other impact however.

The proprietary nvidia driver /always/ puts the kernel in the "tainted" state. This has nothing to do with the issue of this bug report.

But the good news is that version 346.47 has this fixed.

*** This bug has been marked as a duplicate of bug 532082 ***