From: PUCCETTI Armand <armand.puccetti@cea.fr>
To: Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com, Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
Date: Wed, 03 Jan 2007 16:26:10 +0100 [thread overview]
Message-ID: <459BCB12.50504@cea.fr> (raw)
In-Reply-To: <C1C16278.7032%keir@xensource.com>
Keir Fraser a écrit :
>
> On 3/1/07 14:33, "PUCCETTI Armand" <armand.puccetti@cea.fr> 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:
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
I have added transmisssion speed for the RX machine to receive properly.
Should I have much more trace messages with this option?
Armand
next prev parent reply other threads:[~2007-01-03 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-03 10:43 Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot] PUCCETTI Armand
2007-01-03 9:48 ` Keir Fraser
2007-01-03 11:04 ` PUCCETTI Armand
2007-01-03 10:12 ` Keir Fraser
2007-01-03 13:02 ` Ian Campbell
2007-01-03 14:33 ` PUCCETTI Armand
2007-01-03 13:39 ` Keir Fraser
2007-01-03 15:26 ` PUCCETTI Armand [this message]
2007-01-03 14:26 ` Ian Campbell
2007-01-03 15:48 ` PUCCETTI Armand
2007-01-03 14:58 ` Keir Fraser
2007-01-03 16:55 ` PUCCETTI Armand
2007-01-04 16:24 ` PUCCETTI Armand
2007-01-03 14:27 ` Keir Fraser
2007-01-03 13:58 ` PUCCETTI Armand
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=459BCB12.50504@cea.fr \
--to=armand.puccetti@cea.fr \
--cc=Ian.Campbell@XenSource.com \
--cc=keir@xensource.com \
--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.