From owner-freebsd-stable@FreeBSD.ORG Sun Dec 28 17:59:40 2014 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED622129 for ; Sun, 28 Dec 2014 17:59:40 +0000 (UTC) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B19E566631 for ; Sun, 28 Dec 2014 17:59:40 +0000 (UTC) Received: by mail-ig0-f178.google.com with SMTP id hl2so10550048igb.17 for ; Sun, 28 Dec 2014 09:59:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=XS2mEcBMLc8Bz8NB2TxK5TRGHGgfZraPSPiQNSSf9rA=; b=nX6VdYAy86KmfFuzCM7WMGsPSc8dW+P6TDmSB4u9N4EML6YZkZ/DHdYke+m0S0L0O6 cXJtIvLvQxpjb7J2PymDJLoQ82CwaDlpnEP0n90vBrDZYmyvREQslarcU6Xdssgl3Ldi uwUOCOHgMDSf3nsM/zblRqc0Tv+3pHH8SC2zLvOAGjvEO+OKhM0amkjk5f5wV6DS+FpC rytIpbx5l4Uk4HRg9EcJgaU4FtRcik+S+FHLHqltf8FVuhtQ8ihM7CXjHqut3ErTKmL/ BNqvXhqz9egUCMNC+NK1TNAvAJak+8EmUvyVLB6yWS9w28SHiCixyuNm57ocBicrWHvb oANg== MIME-Version: 1.0 X-Received: by 10.51.17.11 with SMTP id ga11mr42140758igd.0.1419789579963; Sun, 28 Dec 2014 09:59:39 -0800 (PST) Sender: kob6558@gmail.com Received: by 10.107.52.19 with HTTP; Sun, 28 Dec 2014 09:59:39 -0800 (PST) In-Reply-To: <54A00A7A.2000100@gibfest.dk> References: <54A00A7A.2000100@gibfest.dk> Date: Sun, 28 Dec 2014 09:59:39 -0800 X-Google-Sender-Auth: 7XbG3R9skzUfwSSTqfR1Ar8DMUQ Message-ID: Subject: Re: "random" hangs during boot, ACPI related ? Workaround problem by disabling HTT From: Kevin Oberman To: Thomas Steen Rasmussen Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Stable ML X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Dec 2014 17:59:41 -0000 On Sun, Dec 28, 2014 at 5:49 AM, Thomas Steen Rasmussen wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello list, > > I've had a problem a couple of times now that I wanted to share with > the list to see what you have to say. The problem is that FreeBSD > sometimes hangs during boot, the last line of output from the kernel > is "ACPI APIC Table: " and then nothing more happens. > > This seems to be related to something not getting initialized correctly > after a soft reboot, but only sometimes. The first time I tried this it > was on > a server that has been in production for months, and suddently after a > reboot during an installworld run it froze. Even a verbose boot doesn't > reveal anything that jumps at me: http://i.imgur.com/y04ACyP.png > > Hard rebooting the server appears to solve it, until next reboot where > it may or may not happen again. > > The same problem seems to affect others. This is the thread where I > found suggestions for workarounds: https://bugs.pcbsd.org/issues/4024 > > Workarounds include disabling C3 or disabling HTT in bios. Disabling C3 > did nothing for me, but disabling HTT made the server boot successfully > again. > > The FreeBSD versions involved are 9 and 10, various versions. I've > attached /var/run/dmesg.boot from one of the servers that had the > problem a few weeks ago. On this server I've disabled HTT in the bios > which worked around the problem. > > I just bought a new server at Hetzner (the hosting provider where I am > experienzing this problem) and the server is not in production yet. I > wanted to hold off on disabling HTT to see if anyone wants me to > check something so we can get this fixed. > > Thoughts ? More info available on request. > > > Best regards, > > /Thomas Steen Rasmussen > I know that C3 (and higher) and TCC don't get along on some platforms. I thought that throttling was now off by default, but I'm not sure as I have it disabled in /boot/loader.conf: # Disable CPU throttling hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 This will not show up until ACPI and EST come up, so it sort of fits. Whether it causes a lockup or not, disabling it is a good idea. It was intended for use as thermal management, not power management. (The 'T' in TCC (or P4TCC) is "Thermal", after all.) -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com