From owner-freebsd-current Fri Jan 7 13:13:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from iaehv.iae.nl (iaehv.IAE.nl [194.151.64.2]) by hub.freebsd.org (Postfix) with ESMTP id BD200154E1 for ; Fri, 7 Jan 2000 13:13:49 -0800 (PST) (envelope-from hansot@iae.nl) Received: from iae.nl (pm8d36.iae.nl [212.61.1.35]) by iaehv.iae.nl (Postfix) with ESMTP id 9E54A7DA1; Fri, 7 Jan 2000 22:13:47 +0100 (CET) Message-ID: <3876570B.37E7EEE9@iae.nl> Date: Fri, 07 Jan 2000 22:13:47 +0100 From: Hans Ottevanger X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: New kernel no longer boots on one of my machines... ata, other problems References: <200001070405.UAA75303@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > Well guys, I tried upgrading one of my older machines today to the > latest 4.0. It was running an older 4.0 kernel (Nov 29 1999). > ...... > HEEEEELP! Whats happening!!! :-( :-( :-( > > At the moment I am stymied. I switched to a GENERIC kernel and got the > same results, so it isn't anything weird that I have done in my own > kernel config. > > I was hoping that someone would have an idea. > > -Matt I also have one of those old Pentiums, with an Intel motherboard and a Mercury chipset. And I have similar problems with CURRENT of a few days ago. When I configure my kernel to use the new ata driver, it hangs when booting. I plan to reproduce this problem this weekend, with a more recent CURRENT. I think the problem is caused by the RZ1000 EIDE controller on this type of motherboard. I suspect that the new ata driver deals with interrupts in ways somewhat different from the old wd driver. According to the Intel documentation, interrupts during data transfers may cause data corruption. This RZ1000 issue has been discussed on this list a few weeks ago, without a real solution. Kind regards, Hans To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message