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

[Ben Guthro]

I'm struggling to get back to a version that works on the Shark Bay /
Haswell platform that I have.

I did get it to work once...but have since updated the BIOS, so am not
sure if that may have an effect on this test.

v3.5 also gave a stack (below) - so without a working version, I
cannot do the bisecting.

Perhaps it is just too early in the Haswell dev cycle for me to try to
get this working?



[   16.599822] ------------[ cut here ]------------
[   16.605099] WARNING: at
/data/home/bguthro/dev/newdev-tip/linux-3.5/drivers/gpu/drm/i915/intel_display.c:976
assert_fdi_tx+0x87/0x90 [i915]()
[   16.619568] Hardware name: Shark Bay Client platform
[   16.625244] FDI TX state assertion failure (expected off, current on)
[   16.632632] Modules linked in: ahci(+) libahci crc32c_intel
e1000e(+) ehci_hcd(+) i915(+) drm_kms_helper drm i2c_algo_bit video
xhci_hcd intel_agp intel_gtt
[   16.648576] Pid: 142, comm: modprobe Not tainted 3.5.0-orc #14
[   16.655275] Call Trace:
[   16.658130]  [<ffffffff8104f67f>] warn_slowpath_common+0x7f/0xc0
[   16.665023]  [<ffffffff8104f776>] warn_slowpath_fmt+0x46/0x50
[   16.665058] usb 1-11: new low-speed USB device number 2 using xhci_hcd
[   16.679111]  [<ffffffffa00b8c57>] assert_fdi_tx+0x87/0x90 [i915]
[   16.686001]  [<ffffffffa00bdd65>] ironlake_crtc_disable+0x185/0x820 [i915]
[   16.689451] usb 1-11: ep 0x81 - rounding interval to 64
microframes, ep desc says 80 microframes
[   16.703942]  [<ffffffffa00be48e>] ironlake_crtc_dpms+0x8e/0xa0 [i915]
[   16.711309]  [<ffffffffa00b9bc8>] intel_crtc_dpms+0x48/0x140 [i915]
[   16.718487]  [<ffffffffa00c1af5>] intel_crtc_disable+0x35/0xb0 [i915]
[   16.721916] usbcore: registered new interface driver usbhid
[   16.721917] usbhid: USB HID core driver
[   16.736714]  [<ffffffffa008c6a5>]
drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper]
[   16.746959]  [<ffffffffa00c3ba7>] intel_modeset_init+0x687/0xe50 [i915]
[   16.754536]  [<ffffffffa009cd3a>] i915_driver_load+0xa9a/0xb80 [i915]
[   16.761932]  [<ffffffffa003aa7b>] ? drm_get_minor+0x26b/0x310 [drm]
[   16.769086]  [<ffffffffa003ce71>] drm_get_pci_dev+0x191/0x2b0 [drm]
[   16.776278]  [<ffffffff8157801e>] ? _raw_spin_unlock_irqrestore+0x1e/0x30
[   16.784065]  [<ffffffffa00e5917>] i915_pci_probe+0x1b/0x1d [i915]
[   16.791041]  [<ffffffff812da410>] pci_device_probe+0xb0/0x140
[   16.797631]  [<ffffffff813909be>] driver_probe_device+0x7e/0x220
[   16.804527]  [<ffffffff81390c0b>] __driver_attach+0xab/0xb0
[   16.810929]  [<ffffffff81390b60>] ? driver_probe_device+0x220/0x220
[   16.818106]  [<ffffffff8138ede6>] bus_for_each_dev+0x56/0x90
[   16.824609]  [<ffffffff813904ce>] driver_attach+0x1e/0x20
[   16.830814]  [<ffffffff81390080>] bus_add_driver+0x1a0/0x270
[   16.837305]  [<ffffffff81391166>] driver_register+0x76/0x130
[   16.843805]  [<ffffffff812da135>] __pci_register_driver+0x55/0xd0
[   16.850795]  [<ffffffff8157bdcd>] ? notifier_call_chain+0x4d/0x70
[   16.857786]  [<ffffffffa003d0aa>] drm_pci_init+0x11a/0x130 [drm]
[   16.859591] usb 1-12: new low-speed USB device number 3 using xhci_hcd
[   16.872169]  [<ffffffffa0116000>] ? 0xffffffffa0115fff
[   16.878075]  [<ffffffffa011608b>] i915_init+0x8b/0x8d [i915]
[   16.884568]  [<ffffffff8100203f>] do_one_initcall+0x3f/0x170
[   16.887716] usb 1-12: ep 0x81 - rounding interval to 128
microframes, ep desc says 192 microframes
[   16.901316]  [<ffffffff810affcf>] sys_init_module+0x8f/0x200
[   16.907797]  [<ffffffff81580069>] system_call_fastpath+0x16/0x1b
[   16.914692] ---[ end trace 941488b1333d181e ]---



On Fri, Aug 10, 2012 at 10:21 PM, Ben Guthro <ben at guthro.net> wrote:
> I'll try to do this early next week, and report back.
>
>
> On Fri, Aug 10, 2012 at 7:37 PM, Ben Widawsky <ben at bwidawsk.net> wrote:
>> On 2012-08-10 09:25, Ben Guthro 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?
>>>
>>
>> Yes it is the codebase you should use. It sounds like a regression, can you
>> bisect it?
>>
>>
>>>
>>> Ben
>>> _______________________________________________
>>> Intel-gfx mailing list
>>> Intel-gfx at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>
>>
>> --
>> Ben Widawsky, Intel Open Source Technology Center
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx