[Bug 52061] WARNING: at drivers/gpu/drm/i915/intel_display.c:1009 intel_wait_for_pipe_off+0x12e/0x13a [i915]()

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Wed Apr 10 08:11:37 PDT 2013


https://bugzilla.kernel.org/show_bug.cgi?id=52061





--- Comment #8 from Kalin KOZHUHAROV <kalin at thinrope.net>  2013-04-10 15:11:36 ---
Hello and sorry for being unresponsive on a bug I filed :-|

At the moment I am running 3.8.0 and the bug is still present (2d ago) when I
booted on my docking station with an external (via HDMI) monitor.

The trace is a bit different this time, at least to my eyes:

[    0.000000] Linux version 3.8.0-r1 (root at ss3) (gcc version 4.6.3 (Gentoo
4.6.3 p1.9, pie-0.5.2) ) #1 SMP Mon Feb 25 00:02:26 JST 2013
[    0.000000] Command line: root=/dev/sda4

....

[    3.789001] ------------[ cut here ]------------
[    3.789049] WARNING: at drivers/gpu/drm/i915/intel_display.c:1028
intel_wait_for_pipe_off+0x14c/0x169 [i915]()
[    3.789051] Hardware name: dynabook R731/W2UB
[    3.789052] pipe_off wait timed out
[    3.789106] Modules linked in: fbcon(+) bitblit softcursor font
i2400m_usb(+) i2400m wimax btusb bluetooth snd_hda_codec_hdmi
snd_hda_codec_realtek arc4 iwldvm mac80211 i915 snd_hda_intel snd_hda_codec
i2c_algo_bit snd_hwdep intel_agp snd_pcm intel_gtt snd_page_alloc iwlwifi
drm_kms_helper snd_timer cfg80211 snd drm toshiba_acpi agpgart sparse_keymap
ehci_pci crc32c_intel wmi rfkill ehci_hcd sdhci_pci sr_mod sdhci xhci_hcd
mmc_core cdrom led_class pata_jmicron usbcore toshiba_bluetooth e1000e joydev
video usb_common
[    3.789112] Pid: 1331, comm: modprobe Tainted: G        W    3.8.0-r1 #1
[    3.789113] Call Trace:
[    3.789130]  [<ffffffff8105528f>] warn_slowpath_common+0x7e/0x96
[    3.789137]  [<ffffffff8105533b>] warn_slowpath_fmt+0x41/0x43
[    3.789166]  [<ffffffffa02619e3>] intel_wait_for_pipe_off+0x14c/0x169 [i915]
[    3.789191]  [<ffffffffa0261b46>] intel_disable_pipe+0x146/0x14e [i915]
[    3.789214]  [<ffffffffa02621bd>] ironlake_crtc_disable+0xc6/0x769 [i915]
[    3.789242]  [<ffffffffa026c898>] ? intel_lvds_mode_fixup+0xb8/0x2e8 [i915]
[    3.789269]  [<ffffffffa0268922>] intel_set_mode+0x3d5/0x7fc [i915]
[    3.789297]  [<ffffffffa026934b>] intel_crtc_set_config+0x602/0x733 [i915]
[    3.789308]  [<ffffffffa020c81a>] drm_fb_helper_set_par+0x69/0xb2
[drm_kms_helper]
[    3.789317]  [<ffffffffa0497e31>] fbcon_init+0x30e/0x409 [fbcon]
[    3.789324]  [<ffffffff812e5293>] visual_init+0xb8/0x10e
[    3.789329]  [<ffffffff812e6484>] bind_con_driver+0x1af/0x2af
[    3.789336]  [<ffffffffa049f000>] ? 0xffffffffa049efff
[    3.789342]  [<ffffffff812e65bc>] take_over_console+0x38/0x45
[    3.789349]  [<ffffffffa04962ed>] fbcon_takeover+0x4f/0x7d [fbcon]
[    3.789356]  [<ffffffffa049f118>] fb_console_init+0x118/0x11f [fbcon]
[    3.789360]  [<ffffffffa049f000>] ? 0xffffffffa049efff
[    3.789366]  [<ffffffff8100209a>] do_one_initcall+0x7a/0x134
[    3.789373]  [<ffffffff810a0684>] load_module+0x1641/0x193d
[    3.789379]  [<ffffffff8109c4ac>] ? sys_getegid16+0x44/0x44
[    3.789386]  [<ffffffff8144d658>] ? page_fault+0x28/0x30
[    3.789391]  [<ffffffff810a0a29>] sys_init_module+0xa9/0xab
[    3.789399]  [<ffffffff8144dc29>] system_call_fastpath+0x16/0x1b
[    3.789402] ---[ end trace 780565dd4a0d8eb7 ]---

Judging from the time in prink, it only occurs on boot with the
dockstation/monitor plugged in around 3.7s from boot on 3.8.0 and 4.7s from
boot on 3.7.1...

Today I booted and later plugged the machine to the dock (followed by at least
1-2 more plug/unplugs), but the bug hasn't shown up. Every replug includes
xrandr --off (actually arandr) since I need to switch my displays.

I just unplugged, waited 5s and re-plugged the HDMI, nothing was reported in
dmesg.

I know it is a WARN only, but are you saying we should just ignore it?
Is there any other test I can be helpful with?
In a bout a week I'll have another revision of the same hardware to test
(dynabook R732), in case it is hardware specific to these laptops.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list