Date: Tue, 10 Aug 2004 10:50:30 -0600 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: "Jurzitza, Dieter" <DJurzitza@harmanbecker.com>, aic7xxx@freebsd.org Cc: luben_tuikov@adaptec.com Subject: Re: Question on domain validation Message-ID: <37946C75250C18F87E63B0FD@aslan.scsiguy.com> In-Reply-To: <CFE6A2529AC5FA439B3D852B0F2A6837DAB0E1@OEKAW2EXVS02.hbi.ad.harman.com> References: <CFE6A2529AC5FA439B3D852B0F2A6837DAB0E1@OEKAW2EXVS02.hbi.ad.harman.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Dear listmembers,
> I use a system having one symbios 2-chanel and one adaptec controler onboard.
> The operating system is linux for sparc, kernel 2.4.26, driver version 6.3.9.
>
> I call the driver with the following options (in the initramdisk):
>
> insmod aic7xxx aic7xxx=verbose.dv:{0}
>
> What I get can be seen in the attachement. dv[0]=0.
> Nevertheless, the device starts entering the DV-thread:
> scsi2: Waking DV thread
> ***
> scsi2: Beginning Domain Validation
> scsi2:A:0:0: Perfomring DV
> ***
>
> How should the commandline for the module look like?
No matter what arguments you give the driver, the domain validation
thread will always run to perform an inquiry scan of new devices. This
is required in order to determine the negotiation capabilities of the
device. The dv setting only controls whether the domain validation
thread goes on to perform transport robustness testing after doing
the inquiry scan.
--
Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37946C75250C18F87E63B0FD>