Ian Campbell a écrit :
On Wed, 2007-01-03 at 16:26 +0100, PUCCETTI Armand wrote:
Keir Fraser a écrit :
On 3/1/07 14:33, "PUCCETTI Armand" <armand.puccetti@xxxxxx> wrote:
Yes the CONFIG_EARLY_PRINTK flag is enabled , but the trace is exactly
the same. :-(
If it's crashing that early then it may be a bad Linux kernel (version
mismatch or similar). OTOH, 'earlyprintk' does not belong on Xen's command
line at all. Maybe you added it to the wrong line in GRUB's config?
-- Keir
I think the option is at the right place as below:
It's not. earlyprintk is a Linux kernel option.
title Xen 3.0.3 / Ubuntu 2.6.16.29
root (hd0,2)
kernel /boot/xen-3.gz dom0_mem=1048576
earlyprintk=serial,ttyS0,115200,keep com1=115200,8n1 noreboot
module /boot/vmlinuz-2.6-xen0 root=/dev/sda3
console=ttyS0,115200 max_loop=64 ro debug
module /boot/initrd.img-2.6.16.29-xen0
savedefault
boot
Ian.
Sorry for the err. Moving the option to the module line, as below,
leaves the trace unchanged.
Armand
title Xen 3.0.3 / Ubuntu 2.6.16.29
root (hd0,2)
kernel /boot/xen-3.gz dom0_mem=1048576 com1=115200,8n1 noreboot
module /boot/vmlinuz-2.6-xen0 root=/dev/sda3
earlyprintk=serial,ttyS0,115200,keep console=ttyS0,115200 max_loop=64 ro
debug
module /boot/initrd.img-2.6.16.29-xen0
savedefault
boot
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|