Keir Fraser
2007-Jan-03 09:48 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
On 3/1/07 10:43, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote:> title Xen 3.0.3 / Ubuntu 2.6.16.29 > root (hd0,2) > kernel /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1 > module /boot/vmlinuz-2.6-xen0 root=/dev/sda3 console=ttyS0,115200 > max_loop=64 ro quiet splash > module /boot/initrd.img-2.6.16.29-xen0 > savedefault > boot > > Is there anything else that I can trace?''quiet'' looks like a good option to remove. ''splash'' can''t do any good either. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Jan-03 10:12 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
On 3/1/07 11:04, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote:> I removed both options but exactly the same trace comes out. > Are there any other options I should add? > > ArmandYou could add ''debug'' as a boot parameter, but it looks like you are crashing too early to get any output. Have you tried disassembling the Linux kernel image (objdump -d vmlinux) and see what function contains address ffffffff80129fc8 (the crashing RIP value)? -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 10:43 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
This parameter is already on the module line of the config file.
Below is the Grub boot entry:
title Xen 3.0.3 / Ubuntu 2.6.16.29
root (hd0,2)
kernel /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1
module /boot/vmlinuz-2.6-xen0 root=/dev/sda3 console=ttyS0,115200
max_loop=64 ro quiet splash
module /boot/initrd.img-2.6.16.29-xen0
savedefault
boot
Is there anything else that I can trace?
Armand
the original trace is repeated below
_________________________________________________________________________
__ __ _____ ___ _____ ___
\ \/ /___ _ __ |___ / / _ \ |___ / / _ \
\ // _ \ ''_ \ |_ \| | | | |_ \ __| | | |
/ \ __/ | | | ___) | |_| | ___) |__| |_| |
/_/\_\___|_| |_| |____(_)___(_)____/ \___/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0.3-0 (root@intra.cea.fr) (gcc version 4.1.2 20060928
(prerelease) (Ubuntu 4.1.1-13ubuntu5)) Fri Dec 22 14:53:08 CET 2006
Latest ChangeSet: unavailable
(XEN) Command line: /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 00000000000a0000 (usable)
(XEN) 00000000000f0000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 00000000dfe86c00 (usable)
(XEN) 00000000dfe86c00 - 00000000dfe88c00 (ACPI NVS)
(XEN) 00000000dfe88c00 - 00000000dfe8ac00 (ACPI data)
(XEN) 00000000dfe8ac00 - 00000000e0000000 (reserved)
(XEN) 00000000f0000000 - 00000000f4000000 (reserved)
(XEN) 00000000fec00000 - 00000000fed00400 (reserved)
(XEN) 00000000fed20000 - 00000000feda0000 (reserved)
(XEN) 00000000fee00000 - 00000000fef00000 (reserved)
(XEN) 00000000ffb00000 - 0000000100000000 (reserved)
(XEN) System RAM: 3582MB (3668120kB)
(XEN) Xen heap: 13MB (14196kB)
(XEN) found SMP MP-table at 000fe710
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v002 DELL ) @
0x00000000000feb00
(XEN) ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd259
(XEN) ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd351
(XEN) ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @
0x00000000fffd86d6
(XEN) ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd445
(XEN) ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd4b7
(XEN) ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd4df
(XEN) ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd546
(XEN) ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @
0x00000000000fd584
(XEN) ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @
0x0000000000000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled)
(XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled)
(XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1])
(XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Initializing CPU#0
(XEN) Detected 3192.202 MHz processor.
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#0.
(XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU0: Thermal monitoring enabled
(XEN) CPU0: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) Intel machine check architecture supported.
(XEN) Intel machine check reporting enabled on CPU#1.
(XEN) CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
(XEN) CPU1: Thermal monitoring enabled
(XEN) CPU1: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) -> Using new ACK method
(XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 14.318MHz HPET
(XEN) Brought up 2 CPUs
(XEN) Machine check exception polling timer started.
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Domain 0 kernel supports features = { 0000001f }.
(XEN) Domain 0 kernel requires features = { 00000000 }.
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 0000000006000000->0000000008000000 (253952 pages
to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: ffffffff80100000->ffffffff806f36e8
(XEN) Init. ramdisk: ffffffff806f4000->ffffffff80f0d800
(XEN) Phys-Mach map: ffffffff80f0e000->ffffffff8110e000
(XEN) Start info: ffffffff8110e000->ffffffff8110e49c
(XEN) Page tables: ffffffff8110f000->ffffffff8111c000
(XEN) Boot stack: ffffffff8111c000->ffffffff8111d000
(XEN) TOTAL: ffffffff80000000->ffffffff81400000
(XEN) ENTRY ADDRESS: ffffffff80100000
(XEN) Dom0 has maximum 2 VCPUs
(XEN) Initrd len 0x819800, start at 0xffffffff806f4000
(XEN) Scrubbing Free RAM: ....................................done.
(XEN) Xen trace buffers: disabled
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times
to switch
input to Xen).
(XEN) domain_crash_sync called from entry.S
(XEN) Domain 0 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0.3-0 x86_64 debug=y Not tainted ]----
(XEN) CPU: 0
(XEN) RIP: e033:[<ffffffff80129fc8>]
(XEN) RFLAGS: 0000000000000286 CONTEXT: guest
(XEN) rax: ffffffff805dbf00 rbx: 0000000000000000 rcx: 0000000000000000
(XEN) rdx: 0000000000000100 rsi: ffffffff805dbee0 rdi: ffffffff80497128
(XEN) rbp: ffffffff805dbed0 rsp: ffffffff805dbe10 r8: 0000000000000000
(XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000
(XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000
(XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0
(XEN) cr3: 0000000006101000 cr2: 0000000000000028
(XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033
(XEN) Guest stack trace from rsp=ffffffff805dbe10:
(XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff80129fc8
(XEN) 000000010000e030 0000000000010086 ffffffff805dbe50 000000000000e02b
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
(XEN) ffffffff805dbfb0 ffffffff8012a347 0000003000000008 ffffffff805dbfc0
(XEN) ffffffff805dbf00 0000000000000000 0000000000000000 ffffffff8062e040
(XEN) 0000000000000100 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000102 0000000000000000 0000000000000102 ffffffff8011b321
(XEN) 0000000006102ff8 0000000000000000 0000000000000102 ffffffff8011b401
(XEN) 000000000000000f 0000000000006102 ffffffff805c7000 0000000000000000
(XEN) ffffffff805dbfb0 ffffffff80111032 0000000000000000 0000000000000000
(XEN) ffffffff805dbff0 ffffffff805dd11e ffff800000000000 ffff804000000000
(XEN) 00000007ffffffff 0000000000000000 0000000000000000 0000000000000000
(XEN) 0000000000000000 0000000000000000
(XEN) Domain 0 crashed: ''noreboot'' set - not rebooting.
>
>
> On 24/12/06 9:04 am, "armand.puccetti"
<armand.puccetti@wanadoo.fr> wrote:
>
>
>> After buying & installing a serial cable, the trace of the boot
process,
>> in which XEN 3.0.3-0 (compiled fom source) gets stuck at boot time is
below.
>>
>> Any idea welcome on what this might be due to!!
>>
>
> Please add console=ttyS0 to the module line of your GRUB config. This is a
> boot parameter to Linux to cause its boot output to appear on your serial
> line. Currently that is missing so we cannot diagnose the problem.
Hopefully
> the crash is not so early that there is no boot output to be seen.
>
> -- Keir
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 11:04 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
I removed both options but exactly the same trace comes out. Are there any other options I should add? Armand Keir Fraser a écrit :> > On 3/1/07 10:43, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote: > > >> title Xen 3.0.3 / Ubuntu 2.6.16.29 >> root (hd0,2) >> kernel /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1 >> module /boot/vmlinuz-2.6-xen0 root=/dev/sda3 console=ttyS0,115200 >> max_loop=64 ro quiet splash >> module /boot/initrd.img-2.6.16.29-xen0 >> savedefault >> boot >> >> Is there anything else that I can trace? >> > > ''quiet'' looks like a good option to remove. ''splash'' can''t do any good > either. > > -- Keir > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2007-Jan-03 13:02 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
On Wed, 2007-01-03 at 10:12 +0000, Keir Fraser wrote:> > > On 3/1/07 11:04, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote: > > > I removed both options but exactly the same trace comes out. > > Are there any other options I should add? > > > > Armand > > You could add ''debug'' as a boot parameter, but it looks like you are > crashing too early to get any output. Have you tried disassembling the Linux > kernel image (objdump -d vmlinux) and see what function contains address > ffffffff80129fc8 (the crashing RIP value)?"earlyprintk=serial,ttyS0" on the kernel command line might help if CONFIG_EARLY_PRINTK is enabled. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Jan-03 13:39 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 13:58 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
The function vprintk is concerned, as the trace contains:
ffffffff80129fb0 <vprintk>:
ffffffff80129fb0: 55 push %rbp
ffffffff80129fb1: 48 89 e5 mov %rsp,%rbp
ffffffff80129fb4: 41 57 push %r15
ffffffff80129fb6: 41 56 push %r14
ffffffff80129fb8: 41 55 push %r13
ffffffff80129fba: 41 54 push %r12
ffffffff80129fbc: 53 push %rbx
ffffffff80129fbd: 48 83 ec 58 sub $0x58,%rsp
ffffffff80129fc1: 44 8b 1d 38 c1 51 00 mov
5357880(%rip),%r11d # ffffffff80646100 <oops_in_progress>
ffffffff80129fc8: 64 48 8b 04 25 28 00 mov %fs:0x28,%rax
ffffffff80129fcf: 00 00
ffffffff80129fd1: 48 89 45 c8 mov
%rax,0xffffffffffffffc8(%rbp)
ffffffff80129fd5: 31 c0 xor %eax,%eax
ffffffff80129fd7: 45 85 db test %r11d,%r11d
ffffffff80129fda: 74 68 je ffffffff8012a044
<vprintk+0x94>
ffffffff80129fdc: 8b 05 ea 8c 3e 00 mov
4099306(%rip),%eax # ffffffff80512ccc <printk_cpu>
ffffffff80129fe2: 85 c0 test %eax,%eax
ffffffff80129fe4: 75 5e jne ffffffff8012a044
<vprintk+0x94>
ffffffff80129fe6: 48 8b 05 13 e2 4a 00 mov
4907539(%rip),%rax # ffffffff805d8200 <jiffies>
ffffffff80129fed: 48 8b 15 2c c5 51 00 mov
5358892(%rip),%rdx # ffffffff80646520 <oops_timestamp.17285>
Now, that should correspond to source code:
asmlinkage int vprintk(const char *fmt, va_list args)
{
unsigned long flags;
int printed_len;
char *p;
static char printk_buf[1024];
static int log_level_unknown = 1;
preempt_disable();
if (unlikely(oops_in_progress) && printk_cpu == smp_processor_id())
/* If a crash is occurring during printk() on this CPU,
* make sure we can''t deadlock */
zap_locks();
which isn''t so much clearer to me...
Keir Fraser a écrit :>
> On 3/1/07 11:04, "PUCCETTI Armand" <armand.puccetti@cea.fr>
wrote:
>
>
>> I removed both options but exactly the same trace comes out.
>> Are there any other options I should add?
>>
>> Armand
>>
>
> You could add ''debug'' as a boot parameter, but it looks
like you are
> crashing too early to get any output. Have you tried disassembling the
Linux
> kernel image (objdump -d vmlinux) and see what function contains address
> ffffffff80129fc8 (the crashing RIP value)?
>
> -- Keir
>
>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Campbell
2007-Jan-03 14:26 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
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@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: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 > bootIan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Jan-03 14:27 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
On 3/1/07 15:26, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote:> 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 > bootIt should be on the module line, not the kernel line. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 14:33 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
Ian Campbell a écrit :> On Wed, 2007-01-03 at 10:12 +0000, Keir Fraser wrote: > >> On 3/1/07 11:04, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote: >> >> >>> I removed both options but exactly the same trace comes out. >>> Are there any other options I should add? >>> >>> Armand >>> >> You could add ''debug'' as a boot parameter, but it looks like you are >> crashing too early to get any output. Have you tried disassembling the Linux >> kernel image (objdump -d vmlinux) and see what function contains address >> ffffffff80129fc8 (the crashing RIP value)? >> > > "earlyprintk=serial,ttyS0" on the kernel command line might help if > CONFIG_EARLY_PRINTK is enabled. > > Ian. > > > >Yes the CONFIG_EARLY_PRINTK flag is enabled , but the trace is exactly the same. :-( Armand __ __ _____ ___ _____ ___ \ \/ /___ _ __ |___ / / _ \ |___ / / _ \ \ // _ \ ''_ \ |_ \| | | | |_ \ __| | | | / \ __/ | | | ___) | |_| | ___) |__| |_| | /_/\_\___|_| |_| |____(_)___(_)____/ \___/ http://www.cl.cam.ac.uk/netos/xen University of Cambridge Computer Laboratory Xen version 3.0.3-0 (root@intra.cea.fr) (gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5)) Fri Dec 22 14:53:08 CET 2006 Latest ChangeSet: unavailable (XEN) Command line: /boot/xen-3.gz dom0_mem=1048576 noreboot com1=115200,8n1 earlyprintk=serial,ttyS0 (XEN) Physical RAM map: (XEN) 0000000000000000 - 00000000000a0000 (usable) (XEN) 00000000000f0000 - 0000000000100000 (reserved) (XEN) 0000000000100000 - 00000000dfe86c00 (usable) (XEN) 00000000dfe86c00 - 00000000dfe88c00 (ACPI NVS) (XEN) 00000000dfe88c00 - 00000000dfe8ac00 (ACPI data) (XEN) 00000000dfe8ac00 - 00000000e0000000 (reserved) (XEN) 00000000f0000000 - 00000000f4000000 (reserved) (XEN) 00000000fec00000 - 00000000fed00400 (reserved) (XEN) 00000000fed20000 - 00000000feda0000 (reserved) (XEN) 00000000fee00000 - 00000000fef00000 (reserved) (XEN) 00000000ffb00000 - 0000000100000000 (reserved) (XEN) System RAM: 3582MB (3668120kB) (XEN) Xen heap: 13MB (14196kB) (XEN) found SMP MP-table at 000fe710 (XEN) DMI 2.3 present. (XEN) Using APIC driver default (XEN) ACPI: RSDP (v002 DELL ) @ 0x00000000000feb00 (XEN) ACPI: XSDT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd259 (XEN) ACPI: FADT (v003 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd351 (XEN) ACPI: SSDT (v001 DELL st_ex 0x00001000 INTL 0x20050309) @ 0x00000000fffd86d6 (XEN) ACPI: MADT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd445 (XEN) ACPI: BOOT (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd4b7 (XEN) ACPI: ASF! (v016 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd4df (XEN) ACPI: MCFG (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd546 (XEN) ACPI: HPET (v001 DELL GX620 0x00000007 ASL 0x00000061) @ 0x00000000000fd584 (XEN) ACPI: DSDT (v001 DELL dt_ex 0x00001000 INTL 0x20050309) @ 0x0000000000000000 (XEN) ACPI: Local APIC address 0xfee00000 (XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) (XEN) Processor #0 15:4 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) (XEN) Processor #1 15:4 APIC version 20 (XEN) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x06] disabled) (XEN) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x07] disabled) (XEN) ACPI: LAPIC_NMI (acpi_id[0xff] high level lint[0x1]) (XEN) ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0]) (XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) (XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) (XEN) ACPI: IRQ0 used by override. (XEN) ACPI: IRQ2 used by override. (XEN) ACPI: IRQ9 used by override. (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs (XEN) ACPI: HPET id: 0x8086a201 base: 0xfed00000 (XEN) Using ACPI (MADT) for SMP configuration information (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Initializing CPU#0 (XEN) Detected 3192.153 MHz processor. (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 2048K (XEN) CPU: Physical Processor ID: 0 (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#0. (XEN) CPU0: Intel P4/Xeon Extended MCE MSRs (24) available (XEN) CPU0: Thermal monitoring enabled (XEN) CPU0: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03 (XEN) Booting processor 1/1 eip 90000 (XEN) Initializing CPU#1 (XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K (XEN) CPU: L2 cache: 2048K (XEN) CPU: Physical Processor ID: 0 (XEN) Intel machine check architecture supported. (XEN) Intel machine check reporting enabled on CPU#1. (XEN) CPU1: Intel P4/Xeon Extended MCE MSRs (24) available (XEN) CPU1: Thermal monitoring enabled (XEN) CPU1: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03 (XEN) Total of 2 processors activated. (XEN) ENABLING IO-APIC IRQs (XEN) -> Using new ACK method (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=-1 pin2=-1 (XEN) checking TSC synchronization across 2 CPUs: passed. (XEN) Platform timer is 14.318MHz HPET (XEN) Brought up 2 CPUs (XEN) Machine check exception polling timer started. (XEN) *** LOADING DOMAIN 0 *** (XEN) Domain 0 kernel supports features = { 0000001f }. (XEN) Domain 0 kernel requires features = { 00000000 }. (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000006000000->0000000008000000 (253952 pages to be allocated) (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80100000->ffffffff806f36e8 (XEN) Init. ramdisk: ffffffff806f4000->ffffffff80f0d800 (XEN) Phys-Mach map: ffffffff80f0e000->ffffffff8110e000 (XEN) Start info: ffffffff8110e000->ffffffff8110e49c (XEN) Page tables: ffffffff8110f000->ffffffff8111c000 (XEN) Boot stack: ffffffff8111c000->ffffffff8111d000 (XEN) TOTAL: ffffffff80000000->ffffffff81400000 (XEN) ENTRY ADDRESS: ffffffff80100000 (XEN) Dom0 has maximum 2 VCPUs (XEN) Initrd len 0x819800, start at 0xffffffff806f4000 (XEN) Scrubbing Free RAM: ....................................done. (XEN) Xen trace buffers: disabled (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). (XEN) domain_crash_sync called from entry.S (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-3.0.3-0 x86_64 debug=y Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: e033:[<ffffffff80129fc8>] (XEN) RFLAGS: 0000000000000286 CONTEXT: guest (XEN) rax: ffffffff805dbf00 rbx: 0000000000000000 rcx: 0000000000000000 (XEN) rdx: 0000000000000100 rsi: ffffffff805dbee0 rdi: ffffffff80497128 (XEN) rbp: ffffffff805dbed0 rsp: ffffffff805dbe10 r8: 0000000000000000 (XEN) r9: 0000000000000000 r10: 0000000000000000 r11: 0000000000000000 (XEN) r12: 0000000000000000 r13: 0000000000000000 r14: 0000000000000000 (XEN) r15: 0000000000000000 cr0: 000000008005003b cr4: 00000000000006f0 (XEN) cr3: 0000000006101000 cr2: 0000000000000028 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff805dbe10: (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff80129fc8 (XEN) 000000010000e030 0000000000010086 ffffffff805dbe50 000000000000e02b (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) ffffffff805dbfb0 ffffffff8012a347 0000003000000008 ffffffff805dbfc0 (XEN) ffffffff805dbf00 0000000000000000 0000000000000000 ffffffff8062e040 (XEN) 0000000000000100 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000102 0000000000000000 0000000000000102 ffffffff8011b321 (XEN) 0000000006102ff8 0000000000000000 0000000000000102 ffffffff8011b401 (XEN) 000000000000000f 0000000000006102 ffffffff805c7000 0000000000000000 (XEN) ffffffff805dbfb0 ffffffff80111032 0000000000000000 0000000000000000 (XEN) ffffffff805dbff0 ffffffff805dd11e ffff800000000000 ffff804000000000 (XEN) 00000007ffffffff 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 (XEN) Domain 0 crashed: ''noreboot'' set - not rebooting. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2007-Jan-03 14:58 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
On 3/1/07 15:48, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote:> Sorry for the err. Moving the option to the module line, as below, > leaves the trace unchanged.It looks rather like it must be a bogus Linux kernel image then. Are you sure it was built from the same repository as Xen, with reasonable kernel config options (e.g., including the Xen console driver)? Something quite simple must be wrong here. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 15:26 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
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 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 15:48 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
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@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: >> > > 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@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-03 16:55 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
Keir Fraser a écrit :> On 3/1/07 15:48, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote: > > >> Sorry for the err. Moving the option to the module line, as below, >> leaves the trace unchanged. >> > > It looks rather like it must be a bogus Linux kernel image then. Are you > sure it was built from the same repository as Xen, with reasonable kernel > config options (e.g., including the Xen console driver)? Something quite > simple must be wrong here. > > -- Keir > > >I have downloaded the source files of XEN 3.0.3-0 just the week after it was made available, ie end october 2005. I had to change my Linux distro to ubuntu 6.10 because the former 6.06 LTS did not support a new replacement graphic card. The (actual) kernel is 2.6.17.10. I checked the dependencies and compiled the sources with gcc 4.1 and the most recent version of the other modules required. That is done by the script $ make dist CC=gcc-4.1 verbose=y debug=y perfc=y debugger=y $ make install CC=gcc-4.1 verbose=y debug=y perfc=y debugger=y As the image crashed, the SATA drivers were suspected and I changed by hand the configuration file in .../xen-3.0.3/linux-2.6.16.29-xen0/.config enabling the SATA options CONFIG_SCSI_SATA=y CONFIG_SCSI_SATA_AHCI=y CONFIG_SCSI_SATA_SVW=y CONFIG_SCSI_ATA_PIIX=y CONFIG_SCSI_SATA_MV=y CONFIG_SCSI_SATA_NV=y The other kernel options were unchanged. In the top Makefile I changed the variable KERNELS ?= linux-2.6-xen0 linux-2.6-xenU and patched panic.c (addition of the function __stack_chk_fail) as someone on the list indicated. Afterwards, I added the boot options to enable the console during boot, through the first serial port, as indicated in the manual. Nothing was recompiled. Armand _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
PUCCETTI Armand
2007-Jan-04 16:24 UTC
Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]
Problem solved! I recompiled XEN 3.0.3 entirely using gcc-3.3 instead of gcc-4.1 and it boots properly. Apparently function vprintk located in .../xen-3.0.3/linux-2.6.16.29-xen0/kernel/printk.c was not compiled correctly by gcc. thank you very much for your help! Armand NOTE1: the extended Linux traces contain much more details on the devices and their drivers. About ATA there is a message about an abnormal port ATA: ata_piix 0000:00:1f.2: version 1.05 ata_piix 0000:00:1f.2: version 1.05 GSI 18 sharing vector 0xA8 and IRQ 18 GSI 18 sharing vector 0xA8 and IRQ 18 ACPI: PCI Interrupt 0000:00:1f.2[C] -> ACPI: PCI Interrupt 0000:00:1f.2[C] -> GSI 20 (level, low) -> IRQ 18 GSI 20 (level, low) -> IRQ 18 PCI: Setting latency timer of device 0000:00:1f.2 to 64 PCI: Setting latency timer of device 0000:00:1f.2 to 64 ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18 ata1: SATA max UDMA/133 cmd 0xFE00 ctl 0xFE12 bmdma 0xFEA0 irq 18 ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18 ata2: SATA max UDMA/133 cmd 0xFE20 ctl 0xFE32 bmdma 0xFEA8 irq 18 ata1: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3e01 87:4023 88:207f ata1: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3e01 87:4023 88:207f ata1: dev 0 ATA-7, max UDMA/133, 488281250 sectors: LBA48 ata1: dev 0 ATA-7, max UDMA/133, 488281250 sectors: LBA48 ata1: dev 0 configured for UDMA/133 ata1: dev 0 configured for UDMA/133 scsi0 : ata_piix scsi0 : ata_piix ATA: abnormal status 0xFF on port 0xFE27 ATA: abnormal status 0xFF on port 0xFE27 ata2: disabling port ata2: disabling port scsi1 : ata_piix scsi1 : ata_piix NOTE2: in the XEN traces there is a note (below) about serial input to dom0. How does this function? (XEN) Xen trace buffers: disabled (XEN) Xen is relinquishing VGA console. (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input to Xen). Keir Fraser a écrit :> On 3/1/07 15:48, "PUCCETTI Armand" <armand.puccetti@cea.fr> wrote: > > >> Sorry for the err. Moving the option to the module line, as below, >> leaves the trace unchanged. >> > > It looks rather like it must be a bogus Linux kernel image then. Are you > sure it was built from the same repository as Xen, with reasonable kernel > config options (e.g., including the Xen console driver)? Something quite > simple must be wrong here. > > -- Keir > > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel