[Intel-gfx] v3.6 haswell regression from v3.5?

[Ben Guthro]

specifically, I get the following in my serial console - it is a
warning...but seems to coincide with when standard vesa modes are
switching over to the higer res KMS modes:

[   15.889193] [drm:__gen6_gt_force_wake_mt_get] *ERROR* Force wake
wait timed out
[   15.897707] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   15.905161] [drm] Driver supports precise vblank timestamp query.
[   15.912293] vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   15.943700] ------------[ cut here ]------------
[   15.949041] WARNING: at
/data/home/bguthro/dev/newdev-tip/linux-3.2/drivers/gpu/drm/i915/intel_display.c:1118
assert_fdi_tx+0x87/0x90 [i915]()
[   15.963591] Hardware name: Shark Bay Client platform
[   15.969288] FDI TX state assertion failure (expected off, current on)
[   15.976678] Modules linked in: crc32c_intel ahci(+) libahci
ehci_hcd(+) e1000e(+) i915(+) drm_kms_helper drm intel_agp
i2c_algo_bit intel_gtt video xhci_hcd
[   15.992621] Pid: 148, comm: modprobe Not tainted 3.6.0-orc #9
[   15.993459] usb 1-5: new low-speed USB device number 2 using xhci_hcd
[   16.006609] Call Trace:
[   16.009462]  [<ffffffff8105284f>] warn_slowpath_common+0x7f/0xc0
[   16.016356]  [<ffffffff81052946>] warn_slowpath_fmt+0x46/0x50
[   16.019911] usb 1-5: ep 0x81 - rounding interval to 64 microframes,
ep desc says 80 microframes
[   16.032989]  [<ffffffffa00c48c7>] assert_fdi_tx+0x87/0x90 [i915]
[   16.040070]  [<ffffffffa00c9f55>] ironlake_crtc_disable+0x185/0x820 [i915]
[   16.047923]  [<ffffffffa00ca67e>] ironlake_crtc_dpms+0x8e/0xa0 [i915]
[   16.055302]  [<ffffffffa00c5a58>] intel_crtc_dpms+0x48/0x140 [i915]
[   16.061100] usbcore: registered new interface driver usbhid
[   16.061101] usbhid: USB HID core driver
[   16.073325]  [<ffffffffa00cdf95>] intel_crtc_disable+0x35/0xb0 [i915]
[   16.080700]  [<ffffffffa0095735>]
drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper]
[   16.090943]  [<ffffffffa00d00a7>] intel_modeset_init+0x6b7/0xf10 [i915]
[   16.098525]  [<ffffffffa00a6bba>] i915_driver_load+0xa8a/0xb90 [i915]
[   16.105913]  [<ffffffffa004372b>] ? drm_get_minor+0x26b/0x310 [drm]
[   16.113082]  [<ffffffffa0045c21>] drm_get_pci_dev+0x191/0x2b0 [drm]
[   16.120276]  [<ffffffff8158f30e>] ? _raw_spin_unlock_irqrestore+0x1e/0x30
[   16.128061]  [<ffffffffa00f309b>] i915_pci_probe+0x4f/0x57 [i915]
[   16.135039]  [<ffffffff812e0d30>] pci_device_probe+0xb0/0x140
[   16.141631]  [<ffffffff8139faab>] driver_probe_device+0x7b/0x240
[   16.148525]  [<ffffffff8139fd1b>] __driver_attach+0xab/0xb0
[   16.154927]  [<ffffffff8139fc70>] ? driver_probe_device+0x240/0x240
[   16.162106]  [<ffffffff8139dec6>] bus_for_each_dev+0x56/0x90
[   16.168607]  [<ffffffff8139f5de>] driver_attach+0x1e/0x20
[   16.174811]  [<ffffffff8139f150>] bus_add_driver+0x190/0x290
[   16.181303]  [<ffffffff813a027a>] driver_register+0x7a/0x160
[   16.187805]  [<ffffffff812e0a55>] __pci_register_driver+0x55/0xd0
[   16.193436] usb 1-6: new low-speed USB device number 3 using xhci_hcd
[   16.202180]  [<ffffffff815930cd>] ? notifier_call_chain+0x4d/0x70
[   16.209173]  [<ffffffffa0045e5a>] drm_pci_init+0x11a/0x130 [drm]
[   16.216061]  [<ffffffffa0125000>] ? 0xffffffffa0124fff
[   16.221970]  [<ffffffffa0125066>] i915_init+0x66/0x68 [i915]
[   16.223558] usb 1-6: ep 0x81 - rounding interval to 128
microframes, ep desc says 192 microframes
[   16.238617]  [<ffffffff8100203f>] do_one_initcall+0x3f/0x170
[   16.245104]  [<ffffffff810b3dbf>] sys_init_module+0x8f/0x200
[   16.251599]  [<ffffffff815973a9>] system_call_fastpath+0x16/0x1b
[   16.258494] ---[ end trace 949ccd38b0452265 ]---




On Fri, Aug 10, 2012 at 12:25 PM, Ben Guthro <ben at guthro.net> wrote:
> Hello, I've been attempting to get a Shark Bay / Haswell platform up &
> running, and have been having some difficulties that I'm hoping you
> all can possibly help with.
>
> I first tried the 3.5 kernel, and had some success after applying the
> following patch:
> https://patchwork.kernel.org/patch/1229541/
>
> This seemed to be necessary to get the  0x0c26 PCI id to be loaded by
> i915, and use KMS.
>
> After doing this, I had some success, but things still would become
> unstable, and flash test patterns on the screen about every third
> boot.
>
>
> I figured that I would move on to the tip, and see if that fixed anything.
>
> However, at the tip, I cannot get i915 to display graphics at all -
> even with applying the patch above.
>
>
> I understand that this is still under development - but this seems
> like a regression from 3.5
> Is there a codebase that I should be using for this testing?
>
>
> Ben