From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-142742-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	by finch.gentoo.org (Postfix) with ESMTP id 2A7021381F3
	for <garchives@archives.gentoo.org>; Mon, 19 Nov 2012 20:16:47 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 045B721C0A1;
	Mon, 19 Nov 2012 20:16:32 +0000 (UTC)
Received: from smarthost03.mail.zen.net.uk (smarthost03.mail.zen.net.uk [212.23.1.3])
	by pigeon.gentoo.org (Postfix) with ESMTP id 0084021C0A1
	for <gentoo-user@lists.gentoo.org>; Mon, 19 Nov 2012 20:15:28 +0000 (UTC)
Received: from [82.71.28.203] (helo=echoes)
	by smarthost03.mail.zen.net.uk with esmtp (Exim 4.72)
	(envelope-from <jdm@jdm.myzen.co.uk>)
	id 1TaXke-0004U9-6f
	for gentoo-user@lists.gentoo.org; Mon, 19 Nov 2012 20:15:28 +0000
Date: Mon, 19 Nov 2012 20:15:24 +0000
From: john <jdm@jdm.myzen.co.uk>
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Boot and udev Woes
Message-ID: <20121119201524.066ea245@echoes>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.12; x86_64-pc-linux-gnu)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Originating-Smarthost03-IP: [82.71.28.203]
X-Archives-Salt: f060133f-d8f5-4360-b186-615e47cd2831
X-Archives-Hash: edf770f8e8a74d51eb9201991eee71fc

Hi Gentoo.

I have recently got a FX8350 and all is going very well.
After a week of using I have had no issues and then realised I had not
set man number of cpus in kernel config. 

This was set to 6. So as FX8350 is an eight core beast. I decided to
set to 8.

Upon reboot the boot hangs at 

waiting for uevents to be processed.

This hangs for 60 seconds and then starts spitting out the following

timeout killing /sbin/modprobe -bv xcpu_vendor 0002 + lots of 4 long
numbers. Sorry, I cannot trap these as they fly by.

in a continous loop. 

Reset required.

Booting from old kernel is still ok (6 cores set).

Looking in /proc/cpuinfo there are only 6 cores.

I can boot ok from Windows which shows 8 cores and I have also updated
BIOS to latest version.

Any ideas

Is there any way to detect or test that I using 8 cores?

-- 
John D Maunder