From owner-freebsd-current@FreeBSD.ORG Sun Feb 15 22:26:44 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 479F016A4CE; Sun, 15 Feb 2004 22:26:44 -0800 (PST) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 018D243D1D; Sun, 15 Feb 2004 22:26:44 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i1G6QhHQ000555; Mon, 16 Feb 2004 01:26:43 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040216055840.GA72555@xor.obsecurity.org> References: <20040216055840.GA72555@xor.obsecurity.org> Date: Mon, 16 Feb 2004 01:26:42 -0500 To: Kris Kennaway , alpha@freebsd.org, current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Scheduling deadlock on alpha? 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, 16 Feb 2004 06:26:44 -0000 At 9:58 PM -0800 2/15/04, Kris Kennaway wrote: >One of the alpha package machines seems to have deadlocked; no >processes are running, but the kernel itself responds to pings, >and I can break to DDB: ...etc... > >WITNESS was not enabled, and the machines are running > >FreeBSD axp1.FreeBSD.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan >21 13:30:26 PST 2004 >kris@bento.FreeBSD.org:/local0/obj/alpha/a/asami/portbuild/alpha/src-client/sys/NETBOOT >alpha > >Scheduler is 4BSD. Hmm. Interesting. UP or SMP? As an interesting coincidence, I had my dual-Athlon machine lock up on me at about 5am on Sunday. I didn't realize it was down until I needed to use that machine for something, so I just rebooted the machine without doing much investigation. I had to turn the machine off and back on to get it's attention (ctrl-alt- delete was ignored). WITNESS is not enabled, and the machine is running: FreeBSD santropez.netel.rpi.edu 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Jan 21 23:28:30 EST 2004 root@santropez.netel.rpi.edu:/usr/obj/usr/src/sys/Dual-Athlon2k i386 The machine had run continuously from the time I did that last installworld/installkernel, without any reboots. It was running some Folding@Home clients, so it would have racked up a lot of CPU time. Other than those clients, it should have been pretty idle for a few hours before it hung up. It NFS-exports some directories to another system, but that other system did not have the directories mounted at the time of the crash. I really doubt it's related, but it is interesting that both machines happen to have kernels from the same day... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu