Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 May 2005 16:40:38 -0400
From:      John Baldwin <jhb@FreeBSD.org>
To:        freebsd-smp@FreeBSD.org
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: 'panic: spin lock held too long' at boot
Message-ID:  <200505121640.39280.jhb@FreeBSD.org>
In-Reply-To: <20050506154458.GA13055@xor.obsecurity.org>
References:  <20050506154458.GA13055@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 06 May 2005 11:44 am, Kris Kennaway wrote:
> The following has happened twice recently while booting 6.0 on a
> 12-processor e4500:
>
> [...]
> Waiting 8 seconds for SCSI devices to settle
> SMP: AP CPU #11 Launched!
> SMP: AP CPU #10 Launched!
> SMP: AP CPU #9 Launched!
> SMP: AP CPU #8 Launched!
> SMP: AP CPU #7 Launched!
> SMP: AP CPU #6 Launched!
> SMP: AP CPU #5 Launched!
> SMP: AP CPU #4 Launched!
> SMP: AP CPU #3 Launched!
> SMP: AP CPU #2 Launched!
> SMP: AP CPU #1 Launched!
> panic: spin lock held too long0xffffff813e774730 foor >5 seecons
> cpuid = 11
> KDB: enter: panic
> [hangs]
>
> Any ideas?

Could be related to how the idle loop is coded.  Try hacking on it so that it 
does a try lock of sched_lock and only calls mi_switch() if it succeeds, 
otherwise loop around and call sched_runnable() again.

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200505121640.39280.jhb>