From owner-freebsd-current  Mon Feb 16 09:14:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA17530
          for freebsd-current-outgoing; Mon, 16 Feb 1998 09:14:47 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17505
          for <current@FreeBSD.ORG>; Mon, 16 Feb 1998 09:14:43 -0800 (PST)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.5/8.8.5) id LAA23188;
	Mon, 16 Feb 1998 11:14:40 -0600 (CST)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199802161714.LAA23188@home.dragondata.com>
Subject: Re: panic: rslock
In-Reply-To: <199802161420.HAA09317@usr01.primenet.com> from Terry Lambert at "Feb 16, 98 02:20:35 pm"
To: tlambert@primenet.com (Terry Lambert)
Date: Mon, 16 Feb 1998 11:14:40 -0600 (CST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > 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?
> 

No, it never does under an UP kernel.... The only places I've been able to
make it crash are doing a 'make buildworld -j4' or a cvsup.

I've got another IDE controller on an ISA card I can try though...

Kevin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message