From owner-freebsd-stable@FreeBSD.ORG Thu Apr 8 07:24:48 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45C541065672; Thu, 8 Apr 2010 07:24:48 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4F3178FC13; Thu, 8 Apr 2010 07:24:46 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA18585; Thu, 08 Apr 2010 10:24:45 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Nzm6X-0000EW-3L; Thu, 08 Apr 2010 10:24:45 +0300 Message-ID: <4BBD84BC.1090302@icyb.net.ua> Date: Thu, 08 Apr 2010 10:24:44 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100321) MIME-Version: 1.0 To: Attilio Rao References: <20100408042958.21d99cea.akephalos.akephalos@gmail.com> <4BBD81B6.4000109@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Akephalos , freebsd-stable@freebsd.org, Ed Maste Subject: Re: CPU problems after 8.0-STABLE update X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2010 07:24:48 -0000 on 08/04/2010 10:22 Attilio Rao said the following: > 2010/4/8 Andriy Gapon : >> on 08/04/2010 04:29 Akephalos said the following: >>> Attilio, I csup-dated several hours ago and rebuilt and installed the kernel >>> (and world, in case it matters). >>> >>> %uname -a FreeBSD free.bsd369441.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Thu >>> Apr 8 03:01:13 EEST 2010 >>> root@free.bsd369441.org:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> The problem persists without the machdep trick, I see only one processor in >>> top with 0.0% CPU load. >>> >> Interesting, I couldn't see anything obviously wrong about your hardware. >> Could you please post a verbose dmesg from a problematic boot somewhere? >> Also, output of 'vmstat -i' and Interrupt request lines portion of 'devinfo -u' >> output. >> Thanks! > > I watched again the patch I committed to STABLE_8 and I can't find > anything wrong with it. > Also the fact that the setting machdep.lapic_all=1 fixes this means > that this may be an atrtc working problem. > Maybe new atom machine expose a problem with it? This doesn't look like an atom machine :-) A mobile AMD rather. > I'm thinking if we might switch this into an opt-in rather than an > opt-out feature. What's strange is that there is no diagnostics from RTC. -- Andriy Gapon