From owner-freebsd-current Wed Sep 23 21:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19611 for freebsd-current-outgoing; Wed, 23 Sep 1998 21:01:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19558 for ; Wed, 23 Sep 1998 21:01:15 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id VAA03623; Wed, 23 Sep 1998 21:54:40 -0600 (MDT) Date: Wed, 23 Sep 1998 21:54:40 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809240354.VAA03623@narnia.plutotech.com> To: Adam McDougall cc: current@FreeBSD.ORG Subject: Re: options DPT_LOST_IRQ Newsgroups: pluto.freebsd.current In-Reply-To: <3609A685.A9B65B3A@ameritech.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3609A685.A9B65B3A@ameritech.net> you wrote: > Does CAM still perform what is supposed to when using this kernel > option? Because it doesn't show any evidence of it in Boot: -v and the > unwanted behavior of not using this option is showing up again, even > though its still in my kernel. The CAM driver does not currently honor this option. It could easily be added again, but it would be nice to know why it is necessary. Is the symptom simply a timeout? One thing I noticed that the Linux driver does in it's interrupt handler that FreeBSD doesn't, is to watch for the busy bit in the aux status register. Is this important? (I don't have any docs...) Could it be that we inadvertantly clear an interrupt before the status packet write is complete? If the problem is in the FreeBSD interrupt code, we should find out for sure. I may not have a fast enough adapter (PM3224A) to make the failure occur here, under a PCI bus analyzer, to determine one way or the other. > Thanks in advance.. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message