From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Anthony Wright <anthony@overnetdata.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems
Date: Tue, 28 Jun 2011 11:07:12 -0400 [thread overview]
Message-ID: <20110628150712.GD16290@dumpdata.com> (raw)
In-Reply-To: <4E09C4C8.7020800@overnetdata.com>
On Tue, Jun 28, 2011 at 01:10:48PM +0100, Anthony Wright wrote:
> On 07/06/2011 15:52, Konrad Rzeszutek Wilk wrote:
> > No. The VGA support one might show up in 3.0 depending on Linus. I sent an
> > email asking him to pull it: https://lkml.org/lkml/2011/6/6/391
> > but it could be considered a feature and the merge window for features elapsed :-(
> >
> > It could also be considered a bug ... anyhow leaving it up to Linus
> > and I would recommend you use 2.6.39.1 and I can respond to this email thread
> > whether Linus has pulled the patch or not.
> I've been using the stable/vga.support branch reference in the lkml
> email on 3.0.0-rc3 and it worked perfectly. I've just upgraded to rc4,
> and all I get now is a blank screen. Is there any chance of a fix?
You can respond to this thread: https://lkml.org/lkml/2011/6/6/391
and tell Linus that you are seriously hampered by the lack of the stable/vga.support
and you urge him to pull it in.
prev parent reply other threads:[~2011-06-28 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22045383.16.1307017943479.JavaMail.root@zimbra.overnetdata.com>
2011-06-02 13:08 ` Screen corruption and crash at boot with Xen 4.1.0 & linux 2.6.39 on some systems Anthony Wright
2011-06-02 14:51 ` Konrad Rzeszutek Wilk
[not found] ` <4DEE0EA3.7070205@overnetdata.com>
[not found] ` <20110607145250.GB8376@dumpdata.com>
2011-06-09 12:59 ` Anthony Wright
2011-06-09 13:23 ` Konrad Rzeszutek Wilk
2011-06-28 12:10 ` Anthony Wright
2011-06-28 15:07 ` Konrad Rzeszutek Wilk [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=20110628150712.GD16290@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=anthony@overnetdata.com \
--cc=xen-devel@lists.xensource.com \
/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;
as well as URLs for NNTP newsgroup(s).