From owner-freebsd-current Mon May 11 23:01:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09029 for freebsd-current-outgoing; Mon, 11 May 1998 23:01:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA09022 for ; Mon, 11 May 1998 23:01:36 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0yZ885-0005zL-00; Mon, 11 May 1998 23:01:34 -0700 Date: Mon, 11 May 1998 23:01:29 -0700 (PDT) From: Tom X-Sender: tom@shell.uniserve.ca To: awhawks@usa.net cc: freebsd-current@FreeBSD.ORG Subject: RE: SCSI problems? In-Reply-To: <199805120038.UAA00736@hawks.caro.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 May 1998 awhawks@usa.net wrote: > I have the old 2940 adapter and it has the timeout problem so I don't think > its related to the revision level. I also have turned off all the ahc_ options It is more related to the devices on the bus. > in -current and I still get the timeouts. Mine are not as infrequent as others > on the lists. I get them every hour it seems. > > The problem didn't seem to be in the 3.0-current code as of aug 3 1997, which > is what I was running until about a month ago when the timeouts started. So > I would guess it was introduced from aug 3 1997 to now in the -current branch. Unlikely. The code is not being developed further. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message