From owner-freebsd-current Tue Jan 23 9:34:29 2001 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 275F337B402 for ; Tue, 23 Jan 2001 09:34:09 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f0NHXrs82881; Tue, 23 Jan 2001 10:33:58 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101231733.f0NHXrs82881@aslan.scsiguy.com> To: John Hay Cc: current@freebsd.org Subject: Re: ahc messages In-Reply-To: Your message of "Sat, 23 Jan 2001 09:30:14 +0200." <200101230730.f0N7UED32260@zibbi.icomtek.csir.co.za> Date: Tue, 23 Jan 2001 10:33:53 -0700 From: "Justin T. Gibbs" 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? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message