Date: Sat, 21 Feb 1998 10:12:35 -0600 (CST) From: Kevin Day <toasty@home.dragondata.com> To: toasty@home.dragondata.com (Kevin Day) Cc: current@FreeBSD.ORG Subject: panic: rslock: cpu: 1 during boot on current kernel (was: panic: vm_page_unwire: invalid wire count: 0) Message-ID: <199802211612.KAA14359@home.dragondata.com> In-Reply-To: <199802211518.JAA09042@home.dragondata.com> from Kevin Day at "Feb 21, 98 09:18:37 am"
next in thread | previous in thread | raw e-mail | index | archive | help
One final thing, I cvsupped today's kernel, and I get:
APIC_IO: routing 8254 via 8259 on pin 0
Considering FFS root f/s.
SMP: AP CPU #1 Launched!
SMP: CPU1 apic_initialize():
lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000000 SVR: 0x0000001ff
panic: rslock: cpu 1, addr: 0xf021e8d0, lock: 0x01000001
mp_lock = 01000002; cpuid = 1; lapic.id = 01000000
Debugger("panic")
It then locks up.
I've tried changing the PCI video card back to an ISA one(mentioned below),
no help with either problem.
Going back to a 02/15/98 kernel stops this panic: rslock from happening.
Somewhere between those dates something broke SMP on my motherboard.
>
> Ok, I can add some more information.
>
> This has happened 7 times now. The trace is always exactly the same. The
> only change we have made was adding a second de ethernet card, and routing
> all nfs traffic over it. The reason being that NFS was very slow over our
> existing really really busy local 10MB ethernet. All NFS now goes over an
> 100MB ethernet dedicated to just NFS. Is this some timings thing perhaps
> then, possibly annoyed further by an SMP kernel?
>
> (ok, honestly, there was another change as well, we switched to a PCI VGA
> card instead of an ISA one. Another machine was out of PCI slots, and we
> needed to add another card, so we swapped them, I doubt that has anything to
> do with this, but I'm putting it out in the open now. :) )
>
> Since this is becoming easily reproducable, can someone tell me what to do
> the next time it crashes, and I'll do it.
>
> Kevin
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?199802211612.KAA14359>