Skip to contentSkip to conversation

*ERROR* Power management discrepancy

drm:gen6_sanitize_pm Oleksij Rempel (fishor) 2 participants 2 messages May 26, 2012 – May 28, 2012

lore
Share & tools
lore
#0 lore raw

Hallo devs,

i get this errors:

[    9.267502] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12060000
[   28.168979] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 00070000, was 18000000
[   33.685072] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12060000
[  302.378301] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18070000, was 18000000
[  662.072034] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18070000, was 18000000
[  722.069224] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 18070000, was 18000000

should i fear some thing, or it is ok?

#1 lore raw
Quoted 16 lines · Oleksij Rempel (fishor)

Hallo devs,

i get this errors:
[    9.267502] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12060000
[   28.168979] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 00070000, was 18000000
[   33.685072] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 18000000, was 12060000
[  302.378301] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 18070000, was 18000000
[  662.072034] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 18070000, was 18000000
[  722.069224] [drm:gen6_sanitize_pm] *ERROR* Power management discrepancy:
GEN6_RP_INTERRUPT_LIMITS expected 18070000, was 18000000

Quoted 1 line

should i fear some thing, or it is ok?

We've newly added this check, but these are the symptoms of the gpu turbo hw getting confused and eventually leading to the gpu being stuck at the lowest frequency. So nothing really to worry about (safe when you've noticed gpu workload slowness which can be fixed by a suspend/resume cycle, because this is the harbinger of it).

A patch to ducttape around this problem some more and another one to again shut up the obnoxious dmesg noise are on track for 3.5-rc1.

Yours,
Daniel

Signature · 2 lines
Daniel Vetter
[email protected] - +41 (0) 79 364 57 48 - http://blog.ffwll.ch