From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvops: boot locks up while initialising PCI Date: Wed, 23 Sep 2009 12:17:23 -0700 Message-ID: <4ABA7443.4050903@goop.org> References: <20090923053202.GA5797@verge.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090923053202.GA5797@verge.net.au> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Simon Horman Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 09/22/09 22:32, Simon Horman wrote: > Hi, > > while trying to boot xen/master at the following changest the boot > locks up somewhere around the initialisation of PCI. Boot log and > config attached. Any insights appreciated. > > commit 398b4b4cabdb27c06a7b8214c2044347ffc08c49 > Merge: 3973dcf... 6e8f158... > Author: Jeremy Fitzhardinge > Date: Tue Sep 22 15:21:28 2009 -0700 > > Merge branch 'xen/dom0/drm' into xen/master > > * xen/dom0/drm: > swiotlb: linux/swiotlb.h needs linux/dma-mapping.h > > > My grub snippet is: > > title Xen > root (hd0,0) > kernel /xen com1=115200,8n1,0x3f8,0 console=com1 loglvl=all guest_loglvl=all dom0_mem=1G > module /vmlinuz-2.6.31-pvops root=/dev/mapper/sam-root_x86_64 console=ttyS0 loglevel=8 ro earlyprintk=xen > module /initrd.img-2.6.31-pvops > > You should really be using hvc0 for the console. I think ttyS0 "passthrough"/emulation should work, but using the Xen console is more reliable. And you're just losing all console output on the switchover, which suggests that serial isn't actually working. Failing that, can you get more info from the VGA console? Aside from that, I'm not sure what's going on. I don't normally see messages from Xen about PCI devices. Are you using MSI? Does booting with pci=nomsi work? Thanks, J