Date: Mon, 16 Feb 1998 14:20:35 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: toasty@home.dragondata.com (Kevin Day) Cc: current@FreeBSD.ORG Subject: Re: panic: rslock Message-ID: <199802161420.HAA09317@usr01.primenet.com> In-Reply-To: <199802160437.WAA04174@home.dragondata.com> from "Kevin Day" at Feb 15, 98 10:37:31 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I get the following panic quite frequently under heavy load on this neptune
> chipset dual P/100:
>
>
> panic: rslock: cpu: 1, addr: 0f860b2a0, lock: 0x01000001
> mp_lock = 01000001; cpuid = 1; lapic.id = 01000000
> Debugger("panic")
> Stopped at _Debugger+0x35: movb $0,_in_Debugger.94
>
> trace shows:
>
> _Debugger
> _panic
> bsl1
> _qsync
> _ffs_sync
> _sync
> _vfs_update
> _kproc_start
> _fork_trampoline
>
> Is this a new one?
I haven't seen it before... doesn't make it new, though.
> wdc0: <CMD 640B IDE> rev 0x02 int a irq 14 on pci0.4.0
[ ... ]
> wdc0: CMD640B workaround enabled
I am not positive that the CMD640B workaround is MP safe (in fact, I'm
not sure it works with a secondary disk, either). You should contact
the maintainers (Bruce Evans, Paul Traina, Junichi, etc.) for details.
Does the crash ever occur in UP mode?
Terry Lambert
terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.
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?199802161420.HAA09317>