current unstable doesn't boot dom0 (SMP bug?)

current unstable doesn't boot dom0 (SMP bug?)

[Gerd Knorr]

   Hi,

This is changeset 7425:7c951e3eb5ab, last messages are:

Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
(XEN) DOM0: (file=mm.c, line=1467) Bad type (saw f0000001 != exp 
a0000000) for mfn 10a2 (pfn 18a2)
kernel BUG at arch/xen/kernel/smpboot.c:184 (vcpu_prepare)!
  [<c0109c96>] dump_stack+0x1e/0x20
  [<c0107166>] vcpu_prepare+0x184/0x190
  [<c0447443>] smp_prepare_cpus+0x134/0x205
  [<c01040a4>] init+0x3a/0x1b6
  [<c01078b5>] kernel_thread_helper+0x5/0xb
Kernel panic - not syncing: BUG!
  smp_send_stop disable_local_APIC
(XEN) Domain 0 shutdown: rebooting machine.

cheers,

   Gerd

Re: current unstable doesn't boot dom0 (SMP bug?)

[Gerd Knorr]

Gerd Knorr wrote:
>   Hi,
> 
> This is changeset 7425:7c951e3eb5ab, last messages are:

Update: UP kernel boots fine.

   Gerd

Re: current unstable doesn't boot dom0 (SMP bug?)

[Vincent Hanquez]

On Wed, Oct 19, 2005 at 03:40:14PM +0200, Gerd Knorr wrote:
>   Hi,
> 
> This is changeset 7425:7c951e3eb5ab, last messages are:
> 
> Mount-cache hash table entries: 512
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 2048K
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> (XEN) DOM0: (file=mm.c, line=1467) Bad type (saw f0000001 != exp 
> a0000000) for mfn 10a2 (pfn 18a2)
> kernel BUG at arch/xen/kernel/smpboot.c:184 (vcpu_prepare)!
>  [<c0109c96>] dump_stack+0x1e/0x20
>  [<c0107166>] vcpu_prepare+0x184/0x190
>  [<c0447443>] smp_prepare_cpus+0x134/0x205
>  [<c01040a4>] init+0x3a/0x1b6
>  [<c01078b5>] kernel_thread_helper+0x5/0xb
> Kernel panic - not syncing: BUG!
>  smp_send_stop disable_local_APIC
> (XEN) Domain 0 shutdown: rebooting machine.

Hi Gerd,

it looks like we can't reproduce the problems here.
apparently the cpu that it's trying to start, got a gdt page which xen
consider as a writable page, where it should not.

The code in arch/xen/kernel/smpboot.c that set the page looks fine:

==============
cpu_gdt_descr[cpu].address = __get_free_page(GFP_KERNEL|__GFP_ZERO);
BUG_ON(cpu_gdt_descr[0].size > PAGE_SIZE);
cpu_gdt_descr[cpu].size = cpu_gdt_descr[0].size;
memcpy((void *)cpu_gdt_descr[cpu].address,
	(void *)cpu_gdt_descr[0].address,
	cpu_gdt_descr[0].size);
make_page_readonly((void *)cpu_gdt_descr[cpu].address);
==============

is there anything special with your box ?

-- 
Vincent Hanquez

RE: current unstable doesn't boot dom0 (SMP bug?)

[Ian Pratt]

 
> Gerd Knorr wrote:
> >   Hi,
> > 
> > This is changeset 7425:7c951e3eb5ab, last messages are:
> 
> Update: UP kernel boots fine.

Do you get this woth our -xen config? It's SMP dom0.

Ian

Re: current unstable doesn't boot dom0 (SMP bug?)

[Ryan Harper]

I traced my dom0 SMP boot failure (SATA controller doesn't find device)
to this changeset, digging deeper.

changeset:   7415:3d27ee7da0c1
user:        kaf24@firebug.cl.cam.ac.uk
date:        Tue Oct 18 11:40:31 2005 +0100
summary:     Merge i386/x86_64 smpboot.c into a simplified common Xen version.

(7415 + 7421 fix for missing defines, SMP kernel)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low) -> IRQ 17
ata1: SATA max UDMA/100 cmd 0xE0804080 ctl 0xE080408A bmdma 0xE0804000 irq 17
ata2: SATA max UDMA/100 cmd 0xE08040C0 ctl 0xE08040CA bmdma 0xE0804008 irq 17
ata1: PIO error, drv_stat 0x50
ata1: dev 0 not supported, ignoring
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil

(7415 + 7421 fix for missing defines, UP kernel)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low) -> IRQ 17
ata1: SATA max UDMA/100 cmd 0xE0804080 ctl 0xE080408A bmdma 0xE0804000 irq 17
ata2: SATA max UDMA/100 cmd 0xE08040C0 ctl 0xE08040CA bmdma 0xE0804008 irq 17
ata1: dev 0 ATA, max UDMA/133, 156312576 sectors:
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
  Vendor: ATA       Model: Maxtor 6Y080M0    Rev: YAR5
  Type:   Direct-Access                      ANSI SCSI revision: 05


(7414 SMP kernel)
ACPI: PCI Interrupt 0000:01:02.0[A] -> GSI 17 (level, low) -> IRQ 17
ata1: SATA max UDMA/100 cmd 0xE0804080 ctl 0xE080408A bmdma 0xE0804000 irq 17
ata2: SATA max UDMA/100 cmd 0xE08040C0 ctl 0xE08040CA bmdma 0xE0804008 irq 17
ata1: dev 0 ATA, max UDMA/133, 156312576 sectors:
ata1: dev 0 configured for UDMA/100
scsi0 : sata_sil
ata2: no device found (phy stat 00000000)
scsi1 : sata_sil
  Vendor: ATA       Model: Maxtor 6Y080M0    Rev: YAR5
  Type:   Direct-Access                      ANSI SCSI revision: 05


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

Re: current unstable doesn't boot dom0 (SMP bug?)

[Gerd Knorr]

>>> This is changeset 7425:7c951e3eb5ab, last messages are:
>> Update: UP kernel boots fine.
> 
> Do you get this woth our -xen config? It's SMP dom0.

This boots fine (well, doesn't crash, it fails to mount the root fs due 
to missing sata driver though).  I'll go figure which config option this 
is ...

cheers,

   Gerd

Re: current unstable doesn't boot dom0 (SMP bug?)

[Gerd Knorr]

Gerd Knorr wrote:
>>>> This is changeset 7425:7c951e3eb5ab, last messages are:
>>> Update: UP kernel boots fine.
>>
>> Do you get this woth our -xen config? It's SMP dom0.
> 
> This boots fine (well, doesn't crash, it fails to mount the root fs due 
> to missing sata driver though).  I'll go figure which config option this 
> is ...

It's CONFIG_SMP_ALTERNATIVES turned off.

cheers,

   Gerd