On Thu, 22 Jan 2004, Havard Eidnes wrote:

> Hi,
>
> and thanks for the console output.  Two comments:
>
>  o The "cpu<n>: processor failed to hatch" comes from an attempt at
>    starting the secondary CPUs spinning; see cpu_boot_secondary() in
>    sys/arch/alpha/alpha/cpu.c.  I do not have any definitive idea why
>    this would happen -- sorry.  I think that as a first try I would
>    try multiplying the time-out with 10, but that's probably not going
>    anywhere useful.
>
>    The kernel should already be waiting for 10 seconds for each CPU
>    for it to spin up.  Does that match what you see on the console
>    while it's doing that part of the autoconfiguration?

Yes. It's waiting a little while before printing out the message.

>  o the kernel panic you get is in ltsleep(), and seems to indicate
>    that a sleep is done outside of a process context, i.e. curlwp is
>    NULL.  It would be interesting to see a stack backtrace to see
>    where this happens.  I'm not sure if this is actually related to
>    the machine running with multiple physical CPUs (but failed to
>    initialize the secondary CPUs).

panic: spinlock_switchcheck: CPU 1 has 1 spin locks
Stopped in pid 5.1 (ioflush) at netbsd:cpu_Debugger+0x4:        ret     zero,(ra
)
db{1}> bt
cpu_Debugger() at netbsd:cpu_Debugger+0x4
panic() at netbsd:panic+0x1f8
spinlock_switchcheck() at netbsd:spinlock_switchcheck+0xa4
prologue botch: displacement 16
frame size botch: adjust register offsets?
mi_switch() at netbsd:mi_switch+0x58
mi_switch() at netbsd:mi_switch+0x58
db{1}>

Not really pretty, I'd say.

	Johnny

Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol