From owner-freebsd-current@FreeBSD.ORG Wed Apr 14 14:49:45 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 DDAD116A4CE for ; Wed, 14 Apr 2004 14:49:45 -0700 (PDT) Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39C3143D1F for ; Wed, 14 Apr 2004 14:49:45 -0700 (PDT) (envelope-from ncbp@bank-pedersen.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1002) id 97C0E114E2; Wed, 14 Apr 2004 23:49:43 +0200 (CEST) Date: Wed, 14 Apr 2004 23:49:43 +0200 From: "Niels Chr. Bank-Pedersen" To: current@freebsd.org Message-ID: <20040414214943.GB37593@bank-pedersen.dk> Mail-Followup-To: "Niels Chr. Bank-Pedersen" , current@freebsd.org References: <20040414202654.503995D07@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040414202654.503995D07@ptavv.es.net> User-Agent: Mutt/1.4.2.1i X-PGP-Fingerprint: 18D0 73F3 767F 3A40 CEBA C595 4783 D7F5 5DD1 FB8C X-PGP-Public-Key: http://freesbee.wheel.dk/~ncbp/gpgkey.pub X-Mailman-Approved-At: Thu, 15 Apr 2004 05:13:22 -0700 Subject: Re: More odd behavior with the new PCI code (and, maybe, ata) 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: Wed, 14 Apr 2004 21:49:46 -0000 On Wed, Apr 14, 2004 at 01:26:54PM -0700, Kevin Oberman wrote: > I have noticed a very odd behavior since the new PCI code went into > CVS. I have virtually no real data on the problem and no idea if it's > really serious. It's only happened three time, always in single-user > mode. > > 1. boot -s > 2. to start sh > 3. fsck -p > 4. adjkerntz -i > 5. swapon -a > 6. mount -a -t ufs > 7. cd /usr/src > > These are the only things I am sure of as common. After this, an attempt > to run something will simply hang. In mergemaster I had it happen when I > tried to do an edit (e b) in a merge. Another time 'make installworld' > hung in 'mktemp'. Interrupting the operation (^C) and restarting does > not seem to help, but doing some other operation that accesses the disk > seems to clear the problem. (E.g. ls /usr/src). > > Once cleared, the problem never seems to recur. I have not seen it in > multi-user mode. I can't imagine what could be causing it, but loss of > interrupts from the ata MIGHT explain it. > > Any suggestions on where to look? Sounds like blocking on random(3). > /tmp is on real disk, not RAM. (I've seen reports of problems with > md's elsewhere.) > > This is probably not enough information to be useful, but I'll try to > collect more information when/if I see it again. I am hoping to find out > if it's just me or a more common issue. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. "Hey, are any of you guys out there actually *using* RFC 2549?"