Re: [Xen-devel] Re: [Xen-users] XEN 3.0.3 on Ubuntu 6.10: Dom0 reboot]

[PUCCETTI Armand <armand.puccetti@xxxxxx>]

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@xxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel