Use drm_dev_set_unique() to set the unique name explicitly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Unknown
|
Unknown
|
|||
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
vivid i386 booted with systemd, on nvidia 346.35 driver with 3.19 kernel (canonical kernel team)
Get that syslog trace:
Jan 23 12:38:35 u32 kernel: [ 32.544667] ------------[ cut here ]------------
Jan 23 12:38:35 u32 kernel: [ 32.544695] WARNING: CPU: 0 PID: 998 at /build/
Jan 23 12:38:35 u32 kernel: [ 32.544795] No drm_driver.
Jan 23 12:38:35 u32 kernel: [ 32.544797] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_
Jan 23 12:38:35 u32 kernel: [ 32.544859] CPU: 0 PID: 998 Comm: Xorg Tainted: G OE 3.19.0-2-generic #2-Ubuntu
Jan 23 12:38:35 u32 kernel: [ 32.544861] Hardware name: ASUSTEK COMPUTER INC P5W DH Deluxe/P5W DH Deluxe, BIOS 3002 07/22/2010
Jan 23 12:38:35 u32 kernel: [ 32.544863] 00000000 00000000 f19e7dd4 c16ef07c f19e7e18 f19e7e08 c10618cb f866b2cc
Jan 23 12:38:35 u32 kernel: [ 32.544868] f19e7e34 000003e6 f866b230 0000008f f86447f5 0000008f f86447f5 f19e7e8c
Jan 23 12:38:35 u32 kernel: [ 32.544874] f65e2c00 ffffffea f19e7e20 c1061933 00000009 f19e7e18 f866b2cc f19e7e34
Jan 23 12:38:35 u32 kernel: [ 32.544879] Call Trace:
Jan 23 12:38:35 u32 kernel: [ 32.544887] [<c16ef07c>] dump_stack+
Jan 23 12:38:35 u32 kernel: [ 32.544892] [<c10618cb>] warn_slowpath_
Jan 23 12:38:35 u32 kernel: [ 32.544906] [<f86447f5>] ? drm_setversion+
Jan 23 12:38:35 u32 kernel: [ 32.544917] [<f86447f5>] ? drm_setversion+
Jan 23 12:38:35 u32 kernel: [ 32.544920] [<c1061933>] warn_slowpath_
Jan 23 12:38:35 u32 kernel: [ 32.544932] [<f86447f5>] drm_setversion+
Jan 23 12:38:35 u32 kernel: [ 32.544945] [<f8644670>] ? drm_noop+0x40/0x40 [drm]
Jan 23 12:38:35 u32 kernel: [ 32.544956] [<f864425c>] drm_ioctl+
Jan 23 12:38:35 u32 kernel: [ 32.544967] [<f8644670>] ? drm_noop+0x40/0x40 [drm]
Jan 23 12:38:35 u32 kernel: [ 32.544972] [<c11bee41>] ? do_filp_
Jan 23 12:38:35 u32 kernel: [ 32.544983] [<f8643fa0>] ? drm_getmap+
Jan 23 12:38:35 u32 kernel: [ 32.544987] [<c11c1532>] do_vfs_
Jan 23 12:38:35 u32 kernel: [ 32.544990] [<c11be02d>] ? final_putname+
Jan 23 12:38:35 u32 kernel: [ 32.544992] [<c11be02d>] ? final_putname+
Jan 23 12:38:35 u32 kernel: [ 32.544995] [<c11be274>] ? putname+0x24/0x40
Jan 23 12:38:35 u32 kernel: [ 32.544999] [<c11ae2ad>] ? do_sys_
Jan 23 12:38:35 u32 kernel: [ 32.545002] [<c11c17c0>] SyS_ioctl+0x60/0x90
Jan 23 12:38:35 u32 kernel: [ 32.545006] [<c16f565f>] sysenter_
Jan 23 12:38:35 u32 kernel: [ 32.545008] ---[ end trace 1116205a4e3186e8 ]---
Jan 23 12:38:35 u32 kernel: [ 32.545011] ------------[ cut here ]------------
Jan 23 12:38:35 u32 kernel: [ 32.545022] WARNING: CPU: 0 PID: 998 at /build/
Jan 23 12:38:35 u32 kernel: [ 32.545074] No drm_driver.
Jan 23 12:38:35 u32 kernel: [ 32.545076] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_
Jan 23 12:38:35 u32 kernel: [ 32.545131] CPU: 0 PID: 998 Comm: Xorg Tainted: G W OE 3.19.0-2-generic #2-Ubuntu
tags: | added: bot-stop-nagging vivid |
Changed in linux (Ubuntu): | |
status: | Incomplete → New |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1413971
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.