From owner-freebsd-current Tue Feb 22 7:15:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id E241837B68C for ; Tue, 22 Feb 2000 07:15:24 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by picalon.gun.de (8.9.3/8.9.3) id QAA05711; Tue, 22 Feb 2000 16:15:13 +0100 (MET) >Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id QAA03433; Tue, 22 Feb 2000 16:04:56 +0100 (CET) (envelope-from andreas) Date: Tue, 22 Feb 2000 16:04:56 +0100 From: Andreas Klemm To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: timeout problems HighPoint HPT366 ATA66 controller && 40 GB Diamond Max Plus Message-ID: <20000222160456.A3127@titan.klemm.gtn.com> References: <20000222131429.A870@titan.klemm.gtn.com> <200002221239.NAA34644@freebsd.dk> Mime-Version: 1.0 X-Mailer: Mutt 1.0.1i In-Reply-To: <200002221239.NAA34644@freebsd.dk>; from sos@freebsd.dk on Tue, Feb 22, 2000 at 01:39:46PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 22, 2000 at 01:39:46PM +0100, Soren Schmidt wrote: > Hmm, this looks very wierd, Oh yes ;-) BTW no problem with win98 or Win2000 installation. > how is your BIOS setup wrt to onboard ATA channels ?? > Try to use a "normal" ie 40pin cable, that will limit the disk to > UDMA33 mode, if that works, well... Will have to buy that. When I ran with the on board IDE chip I had a drive mode (something like) mdma2. That worked even with FreeBSD. I now tried BIOS setup values. First entered BIOS default values, which are turning off most features, then I enabled SETUP defaults and then changed no performance boosting things. RAM Timing I changed to automatic 70ns, although I have 60 ns RAM. On chip PCI IDE is completely disabled. Then I changed as a last resort method the mode to hw.atamodes: ---,---,---,---,pio,---,---,---, Even with PIO the drive has problems, but is then able to recover: ata2-master: success setting up PIO4 mode on HPT366 chip ad4: invalid primary partition table: no magic this is. because I newfs'd ad4c on the whole ... quick and dirty for testing... now bonnie -s 100 ad4: WRITE command timeout - resetting ata2: resetting devices .. ata2: mask=01 status0=50 status1=00 ata2-master: success setting up PIO4 mode on HPT366 chip done ad4: timeout waiting for DRQ How can I force the driver with kernel modifications to use mdma2 mode or something like this ??? BTW, I have a 5 Slot PCI machine ... in the first slot there is the abit controller in the last the Matrox Millenium card. They share the same IRQ 15... Is this sane ? Or might my problem be SMP related ??? Well, have to go to the supermarket now ... I'll remove one card later, to free one IRQ and will try to use a single cpu kernel... -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message