public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-kernel@vger.kernel.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>, jesse.barnes@intel.com
Subject: [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load
Date: Mon, 24 Jan 2011 19:48:55 +0100	[thread overview]
Message-ID: <4D3DC997.5040605@t-online.de> (raw)

On an AOpen i915GMm-HFS I see the following problem:
The LCD panel connected to DVI-1 gets disabled and then reenabled
under high system load (e.g. -j 15 kernel compile) if I am working on the
framebuffer console (no problems in X).

Kernels affected: 2.6.37, 2.6.38-rc1, 2.6.38-rc2
Kernel _not_ affected: 2.6.31.14, 2.6.36.3

Details: There is a DVI (DVI-1) connector and a VGA (VGA-1) connector
present.
The kernel also detects a connector VGA-2, but there is no hardware
connector for that.

I tried to bisect, but that did not provide a reasonable result because
of other problems
with the code.

Further inspection showed: The problem is related to the 10 second
connector rescan.

Idling at the prompt the status of VGA-2 is an almost stable
connector_status_unknown (3).
Under load that changes, the connector status is floating between
connector_status_unknown and connector_status_disconnected. During the
action
taken after a status changes DVI-1 temporarily gets disabled.

Disabling the connector rescan in the source code fixes the problem,
but obviously that is not the best possible fix ;-)

Knut

             reply	other threads:[~2011-01-24 18:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 18:48 Knut Petersen [this message]
2011-01-24 19:13 ` [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load Chris Wilson
2011-01-25 11:50   ` Knut Petersen
2011-01-25 12:11     ` Chris Wilson
2011-01-25 12:35       ` Knut Petersen
2011-01-25 13:50         ` Chris Wilson
2011-01-25 14:14       ` Knut Petersen
2011-01-25 14:44         ` Chris Wilson
2011-01-25 15:06     ` [PATCH] drm/i915/sdvo: If at first we don't succeed in reading the response, wait Chris Wilson
2011-01-25 22:01       ` Knut Petersen
2011-01-25 22:11         ` [PATCH] drm/i915/sdvo: If at first we dont " Chris Wilson
2011-01-25 22:32           ` Knut Petersen

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=4D3DC997.5040605@t-online.de \
    --to=knut_petersen@t-online.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox