From owner-freebsd-stable@FreeBSD.ORG Thu Mar 11 17:26:12 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 AACC5106564A; Thu, 11 Mar 2010 17:26:12 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop1.sarenet.es (proxypop1.sarenet.es [194.30.0.99]) by mx1.freebsd.org (Postfix) with ESMTP id 5EE118FC0C; Thu, 11 Mar 2010 17:26:11 +0000 (UTC) Received: from [172.16.1.204] (unknown [192.148.167.2]) by proxypop1.sarenet.es (Postfix) with ESMTP id 8EAA06158; Thu, 11 Mar 2010 18:26:10 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20100311150822.107231cvjvgs9gsg@webmail.leidinger.net> Date: Thu, 11 Mar 2010 18:26:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <35ADB9B1-F571-4EE4-9089-5363ACEBE159@sarenet.es> References: <864468D4-DCE9-493B-9280-00E5FAB2A05C@lassitu.de> <20100309122954.GE3155@garage.freebsd.pl> <20100309125815.GF3155@garage.freebsd.pl> <20100310110202.GA1715@garage.freebsd.pl> <20100310173143.GD1715@garage.freebsd.pl> <20100311084527.2934034895hvgxaw@webmail.leidinger.net> <764BD545-B86C-47DC-9004-964EB2216AF0@sarenet.es> <20100311150822.107231cvjvgs9gsg@webmail.leidinger.net> To: Alexander Leidinger X-Mailer: Apple Mail (2.1077) Cc: freebsd-fs@FreeBSD.org, Pawel Jakub Dawidek , FreeBSD@FreeBSD.org, Stable Subject: Re: Many processes stuck in zfs 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, 11 Mar 2010 17:26:12 -0000 On Mar 11, 2010, at 3:08 PM, Alexander Leidinger wrote: >>> Borja, can you confirm that the CPU is correctly announced in = FreeBSD (just look at "dmesg | grep CPU:" output, if it tells you it is = a AMD or Intel XXX CPU it is correctly detected by the BIOS)? >>=20 >> A CPU bug? Weird. Very. >=20 > It depends. CPUs have bugs. You do not want to run any modern CPU = without an microcode update. The BIOS is doing it for you at system = start. >=20 > I do not want to say that this is the problem you have, I just want to = point out that it may be possible (but see below). I got hit by this = last december and I was finding the solution (replacing the complete = system, as only replacing the CPU was not an option) in January. Of course CPUs have bugs, I don't doubt it. I was just wondering how I = coud reproduce the problem with a different hardware :) That's why I = said it was unlikely. Besides, such a low level fault should produce many more problems than = such a well defined failure mode, as far as I know. >> As the servers had to be rolled into production, and such tests with = real servers can be quite time consuming, I set up a couple of FreeBSD = virtual machines, using VMWare Fusion (version 2 then, now version 3) on = a Macbook (Macbook 4,1 Intel Core2Duo, 2.1 GHz) and tried to reproduce = it. >=20 >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (2496.25-MHz = K8-class CPU) >> Origin =3D "GenuineIntel" Id =3D 0x1067a Stepping =3D 10 >=20 >> The virtual machine (VMWare Fusion 3.0.0, Macbook, Mac OS X 10.6.2) = reports this: >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz (2116.62-MHz = K8-class CPU) >> Origin =3D "GenuineIntel" Id =3D 0x10676 Stepping =3D 6 >=20 > Summary: you confirmed the problem on a different kind of CPU. >=20 > Because of this it makes it even more unlikely that it is a CPU = problem. Indeed :) Borja. >=20 > Bye, > Alexander. >=20 > --=20 > A good plan today is better than a perfect plan tomorrow. > -- Patton >=20 > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D = B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D = 72077137