From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Simon Horman <horms@verge.net.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: pvops: boot locks up while initialising PCI
Date: Wed, 23 Sep 2009 12:17:23 -0700 [thread overview]
Message-ID: <4ABA7443.4050903@goop.org> (raw)
In-Reply-To: <20090923053202.GA5797@verge.net.au>
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 <jeremy.fitzhardinge@citrix.com>
> 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
prev parent reply other threads:[~2009-09-23 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 5:32 pvops: boot locks up while initialising PCI Simon Horman
2009-09-23 7:00 ` Pasi Kärkkäinen
2009-09-23 23:05 ` Simon Horman
2009-09-23 23:29 ` Jeremy Fitzhardinge
2009-09-24 7:26 ` Keir Fraser
2009-09-24 7:28 ` Han, Weidong
2009-09-25 0:05 ` Simon Horman
2009-09-23 19:17 ` Jeremy Fitzhardinge [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=4ABA7443.4050903@goop.org \
--to=jeremy@goop.org \
--cc=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.