All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, Dave Airlie <airlied@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: [regression] *ERROR* timed out waiting for FORCE_DETECT in 36rc3 on i915
Date: Wed, 08 Sep 2010 15:53:16 +0200	[thread overview]
Message-ID: <87mxrswddf.fsf@basil.nowhere.org> (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)

-- 
ak@linux.intel.com -- Speaking for myself only.

             reply	other threads:[~2010-09-08 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 13:53 Andi Kleen [this message]
2010-09-12 18:40 ` Maciej Rutecki
2010-09-12 19:07 ` [PATCH] drm/i915/crt: Downgrade warnings for hotplug failures Chris Wilson
2010-09-12 19:07   ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mxrswddf.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=airlied@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [regression] *ERROR* timed out waiting for FORCE_DETECT in 36rc3 on i915' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.