Skip to contentSkip to conversation

*ERROR* timed out waiting for FORCE_DETECT in 36rc3 on i915

regression New Andi Kleen 3 participants 3 messages Sep 8, 2010 – Sep 12, 2010

Subsystems (2)
lore
Share & tools
lore

Andi Kleen

author
#0 lore raw

One of my test box with Intel graphics spews out a lot of

[drm:intel_crt_detect_hotplug] *ERROR* timed out waiting for FORCE_DETECT to go off

messages after boot now. This didn't show in 2.6.35, so it seems like a regression. The system just runs in VGA text mode (but with KMS) without X.

-Andi

Hardware information

[drm] Initialized drm 1.1.0 20060810
[drm] radeon defaulting to userspace modesetting.
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
i915 0000:00:02.0: setting latency timer to 64
alloc irq_desc for 42 on node -1
alloc kstat_irqs on node -1
i915 0000:00:02.0: irq 42 for MSI/MSI-X
[drm] set up 7M of stolen space
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm] initialized overlay support
Console: switching to colour frame buffer device 128x48
fb0: inteldrmfb frame buffer device
drm: registered panic notifier
No ACPI video bus found
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

00:02.0 VGA compatible controller: Intel Corporation: Unknown device 29c2 (rev 02)

Signature · 1 line
[email protected] -- Speaking for myself only.
#1 lore raw
Quoted 4 lines · On środa, 8 września 2010 o 15:53:16 Andi Kleen wrote:

One of my test box with Intel graphics spews out a lot of

[drm:intel_crt_detect_hotplug] *ERROR* timed out waiting for FORCE_DETECT to go off

I created a Bugzilla entry at
https://bugzilla.kernel.org/show_bug.cgi?id=18332
for your bug report, please add your address to the CC list in there, thanks!

Signature · 2 lines
Maciej Rutecki
http://www.maciek.unixy.pl
#2 lore raw

PATCH 1/1 drm/i915/crt: Downgrade warnings for hotplug failures

In reply to Andi Kleen

These are not fatal errors, so do not alarm the user by filling the logs with *** ERROR ***. Especially as we know that g4x CRT detection is a little sticky.

On the one hand the errors are valid since they are warning us of a stall -- we poll the register whilst holding the mode lock so not even the mouse will update. On the other hand, those stalls were already present yet nobody complained.

Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=18332

---
 drivers/gpu/drm/i915/intel_crt.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_crt.c +2 -2
index a02a8df..197d4f3 100644
@@ -188,7 +188,7 @@ static bool intel_ironlake_crt_detect_hotplug(struct drm_connector *connector)
 
 	if (wait_for((I915_READ(PCH_ADPA) & ADPA_CRT_HOTPLUG_FORCE_TRIGGER) == 0,
 		     1000, 1))
-		DRM_ERROR("timed out waiting for FORCE_TRIGGER");
+		DRM_DEBUG_KMS("timed out waiting for FORCE_TRIGGER");
 
 	if (turn_off_dac) {
 		I915_WRITE(PCH_ADPA, temp);
@@ -245,7 +245,7 @@ static bool intel_crt_detect_hotplug(struct drm_connector *connector)
 		if (wait_for((I915_READ(PORT_HOTPLUG_EN) &
 			      CRT_HOTPLUG_FORCE_DETECT) == 0,
 			     1000, 1))
-			DRM_ERROR("timed out waiting for FORCE_DETECT to go off");
+			DRM_DEBUG_KMS("timed out waiting for FORCE_DETECT to go off");
 	}
 
 	stat = I915_READ(PORT_HOTPLUG_STAT);
Signature · 1 line
1.7.1