Bug 14832 - nVidia driver kernel error
Summary: nVidia driver kernel error
Status: RESOLVED DUPLICATE of bug 14769
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Anssi Hannula
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-18 02:12 CET by Juan Magallon
Modified: 2014-12-19 08:58 CET (History)
3 users (show)

See Also:
Source RPM: nvidia-current-340.65-1.mga5.nonfree.src.rpm
CVE:
Status comment:


Attachments

Description Juan Magallon 2014-12-18 02:12:05 CET
Using the nVidia propietary driver, I get this error on dmesg:

[   23.911482] No drm_driver.set_busid() implementation provided by nv_drm_driver [nvidia]. Use drm_dev_set_unique() to set the unique name explicitly.

followed by a backtrace.
Possible solution/patch is 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/

Could you pick the patch ?
TIA

Reproducible: 

Steps to Reproduce:
Sander Lepik 2014-12-18 08:28:21 CET

CC: (none) => mageia, tmb
Assignee: bugsquad => anssi.hannula

Comment 1 Thomas Backlund 2014-12-18 16:19:08 CET
Fix merged in nvidia-current-340.65-2.mga5, thanks for the pointer

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

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE

Comment 2 Juan Magallon 2014-12-19 00:04:47 CET
For some reason the patch is incorect, it does not build with current kernel.
The hunks like:

-    return nvidia_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+    return nvidia_ioctl(file->f_path.f_dentry->d_inode, file, cmd, i_arg);

should look like

-    return nvidia_ioctl(file->f_dentry->d_inode, file, cmd, i_arg);
+    return nvidia_ioctl(file->f_path.dentry->d_inode, file, cmd, i_arg);

Note the chage from 'f_dentry' to just 'dentry'.
There are 3 of them.

Probably this was introduced in 3.18.1, and patch was born for 3.18.0...

CC: (none) => jamagallon

Comment 3 Thomas Backlund 2014-12-19 08:58:14 CET
Nope, it was me messing it up with a too quick c/p :/

fixed in nvidia-current-340.65-3.mga5 and confirmed with the kmod-nvidia-current-340.65-5.mga5 build

Note You need to log in before you can comment on or make changes to this bug.