Date: Tue, 17 Feb 1998 10:10:22 +0100 (MET) From: Wolfgang Helbig <helbig@Informatik.BA-Stuttgart.DE> To: tlambert@primenet.com (Terry Lambert) Cc: toasty@home.dragondata.com, current@FreeBSD.ORG Subject: Re: panic: rslock Message-ID: <199802170910.KAA00306@rvc1.informatik.ba-stuttgart.de> In-Reply-To: <199802161420.HAA09317@usr01.primenet.com> from Terry Lambert at "Feb 16, 98 02:20:35 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
Well, I think it's not tested on an MP machine, there is no reason it
shouldn't work.
> not sure it works with a secondary disk, either). You should contact
It works.
> 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
>
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?199802170910.KAA00306>