Bug 92718 - [REGRESSION] 4.3.0-rc7 - Multiple identical kernel warnings from drm_atomic.c:491 drm_atomic_check_only
Summary: [REGRESSION] 4.3.0-rc7 - Multiple identical kernel warnings from drm_atomic.c...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-29 01:23 UTC by Karsten Hohmeier
Modified: 2017-07-24 22:44 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Karsten Hohmeier 2015-10-29 01:23:04 UTC
Hello,

Tested latest kernel RCs (rc6 and rc7) from kernel.org.
Getting multiple identical kernel warnings during boot (both RCs). It is ugly but the system seems fine otherwise.

Notebook has Intel GME965/GLE960 mobile graphics.
Please notify if further info is needed.

Best Regards

Karsten Hohmeier

[drm] initialized overlay support
------------[ cut here ]------------
WARNING: CPU: 1 PID: 88 at drivers/gpu/drm/drm_atomic.c:491 drm_atomic_check_only+0x4e9/0x580 [drm]()
Modules linked in: iTCO_wdt iTCO_vendor_support hp_wmi(+) sparse_keymap snd_hda_codec_hdmi arc4 iwl3945 snd_hda_codec_analog iwlegacy snd_hda_codec_generic i915(+) coretemp snd_hda_intel drm_kms_helper mac80211 snd_hda_codec psmouse evdev snd_hwdep drm serio_raw snd_hda_core pcspkr lpc_ich mfd_core i2c_algo_bit cfg80211 i2c_core snd_pcm rfkill snd_timer snd soundcore shpchp battery wmi tpm_infineon tpm_tis tpm video hp_accel acpi_cpufreq lis3lv02d input_polldev ac processor button loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sr_mod cdrom sd_mod ata_generic ahci ata_piix libahci libata scsi_mod fan thermal ehci_pci uhci_hcd ehci_hcd usbcore e1000e usb_common ptp pps_core
CPU: 1 PID: 88 Comm: kworker/u4:2 Not tainted 4.3.0-rc7+ #2
Hardware name: Hewlett-Packard HP Compaq 6720s/30D8, BIOS 68MDU Ver. F.0D 11/04/2008
Workqueue: events_unbound async_run_entry_fn
 ffffffffa04124ee ffffffff812bb9c3 0000000000000000 ffffffff8106c541
 ffff88007b03f000 0000000000000000 ffff88007b401600 0000000000000001
 0000000000000000 ffffffffa03fd859 ffff88007b03f000 ffff88007a0ec000
Call Trace:
 [<ffffffff812bb9c3>] ? dump_stack+0x40/0x5d
 [<ffffffff8106c541>] ? warn_slowpath_common+0x81/0xb0
 [<ffffffffa03fd859>] ? drm_atomic_check_only+0x4e9/0x580 [drm]
 [<ffffffffa03fcbb2>] ? drm_atomic_set_crtc_for_plane+0x72/0xf0 [drm]
 [<ffffffffa03fd902>] ? drm_atomic_commit+0x12/0x60 [drm]
 [<ffffffffa063346d>] ? intel_get_load_detect_pipe+0x3dd/0x540 [i915]
 [<ffffffffa066944d>] ? intel_tv_detect+0x13d/0x570 [i915]
 [<ffffffffa03f0a47>] ? drm_property_replace_global_blob+0xc7/0x120 [drm]
 [<ffffffffa05a9a4b>] ? drm_helper_probe_single_connector_modes_merge_bits+0x28b/0x4a0 [drm_kms_helper]
 [<ffffffffa05b3aa5>] ? drm_fb_helper_probe_connector_modes.isra.3+0x45/0x60 [drm_kms_helper]
 [<ffffffffa05b4cb1>] ? drm_fb_helper_initial_config+0x41/0x3b0 [drm_kms_helper]
 [<ffffffff8108b033>] ? async_run_entry_fn+0x43/0x150
 [<ffffffff81082fcc>] ? process_one_work+0x14c/0x3d0
 [<ffffffff81083965>] ? worker_thread+0x65/0x460
 [<ffffffff81083900>] ? rescuer_thread+0x2f0/0x2f0
 [<ffffffff8108892f>] ? kthread+0xcf/0xf0
 [<ffffffff81088860>] ? kthread_park+0x50/0x50
 [<ffffffff8153338f>] ? ret_from_fork+0x3f/0x70
 [<ffffffff81088860>] ? kthread_park+0x50/0x50
---[ end trace 226220945234194c ]---
fbcon: inteldrmfb (fb0) is primary device
------------[ cut here ]------------
Comment 1 Felix Schwarz 2016-01-27 11:39:37 UTC
Karsten: Can you check if the problem is still present with kernel 4.4?

I found a Debian bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808916) where a user mentioned that upgrading to 4.4 helped.
Comment 2 Karsten Hohmeier 2016-01-27 13:21:07 UTC
Hello,

I am currently ~100 miles away from the affected system. But I'll return next week. I'll give feedback once i get the chance to test it (~ February 3rd).

Best Regards

Karsten
Comment 3 Karsten Hohmeier 2016-02-01 14:15:55 UTC
Tested with 4.4.1 from kernel.org, the error in drm_atomic.c is gone.

But a new one in drm_irq.c showed up. This one is seriously spamming my system logs.

------------[ cut here ]------------
WARNING: CPU: 1 PID: 1003 at drivers/gpu/drm/drm_irq.c:1268 drm_wait_one_vblank+0x13b/0x180 [drm]()
vblank wait timed out on crtc 0
Modules linked in: cpufreq_stats cpufreq_userspace pci_stub cpufreq_conservative vboxpci(O) cpufreq_powersave vboxnetadp(O) vboxnetflt(O) vboxdrv(O) nfsd auth_rpcgss oid_registry nfs_acl nfs lockd grace fscache sunrpc joydev hid_generic usbhid hid iTCO_wdt iTCO_vendor_support hp_wmi sparse_keymap arc4 coretemp evdev iwl3945 psmouse serio_raw pcspkr iwlegacy snd_hda_codec_hdmi i915 mac80211 snd_hda_codec_analog snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep drm_kms_helper lpc_ich mfd_core cfg80211 snd_hda_core snd_pcm rfkill snd_timer drm snd soundcore shpchp i2c_algo_bit i2c_core wmi battery tpm_infineon hp_accel acpi_cpufreq lis3lv02d video tpm_tis input_polldev tpm ac button processor loop fuse parport_pc ppdev lp parport autofs4 usb_storage ext4 crc16 mbcache jbd2 dm_mod sg sd_mod sr_mod cdrom ata_generic ahci libahci ata_piix libata scsi_mod fan thermal ehci_pci uhci_hcd ehci_hcd usbcore usb_common e1000e ptp pps_core
CPU: 1 PID: 1003 Comm: Xorg Tainted: G        W  O    4.4.1+ #5
Hardware name: Hewlett-Packard HP Compaq 6720s/30D8, BIOS 68MDU Ver. F.0D 11/04/2008
 ffffffffa036246d ffffffff812c23c3 ffff88007a74fa00 ffffffff8106db61
 0000000000000000 ffff88007a74fa50 0000000000000000 000000000b000006
 ffff88007b470c08 ffffffff8106dbdc ffffffffa0365198 0000000000000020
Call Trace:
 [<ffffffff812c23c3>] ? dump_stack+0x40/0x5d
 [<ffffffff8106db61>] ? warn_slowpath_common+0x81/0xb0
 [<ffffffff8106dbdc>] ? warn_slowpath_fmt+0x4c/0x50
 [<ffffffffa0336fbb>] ? drm_wait_one_vblank+0x13b/0x180 [drm]
 [<ffffffff810a8df0>] ? wait_woken+0x90/0x90
 [<ffffffffa05e7e87>] ? intel_get_load_detect_pipe+0x537/0x540 [i915]
 [<ffffffffa06200ad>] ? intel_tv_detect+0x13d/0x570 [i915]
 [<ffffffffa0473ab3>] ? drm_helper_probe_single_connector_modes_merge_bits+0x293/0x4b0 [drm_kms_helper]
 [<ffffffff8153e15e>] ? mutex_lock+0xe/0x30
 [<ffffffffa03423cf>] ? drm_mode_getconnector+0x2df/0x330 [drm]
 [<ffffffffa0335346>] ? drm_ioctl+0x126/0x490 [drm]
 [<ffffffffa03420f0>] ? drm_mode_getcrtc+0x120/0x120 [drm]
 [<ffffffff811f79a9>] ? fsnotify_destroy_marks+0x59/0x70
 [<ffffffff811cc374>] ? do_vfs_ioctl+0x2c4/0x490
 [<ffffffff811cc5b6>] ? SyS_ioctl+0x76/0x90
 [<ffffffff81003310>] ? exit_to_usermode_loop+0xa0/0xc0
 [<ffffffff8153ff36>] ? entry_SYSCALL_64_fastpath+0x16/0x75
---[ end trace 06f1669746ac2817 ]---
------------[ cut here ]------------
Comment 4 Karsten Hohmeier 2016-02-01 14:38:46 UTC
Tested again with 4.5 RC2. Seems to be gone now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.