From: Knut Petersen <Knut_Petersen@t-online.de>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/sdvo: If at first we dont succeed in reading the response, wait
Date: Tue, 25 Jan 2011 23:32:38 +0100 [thread overview]
Message-ID: <4D3F4F86.5080207@t-online.de> (raw)
In-Reply-To: <b7da2f$q83ub3@fmsmga001.fm.intel.com>
Am 25.01.2011 23:11, schrieb Chris Wilson:
> On Tue, 25 Jan 2011 23:01:45 +0100, Knut Petersen <Knut_Petersen@t-online.de> wrote:
>
>> I think that patch also should be a candidate for 2.6.37.1 as it fixes a
>> regression
>> introduced in 2.6.37.
>>
> (Actually I think the bug is older than that...)
>
You are right, but I used 2.6.31.14 for a long time. After feeling the need
to change I found 2.6.32 to 2.6.35 to be unusuable on my system, 2.6.36.3
is ok with the lvds patch I submitted for my i915GMm-HFS mobos.
I think tomorrow I will try to find some more information on the X crash
caused by enabling automated cgroup scheduling in .38-rc*
Knut
prev parent reply other threads:[~2011-01-25 22:32 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
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 [this message]
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=4D3F4F86.5080207@t-online.de \
--to=knut_petersen@t-online.de \
--cc=chris@chris-wilson.co.uk \
--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