Re: [Intel-gfx] v3.6 haswell regression from v3.5?
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] [8104f67f] warn_slowpath_common+0x7f/0xc0 [ 16.665023] [8104f776] warn_slowpath_fmt+0x46/0x50 [ 16.665058] usb 1-11: new low-speed USB device number 2 using xhci_hcd [ 16.679111] [a00b8c57] assert_fdi_tx+0x87/0x90 [i915] [ 16.686001] [a00bdd65] 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] [a00be48e] ironlake_crtc_dpms+0x8e/0xa0 [i915] [ 16.711309] [a00b9bc8] intel_crtc_dpms+0x48/0x140 [i915] [ 16.718487] [a00c1af5] intel_crtc_disable+0x35/0xb0 [i915] [ 16.721916] usbcore: registered new interface driver usbhid [ 16.721917] usbhid: USB HID core driver [ 16.736714] [a008c6a5] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [ 16.746959] [a00c3ba7] intel_modeset_init+0x687/0xe50 [i915] [ 16.754536] [a009cd3a] i915_driver_load+0xa9a/0xb80 [i915] [ 16.761932] [a003aa7b] ? drm_get_minor+0x26b/0x310 [drm] [ 16.769086] [a003ce71] drm_get_pci_dev+0x191/0x2b0 [drm] [ 16.776278] [8157801e] ? _raw_spin_unlock_irqrestore+0x1e/0x30 [ 16.784065] [a00e5917] i915_pci_probe+0x1b/0x1d [i915] [ 16.791041] [812da410] pci_device_probe+0xb0/0x140 [ 16.797631] [813909be] driver_probe_device+0x7e/0x220 [ 16.804527] [81390c0b] __driver_attach+0xab/0xb0 [ 16.810929] [81390b60] ? driver_probe_device+0x220/0x220 [ 16.818106] [8138ede6] bus_for_each_dev+0x56/0x90 [ 16.824609] [813904ce] driver_attach+0x1e/0x20 [ 16.830814] [81390080] bus_add_driver+0x1a0/0x270 [ 16.837305] [81391166] driver_register+0x76/0x130 [ 16.843805] [812da135] __pci_register_driver+0x55/0xd0 [ 16.850795] [8157bdcd] ? notifier_call_chain+0x4d/0x70 [ 16.857786] [a003d0aa] drm_pci_init+0x11a/0x130 [drm] [ 16.859591] usb 1-12: new low-speed USB device number 3 using xhci_hcd [ 16.872169] [a0116000] ? 0xa0115fff [ 16.878075] [a011608b] i915_init+0x8b/0x8d [i915] [ 16.884568] [8100203f] do_one_initcall+0x3f/0x170 [ 16.887716] usb 1-12: ep 0x81 - rounding interval to 128 microframes, ep desc says 192 microframes [ 16.901316] [810affcf] sys_init_module+0x8f/0x200 [ 16.907797] [81580069] system_call_fastpath+0x16/0x1b [ 16.914692] ---[ end trace 941488b1333d181e ]--- On Fri, Aug 10, 2012 at 10:21 PM, Ben Guthro b...@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 b...@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@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Ben Widawsky, Intel Open Source Technology Center
[Intel-gfx] v3.6 haswell regression from v3.5?
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 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] v3.6 haswell regression from v3.5?
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::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] [8105284f] warn_slowpath_common+0x7f/0xc0 [ 16.016356] [81052946] warn_slowpath_fmt+0x46/0x50 [ 16.019911] usb 1-5: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 16.032989] [a00c48c7] assert_fdi_tx+0x87/0x90 [i915] [ 16.040070] [a00c9f55] ironlake_crtc_disable+0x185/0x820 [i915] [ 16.047923] [a00ca67e] ironlake_crtc_dpms+0x8e/0xa0 [i915] [ 16.055302] [a00c5a58] intel_crtc_dpms+0x48/0x140 [i915] [ 16.061100] usbcore: registered new interface driver usbhid [ 16.061101] usbhid: USB HID core driver [ 16.073325] [a00cdf95] intel_crtc_disable+0x35/0xb0 [i915] [ 16.080700] [a0095735] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [ 16.090943] [a00d00a7] intel_modeset_init+0x6b7/0xf10 [i915] [ 16.098525] [a00a6bba] i915_driver_load+0xa8a/0xb90 [i915] [ 16.105913] [a004372b] ? drm_get_minor+0x26b/0x310 [drm] [ 16.113082] [a0045c21] drm_get_pci_dev+0x191/0x2b0 [drm] [ 16.120276] [8158f30e] ? _raw_spin_unlock_irqrestore+0x1e/0x30 [ 16.128061] [a00f309b] i915_pci_probe+0x4f/0x57 [i915] [ 16.135039] [812e0d30] pci_device_probe+0xb0/0x140 [ 16.141631] [8139faab] driver_probe_device+0x7b/0x240 [ 16.148525] [8139fd1b] __driver_attach+0xab/0xb0 [ 16.154927] [8139fc70] ? driver_probe_device+0x240/0x240 [ 16.162106] [8139dec6] bus_for_each_dev+0x56/0x90 [ 16.168607] [8139f5de] driver_attach+0x1e/0x20 [ 16.174811] [8139f150] bus_add_driver+0x190/0x290 [ 16.181303] [813a027a] driver_register+0x7a/0x160 [ 16.187805] [812e0a55] __pci_register_driver+0x55/0xd0 [ 16.193436] usb 1-6: new low-speed USB device number 3 using xhci_hcd [ 16.202180] [815930cd] ? notifier_call_chain+0x4d/0x70 [ 16.209173] [a0045e5a] drm_pci_init+0x11a/0x130 [drm] [ 16.216061] [a0125000] ? 0xa0124fff [ 16.221970] [a0125066] i915_init+0x66/0x68 [i915] [ 16.223558] usb 1-6: ep 0x81 - rounding interval to 128 microframes, ep desc says 192 microframes [ 16.238617] [8100203f] do_one_initcall+0x3f/0x170 [ 16.245104] [810b3dbf] sys_init_module+0x8f/0x200 [ 16.251599] [815973a9] system_call_fastpath+0x16/0x1b [ 16.258494] ---[ end trace 949ccd38b0452265 ]--- On Fri, Aug 10, 2012 at 12:25 PM, Ben Guthro b...@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 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] v3.6 haswell regression from v3.5?
On Fri, Aug 10, 2012 at 12:51:42PM -0400, Ben Guthro wrote: 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: Can you try to boot with i915.i915_enable_rc6=0 please? -Daniel [ 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::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] [8105284f] warn_slowpath_common+0x7f/0xc0 [ 16.016356] [81052946] warn_slowpath_fmt+0x46/0x50 [ 16.019911] usb 1-5: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 16.032989] [a00c48c7] assert_fdi_tx+0x87/0x90 [i915] [ 16.040070] [a00c9f55] ironlake_crtc_disable+0x185/0x820 [i915] [ 16.047923] [a00ca67e] ironlake_crtc_dpms+0x8e/0xa0 [i915] [ 16.055302] [a00c5a58] intel_crtc_dpms+0x48/0x140 [i915] [ 16.061100] usbcore: registered new interface driver usbhid [ 16.061101] usbhid: USB HID core driver [ 16.073325] [a00cdf95] intel_crtc_disable+0x35/0xb0 [i915] [ 16.080700] [a0095735] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [ 16.090943] [a00d00a7] intel_modeset_init+0x6b7/0xf10 [i915] [ 16.098525] [a00a6bba] i915_driver_load+0xa8a/0xb90 [i915] [ 16.105913] [a004372b] ? drm_get_minor+0x26b/0x310 [drm] [ 16.113082] [a0045c21] drm_get_pci_dev+0x191/0x2b0 [drm] [ 16.120276] [8158f30e] ? _raw_spin_unlock_irqrestore+0x1e/0x30 [ 16.128061] [a00f309b] i915_pci_probe+0x4f/0x57 [i915] [ 16.135039] [812e0d30] pci_device_probe+0xb0/0x140 [ 16.141631] [8139faab] driver_probe_device+0x7b/0x240 [ 16.148525] [8139fd1b] __driver_attach+0xab/0xb0 [ 16.154927] [8139fc70] ? driver_probe_device+0x240/0x240 [ 16.162106] [8139dec6] bus_for_each_dev+0x56/0x90 [ 16.168607] [8139f5de] driver_attach+0x1e/0x20 [ 16.174811] [8139f150] bus_add_driver+0x190/0x290 [ 16.181303] [813a027a] driver_register+0x7a/0x160 [ 16.187805] [812e0a55] __pci_register_driver+0x55/0xd0 [ 16.193436] usb 1-6: new low-speed USB device number 3 using xhci_hcd [ 16.202180] [815930cd] ? notifier_call_chain+0x4d/0x70 [ 16.209173] [a0045e5a] drm_pci_init+0x11a/0x130 [drm] [ 16.216061] [a0125000] ? 0xa0124fff [ 16.221970] [a0125066] i915_init+0x66/0x68 [i915] [ 16.223558] usb 1-6: ep 0x81 - rounding interval to 128 microframes, ep desc says 192 microframes [ 16.238617] [8100203f] do_one_initcall+0x3f/0x170 [ 16.245104] [810b3dbf] sys_init_module+0x8f/0x200 [ 16.251599] [815973a9] system_call_fastpath+0x16/0x1b [ 16.258494] ---[ end trace 949ccd38b0452265 ]--- On Fri, Aug 10, 2012 at 12:25 PM, Ben Guthro b...@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 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Mail:
Re: [Intel-gfx] v3.6 haswell regression from v3.5?
well...it gave me a different stack...but still no graphics: This is with the drm-intel-fixes branch merged in - I thought that branch might help...but it didn't seem to. [ 16.615950] [ cut here ] [ 16.621229] WARNING: at /data/home/bguthro/dev/newdev-tip/linux-3.2/drivers/gpu/drm/i915/intel_display.c:1119 assert_fdi_tx+0x87/0x90 [i915]() [ 16.635796] Hardware name: Shark Bay Client platform [ 16.641472] FDI TX state assertion failure (expected off, current on) [ 16.648863] 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 [ 16.664808] Pid: 141, comm: modprobe Not tainted 3.6.0-orc #11 [ 16.671503] Call Trace: [ 16.674364] [8105284f] warn_slowpath_common+0x7f/0xc0 [ 16.681250] [81052946] warn_slowpath_fmt+0x46/0x50 [ 16.681305] usb 1-5: new low-speed USB device number 2 using xhci_hcd [ 16.695251] [a00c48f7] assert_fdi_tx+0x87/0x90 [i915] [ 16.702135] [a00c9fd5] ironlake_crtc_disable+0x185/0x820 [i915] [ 16.710013] [a00ca6fe] ironlake_crtc_dpms+0x8e/0xa0 [i915] [ 16.711864] usb 1-5: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 16.727384] [a00c5a88] intel_crtc_dpms+0x48/0x140 [i915] [ 16.734590] [a00ce015] intel_crtc_disable+0x35/0xb0 [i915] [ 16.741932] [a0095735] drm_helper_disable_unused_functions+0x115/0x190 [drm_kms_helper] [ 16.751668] usbcore: registered new interface driver usbhid [ 16.751669] usbhid: USB HID core driver [ 16.763019] [a00d0127] intel_modeset_init+0x6b7/0xf10 [i915] [ 16.770594] [a00a6bba] i915_driver_load+0xa8a/0xb90 [i915] [ 16.777977] [a004372b] ? drm_get_minor+0x26b/0x310 [drm] [ 16.785143] [a0045c21] drm_get_pci_dev+0x191/0x2b0 [drm] [ 16.792337] [8158553e] ? _raw_spin_unlock_irqrestore+0x1e/0x30 [ 16.800125] [a00f31eb] i915_pci_probe+0x4f/0x57 [i915] [ 16.807096] [812e0d30] pci_device_probe+0xb0/0x140 [ 16.813689] [813997cb] driver_probe_device+0x7b/0x240 [ 16.820582] [81399a3b] __driver_attach+0xab/0xb0 [ 16.826984] [8130] ? driver_probe_device+0x240/0x240 [ 16.834163] [81397be6] bus_for_each_dev+0x56/0x90 [ 16.840664] [813992fe] driver_attach+0x1e/0x20 [ 16.840694] usb 1-6: new low-speed USB device number 3 using xhci_hcd [ 16.854251] [81398e70] bus_add_driver+0x190/0x290 [ 16.860748] [81399f9a] driver_register+0x7a/0x160 [ 16.867247] [812e0a55] __pci_register_driver+0x55/0xd0 [ 16.868830] usb 1-6: ep 0x81 - rounding interval to 128 microframes, ep desc says 192 microframes [ 16.884396] [8158930d] ? notifier_call_chain+0x4d/0x70 [ 16.891397] [a0045e5a] drm_pci_init+0x11a/0x130 [drm] [ 16.898260] [a0125000] ? 0xa0124fff [ 16.904172] [a0125066] i915_init+0x66/0x68 [i915] [ 16.910666] [8100203f] do_one_initcall+0x3f/0x170 [ 16.917167] [810b3dbf] sys_init_module+0x8f/0x200 [ 16.923652] [8158d5e9] system_call_fastpath+0x16/0x1b [ 16.930548] ---[ end trace fa81da3bacf4c4b0 ]--- On Fri, Aug 10, 2012 at 1:16 PM, Daniel Vetter dan...@ffwll.ch wrote: On Fri, Aug 10, 2012 at 12:51:42PM -0400, Ben Guthro wrote: 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: Can you try to boot with i915.i915_enable_rc6=0 please? -Daniel [ 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::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] [8105284f] warn_slowpath_common+0x7f/0xc0 [ 16.016356] [81052946] warn_slowpath_fmt+0x46/0x50 [ 16.019911] usb 1-5: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 16.032989] [a00c48c7] assert_fdi_tx+0x87/0x90 [i915] [ 16.040070] [a00c9f55]
Re: [Intel-gfx] v3.6 haswell regression from v3.5?
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@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Ben Widawsky, Intel Open Source Technology Center ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] v3.6 haswell regression from v3.5?
I'll try to do this early next week, and report back. On Fri, Aug 10, 2012 at 7:37 PM, Ben Widawsky b...@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@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Ben Widawsky, Intel Open Source Technology Center ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
