From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Announcing xen/master: pvops git trees rearranged Date: Thu, 15 Oct 2009 16:04:09 -0400 Message-ID: <20091015200409.GD11348@phenom.dumpdata.com> References: <4AB431AD.1030205@goop.org> <20091011153900.GW1434@reaktio.net> <20091012200248.GA16486@phenom.dumpdata.com> <20091014211415.GQ1434@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <20091014211415.GQ1434@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Cc: Jeremy Fitzhardinge , Xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Oct 15, 2009 at 12:14:15AM +0300, Pasi K=E4rkk=E4inen wrote: > On Mon, Oct 12, 2009 at 04:02:48PM -0400, Konrad Rzeszutek Wilk wrote: > > On Sun, Oct 11, 2009 at 06:39:00PM +0300, Pasi K=E4rkk=E4inen wrote: > > > On Fri, Sep 18, 2009 at 06:19:41PM -0700, Jeremy Fitzhardinge wrote= : > > > >=20 > > > > This is definitely a work-in-progress kernel. I'd appreciate all= bug > > > > *and* success reports so I can get some idea of how many people a= re > > > > using this thing, and how often there are problems. Patches grat= efully > > > > accepted. > > > >=20 > > >=20 > > > I just tried the latest pv_ops dom0 git tree (11 Oct 2009) on x86_6= 4 AHCI box. > > >=20 > > > The good news is that the dom0 kernel boots up, but there are some = error > > > messages. > > >=20 > > > Using the default options (modeset) the VGA console doesn't work, i= t > > > goes blank (display says "power save") in the beginning of dom0 ker= nel boot: > > > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/dmesg-2.6.31.1-2009-= 10-11.txt > >=20 > > This line: > > [drm:radeon_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E= 4)=3D0xCAFEDEAD) > >=20 > > Is a pretty good pointer at what the fault is. If you look at git com= mit > > 93e7c3850b8431e19c9cba91413066bfd2360671 you will see the band-aid Je= remy added. > > It looks though as if not all of the radeon drivers allocate their ri= ng buffer memory via > > drm_sg_alloc calls thought. Not sure how the r100 (and the correspond= ing X driver) does it. > > The long/erro traceback about the HARDIRQ is a red-herring in this ca= se. > >=20 > > Here is a couple of things that I would like you to try, if you can: > >=20 >=20 > Sure. >=20 > > 1). Pass in 'drm.debug=3D255' and send the output. It should have ton= s of extra > > output.=20 > >=20 >=20 > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/radeondebug/dmesg-2.6.31= .1-2009-10-14-drmdebug.txt >=20 > Unknown boot option `drm.debug=3D255': ignoring I forgot to mention that you probably need to have CONFIG_DRM set to 'y' = instead of 'm' for this to work. Or you could hack up the initrd (modprobe.conf) and mak= e drm load with the 'debug=3D255' parameter. .. snip .. > seems to work there! (Fedora kernel contains newer graphics/drm drivers= ). >=20 > But the same USB related error is there with the fedora kernel: > [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ] >=20 > http://pasik.reaktio.net/xen/pv_ops-dom0-debug/radeondebug/dmesg-2.6.31= .3-1.2.71.xendom0.fc12.x86_64-2009-10-14.txt Nah. Still has the same problem: [drm:r100_ring_test] *ERROR* radeon: ring test failed (sracth(0x15E4)=3D0= xCAFEDEAD) [drm:r100_cp_init] *ERROR* radeon: cp isn't working (- >=20 >=20 > > 2). Send in the Xorg.log (or whatever output the program in the userl= and that > > starts the modesetting produces). I don't have much knowledge in ho= w modesetting works, > > so this might require some digging. > >=20 >=20 > Hmm.. yeah, I'm not sure either which is the first program setting up > graphics mode using kernel modesetting (KMS) in Fedora..=20 >=20 > I extracted the initrd image and checked the 'init' script: >=20 > echo "Loading drm module" > modprobe -q drm > echo "Loading ttm module" > modprobe -q ttm > echo "Loading radeon module" > modprobe -q radeon > /lib/udev/console_init tty0 add here: export LIBGL_DEBUG=3Dverbose > plymouth --show-splash >=20 > So I guess plymouth is asking for a graphics mode.. Add this to your kernel command line: plymouth:debug