Summary: | Intel driver crashes after resume. | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Gaurav <g_kh> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | blocker | ||||||
Priority: | high | CC: | intel-gfx-bugs | ||||
Version: | XOrg git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | BDW | i915 features: | display/atomic | ||||
Attachments: |
|
Description
Gaurav
2016-07-09 05:27:23 UTC
Additional options in grub: quiet splash acpi_osi=Linux acpi=force acpi_enforce_resources=lax iwlwifi.power_save=1 i915.enable_rc6=7 i915.enable_fbc=1 i915.lvds_downclock=1 i915.enable_dc=2 i915.use_mmio_flip=1 i915.enable_psr=1 (In reply to Gaurav from comment #1) > Additional options in grub: quiet splash acpi_osi=Linux acpi=force > acpi_enforce_resources=lax iwlwifi.power_save=1 i915.enable_rc6=7 > i915.enable_fbc=1 i915.lvds_downclock=1 i915.enable_dc=2 > i915.use_mmio_flip=1 i915.enable_psr=1 These options will taint your kernel as they are *dangerous*. As a rule we will mark any bug as invalid if they are not reproduced using default options. Please do confirm this bug is present in a default configuration. (It should be.) And please attach the full dmesg. Created attachment 125064 [details]
Output of dmesg
I was able to reproduce the bug with default configuration also. Same behavior i.e. immediately hangs after resume. The laptop had 8-10 suspend/resume operations over last 2 days before this one where it slowed down the machine considerably i.e. gnome shell taking seconds to respond to any keyboard event (and this was when dmesg's output was taken) and ended up in hung state. More information: Using gnome shell 3.18.5. I had run powertop --auto-tune in the last session i.e. before suspending (closing the lid). Added complete output of dmesg (compressed) in the attachments. Does anyone any clue here? Is this issue still seen on latest kernel? Yes, I can still see this on 4.8.6 with default options. Distribution: ArchLinux Desktop environment: Cinnamon 3.2.7 Kernel: 4.8.13-1-ARCH Card: Intel Corporation HD Graphics 5500 (rev 09) Laptop: ASUS Zenbook UX305L Kernel options: quiet acpi_osi= nmi_watchdog=0 mesa 13.0.2 xf86-video-intel 1:2.99.917+746+g169c74f-1 Same card and same way of reproducing the bug as OP. janv. 07 20:44:40 archtop kernel: WARNING: CPU: 3 PID: 383 at drivers/gpu/drm/drm_irq.c:1224 drm_wait_one_vblank+0x1b1/0x1c0 [drm] janv. 07 20:44:40 archtop kernel: vblank wait timed out on crtc 0 janv. 07 20:44:40 archtop kernel: Modules linked in: ctr ccm fuse joydev mousedev arc4 iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerc janv. 07 20:44:40 archtop kernel: 8250_dw snd_hda_codec i2c_designware_platform i2c_i801 i2c_designware_core int3400_thermal acpi_als snd_hda_core janv. 07 20:44:40 archtop kernel: CPU: 3 PID: 383 Comm: Xorg Tainted: G U O 4.8.13-1-ARCH #1 janv. 07 20:44:40 archtop kernel: Hardware name: ASUSTeK COMPUTER INC. UX305LA/UX305LA, BIOS UX305LA.206 08/03/2015 janv. 07 20:44:40 archtop kernel: 0000000000000286 00000000460f4eb6 ffff88023ad038d8 ffffffff812fddc0 janv. 07 20:44:40 archtop kernel: ffff88023ad03928 0000000000000000 ffff88023ad03918 ffffffff8107c85b janv. 07 20:44:40 archtop kernel: 000004c800000000 ffff880242f90000 0000000000000000 0000000000000000 janv. 07 20:44:40 archtop kernel: Call Trace: janv. 07 20:44:40 archtop kernel: [<ffffffff812fddc0>] dump_stack+0x63/0x83 janv. 07 20:44:40 archtop kernel: [<ffffffff8107c85b>] __warn+0xcb/0xf0 janv. 07 20:44:40 archtop kernel: [<ffffffff8107c8df>] warn_slowpath_fmt+0x5f/0x80 janv. 07 20:44:40 archtop kernel: [<ffffffff810bffb5>] ? finish_wait+0x55/0x70 janv. 07 20:44:40 archtop kernel: [<ffffffffa043fca1>] drm_wait_one_vblank+0x1b1/0x1c0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffff810c0450>] ? wake_atomic_t_function+0x60/0x60 janv. 07 20:44:40 archtop kernel: [<ffffffffa06530ec>] hsw_disable_ips+0xcc/0x100 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa065314e>] intel_pre_disable_primary+0x2e/0x40 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa065350f>] intel_pre_plane_update+0x11f/0x170 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa0653634>] intel_update_crtc.isra.84+0xd4/0xe0 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa06536ac>] intel_update_crtcs+0x6c/0x90 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa0653d99>] intel_atomic_commit_tail+0x329/0x1050 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffff811e245c>] ? kmem_cache_alloc_trace+0x19c/0x1b0 janv. 07 20:44:40 archtop kernel: [<ffffffffa0654ef1>] intel_atomic_commit+0x431/0x540 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa04587b7>] ? drm_atomic_check_only+0x187/0x610 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa0458c77>] drm_atomic_commit+0x37/0x60 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa056964c>] drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper] janv. 07 20:44:40 archtop kernel: [<ffffffffa04576d5>] ? drm_modeset_lock+0x35/0xe0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa0446a2b>] __setplane_internal+0x17b/0x270 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa0457a04>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa044b4ec>] drm_mode_setplane+0x15c/0x1d0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa043dd40>] drm_ioctl+0x200/0x4f0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa044b390>] ? drm_plane_check_pixel_format+0x50/0x50 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffff8121c2f3>] do_vfs_ioctl+0xa3/0x5f0 janv. 07 20:44:40 archtop kernel: [<ffffffff810c7c37>] ? percpu_up_read+0x17/0x40 janv. 07 20:44:40 archtop kernel: [<ffffffff81227567>] ? __fget+0x77/0xb0 janv. 07 20:44:40 archtop kernel: [<ffffffff8121c8b9>] SyS_ioctl+0x79/0x90 janv. 07 20:44:40 archtop kernel: [<ffffffff815f8032>] entry_SYSCALL_64_fastpath+0x1a/0xa4 Followed by: janv. 07 20:44:40 archtop kernel: WARNING: CPU: 3 PID: 383 at drivers/gpu/drm/i915/intel_display.c:13712 intel_atomic_commit_tail+0x1037/0x1050 [i9 janv. 07 20:44:40 archtop kernel: pipe A vblank wait timed out janv. 07 20:44:40 archtop kernel: Modules linked in: ctr ccm fuse joydev mousedev arc4 iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerc janv. 07 20:44:40 archtop kernel: 8250_dw snd_hda_codec i2c_designware_platform i2c_i801 i2c_designware_core int3400_thermal acpi_als snd_hda_core janv. 07 20:44:40 archtop kernel: CPU: 3 PID: 383 Comm: Xorg Tainted: G U W O 4.8.13-1-ARCH #1 janv. 07 20:44:40 archtop kernel: Hardware name: ASUSTeK COMPUTER INC. UX305LA/UX305LA, BIOS UX305LA.206 08/03/2015 janv. 07 20:44:40 archtop kernel: 0000000000000286 00000000460f4eb6 ffff88023ad03a38 ffffffff812fddc0 janv. 07 20:44:40 archtop kernel: ffff88023ad03a88 0000000000000000 ffff88023ad03a78 ffffffff8107c85b janv. 07 20:44:40 archtop kernel: 0000359000000000 0000000000000000 0000000000000000 ffff880242f90000 janv. 07 20:44:40 archtop kernel: Call Trace: janv. 07 20:44:40 archtop kernel: [<ffffffff812fddc0>] dump_stack+0x63/0x83 janv. 07 20:44:40 archtop kernel: [<ffffffff8107c85b>] __warn+0xcb/0xf0 janv. 07 20:44:40 archtop kernel: [<ffffffff8107c8df>] warn_slowpath_fmt+0x5f/0x80 janv. 07 20:44:40 archtop kernel: [<ffffffff810bffb5>] ? finish_wait+0x55/0x70 janv. 07 20:44:40 archtop kernel: [<ffffffffa0654aa7>] intel_atomic_commit_tail+0x1037/0x1050 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffff810c0450>] ? wake_atomic_t_function+0x60/0x60 janv. 07 20:44:40 archtop kernel: [<ffffffffa0654ef1>] intel_atomic_commit+0x431/0x540 [i915] janv. 07 20:44:40 archtop kernel: [<ffffffffa04587b7>] ? drm_atomic_check_only+0x187/0x610 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa0458c77>] drm_atomic_commit+0x37/0x60 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa056964c>] drm_atomic_helper_disable_plane+0xac/0xf0 [drm_kms_helper] janv. 07 20:44:40 archtop kernel: [<ffffffffa04576d5>] ? drm_modeset_lock+0x35/0xe0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa0446a2b>] __setplane_internal+0x17b/0x270 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa0457a04>] ? drm_modeset_lock_all_ctx+0xa4/0xb0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa044b4ec>] drm_mode_setplane+0x15c/0x1d0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa043dd40>] drm_ioctl+0x200/0x4f0 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffffa044b390>] ? drm_plane_check_pixel_format+0x50/0x50 [drm] janv. 07 20:44:40 archtop kernel: [<ffffffff8121c2f3>] do_vfs_ioctl+0xa3/0x5f0 janv. 07 20:44:40 archtop kernel: [<ffffffff810c7c37>] ? percpu_up_read+0x17/0x40 janv. 07 20:44:40 archtop kernel: [<ffffffff81227567>] ? __fget+0x77/0xb0 janv. 07 20:44:40 archtop kernel: [<ffffffff8121c8b9>] SyS_ioctl+0x79/0x90 janv. 07 20:44:40 archtop kernel: [<ffffffff815f8032>] entry_SYSCALL_64_fastpath+0x1a/0xa4 With latest atomic and waterwmark done can you see this still on drm-tip? This looks fixed, at least on my system: 4.10.10-1-ARCH (+ other specs before) (In reply to Edgar Fournival from comment #10) > This looks fixed, at least on my system: 4.10.10-1-ARCH (+ other specs > before) Thanks Edgar. @Gaurav, can you confirm also on your side? This issue should be indeed fixed by now. Reporter, please comment if issues seen further, closing now. Feel free to-re-open if issues seen still. |
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.