Re: [ACPI x86_64] 2.6.1-rc{1,2} hang while booting on Sun v20z akaNewisys 2100

[Len Brown]

On Thu, 2004-04-22 at 15:45, Shantanu Goel wrote:

> This works ok though again with only one cpu coming up.  Here is the output:
> 
> Bootdata ok (command line is ro root=LABEL=/ console=ttyS0 console=tty0 
> debug acpi=off)
> Linux version 2.6.5-x86_64 (root@njlxlabstinger2) (gcc version 3.2.3 
> 20030502 (Red Hat Linux 3.2.3-24)) #2 SMP Thu Apr 22 14:50:09 EDT 2004

> Intel MultiProcessor Specification v1.4
>     Virtual Wire compatibility mode.
> SMP mptable: bad signature [  ]!
> BIOS bug, MP table errors detected!...
> ... disabling SMP support. (tell your hw vendor)

This explains why MPS doesn't boot SMP when acpi=off...

> 
> >Anyway, try acpi=ht to get your cpus back.
> >  
> >
> 
> This hangs.  Here is the output:
> 
> Bootdata ok (command line is ro root=LABEL=/ console=ttyS0 console=tty0 
> debug acpi=ht)
> Linux version 2.6.5-x86_64 (root@njlxlabstinger2) (gcc version 3.2.3 
> 20030502 (Red Hat Linux 3.2.3-24)) #2 SMP Thu Apr 22 14:50:09 EDT 2004
> BIOS-provided physical RAM map:

> ACPI: Subsystem revision 20040326
> ACPI: Interpreter enabled

oops, acpi=ht doesn't work on x86_64 -- yet.

> >More interesting would be if pci=noacpi works on 2.6.
> >
> 
> This hangs as well.  Here is the output:
> 
> Bootdata ok (command line is ro root=LABEL=/ console=ttyS0 console=tty0 
> debug pci=noacpi)
> Linux version 2.6.5-x86_64 (root@njlxlabstinger2) (gcc version 3.2.3 
> 20030502 (Red Hat Linux 3.2.3-24)) #2 SMP Thu Apr 22 14:50:09 EDT 2004
> BIOS-provided physical RAM map:

> Intel MultiProcessor Specification v1.4
>     Virtual Wire compatibility mode.
> SMP mptable: bad signature [<3>BIOS bug, MP table errors detected!...
> ... disabling SMP support. (tell your hw vendor)

Broken BIOS/MPS tables own this failure.
See if you can disable MPS in the BIOS/SETUP.
that is, after you verify you've got the latest BIOS...

cheers,
-Len


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/