From owner-freebsd-stable@FreeBSD.ORG Mon Jul 12 15:40:38 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 CC5A61065670 for ; Mon, 12 Jul 2010 15:40:38 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [76.96.59.227]) by mx1.freebsd.org (Postfix) with ESMTP id 76F8B8FC13 for ; Mon, 12 Jul 2010 15:40:38 +0000 (UTC) Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta12.westchester.pa.mail.comcast.net with comcast id h0i61e00816LCl05C3gewG; Mon, 12 Jul 2010 15:40:38 +0000 Received: from koitsu.dyndns.org ([98.248.41.155]) by omta06.westchester.pa.mail.comcast.net with comcast id h3gd1e00G3LrwQ23S3geJ0; Mon, 12 Jul 2010 15:40:38 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 39C239B425; Mon, 12 Jul 2010 08:40:36 -0700 (PDT) Date: Mon, 12 Jul 2010 08:40:36 -0700 From: Jeremy Chadwick To: Markus Gebert Message-ID: <20100712154036.GA13481@icarus.home.lan> References: <6B57591F-9FA2-45EB-825F-1DB025C0635D@hostpoint.ch> <201007120851.35529.jhb@freebsd.org> <0CF6CF2B-907C-42EF-B57E-DF50F0564455@hostpoint.ch> <201007121106.59454.jhb@freebsd.org> <4615FFAA-F78B-475E-B40B-CC33791F1D23@hostpoint.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4615FFAA-F78B-475E-B40B-CC33791F1D23@hostpoint.ch> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-stable , John Baldwin Subject: Re: 8.1-RC2 - PCI fatal error or MCE triggered by USB/ehci on Sun X4100M2? 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: Mon, 12 Jul 2010 15:40:38 -0000 On Mon, Jul 12, 2010 at 05:23:23PM +0200, Markus Gebert wrote: > > On 12.07.2010, at 17:06, John Baldwin wrote: > > > Are you using Cx states other than C1 for the CPUs at all? > > Not sure how to find out, but I did not change anything in the BIOS settings (if even possible) or through sysctl regarding cpu idle modes. Anyway, here's what I found: > > # sysctl machdep.idle machdep.idle_available > machdep.idle: amdc1e > machdep.idle_available: spin, amdc1e, hlt, acpi, > > Not sure if "amdc1e" qualifies for something "other than C1". I tried "hlt" once, which didn't make a difference IIRC. And if that's not what you needed, here's more: > > # sysctl dev.cpu > [...] > dev.cpu.0.freq_levels: 2786/95000 2587/81800 2388/69811 2189/58977 1990/49240 1791/44316 995/22525 > dev.cpu.0.cx_supported: C1/0 > dev.cpu.0.cx_lowest: C1 > [...] cx_supported indicates your CPU only supports C1 and not lower power-saving states (C2/C3/C4, etc.). Non-C1 states can sometimes do "interesting" things when it comes to interrupt handling. I believe your system may support the C1E state (given what machdep.idle_available shows), but that's often controlled by the system BIOS (on both Intel and AMD processors, but I'm trying to focus on AMD here). C1E, as far as I know, is the same as C1 state except can save a little bit more power. I believe neither C1 nor C1E do anything with interrupts, instead just halting the core when idle/not in use. HLT mode, at least on multi-core AMD CPUs, equates to C1E. Shot in the dark: you're not running powerd(8) on this system are you? -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |