From owner-freebsd-current Mon Jan 4 09:13:02 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA07336 for freebsd-current-outgoing; Mon, 4 Jan 1999 09:13:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07312 for ; Mon, 4 Jan 1999 09:12:48 -0800 (PST) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.9.1/BNET-98/09/30-E) with ESMTP id IAA20227; Mon, 4 Jan 1999 08:04:52 -0800 (PST) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id IAA11336; Mon, 4 Jan 1999 08:04:20 -0800 (PST) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id HAA06449; Mon, 4 Jan 1999 07:59:27 -0800 To: mike@smith.net.au Cc: rjlynn@rjlynn.ddns.org, FreeBSD-current@FreeBSD.ORG Subject: Re: IDE Problem In-Reply-To: Your message of "Fri, 01 Jan 1999 18:49:09 -0800" <199901020249.SAA06391@dingo.cdrom.com> References: <199901020249.SAA06391@dingo.cdrom.com> X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990104075927E.thomma@baynetworks.com> Date: Mon, 04 Jan 1999 07:59:27 -0800 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 29 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm just starting out on -Current and heard theres been a problem with wd > > disks since Christmas, is that true? > > No. There's an outstanding problem with secondary IDE channels on some > motherboards, but the problem has been with us for quite some time. As just datapoint, two of my systems started having wd timeout problem sometime around Christmas. It has been working for about year or so with DMA on. The system are: FIC PA-2007 wd0: Quantum 6.4G Fireball (flags was 0xb0ff, yes LBA is on, now 0x90ff) wd1: none wd2: Maxtor 11G DiamondMax (flags was 0xa0ff, and it is 0xa0ff) wd3: Mitsumi IDE CDROM FIC PA-2007 wd0: IBM 6.4G Deskstar (flags 0xa0ff, it is 0x80ff) boot disk wd1: none wd2: none wd3: none ccd0: 2.1G x 2 on NCR 875 Sometime after Christmas, I had to turn off DMA on wd0 to bring up the system. The kernel before Christmas (mid December 1998) doesn't have this problem. Funny thing is that wd2 Maxtor doesn't show the problem even though it shares the bus with old IDE CDROM. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message