From owner-freebsd-current Fri Nov 26 3:10: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp.wirehub.nl (smtp.wirehub.nl [195.86.25.80]) by hub.freebsd.org (Postfix) with ESMTP id 3413514E5A for ; Fri, 26 Nov 1999 03:10:02 -0800 (PST) (envelope-from Ben.Grimm@wirehub.net) Received: from ben.wirehub.nl (ben.wirehub.nl [195.86.25.13]) by smtp.wirehub.nl (8.9.3/8.9.3) with SMTP id MAA20364 for ; Fri, 26 Nov 1999 12:09:53 +0100 (CET) From: "Ben C. O. Grimm" To: freebsd-current@freebsd.org Subject: Re: AHC0 fireworks ? Date: Fri, 26 Nov 1999 12:09:53 +0100 Organization: Wirehub! Internet Engineering Message-ID: <38qs3sgfgsa87qhd34ecfq67mqha7bffot@smtp.wirehub.nl> References: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4.newsgate.clinet.fi> In-Reply-To: <4.2.0.58.19991120091815.00c2ced0@194.184.65.4.newsgate.clinet.fi> X-Mailer: Forte Agent 1.7/32.534 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 20 Nov 1999 11:20:23 +0200, Gianmarco Giovannelli wrote: > But I have now a lot of errors (as you can see in this logs) on my scsi chain. > I had never experienced such things in the near past (even if as an old > current user sometimes I see also worse things :-) > > Btw I don't see in the current mailing list threads about iussues on the > scsi subsystem recently so it can be a problem related to my hardware (even > if I didn't experience it before)... > Nov 20 09:17:49 gmarco /kernel: ahc0: adapter> irq 19 at device 6.0 on pci0 > Nov 20 09:17:49 gmarco /kernel: (da0:ahc0:0:0:0): parity error during > Data-In phase. Please look up the following discussion in freebsd-questions. I'm reading these lists on Usenet, so I'm going to give you Usenet message-Id's: <19991124135732.E23235@mincom.com.newsgate.clinet.fi> <9911240640.AA10118@CS.UH.EDU.newsgate.clinet.fi> <19991124182926.K23235@mincom.com.newsgate.clinet.fi> <95ln3skv9r10s0f6sp0lhd8nhslh1hgrh7@smtp.wirehub.nl.newsgate.clinet.fi> The last one is a log extract quite similar to yours ... it's Adaptec that's seemingly causing the problems here. I'm running 3.3-RELEASE, and problems started on two machines with a lot of disk usage (both news related) when I upgraded from 3.1/3.2 -> 3.3. The fact that this hasn't been fixed anywhere in the cvsup route makes me rather sad. I'm really waiting for fixes/patches .. -- - Ben C. O. Grimm ----------------- Ben.Grimm@wirehub.net - - Wirehub! Internet Engineering - http://www.wirehub.net/ - - Wirehub! Backbone --- http://doema.wirehub.net/wirehub/ - - Private Ponderings ------- http://libertas.wirehub.net/ - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message