From owner-freebsd-current@FreeBSD.ORG Thu May 8 10:53:52 2003 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 45C0937B401 for ; Thu, 8 May 2003 10:53:52 -0700 (PDT) Received: from bragi.housing.ufl.edu (bragi.housing.ufl.edu [128.227.47.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91B7A43F93 for ; Thu, 8 May 2003 10:53:51 -0700 (PDT) (envelope-from WillS@housing.ufl.edu) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Date: Thu, 8 May 2003 13:53:49 -0400 Message-ID: <0E972CEE334BFE4291CD07E056C76ED8CBBC51@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: hard lockups Thread-Index: AcMVisE8h+Fqo/fZSqurBwLgUTTBhA== From: "Will Saxon" To: Subject: hard lockups 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: Thu, 08 May 2003 17:53:52 -0000 Has anyone been experiencing non-panic hard freezes lately? I just = started running -current a couple of weeks ago, before that I had = 5.0-RELEASE without seeing any problems. Occasionally, I will just have a machine lockup, no panics, nothing. The = machine is unresponsive to the network also. Usually, there is some sort of disk activity - I have seen the lockup 3 = or 4 times trying to compile/install things, and 2x today, once = compiling a new kernel, the other while redirecting output from a job to = a text file. Today's lockups were using a May 6 kernel, SMP, none of the debugging = options, SCHED_ULE, LAZY_SWITCH, ADAPTIVE_MUTEXES, and = ZERO_COPY_SOCKETS. I have since recompiled to include all the debugging = options, but the only thing that has shown up is a lock order reversal = in the sound code. This machine is a dual celeron and uses ata drives. DMA is turned on. = Ethernet is via a 3c905B controller. The one hard drive is using the = onboard HPT366 controller, not the PIIX one. I'm not sure what else to include. I am always suspicious of hard = lockups, it is difficult to pinpoint what causes them since there is no = log entry to read. It could easily be a hardware issue, but since I = hadn't had problems before -current I thought I would write in. -Will