Created attachment 72323 [details] dmesg from Booting up Environment: --------------------- kernel commit: c0c36b941b6f0be6ac74f340040cbb29d6a0b06c drm/i915: Return the real error code from intel_set_mode() Description: --------------------- After booting up, there's an error in dmesg like below: [drm:i915_write32] *ERROR* Unknown unclaimed register before writing to c5100
Created attachment 72324 [details] message from intel_reg_dumper
Created attachment 72326 [details] lspci message
is this regression? I'm decreasing severity as I don't see real bad impact to users.
The first one is likely garbage left over from the BIOS, I think we need to tune down the debug message there. The later ones sound like real bugs ...
Created attachment 72614 [details] [review] tune down debug message
(In reply to comment #5) > Created attachment 72614 [details] [review] [review] > tune down debug message This patch worked, this error dmesg doesn't exist while this patch applied on latest -next-queued commit.
Created attachment 72775 [details] [review] reset unclaimed register writes errors on takeover New patch for you to test, with a different approach.
(In reply to comment #7) > Created attachment 72775 [details] [review] [review] > reset unclaimed register writes errors on takeover > > New patch for you to test, with a different approach. Apply this patch on top commit of branch -next-queued, this error information will appeared in dmesg. commit: 9c7a47e7ca7c694ff4f19b568ad4ce1dba64dbd0 [ 1.786664] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed
Created attachment 72840 [details] dmesg (In reply to comment #8) > (In reply to comment #7) > > Created attachment 72775 [details] [review] [review] [review] > > reset unclaimed register writes errors on takeover > > > > New patch for you to test, with a different approach. > > Apply this patch on top commit of branch -next-queued, > > this error information will appeared in dmesg. > > commit: 9c7a47e7ca7c694ff4f19b568ad4ce1dba64dbd0 > > [ 1.786664] [drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed Modify: --------------- [ 5.032931] [drm:i915_write32] *ERROR* Unknown unclaimed register before writing to c5100
Hm, then there's something strange going on, I need to analyze this further ...
*** Bug 59549 has been marked as a duplicate of this bug. ***
Daniel's patch certainly fixes the problem for me... Are you really sure you tested a Kernel with Daniel's patch? Anyway, I've proposed changing from GEN7_ERROR_INT to FPGA_DBG, so there's a new patch on the mailing list that will fix this bug after we convert to FPGA_DBG.
(In reply to comment #12) > Daniel's patch certainly fixes the problem for me... Are you really sure you > tested a Kernel with Daniel's patch? > I applied the patch on top -next-queued commit, then retest it on my HSW machine, the error dmesg also exist. Machine Information: ---------------------------- HSW desktop: BIOS Version: HSWLPTU1.86C.0093.R00.1209242321 Stepping: C0 > Anyway, I've proposed changing from GEN7_ERROR_INT to FPGA_DBG, so there's a > new patch on the mailing list that will fix this bug after we convert to > FPGA_DBG. Please give a link of the patch, I can't find a patch related to this bug on mailing list. Thanks...
(In reply to comment #13) > (In reply to comment #12) > > Daniel's patch certainly fixes the problem for me... Are you really sure you > > tested a Kernel with Daniel's patch? > > > I applied the patch on top -next-queued commit, then retest it on my HSW > machine, the error dmesg also exist. Can you please attach dmesg? > > Machine Information: > ---------------------------- > HSW desktop: > BIOS Version: HSWLPTU1.86C.0093.R00.1209242321 > Stepping: C0 > > > Anyway, I've proposed changing from GEN7_ERROR_INT to FPGA_DBG, so there's a > > new patch on the mailing list that will fix this bug after we convert to > > FPGA_DBG. > > Please give a link of the patch, I can't find a patch related to this bug on > mailing list. Thanks... http://lists.freedesktop.org/archives/intel-gfx/2013-January/024116.html http://lists.freedesktop.org/archives/intel-gfx/2013-January/024117.html http://lists.freedesktop.org/archives/intel-gfx/2013-January/024211.html If this also doesn't help you, please attach dmesg.
> http://lists.freedesktop.org/archives/intel-gfx/2013-January/024116.html > http://lists.freedesktop.org/archives/intel-gfx/2013-January/024117.html > http://lists.freedesktop.org/archives/intel-gfx/2013-January/024211.html > > If this also doesn't help you, please attach dmesg. I tested with -next-queued top commit: 209d52110a32c2069b5d870504e73fdb0e30fc51, and applied the patches. The error also exists in dmesg. I attached the dmesg in attachment, any more message you want, I'm glad to try and doing for this.
Created attachment 74031 [details] error in dmesg after booting up
this seems to have been fixed in drm-intel-nightly which has those three commits
(In reply to comment #17) > this seems to have been fixed in drm-intel-nightly which has those three > commits Our HSW C0 has been updated to C2, and I tried latest drm-intel-nightly and drm-intel-next-queued, this bug has gone. Verified here.
In which kernel version is the fix included? I run 3.8.0-27 on a Ubuntu 13.04 istallation and this message is still displayed.
3.8.0-27 is Ubuntu's kernel, almost 9 months behind the curve. Support queries should be addressed to them first.
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.