From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "todd.deshane@xen.org" <todd.deshane@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>,
"Pasi Kärkkäinen" <pasik@iki.fi>, Mario <mario@slackverse.org>
Subject: Re: PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels
Date: Tue, 17 May 2011 10:23:49 -0400 [thread overview]
Message-ID: <20110517142349.GD6816@dumpdata.com> (raw)
In-Reply-To: <1305634443.20907.49.camel@zakaz.uk.xensource.com>
On Tue, May 17, 2011 at 01:14:03PM +0100, Ian Campbell wrote:
> On Tue, 2011-05-17 at 13:09 +0100, Pasi Kärkkäinen wrote:
> > On Tue, May 17, 2011 at 01:20:32PM +0200, Mario wrote:
>
> > > When i first experienced this problem, it was back when i first tried
> > > Xen 4.0.1, however, i had just a blank screen with blinking cursor to
> > > work with. So i had to set up a serial console to figure out what was
> > > wrong. After seeing how it stops on framebuffer, i blacklisted the
> > > module, and it worked. I kept on doing so on every other setup i have
> > > made, but now, one year later, i was wondering if this is ever going to
> > > be fixed, or if i can somehow help to get it fixed.. :-)
Make sure you attach the full serial log, and include 'drm.debug=255' on your
Linux bootline.
> > >
> >
> > Yep, you can help by posting the full boot logs from serial console,
> > both Xen and dom0 linux kernel logs.
> >
> > http://wiki.xen.org/xenwiki/XenSerialConsole
> >
> > and: http://wiki.xensource.com/xenwiki/XenParavirtOps,
> > especially the "Are there more debugging options .." section.
>
> There's a reasonable chance this is already fixed in one of Konrad's GFX
> branches, although I'm not sure specifically which branch is current.
I think it was the #devel/agp.pci-api but it might need another pass
as it probably doesn't compile anymore :-(
Mario, you could also try to use the VESA fb instead of the s3.
>
> Ian.
prev parent reply other threads:[~2011-05-17 14:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DCFC8BB.9030201@slackverse.org>
[not found] ` <20110515155322.GM32595@reaktio.net>
[not found] ` <4DCFF8FA.8020409@slackverse.org>
[not found] ` <20110515161203.GN32595@reaktio.net>
[not found] ` <4DCFFE2B.4040302@slackverse.org>
[not found] ` <20110515163444.GO32595@reaktio.net>
[not found] ` <4DD00235.1090207@slackverse.org>
[not found] ` <20110515170345.GP32595@reaktio.net>
[not found] ` <20110515172030.GQ32595@reaktio.net>
[not found] ` <4DD00C66.7080100@slackverse.org>
2011-05-16 6:51 ` PV networking issue in 2.6.38.6 and 2.6.39-rc7 pvops dom0 kernels Pasi Kärkkäinen
2011-05-16 7:58 ` [Xen-users] " Ian Campbell
2011-05-16 8:56 ` Mario
2011-05-16 8:59 ` Ian Campbell
2011-05-16 9:03 ` Mario
2011-05-16 11:04 ` Mario
2011-05-16 12:46 ` [Xen-users] " Ian Campbell
2011-05-16 12:56 ` Mario
2011-05-16 13:00 ` [Xen-users] " Ian Campbell
2011-05-16 13:04 ` Mario
2011-05-16 13:06 ` Ian Campbell
2011-05-16 13:09 ` Mario
2011-05-16 13:15 ` Mario
2011-05-16 13:22 ` Pasi Kärkkäinen
2011-05-17 10:49 ` Mario
2011-05-17 11:04 ` Pasi Kärkkäinen
2011-05-17 11:20 ` Mario
2011-05-17 12:09 ` Pasi Kärkkäinen
2011-05-17 12:14 ` Ian Campbell
2011-05-17 14:23 ` 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=20110517142349.GD6816@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=mario@slackverse.org \
--cc=pasik@iki.fi \
--cc=todd.deshane@xen.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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).