Bug 41343 - i915: [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
Summary: i915: [drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Chris Wilson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-29 10:58 UTC by mlambda
Modified: 2017-07-24 23:03 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:

Attachments
Kernel config (77.98 KB, text/plain)
2011-09-29 10:59 UTC, mlambda 		no flags Details
Output of dmesg (61.79 KB, text/plain)
2011-09-29 11:00 UTC, mlambda 		no flags Details
Output of 'lspci -vvnn' (11.92 KB, text/plain)
2011-09-29 11:01 UTC, mlambda 		no flags Details
/var/log/Xorg.0.log (32.56 KB, text/plain)
2011-09-29 11:02 UTC, mlambda 		no flags Details
/proc/cpuinfo (6.79 KB, text/plain)
2011-09-29 11:02 UTC, mlambda 		no flags Details
dmesg with patches (62.54 KB, text/plain)
2011-10-04 15:09 UTC, mlambda 		no flags Details
Xorg.0.log with patches (32.33 KB, text/plain)
2011-10-04 15:10 UTC, mlambda 		no flags Details
View All

Description mlambda 2011-09-29 10:58:45 UTC 
On my HP Pavilion dv7 notebook i get the following message at startup:
[drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH

This is the same bug as https://bugs.freedesktop.org/show_bug.cgi?id=41140 but without any external monitor

Kernel: latest git kernel (commit d5767c53535ac79758084773418e0ad186aba4a2), Linux hp 3.1.0-rc8-custom #1 SMP Wed Sep 28 21:23:06 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux

Distribution: Ubuntu 11.04 64 bit

lsmod:
Module                  Size  Used by
vboxnetadp             13340  0 
vboxnetflt             28297  0 
vboxdrv               252684  2 vboxnetadp,vboxnetflt
radeon               1016473  0 
iwlagn                311183  0 
ttm                    72079  1 radeon
r8169                  55918  0
Comment 1 mlambda 2011-09-29 10:59:56 UTC 
Created attachment 51771 [details]
Kernel config
Comment 2 mlambda 2011-09-29 11:00:45 UTC 
Created attachment 51772 [details]
Output of dmesg
Comment 3 mlambda 2011-09-29 11:01:19 UTC 
Created attachment 51773 [details]
Output of 'lspci -vvnn'
Comment 4 mlambda 2011-09-29 11:02:04 UTC 
Created attachment 51774 [details]
/var/log/Xorg.0.log
Comment 5 mlambda 2011-09-29 11:02:39 UTC 
Created attachment 51775 [details]
/proc/cpuinfo
Comment 6 mlambda 2011-09-29 11:06:23 UTC 
Additionally I encounter the following error:
[drm] MTRR allocation failed.  Graphics performance may suffer.
Comment 7 mlambda 2011-09-30 09:36:33 UTC 
I just tried commit 8e8e500fcadaf2e39f4f119ae60c289456527727 but it doesn't resolve the issue.
Comment 8 Paulo Zanoni 2011-10-04 13:54:10 UTC 
There is a series of 9 patches in intel-gfx@ that might be worth trying if you have some time:
http://lists.freedesktop.org/archives/intel-gfx/2011-September/012266.html

These patches change the code you're hitting.
Comment 9 mlambda 2011-10-04 15:08:46 UTC 
(In reply to comment #8)
> There is a series of 9 patches in intel-gfx@ that might be worth trying if you
> have some time:
> http://lists.freedesktop.org/archives/intel-gfx/2011-September/012266.html
> 
> These patches change the code you're hitting.

I applied the patch series to commit a8062e421f8a5800c83b85ab10c4cefd8409844f and the error message is gone.
Comment 10 mlambda 2011-10-04 15:09:27 UTC 
Created attachment 51979 [details]
dmesg with patches
Comment 11 mlambda 2011-10-04 15:10:17 UTC 
Created attachment 51980 [details]
Xorg.0.log with patches
Comment 12 mlambda 2011-10-10 06:25:24 UTC 
Will the patches be submitted to the mainline kernel?
Comment 13 Paulo Zanoni 2011-10-10 06:40:37 UTC 
(In reply to comment #12)
> Will the patches be submitted to the mainline kernel?

Only for the next round, which will become Kernel 3.2.

Besides the error message, do you see any related bug affecting you? Just because you see the message it doesn`t mean there is a bug.
Comment 14 mlambda 2011-10-10 07:32:51 UTC 
(In reply to comment #13)
> (In reply to comment #12)
> > Will the patches be submitted to the mainline kernel?
> 
> Only for the next round, which will become Kernel 3.2.
> 
> Besides the error message, do you see any related bug affecting you? Just
> because you see the message it doesn`t mean there is a bug.

I don't see any related bug, you can close the bug report.
Comment 15 Paulo Zanoni 2011-11-01 10:03:17 UTC 
Closing bug. The patches you tested are in Linus' 3.2 git tree.

Please reopen if the problem still affects you with Kernel 3.2.

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.