From owner-freebsd-current Mon Jan 10 3:51:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from godfather.webvolution.net (unknown.cust-X.hecenter.com [208.231.0.74]) by hub.freebsd.org (Postfix) with ESMTP id 508FB1510D for ; Mon, 10 Jan 2000 03:50:14 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: (from nobody@localhost) by godfather.webvolution.net (13.5.3/13.5.3) id LAA35188; Mon, 10 Jan 2000 11:50:01 GMT (envelope-from jpedras@webvolution.net) Date: Mon, 10 Jan 2000 11:50:01 GMT Message-Id: <200001101150.LAA35188@godfather.webvolution.net> X-Authentication-Warning: godfather.webvolution.net: nobody set sender to jpedras@webvolution.net using -f From: Joao Pedras To: djb@Wit389306.student.utwente.nl Reply-To: Joao Pedras Cc: freebsd-current@freebsd.org References: <20000110025813.A353@relativity.student.utwente.nl> <20000110032017.A499@relativity.student.utwente.nl> In-Reply-To: <20000110032017.A499@relativity.student.utwente.nl> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP3 Imap webMail Program 2.0.11 X-Originating-IP: 193.137.208.1 Subject: Re: freezing... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello again No, my problem is not ahc related. This single processor system doesn't have any scsi It's a : PPro200/64MbRAM/8.4QuantumIDE/IntelVS440FX/Pioneer12x(which is not detected after upgraded to -CURRENT)/Digital 21240 (de0)/S3 Virge What I have in common with Christian is that it hangs during high usage, as I mentioned in my first post (e.g. compiling something, buildworld). I performed a buildworld this night with yesterday's code (in a common console) and it worked ok. I ONLY noticed this when having high CPU usage (e.g. compiling mysql port) when in using X. I am not saying this is X related. Common point here seems to be a busy system Joao Quoting "Dave J. Boers" : > On Mon, Jan 10, 2000 at 04:10:37AM +0100, Christian Carstensen wrote: > > this runs stable for 3 hours now... > > try a current kernel (checked out 4 hours ago), using a version of the > > file /usr/src/sys/pci/ahc_pci.c from 2000/01/06. ok, maybe it's not by > any > > means stable, but works better than everything else within the last 24 > > hours. > > Actually, I've booted a kernel from just before newyear (28 december) which > works _reasonably_ fine (although it's the same kernel that gave me the > lockup earlier) with a userland of today. > > Problem is that the lockups (I think) are ahc-related and my SCSI hard > drive did refuse to come online on one or two occasions while booting the > system cold... I therefore concluded that it might be a problem with the > hardware. Now (with the new kernel) I find the scsi system unstable and I > have doubts again. > > One piece of information might also be useful in this context. After the > system lockup I sort of benchmarked the scsi performance by doing "dd > if=/dev/zero of=./testfile bs=1000000 count=128" (actually I varied the > blocksize) and got a _very poor_ performance of only 4 Mb/sec (which is > usually around 10 to 12 Mb/sec). I isolated my drive to be the only scsi > device and I even clocked the SCSI bus down from 20 Mhz to 8 Mhz, but to no > avail. > > In the mean time, I disconnected my scsi hard drive and I am running from > my IDE disk. ------------------------------- Powered by Webvolution Networks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message