| Summary: | [ivb] BIOS does not support MT forcewake | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | anish613 | ||||||||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||||||
| Severity: | normal | ||||||||||||||||
| Priority: | medium | ||||||||||||||||
| Version: | XOrg git | ||||||||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||||||
| OS: | Linux (All) | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| i915 platform: | i915 features: | ||||||||||||||||
| Attachments: |
|
||||||||||||||||
Created attachment 81376 [details]
Dmesg logs when booting with kernel 3.7.9
Created attachment 81377 [details]
Lspci outpuit
Created attachment 81378 [details]
Non-working kernel Xorg.log
Created attachment 81379 [details]
Working kernel Xorg.log
Can you see if there is an upgrade for your BIOS - it doesn't seem to be entirely ready for IVB? I just updated my bios to an update released on 2013-03-05 and the problem still persists. I am not sure if the forcewake ERROR is as red herring because both the working and nonworking dmesg logs show that error, but the nonworking kernel contains: [ 4.174355] [drm:init_ring_common] *ERROR* bsd ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000 [ 4.174432] [drm:gm45_get_vblank_counter], trying to get vblank count for disabled pipe C [ 4.174439] [drm:i915_driver_load] *ERROR* failed to init modeset [ 4.175224] i915: probe of 0000:00:02.0 failed with error -5 I just learned about git bisect and I am attempting to narrow down the issue between kernel 3.7.9 and 3.8.3. (Linux takes a long time to build) It seems that the BIOS upgrade did have some impact on the behavior. Now when I boot using linux 3.8 or 3.9, the screen either randomly shows scrambled lines as before or starts X as normal and the CPU hangs after I log in. because of the random behavior, it has been difficult to bisect the code which lead to this problem. I am attaching a file which contains the dmesg logs showing the CPU hard lockup error. Created attachment 82130 [details]
CPU Hang dmesg log
Partial revert merged to -fixes with cc: stable: commit c11e5f35ab490bd30591563816fbc83526521777 Author: Guenter Roeck <linux@roeck-us.net> Date: Tue Jul 9 16:00:31 2013 -0700 Partially revert "drm/i915: unconditionally use mt forcewake on hsw/ivb" |
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.
Created attachment 81375 [details] Dmesg logs with errors when booting with kernel 3.9.7 When booting with Linux kernel 3.8.x or higher, the video output is corrupted (usually red and green lines) and X does not start. It starts working again after I downgrade to kernel 3.7.9 These are the packages installed on my machine: Name : intel-dri Version : 9.1.3-2 Description : Mesa drivers for Intel Architecture : x86_64 Name : linux Version : 3.9.7-1 Description : The linux kernel and modules Architecture : x86_64 Name : mesa Version : 9.1.3-2 Description : an open-source implementation of the OpenGL specification Architecture : x86_64 The behavior is the same regardless of the inter-dri version I have installed. I am attaching the dmesg output with drm.debug=0xe in the kernel boot parameters for the working and nonworking kernels. I am also attaching the working and nonworking Xorg.log files and the output of "lspci -v". Let me know if I can provide any more information.