Created attachment 85886 [details] dmesg: boot up with "*ERROR* GT fifo" Environment: -------------------- Kernel: (drm-intel-next-queued)6c4a8962a4a078cacfc8eb5d4bd79f6343b8cd7a Author: Jesse Barnes <jbarnes@virtuousgeek.org> Date: Tue Sep 10 14:54:42 2013 -0700 drm/i915/vlv: re-enable hotplug detect based probing on VLV/BYT lspci: -------------------- 00:02.0 VGA compatible controller: Intel Corporation ValleyView Gen7 (rev 0a) Description: -------------------- Test with latest -next-queued kernel, there's "*ERROR* GT fifo" in dmesg when machine boot up. I tested other IVB platform, there's not this issue. Older kernels also reproduceable. We are testing Baytrail machine recently, and it might not be a regression. Error: -------------------- [ 2.710082] [drm:valleyview_enable_rps] *ERROR* GT fifo had a previous error 10
This is actually a BIOS bug. I've filed a bug with them to investigate, but it occurs even without the gfx driver loaded, so I'm marking as "not our bug" and reducing the message to a debug one.
(In reply to comment #1) > This is actually a BIOS bug. I've filed a bug with them to investigate, but > it occurs even without the gfx driver loaded, so I'm marking as "not our > bug" and reducing the message to a debug one. Got it, can you comment the Bug ID here? We wanna to track it. Thx.
(In reply to comment #1) > This is actually a BIOS bug. I've filed a bug with them to investigate, but > it occurs even without the gfx driver loaded, so I'm marking as "not our > bug" and reducing the message to a debug one. Hi Jesse, can you paste your Bug ID here, and we want to have a bug to track this issue. When you the information, I could verify this bug. Thx.
https://vthsd.intel.com/hsd/clientsw/bug/default.aspx?bug_id=5154767
(In reply to comment #4) > https://vthsd.intel.com/hsd/clientsw/bug/default.aspx?bug_id=5154767 Sorry, bother you again. I tried to open this link, but the page remind me "Record 5154767 not found". :)
Closing old verified.
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.