From owner-freebsd-current  Sun Sep 20 10:37:33 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA00739
          for freebsd-current-outgoing; Sun, 20 Sep 1998 10:37:33 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00714
          for <current@FreeBSD.ORG>; Sun, 20 Sep 1998 10:37:24 -0700 (PDT)
          (envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.1/8.9.1) id TAA18431;
	Sun, 20 Sep 1998 19:35:59 +0200 (SAT)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199809201735.TAA18431@zibbi.mikom.csir.co.za>
Subject: Re: [CAM] Broken tagged queuing drive?
In-Reply-To: <18392.906310982@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 20, 98 10:03:02 am"
To: jkh@time.cdrom.com (Jordan K. Hubbard)
Date: Sun, 20 Sep 1998 19:35:59 +0200 (SAT)
Cc: gibbs@plutotech.com, mantar@netcom.com, kato@ganko.eps.nagoya-u.ac.jp,
        current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (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 also see it here on my dual P5 machine. It seems to be caused by the
latest version of isa/clock.c. If I go to the previous version (while
keeping the rest of the source the same), the panic disappear. It only
happens on the dual P5 machine, the 486 runs happily with the latest
version of isa/clock.c.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> Aha!  That message looks very similiar to what flashes by very quickly
> on Bento.  I'm glad that someone, at least, was able to see it long
> enough to transcribe it. :) I believe it's exactly the same problem I
> reported earlier (with SMP).  I can build and install a UMP kernel
> on bento if you think it will help.
> 
> - Jordan
> 
> > >It still does it.
> > >I booted in single user and did fsck. It panicked
> > >This time it stopped scrolling and here is the output.:
> > >panic: rslock: cpu: 1, addr: 0xf0248fcc, lock: 0x01000001
> > >mp_lock = 01000003; cpuid = 1; lapic.id = 0c000000
> > >boot() called on cpu#1
> > 
> > Can you reproduce a panic using a UP kernel?  What kind of
> > DPT board are you using?
> > 
> > --
> > Justin

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