From: Chris Wilson <chris@chris-wilson.co.uk>
To: Knut Petersen <Knut_Petersen@t-online.de>
Cc: jesse.barnes@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load
Date: Tue, 25 Jan 2011 14:44:58 +0000 [thread overview]
Message-ID: <b9dded$hokqnl@orsmga002.jf.intel.com> (raw)
In-Reply-To: <4D3EDACF.8040702@t-online.de>
On Tue, 25 Jan 2011 15:14:39 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
> Well, I don't know if openSuSE 11.3 is recent enough.
> Setup: 2 Monitors, attached to VGA1 and DVI1, resolution 1280x1024
>
> xrandr --output VGA1 --pos [1..768]
> ============================
> Everything ok. Works as expected.
>
> xrandr --output VGA1 --pos 769
Just retested on my PineView netbook:
$ xrandr --output LVDS1 --mode 1024x600 \
--output VGA1 --mode 1920x1080 --right-of LVDS1
is working fine.
The empty backtrace is most bizarre. Do you get a more reliable stacktrace
if you attach gdb before the crash?
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-25 14:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 18:48 [BUG/REGRESSION] DRM / i915 / 2.6.37 and 2.6.38-rc*: DVI output gets disabled/reenabled under load Knut Petersen
2011-01-24 19:13 ` 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 [this message]
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='b9dded$hokqnl@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=Knut_Petersen@t-online.de \
--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 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.