From owner-freebsd-bugs@FreeBSD.ORG Tue Oct 13 10:00:29 2009 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17F581065672 for ; Tue, 13 Oct 2009 10:00:29 +0000 (UTC) (envelope-from maurovale@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id A3CB68FC23 for ; Tue, 13 Oct 2009 10:00:28 +0000 (UTC) Received: by fxm22 with SMTP id 22so8819226fxm.36 for ; Tue, 13 Oct 2009 03:00:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=53G69CUdy0/UF5ynkwE14dlv51aRhNAByksnnNwDdJ4=; b=lLHsU/pCkp2sBovmbVMtSF812OhcphXCtiBZ8qvBPVOy/e1rIPIxj2Xxm2aCOXxQgZ dx3EUqL57tDprj+SJR1aGcUoJEL0LhXlYFFy00mjZdxgbEpT7i1SU0vheAxA6gCcScyb 3chMUyAoy0PUTri6GS64lbsnAIK+e8iG1JIOU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=MREP+TO3bYz9QdiWBQaPMpY13G90mNV85c/AWYUGRenIBq6kg19czqCzkUZiJzCvIw jlFwqM9j51MfqB7Iai7AGKfOdDrTKh2H7bGBk8PTNeTT61vgSNvgW5qAurKC47jy9Nwy IG9p5buNjM7cl6iHsgz1f9kepmntmYsW+iypk= MIME-Version: 1.0 Received: by 10.204.15.22 with SMTP id i22mr6064720bka.13.1255426772577; Tue, 13 Oct 2009 02:39:32 -0700 (PDT) Date: Tue, 13 Oct 2009 10:39:32 +0100 Message-ID: <85d001330910130239qd31d558ve0bf0c1b08909e27@mail.gmail.com> From: "M. Vale" To: freebsd-bugs@FreeBSD.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Martin K Subject: misc/139247: hald uses nearly 100% of CPU on 8.0-rc1 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 10:00:29 -0000 HI I can also confirm this in 8.0 RC1 After some time hald uses nearly 100% of CPU, and then without anything to the logs or coredumps with hard locks the entire S.O. The only Solution is to make a hard reset.