From: Lucas <canolucas@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org, stable@vger.kernel.org,
lwn@lwn.net, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 3.8.6
Date: Sat, 06 Apr 2013 15:10:26 -0300 [thread overview]
Message-ID: <51606512.8030703@gmail.com> (raw)
In-Reply-To: <20130405174012.GA28836@kroah.com>
On 05/04/13 14:40, Greg KH wrote:
> I'm announcing the release of the 3.8.6 kernel.
>
> All users of the 3.8 kernel series must upgrade.
>
> The updated 3.8.y git tree can be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.8.y
> and can be browsed at the normal kernel.org git web browser:
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
> thanks,
>
> greg k-h
>
Hi Greg, I have an issue with a Lenovo T60's Notebook, which has an
Intel VGA card.
[lucas@tux ~]$ lspci | grep "VGA"
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
The screen turns black whenever X is executed, due to the following bug:
https://bugs.freedesktop.org/show_bug.cgi?id=57365
https://bugs.archlinux.org/task/33062
Those sites havethe error output that is generated from X attempts to
start. Nonetheless, the causes of this issue have already been figured:
According to comment #32 in the freedesktop site (
https://bugs.freedesktop.org/show_bug.cgi?id=57365#c32 ), the fix has
been introduced in the 3.9 series.
Believe it or not, the last stable release in which X is able to start
is 3.6.11. The whole 3.7 and 3.8 series together were unable to tackle
this issue down. Seems that Intel is not doing its homework here :(
My question is:
Knowing that the following patches solve the issue, can they be
backported and included in the next release of 3.8 ?
Thank you very much,
Lucas
commit 24a1f16de97c4cf0029d9acd04be06db32208726
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date: Fri Feb 8 16:35:37 2013 +0200
drm/i915: disable shared panel fitter for pipe
commit 9d6d9f19e8146fa24903cb561e204a22232740e3
Author: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Date: Fri Feb 8 16:35:38 2013 +0200
drm/i915: clean up panel fitter handling in lvds
next prev parent reply other threads:[~2013-04-06 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 17:40 Linux 3.8.6 Greg KH
2013-04-05 17:40 ` Greg KH
2013-04-06 18:10 ` Lucas [this message]
2013-04-06 18:18 ` Greg KH
2013-04-06 18:44 ` Lucas
2013-04-06 21:41 ` Daniel Vetter
2013-04-06 22:56 ` Lucas
2013-04-07 18:28 ` Daniel Vetter
2013-04-08 1:17 ` Lucas
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=51606512.8030703@gmail.com \
--to=canolucas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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