From owner-freebsd-current Sun Sep 20 14:21:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09424 for freebsd-current-outgoing; Sun, 20 Sep 1998 14:21:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09416 for ; Sun, 20 Sep 1998 14:21:19 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA22763; Sun, 20 Sep 1998 14:20:51 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp01.primenet.com, id smtpd022686; Sun Sep 20 14:20:45 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id OAA01510; Sun, 20 Sep 1998 14:20:37 -0700 (MST) From: Terry Lambert Message-Id: <199809202120.OAA01510@usr04.primenet.com> Subject: Re: [CAM] Broken tagged queuing drive? To: gibbs@plutotech.com (Justin T. Gibbs) Date: Sun, 20 Sep 1998 21:20:37 +0000 (GMT) Cc: jkh@time.cdrom.com, gibbs@plutotech.com, mantar@netcom.com, kato@ganko.eps.nagoya-u.ac.jp, current@FreeBSD.ORG In-Reply-To: <199809201704.LAA09379@pluto.plutotech.com> from "Justin T. Gibbs" at Sep 20, 98 10:58:29 am 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 > >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 > > When did you start seeing this problem? I just looked through the aic7xxx > driver diffs and didn't see anything suspicious. I'm wondering if the > driver grew/shrank just a bit and we're seeing some code displacement that > causes this error. > > Do any SMP savvy folks know what this error means? Someone needs to do a sort-n on their kernel that got the panic: | 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 Looking for 0xf0248fcc, and get a traceback. Specifically, this should allow them to identify the code that is attempting to reentrantly lock an already held exclusive lock. 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