From owner-freebsd-current Tue Jan 23 10:34:39 2001 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 3D6F837B404 for ; Tue, 23 Jan 2001 10:34:18 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id f0NIY5G47608; Tue, 23 Jan 2001 20:34:05 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200101231834.f0NIY5G47608@zibbi.icomtek.csir.co.za> Subject: Re: ahc messages In-Reply-To: <200101231733.f0NHXrs82881@aslan.scsiguy.com> from "Justin T. Gibbs" at "Jan 23, 2001 10:33:53 am" To: gibbs@scsiguy.com (Justin T. Gibbs) Date: Tue, 23 Jan 2001 20:34:05 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 > >On a current SMP box running a kernel from this morning I see messages > >from the ahc driver I haven't seen before. The machine keeps on running > >though. Should I worry about them or back down to kernel of yesterday? > > Hmmm. Can you add a call to "ahc_dump_card_state(ahc);" after the > "WARNING" printf in aic7xxx.c? I'm trying to reproduce this here as > well. I don't know what I've changed that could cause the qoutfifo > to become confused. How many drives do you have on the controller? There are 3 drives on the controller. Almost everything is on da0 except /usr/obj that is on da2. Releases are also built on da2. da1 is mostly idle. I have only seen it once. The first time after a reboot with the new kernel. I have now rebooted again with the same kernel and built a whole release with a squeek from ahc. Is it possible that it could have been some interaction or leftover from the previous sequencer code or something like that? I'll put ahc_dump_card_state(ahc) in. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message