From owner-freebsd-current@FreeBSD.ORG Mon Sep 20 16:00:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 045B116A4D2; Mon, 20 Sep 2004 16:00:51 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7402243D75; Mon, 20 Sep 2004 16:00:20 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.12.10) with ESMTP id i8KG0J90003546; Mon, 20 Sep 2004 12:00:20 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.12.10/Submit) id i8KG0Jgx003545; Mon, 20 Sep 2004 12:00:19 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Mon, 20 Sep 2004 12:00:19 -0400 From: David Schultz To: Nik Clayton Message-ID: <20040920160019.GA3403@VARK.MIT.EDU> Mail-Followup-To: Nik Clayton , current@FreeBSD.ORG References: <20040920100038.GA30307@clan.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040920100038.GA30307@clan.nothing-going-on.org> cc: current@FreeBSD.ORG Subject: Re: Brief freezes with -current as of early last week X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Sep 2004 16:00:51 -0000 On Mon, Sep 20, 2004, Nik Clayton wrote: > After updating from -current built on 2004/04/27 to -current built on > 2004/09/13, I'm seeing some annoying 'freezes'. I'd not seen these with > the earlier -current. > > To complicate matters, right around the time I did the update I also > switched from a configuration with two SCSI disks and an IDE disk, to a > configuration with two IDE disks (each SCSI disk, bought at the same > time, from the same supplier, died within 4 days of each other -- > sheesh). > > So, I guess what I might be seeing is plain old I/O contention -- > although I'm surprised that it freezes the box. According to > 'atacontrol mode 0', both IDE devices are using UDMA100, which is the > maximum the motherboard (dual 1GHz PIII) supports). > > The symptoms typically manifest themselves right after kicking off a > portupgrade command. The system will (sort-of) freeze. If I'm in X, > the mouse cursor stops responding, there's no response to the keyboard. > However, if I happen to have top(1) running in an xterm, the top(1) > display keeps updating. This lasts (wall-clock) 10 to 15 seconds, and > then the system becomes responsive again. This sounds like an I/O hang. I've been having similar problems related to WRITE_DMA and READ_DMA timeouts from the ata driver in the last week or so, as discussed last week on this list. Are you seeing these messages from the kernel? Julian suggested disabling preemption, which I haven't tried yet, but other people report limited success.