From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
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
Message-ID: <20110517142349.GD6816@dumpdata.com>
References: <4DD120EA.4060204@slackverse.org>
	<1305551216.20907.12.camel@zakaz.uk.xensource.com>
	<4DD12212.7020403@slackverse.org> <4DD12389.1020905@slackverse.org>
	<20110516132231.GS32595@reaktio.net>
	<4DD252AE.6080609@slackverse.org>
	<20110517110440.GU32595@reaktio.net>
	<4DD25A00.6090707@slackverse.org>
	<20110517120902.GV32595@reaktio.net>
	<1305634443.20907.49.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-users-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <1305634443.20907.49.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-users@lists.xensource.com>
List-Help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>,
	<mailto:xen-users-request@lists.xensource.com?subject=subscribe>
Sender: xen-users-bounces@lists.xensource.com
Errors-To: xen-users-bounces@lists.xensource.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 =?iso-8859-1?Q?K=E4rkk=E4inen?= <pasik@iki.fi>, Mario <mario@slackverse.org>
List-Id: xen-devel@lists.xenproject.org

On Tue, May 17, 2011 at 01:14:03PM +0100, Ian Campbell wrote:
> On Tue, 2011-05-17 at 13:09 +0100, Pasi K=E4rkk=E4inen wrote:
> > On Tue, May 17, 2011 at 01:20:32PM +0200, Mario wrote:
>=20
> > > When i first experienced this problem, it was back when i first tri=
ed =20
> > > Xen 4.0.1, however, i had just a blank screen with blinking cursor =
to =20
> > > work with. So i had to set up a serial console to figure out what w=
as =20
> > > wrong. After seeing how it stops on framebuffer, i blacklisted the =
=20
> > > module, and it worked. I kept on doing so on every other setup i ha=
ve =20
> > > made, but now, one year later, i was wondering if this is ever goin=
g to =20
> > > be fixed, or if i can somehow help to get it fixed.. :-)

Make sure you attach the full serial log, and include 'drm.debug=3D255' o=
n your
Linux bootline.
> > >
> >=20
> > Yep, you can help by posting the full boot logs from serial console,=20
> > both Xen and dom0 linux kernel logs.
> >=20
> > http://wiki.xen.org/xenwiki/XenSerialConsole
> >=20
> > and: http://wiki.xensource.com/xenwiki/XenParavirtOps,=20
> > especially the "Are there more debugging options .." section.
>=20
> There's a reasonable chance this is already fixed in one of Konrad's GF=
X
> 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.

>=20
> Ian.