Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!xlink.net!math.fu-berlin.de!uniol!news.fh-lippe.de!bi-link.owl.de!martin From: martin@bi-link.owl.de (Martin Husemann) Subject: Re: sd0 timeout problems!!! References: <27sf7u$mru@genesis.ait.psu.edu> Organization: IN - individual network, Ostwestfalen-Lippe, FRG Date: Fri, 24 Sep 1993 06:34:50 GMT Message-ID: <CDuIA2.L3@bi-link.owl.de> Lines: 30 D. Jay Newman <dn5@psu.edu> writes: >I am new to NetBSD, and I installed it on my machine last night using >the kc-ahbbt-09p1.fs floppy downloaded from sun-lamp. >During ftp, I started getting "ahb0 targ 0: device timeout" errors, then >frantic synching behavior, then a reboot into unix. I'm very glad to here that - I already thaught I would be the only one with that kind of problems. There is an easy workaround: set your Adaptec to "Standard mode" and use the aha kernel :-( I have NetBSD running in all versions since 0.8 and this happens every time in any version whenever I switch to the 1742 driver. Chris Demetriou assured me he has several machines running this driver without any problems. Mine won't run. Needless to say it works fine with DOS. With NetBSD running at a certain load with lots of writes (e.g. a kernel build or make in /usr/src) it will get a timeout within a few minutes and scramble my disk. There were rumours on the net about a broken DMA chip in most new SIS mainboards. I happen to use such a board and haven't got hold of a non-SIS one to verify this yet. Martin -- "And I think infinity is a little beyond me" Larry Wall