* Linux 4.1 WARNING in drm_ioctl.c
@ 2015-06-22 14:04 ` Fabio Coatti
0 siblings, 0 replies; 13+ messages in thread
From: Fabio Coatti @ 2015-06-22 14:04 UTC (permalink / raw)
To: David Airlie, dri-devel, kernel list
Hi All,
just compiled 4.1 and just got this warning, twice, in my dmesg:
[lun giu 22 11:43:18 2015] ------------[ cut here ]------------
[lun giu 22 11:43:18 2015] WARNING: CPU: 1 PID: 2184 at
drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0xe1/0x179()
[lun giu 22 11:43:18 2015] No drm_driver.set_busid() implementation provided
by 0xffffffff81ec3980. Use drm_dev_set_unique() to set the unique name
explicitly.
[lun giu 22 11:43:18 2015] Modules linked in:
[lun giu 22 11:43:18 2015] bnep algif_skcipher cdc_wdm cdc_acm uvcvideo
videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev btusb
btbcm btintel bluetooth hp_wmi sparse_keymap intel_rapl iosf_mbi
x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp kvm_intel
kvm snd_hda_codec_generic crct10dif_pclmul crc32_pclmul snd_hda_intel iwldvm
snd_hda_controller snd_hda_codec snd_hwdep psmouse snd_hda_core iwlwifi
snd_pcm snd_timer snd soundcore wmi hp_accel(+) hp_wireless lis3lv02d
sch_fq_codel dm_zero dm_persistent_data dm_service_time dm_round_robin
dm_queue_length dm_multipath dm_delay virtio_pci virtio_blk virtio_balloon
virtio_ring virtio fuse overlay linear raid0 dm_raid dm_snapshot dm_bufio
dm_mirror dm_region_hash dm_log ohci_pci ohci_hcd uhci_hcd
[lun giu 22 11:43:18 2015] CPU: 1 PID: 2184 Comm: X Tainted: G W
4.1.0 #1
[lun giu 22 11:43:18 2015] Hardware name: Hewlett-Packard HP EliteBook Folio
9470m/18DF, BIOS 68IBD Ver. F.40 02/01/2013
[lun giu 22 11:43:18 2015] 0000000000000000 0000000000000009 ffffffff818d8bfd
ffff8800b226fd38
[lun giu 22 11:43:18 2015] ffffffff810c5426 ffff880235437240 ffffffff8152870c
ffff8800b2f16000
[lun giu 22 11:43:18 2015] ffff880234ffc000 ffff8800b226fdf0 ffff8800b2c8f300
00000000c0106407
[lun giu 22 11:43:18 2015] Call Trace:
[lun giu 22 11:43:18 2015] [<ffffffff818d8bfd>] ? dump_stack+0x47/0x67
[lun giu 22 11:43:18 2015] [<ffffffff810c5426>] ?
warn_slowpath_common+0x9d/0xb5
[lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
[lun giu 22 11:43:18 2015] [<ffffffff810c5488>] ? warn_slowpath_fmt+0x4a/0x4f
[lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
[lun giu 22 11:43:18 2015] [<ffffffff81528465>] ? drm_ioctl+0x376/0x3dd
[lun giu 22 11:43:18 2015] [<ffffffff8152862b>] ? drm_version+0x8d/0x8d
[lun giu 22 11:43:18 2015] [<ffffffff811ca766>] ? do_filp_open+0x30/0x74
[lun giu 22 11:43:18 2015] [<ffffffff811cc591>] ? do_vfs_ioctl+0x379/0x431
[lun giu 22 11:43:18 2015] [<ffffffff811d4784>] ? __fd_install+0x20/0x52
[lun giu 22 11:43:18 2015] [<ffffffff811bccab>] ? do_sys_open+0x1c0/0x1d2
[lun giu 22 11:43:18 2015] [<ffffffff811cc687>] ? SyS_ioctl+0x3e/0x5a
[lun giu 22 11:43:18 2015] [<ffffffff818e0d9b>] ?
system_call_fastpath+0x16/0x6e
[lun giu 22 11:43:18 2015] ---[ end trace 46364eedd82ef148 ]---
It does not seems to affect normal behaviour, but maybe the report could be
interesting for maintainers.
Sorry if this has already been reported; if more information is needed just
let me know (please CC: me as I'm not subscribed to lists.)
Many thanks.
--
Fabio
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 13+ messages in thread
* Linux 4.1 WARNING in drm_ioctl.c
@ 2015-06-22 14:04 ` Fabio Coatti
0 siblings, 0 replies; 13+ messages in thread
From: Fabio Coatti @ 2015-06-22 14:04 UTC (permalink / raw)
To: David Airlie, dri-devel, kernel list
Hi All,
just compiled 4.1 and just got this warning, twice, in my dmesg:
[lun giu 22 11:43:18 2015] ------------[ cut here ]------------
[lun giu 22 11:43:18 2015] WARNING: CPU: 1 PID: 2184 at
drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0xe1/0x179()
[lun giu 22 11:43:18 2015] No drm_driver.set_busid() implementation provided
by 0xffffffff81ec3980. Use drm_dev_set_unique() to set the unique name
explicitly.
[lun giu 22 11:43:18 2015] Modules linked in:
[lun giu 22 11:43:18 2015] bnep algif_skcipher cdc_wdm cdc_acm uvcvideo
videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev btusb
btbcm btintel bluetooth hp_wmi sparse_keymap intel_rapl iosf_mbi
x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp kvm_intel
kvm snd_hda_codec_generic crct10dif_pclmul crc32_pclmul snd_hda_intel iwldvm
snd_hda_controller snd_hda_codec snd_hwdep psmouse snd_hda_core iwlwifi
snd_pcm snd_timer snd soundcore wmi hp_accel(+) hp_wireless lis3lv02d
sch_fq_codel dm_zero dm_persistent_data dm_service_time dm_round_robin
dm_queue_length dm_multipath dm_delay virtio_pci virtio_blk virtio_balloon
virtio_ring virtio fuse overlay linear raid0 dm_raid dm_snapshot dm_bufio
dm_mirror dm_region_hash dm_log ohci_pci ohci_hcd uhci_hcd
[lun giu 22 11:43:18 2015] CPU: 1 PID: 2184 Comm: X Tainted: G W
4.1.0 #1
[lun giu 22 11:43:18 2015] Hardware name: Hewlett-Packard HP EliteBook Folio
9470m/18DF, BIOS 68IBD Ver. F.40 02/01/2013
[lun giu 22 11:43:18 2015] 0000000000000000 0000000000000009 ffffffff818d8bfd
ffff8800b226fd38
[lun giu 22 11:43:18 2015] ffffffff810c5426 ffff880235437240 ffffffff8152870c
ffff8800b2f16000
[lun giu 22 11:43:18 2015] ffff880234ffc000 ffff8800b226fdf0 ffff8800b2c8f300
00000000c0106407
[lun giu 22 11:43:18 2015] Call Trace:
[lun giu 22 11:43:18 2015] [<ffffffff818d8bfd>] ? dump_stack+0x47/0x67
[lun giu 22 11:43:18 2015] [<ffffffff810c5426>] ?
warn_slowpath_common+0x9d/0xb5
[lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
[lun giu 22 11:43:18 2015] [<ffffffff810c5488>] ? warn_slowpath_fmt+0x4a/0x4f
[lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
[lun giu 22 11:43:18 2015] [<ffffffff81528465>] ? drm_ioctl+0x376/0x3dd
[lun giu 22 11:43:18 2015] [<ffffffff8152862b>] ? drm_version+0x8d/0x8d
[lun giu 22 11:43:18 2015] [<ffffffff811ca766>] ? do_filp_open+0x30/0x74
[lun giu 22 11:43:18 2015] [<ffffffff811cc591>] ? do_vfs_ioctl+0x379/0x431
[lun giu 22 11:43:18 2015] [<ffffffff811d4784>] ? __fd_install+0x20/0x52
[lun giu 22 11:43:18 2015] [<ffffffff811bccab>] ? do_sys_open+0x1c0/0x1d2
[lun giu 22 11:43:18 2015] [<ffffffff811cc687>] ? SyS_ioctl+0x3e/0x5a
[lun giu 22 11:43:18 2015] [<ffffffff818e0d9b>] ?
system_call_fastpath+0x16/0x6e
[lun giu 22 11:43:18 2015] ---[ end trace 46364eedd82ef148 ]---
It does not seems to affect normal behaviour, but maybe the report could be
interesting for maintainers.
Sorry if this has already been reported; if more information is needed just
let me know (please CC: me as I'm not subscribed to lists.)
Many thanks.
--
Fabio
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-22 14:04 ` Fabio Coatti
@ 2015-06-23 6:39 ` Daniel Vetter
-1 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2015-06-23 6:39 UTC (permalink / raw)
To: Fabio Coatti; +Cc: David Airlie, dri-devel, kernel list
On Mon, Jun 22, 2015 at 04:04:20PM +0200, Fabio Coatti wrote:
> Hi All,
>
> just compiled 4.1 and just got this warning, twice, in my dmesg:
>
>
> [lun giu 22 11:43:18 2015] ------------[ cut here ]------------
> [lun giu 22 11:43:18 2015] WARNING: CPU: 1 PID: 2184 at
> drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0xe1/0x179()
> [lun giu 22 11:43:18 2015] No drm_driver.set_busid() implementation provided
> by 0xffffffff81ec3980. Use drm_dev_set_unique() to set the unique name
> explicitly.
> [lun giu 22 11:43:18 2015] Modules linked in:
> [lun giu 22 11:43:18 2015] bnep algif_skcipher cdc_wdm cdc_acm uvcvideo
> videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev btusb
> btbcm btintel bluetooth hp_wmi sparse_keymap intel_rapl iosf_mbi
> x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp kvm_intel
> kvm snd_hda_codec_generic crct10dif_pclmul crc32_pclmul snd_hda_intel iwldvm
> snd_hda_controller snd_hda_codec snd_hwdep psmouse snd_hda_core iwlwifi
> snd_pcm snd_timer snd soundcore wmi hp_accel(+) hp_wireless lis3lv02d
> sch_fq_codel dm_zero dm_persistent_data dm_service_time dm_round_robin
> dm_queue_length dm_multipath dm_delay virtio_pci virtio_blk virtio_balloon
> virtio_ring virtio fuse overlay linear raid0 dm_raid dm_snapshot dm_bufio
> dm_mirror dm_region_hash dm_log ohci_pci ohci_hcd uhci_hcd
> [lun giu 22 11:43:18 2015] CPU: 1 PID: 2184 Comm: X Tainted: G W
> 4.1.0 #1
> [lun giu 22 11:43:18 2015] Hardware name: Hewlett-Packard HP EliteBook Folio
> 9470m/18DF, BIOS 68IBD Ver. F.40 02/01/2013
> [lun giu 22 11:43:18 2015] 0000000000000000 0000000000000009 ffffffff818d8bfd
> ffff8800b226fd38
> [lun giu 22 11:43:18 2015] ffffffff810c5426 ffff880235437240 ffffffff8152870c
> ffff8800b2f16000
> [lun giu 22 11:43:18 2015] ffff880234ffc000 ffff8800b226fdf0 ffff8800b2c8f300
> 00000000c0106407
> [lun giu 22 11:43:18 2015] Call Trace:
> [lun giu 22 11:43:18 2015] [<ffffffff818d8bfd>] ? dump_stack+0x47/0x67
> [lun giu 22 11:43:18 2015] [<ffffffff810c5426>] ?
> warn_slowpath_common+0x9d/0xb5
> [lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
> [lun giu 22 11:43:18 2015] [<ffffffff810c5488>] ? warn_slowpath_fmt+0x4a/0x4f
> [lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
> [lun giu 22 11:43:18 2015] [<ffffffff81528465>] ? drm_ioctl+0x376/0x3dd
> [lun giu 22 11:43:18 2015] [<ffffffff8152862b>] ? drm_version+0x8d/0x8d
> [lun giu 22 11:43:18 2015] [<ffffffff811ca766>] ? do_filp_open+0x30/0x74
> [lun giu 22 11:43:18 2015] [<ffffffff811cc591>] ? do_vfs_ioctl+0x379/0x431
> [lun giu 22 11:43:18 2015] [<ffffffff811d4784>] ? __fd_install+0x20/0x52
> [lun giu 22 11:43:18 2015] [<ffffffff811bccab>] ? do_sys_open+0x1c0/0x1d2
> [lun giu 22 11:43:18 2015] [<ffffffff811cc687>] ? SyS_ioctl+0x3e/0x5a
> [lun giu 22 11:43:18 2015] [<ffffffff818e0d9b>] ?
> system_call_fastpath+0x16/0x6e
> [lun giu 22 11:43:18 2015] ---[ end trace 46364eedd82ef148 ]---
>
> It does not seems to affect normal behaviour, but maybe the report could be
> interesting for maintainers.
>
> Sorry if this has already been reported; if more information is needed just
> let me know (please CC: me as I'm not subscribed to lists.)
Which drm driver are you using? I didn't spot anything in your module list
but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
will tell us for sure.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
@ 2015-06-23 6:39 ` Daniel Vetter
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2015-06-23 6:39 UTC (permalink / raw)
To: Fabio Coatti; +Cc: kernel list, dri-devel
On Mon, Jun 22, 2015 at 04:04:20PM +0200, Fabio Coatti wrote:
> Hi All,
>
> just compiled 4.1 and just got this warning, twice, in my dmesg:
>
>
> [lun giu 22 11:43:18 2015] ------------[ cut here ]------------
> [lun giu 22 11:43:18 2015] WARNING: CPU: 1 PID: 2184 at
> drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0xe1/0x179()
> [lun giu 22 11:43:18 2015] No drm_driver.set_busid() implementation provided
> by 0xffffffff81ec3980. Use drm_dev_set_unique() to set the unique name
> explicitly.
> [lun giu 22 11:43:18 2015] Modules linked in:
> [lun giu 22 11:43:18 2015] bnep algif_skcipher cdc_wdm cdc_acm uvcvideo
> videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev btusb
> btbcm btintel bluetooth hp_wmi sparse_keymap intel_rapl iosf_mbi
> x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp kvm_intel
> kvm snd_hda_codec_generic crct10dif_pclmul crc32_pclmul snd_hda_intel iwldvm
> snd_hda_controller snd_hda_codec snd_hwdep psmouse snd_hda_core iwlwifi
> snd_pcm snd_timer snd soundcore wmi hp_accel(+) hp_wireless lis3lv02d
> sch_fq_codel dm_zero dm_persistent_data dm_service_time dm_round_robin
> dm_queue_length dm_multipath dm_delay virtio_pci virtio_blk virtio_balloon
> virtio_ring virtio fuse overlay linear raid0 dm_raid dm_snapshot dm_bufio
> dm_mirror dm_region_hash dm_log ohci_pci ohci_hcd uhci_hcd
> [lun giu 22 11:43:18 2015] CPU: 1 PID: 2184 Comm: X Tainted: G W
> 4.1.0 #1
> [lun giu 22 11:43:18 2015] Hardware name: Hewlett-Packard HP EliteBook Folio
> 9470m/18DF, BIOS 68IBD Ver. F.40 02/01/2013
> [lun giu 22 11:43:18 2015] 0000000000000000 0000000000000009 ffffffff818d8bfd
> ffff8800b226fd38
> [lun giu 22 11:43:18 2015] ffffffff810c5426 ffff880235437240 ffffffff8152870c
> ffff8800b2f16000
> [lun giu 22 11:43:18 2015] ffff880234ffc000 ffff8800b226fdf0 ffff8800b2c8f300
> 00000000c0106407
> [lun giu 22 11:43:18 2015] Call Trace:
> [lun giu 22 11:43:18 2015] [<ffffffff818d8bfd>] ? dump_stack+0x47/0x67
> [lun giu 22 11:43:18 2015] [<ffffffff810c5426>] ?
> warn_slowpath_common+0x9d/0xb5
> [lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
> [lun giu 22 11:43:18 2015] [<ffffffff810c5488>] ? warn_slowpath_fmt+0x4a/0x4f
> [lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179
> [lun giu 22 11:43:18 2015] [<ffffffff81528465>] ? drm_ioctl+0x376/0x3dd
> [lun giu 22 11:43:18 2015] [<ffffffff8152862b>] ? drm_version+0x8d/0x8d
> [lun giu 22 11:43:18 2015] [<ffffffff811ca766>] ? do_filp_open+0x30/0x74
> [lun giu 22 11:43:18 2015] [<ffffffff811cc591>] ? do_vfs_ioctl+0x379/0x431
> [lun giu 22 11:43:18 2015] [<ffffffff811d4784>] ? __fd_install+0x20/0x52
> [lun giu 22 11:43:18 2015] [<ffffffff811bccab>] ? do_sys_open+0x1c0/0x1d2
> [lun giu 22 11:43:18 2015] [<ffffffff811cc687>] ? SyS_ioctl+0x3e/0x5a
> [lun giu 22 11:43:18 2015] [<ffffffff818e0d9b>] ?
> system_call_fastpath+0x16/0x6e
> [lun giu 22 11:43:18 2015] ---[ end trace 46364eedd82ef148 ]---
>
> It does not seems to affect normal behaviour, but maybe the report could be
> interesting for maintainers.
>
> Sorry if this has already been reported; if more information is needed just
> let me know (please CC: me as I'm not subscribed to lists.)
Which drm driver are you using? I didn't spot anything in your module list
but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
will tell us for sure.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-23 6:39 ` Daniel Vetter
(?)
@ 2015-06-23 7:12 ` Fabio Coatti
-1 siblings, 0 replies; 13+ messages in thread
From: Fabio Coatti @ 2015-06-23 7:12 UTC (permalink / raw)
To: Daniel Vetter; +Cc: David Airlie, dri-devel, kernel list
[-- Attachment #1: Type: text/plain, Size: 3829 bytes --]
In data martedì 23 giugno 2015 08:39:47, Daniel Vetter ha scritto:
> On Mon, Jun 22, 2015 at 04:04:20PM +0200, Fabio Coatti wrote:
> > Hi All,
> >
> > just compiled 4.1 and just got this warning, twice, in my dmesg:
> >
> >
> > [lun giu 22 11:43:18 2015] ------------[ cut here ]------------
> > [lun giu 22 11:43:18 2015] WARNING: CPU: 1 PID: 2184 at
> > drivers/gpu/drm/drm_ioctl.c:144 drm_setversion+0xe1/0x179()
> > [lun giu 22 11:43:18 2015] No drm_driver.set_busid() implementation
> > provided by 0xffffffff81ec3980. Use drm_dev_set_unique() to set the
> > unique name explicitly.
> > [lun giu 22 11:43:18 2015] Modules linked in:
> > [lun giu 22 11:43:18 2015] bnep algif_skcipher cdc_wdm cdc_acm uvcvideo
> > videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev
> > btusb btbcm btintel bluetooth hp_wmi sparse_keymap intel_rapl iosf_mbi
> > x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp
> > kvm_intel
> > kvm snd_hda_codec_generic crct10dif_pclmul crc32_pclmul snd_hda_intel
> > iwldvm snd_hda_controller snd_hda_codec snd_hwdep psmouse snd_hda_core
> > iwlwifi snd_pcm snd_timer snd soundcore wmi hp_accel(+) hp_wireless
> > lis3lv02d sch_fq_codel dm_zero dm_persistent_data dm_service_time
> > dm_round_robin dm_queue_length dm_multipath dm_delay virtio_pci
> > virtio_blk virtio_balloon virtio_ring virtio fuse overlay linear raid0
> > dm_raid dm_snapshot dm_bufio dm_mirror dm_region_hash dm_log ohci_pci
> > ohci_hcd uhci_hcd
> > [lun giu 22 11:43:18 2015] CPU: 1 PID: 2184 Comm: X Tainted: G W
> > 4.1.0 #1
> > [lun giu 22 11:43:18 2015] Hardware name: Hewlett-Packard HP EliteBook
> > Folio 9470m/18DF, BIOS 68IBD Ver. F.40 02/01/2013
> > [lun giu 22 11:43:18 2015] 0000000000000000 0000000000000009
> > ffffffff818d8bfd ffff8800b226fd38
> > [lun giu 22 11:43:18 2015] ffffffff810c5426 ffff880235437240
> > ffffffff8152870c ffff8800b2f16000
> > [lun giu 22 11:43:18 2015] ffff880234ffc000 ffff8800b226fdf0
> > ffff8800b2c8f300 00000000c0106407
> > [lun giu 22 11:43:18 2015] Call Trace:
> > [lun giu 22 11:43:18 2015] [<ffffffff818d8bfd>] ? dump_stack+0x47/0x67
> > [lun giu 22 11:43:18 2015] [<ffffffff810c5426>] ?
> > warn_slowpath_common+0x9d/0xb5
> > [lun giu 22 11:43:18 2015] [<ffffffff8152870c>] ?
> > drm_setversion+0xe1/0x179 [lun giu 22 11:43:18 2015]
> > [<ffffffff810c5488>] ? warn_slowpath_fmt+0x4a/0x4f [lun giu 22 11:43:18
> > 2015] [<ffffffff8152870c>] ? drm_setversion+0xe1/0x179 [lun giu 22
> > 11:43:18 2015] [<ffffffff81528465>] ? drm_ioctl+0x376/0x3dd [lun giu 22
> > 11:43:18 2015] [<ffffffff8152862b>] ? drm_version+0x8d/0x8d [lun giu 22
> > 11:43:18 2015] [<ffffffff811ca766>] ? do_filp_open+0x30/0x74 [lun giu 22
> > 11:43:18 2015] [<ffffffff811cc591>] ? do_vfs_ioctl+0x379/0x431 [lun giu
> > 22 11:43:18 2015] [<ffffffff811d4784>] ? __fd_install+0x20/0x52 [lun giu
> > 22 11:43:18 2015] [<ffffffff811bccab>] ? do_sys_open+0x1c0/0x1d2 [lun
> > giu 22 11:43:18 2015] [<ffffffff811cc687>] ? SyS_ioctl+0x3e/0x5a [lun
> > giu 22 11:43:18 2015] [<ffffffff818e0d9b>] ?
> > system_call_fastpath+0x16/0x6e
> > [lun giu 22 11:43:18 2015] ---[ end trace 46364eedd82ef148 ]---
> >
> > It does not seems to affect normal behaviour, but maybe the report could
> > be
> > interesting for maintainers.
> >
> > Sorry if this has already been reported; if more information is needed
> > just
> > let me know (please CC: me as I'm not subscribed to lists.)
>
> Which drm driver are you using? I didn't spot anything in your module list
> but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> will tell us for sure.
> -Daniel
Attached the drm.debug output, grepped for "drm". Let me know if I stripped
something useful.
Thanks,
--
Fabio
[-- Attachment #2: drm.debug.gz --]
[-- Type: application/gzip, Size: 18040 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-23 6:39 ` Daniel Vetter
@ 2015-06-23 7:27 ` Daniel Stone
-1 siblings, 0 replies; 13+ messages in thread
From: Daniel Stone @ 2015-06-23 7:27 UTC (permalink / raw)
To: Fabio Coatti, David Airlie, dri-devel, kernel list
Hi,
On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> Which drm driver are you using? I didn't spot anything in your module list
> but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> will tell us for sure.
That'd be vgem.
Cheers,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
@ 2015-06-23 7:27 ` Daniel Stone
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Stone @ 2015-06-23 7:27 UTC (permalink / raw)
To: Fabio Coatti, David Airlie, dri-devel, kernel list
Hi,
On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> Which drm driver are you using? I didn't spot anything in your module list
> but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> will tell us for sure.
That'd be vgem.
Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-23 7:27 ` Daniel Stone
@ 2015-06-23 9:48 ` Daniel Vetter
-1 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2015-06-23 9:48 UTC (permalink / raw)
To: Daniel Stone; +Cc: Fabio Coatti, David Airlie, dri-devel, kernel list
On Tue, Jun 23, 2015 at 08:27:13AM +0100, Daniel Stone wrote:
> Hi,
>
> On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> > Which drm driver are you using? I didn't spot anything in your module list
> > but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> > will tell us for sure.
>
> That'd be vgem.
If so then the below diff should help.
-Daniel
diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
index 7a207ca547be..b491fb32cddb 100644
--- a/drivers/gpu/drm/vgem/vgem_drv.c
+++ b/drivers/gpu/drm/vgem/vgem_drv.c
@@ -328,6 +328,8 @@ static int __init vgem_init(void)
goto out;
}
+ drm_dev_set_unique(drm, "vgem");
+
ret = drm_dev_register(vgem_device, 0);
if (ret)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
@ 2015-06-23 9:48 ` Daniel Vetter
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2015-06-23 9:48 UTC (permalink / raw)
To: Daniel Stone; +Cc: dri-devel, Fabio Coatti, kernel list
On Tue, Jun 23, 2015 at 08:27:13AM +0100, Daniel Stone wrote:
> Hi,
>
> On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> > Which drm driver are you using? I didn't spot anything in your module list
> > but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> > will tell us for sure.
>
> That'd be vgem.
If so then the below diff should help.
-Daniel
diff --git a/drivers/gpu/drm/vgem/vgem_drv.c b/drivers/gpu/drm/vgem/vgem_drv.c
index 7a207ca547be..b491fb32cddb 100644
--- a/drivers/gpu/drm/vgem/vgem_drv.c
+++ b/drivers/gpu/drm/vgem/vgem_drv.c
@@ -328,6 +328,8 @@ static int __init vgem_init(void)
goto out;
}
+ drm_dev_set_unique(drm, "vgem");
+
ret = drm_dev_register(vgem_device, 0);
if (ret)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply related [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-23 9:48 ` Daniel Vetter
(?)
@ 2015-06-23 10:46 ` Fabio Coatti
2015-06-23 13:29 ` Daniel Vetter
-1 siblings, 1 reply; 13+ messages in thread
From: Fabio Coatti @ 2015-06-23 10:46 UTC (permalink / raw)
To: Daniel Vetter; +Cc: Daniel Stone, David Airlie, dri-devel, kernel list
In data martedì 23 giugno 2015 11:48:47, Daniel Vetter ha scritto:
> On Tue, Jun 23, 2015 at 08:27:13AM +0100, Daniel Stone wrote:
> > Hi,
> >
> > On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > Which drm driver are you using? I didn't spot anything in your module
> > > list
> > > but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> > > will tell us for sure.
> >
> > That'd be vgem.
>
> If so then the below diff should help.
> -Daniel
> diff --git a/drivers/gpu/drm/vgem/vgem_drv.c
> b/drivers/gpu/drm/vgem/vgem_drv.c index 7a207ca547be..b491fb32cddb 100644
> --- a/drivers/gpu/drm/vgem/vgem_drv.c
> +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> @@ -328,6 +328,8 @@ static int __init vgem_init(void)
> goto out;
> }
>
> + drm_dev_set_unique(drm, "vgem");
> +
> ret = drm_dev_register(vgem_device, 0);
>
> if (ret)
Not really sure about "drm" in drm_dev_set_unique():
CHK include/generated/compile.h
GZIP kernel/config_data.gz
CHK kernel/config_data.h
CC drivers/gpu/drm/vgem/vgem_drv.o
drivers/gpu/drm/vgem/vgem_drv.c: In function ‘vgem_init’:
drivers/gpu/drm/vgem/vgem_drv.c:331:21: error: ‘drm’ undeclared (first use in
this function)
--
Fabio
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-23 10:46 ` Fabio Coatti
@ 2015-06-23 13:29 ` Daniel Vetter
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2015-06-23 13:29 UTC (permalink / raw)
To: Fabio Coatti
Cc: Daniel Vetter, Daniel Stone, David Airlie, dri-devel, kernel list
On Tue, Jun 23, 2015 at 12:46:09PM +0200, Fabio Coatti wrote:
> In data martedì 23 giugno 2015 11:48:47, Daniel Vetter ha scritto:
> > On Tue, Jun 23, 2015 at 08:27:13AM +0100, Daniel Stone wrote:
> > > Hi,
> > >
> > > On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > > Which drm driver are you using? I didn't spot anything in your module
> > > > list
> > > > but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> > > > will tell us for sure.
> > >
> > > That'd be vgem.
> >
> > If so then the below diff should help.
> > -Daniel
> > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c
> > b/drivers/gpu/drm/vgem/vgem_drv.c index 7a207ca547be..b491fb32cddb 100644
> > --- a/drivers/gpu/drm/vgem/vgem_drv.c
> > +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> > @@ -328,6 +328,8 @@ static int __init vgem_init(void)
> > goto out;
> > }
> >
> > + drm_dev_set_unique(drm, "vgem");
> > +
> > ret = drm_dev_register(vgem_device, 0);
> >
> > if (ret)
>
>
> Not really sure about "drm" in drm_dev_set_unique():
>
> CHK include/generated/compile.h
> GZIP kernel/config_data.gz
> CHK kernel/config_data.h
> CC drivers/gpu/drm/vgem/vgem_drv.o
> drivers/gpu/drm/vgem/vgem_drv.c: In function ‘vgem_init’:
> drivers/gpu/drm/vgem/vgem_drv.c:331:21: error: ‘drm’ undeclared (first use in
> this function)
s/drm/vgem_device/ ... copypaste fail without running gcc.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
@ 2015-06-23 13:29 ` Daniel Vetter
0 siblings, 0 replies; 13+ messages in thread
From: Daniel Vetter @ 2015-06-23 13:29 UTC (permalink / raw)
To: Fabio Coatti; +Cc: dri-devel, kernel list
On Tue, Jun 23, 2015 at 12:46:09PM +0200, Fabio Coatti wrote:
> In data martedì 23 giugno 2015 11:48:47, Daniel Vetter ha scritto:
> > On Tue, Jun 23, 2015 at 08:27:13AM +0100, Daniel Stone wrote:
> > > Hi,
> > >
> > > On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > > Which drm driver are you using? I didn't spot anything in your module
> > > > list
> > > > but might have missed it. Booting with drm.debug=0xe and grabbing dmesg
> > > > will tell us for sure.
> > >
> > > That'd be vgem.
> >
> > If so then the below diff should help.
> > -Daniel
> > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c
> > b/drivers/gpu/drm/vgem/vgem_drv.c index 7a207ca547be..b491fb32cddb 100644
> > --- a/drivers/gpu/drm/vgem/vgem_drv.c
> > +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> > @@ -328,6 +328,8 @@ static int __init vgem_init(void)
> > goto out;
> > }
> >
> > + drm_dev_set_unique(drm, "vgem");
> > +
> > ret = drm_dev_register(vgem_device, 0);
> >
> > if (ret)
>
>
> Not really sure about "drm" in drm_dev_set_unique():
>
> CHK include/generated/compile.h
> GZIP kernel/config_data.gz
> CHK kernel/config_data.h
> CC drivers/gpu/drm/vgem/vgem_drv.o
> drivers/gpu/drm/vgem/vgem_drv.c: In function ‘vgem_init’:
> drivers/gpu/drm/vgem/vgem_drv.c:331:21: error: ‘drm’ undeclared (first use in
> this function)
s/drm/vgem_device/ ... copypaste fail without running gcc.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: Linux 4.1 WARNING in drm_ioctl.c
2015-06-23 13:29 ` Daniel Vetter
(?)
@ 2015-06-23 14:03 ` Fabio Coatti
-1 siblings, 0 replies; 13+ messages in thread
From: Fabio Coatti @ 2015-06-23 14:03 UTC (permalink / raw)
To: Daniel Vetter; +Cc: Daniel Stone, David Airlie, dri-devel, kernel list
In data martedì 23 giugno 2015 15:29:41, Daniel Vetter ha scritto:
> On Tue, Jun 23, 2015 at 12:46:09PM +0200, Fabio Coatti wrote:
> > In data martedì 23 giugno 2015 11:48:47, Daniel Vetter ha scritto:
> > > On Tue, Jun 23, 2015 at 08:27:13AM +0100, Daniel Stone wrote:
> > > > Hi,
> > > >
> > > > On 23 June 2015 at 07:39, Daniel Vetter <daniel@ffwll.ch> wrote:
> > > > > Which drm driver are you using? I didn't spot anything in your
> > > > > module
> > > > > list
> > > > > but might have missed it. Booting with drm.debug=0xe and grabbing
> > > > > dmesg
> > > > > will tell us for sure.
> > > >
> > > > That'd be vgem.
> > >
> > > If so then the below diff should help.
> > > -Daniel
> > > diff --git a/drivers/gpu/drm/vgem/vgem_drv.c
> > > b/drivers/gpu/drm/vgem/vgem_drv.c index 7a207ca547be..b491fb32cddb
> > > 100644
> > > --- a/drivers/gpu/drm/vgem/vgem_drv.c
> > > +++ b/drivers/gpu/drm/vgem/vgem_drv.c
> > > @@ -328,6 +328,8 @@ static int __init vgem_init(void)
> > >
> > > goto out;
> > >
> > > }
> > >
> > > + drm_dev_set_unique(drm, "vgem");
> > > +
> > >
> > > ret = drm_dev_register(vgem_device, 0);
> > >
> > > if (ret)
> >
> > Not really sure about "drm" in drm_dev_set_unique():
> > CHK include/generated/compile.h
> > GZIP kernel/config_data.gz
> > CHK kernel/config_data.h
> > CC drivers/gpu/drm/vgem/vgem_drv.o
> >
> > drivers/gpu/drm/vgem/vgem_drv.c: In function ‘vgem_init’:
> > drivers/gpu/drm/vgem/vgem_drv.c:331:21: error: ‘drm’ undeclared (first use
> > in this function)
>
> s/drm/vgem_device/ ... copypaste fail without running gcc.
> -Daniel
Ok, that fixed, it; no more drm WARNING messages in dmesg.
Many thanks!
--
Fabio
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2015-06-23 14:03 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-22 14:04 Linux 4.1 WARNING in drm_ioctl.c Fabio Coatti
2015-06-22 14:04 ` Fabio Coatti
2015-06-23 6:39 ` Daniel Vetter
2015-06-23 6:39 ` Daniel Vetter
2015-06-23 7:12 ` Fabio Coatti
2015-06-23 7:27 ` Daniel Stone
2015-06-23 7:27 ` Daniel Stone
2015-06-23 9:48 ` Daniel Vetter
2015-06-23 9:48 ` Daniel Vetter
2015-06-23 10:46 ` Fabio Coatti
2015-06-23 13:29 ` Daniel Vetter
2015-06-23 13:29 ` Daniel Vetter
2015-06-23 14:03 ` Fabio Coatti
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.