Date: Tue, 13 Oct 1998 18:14:40 -0700 (PDT) From: Chris Timmons <skynyrd@opus.cts.cwu.edu> To: Manfred Antar <mantar@netcom.com> Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: Panic when rebooting with current kernel Message-ID: <Pine.BSF.3.96.981013181219.11897I-100000@opus.cts.cwu.edu> In-Reply-To: <4.1.19981013171511.00a2b100@192.168.0.1>
next in thread | previous in thread | raw e-mail | index | archive | help
I've filed this as kern/8309, which contains a trace (I have a core, -g'd
kernel and the aout gdb if anybody wants them :)
I will say that this was the first time I built a kernel slightly out of
sync with the world, so I am going to go back and do that to make sure
there isn't something goofy in that regard.
-Chris
On Tue, 13 Oct 1998, Manfred Antar wrote:
> For the past day every time I reboot (shutdown -r now) I get
>
> boot called on cpu#0
>
>
> syncing disks... 3 done
> panic: rslock: cpu: 1, addr:0xf5b49f88, lock: 0x01000001
> mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000
> Debugger("panic")
> Stopped at Debugger+0x35: movb $0,in_Debugger.98
>
> This happens with both aout and elf kernels.
> This is an SMP Intel PR440FX with a DPT (no-raid) controller.
> The sources are current as 5pm Oct 13 PDT.
> A kernel from 24 hours ago works fine. There were alot of changes
> to the sys tree in the past day. I try backing out to 1 day ago.
> And see if i can find the change that caused this
> Manfred
> ==============================
> || mantar@netcom.com ||
> || pozo@infinex.com ||
> || Ph. (415) 681-6235 ||
> ==============================
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.981013181219.11897I-100000>