From owner-freebsd-current  Mon Feb 16 06:34:38 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id GAA08700
          for freebsd-current-outgoing; Mon, 16 Feb 1998 06:34:38 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08678
          for <current@FreeBSD.ORG>; Mon, 16 Feb 1998 06:34:35 -0800 (PST)
          (envelope-from tlambert@usr01.primenet.com)
Received: (from daemon@localhost)
	by smtp02.primenet.com (8.8.8/8.8.8) id HAA29806;
	Mon, 16 Feb 1998 07:20:38 -0700 (MST)
Received: from usr01.primenet.com(206.165.6.201)
 via SMTP by smtp02.primenet.com, id smtpd029789; Mon Feb 16 07:20:36 1998
Received: (from tlambert@localhost)
	by usr01.primenet.com (8.8.5/8.8.5) id HAA09317;
	Mon, 16 Feb 1998 07:20:35 -0700 (MST)
From: Terry Lambert <tlambert@primenet.com>
Message-Id: <199802161420.HAA09317@usr01.primenet.com>
Subject: Re: panic: rslock
To: toasty@home.dragondata.com (Kevin Day)
Date: Mon, 16 Feb 1998 14:20:35 +0000 (GMT)
Cc: current@FreeBSD.ORG
In-Reply-To: <199802160437.WAA04174@home.dragondata.com> from "Kevin Day" at Feb 15, 98 10:37:31 pm
X-Mailer: ELM [version 2.4 PL25]
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?


					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