Bug 146764

Summary:	gentoo-sources-2.6.17-r7 - only once CPU found on a Pentium IV HT
Product:	Gentoo Linux	Reporter:	Christopher Head <bugs>
Component:	[OLD] Core system	Assignee:	Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status:	VERIFIED INVALID
Severity:	normal
Priority:	High
Version:	2006.0
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	Output of dmesg Kernel config Dmesg with both procs working

Description Christopher Head 2006-09-07 17:18:56 UTC

I'm running gentoo-sources-2.6.17-r7 on a Pentium IV HT. Sometimes (quite often) at bootup, only CPU0 is started. Sometimes rebooting will solve the problem, sometimes not. The problem seems (subjectively) to be worse since installing -r7 than it was with -r4.

Comment 1 Christopher Head 2006-09-07 17:19:34 UTC

Created attachment 96354 [details]
Output of dmesg

Comment 2 Christopher Head 2006-09-07 17:20:04 UTC

Created attachment 96355 [details]
Kernel config

Comment 3 Daniel Drake (RETIRED) gentoo-dev

2006-09-16 20:24:01 UTC

Please post dmesg output from a boot where both CPU's are working

Comment 4 Christopher Head 2006-09-17 12:21:48 UTC

Created attachment 97272 [details]
Dmesg with both procs working

This a full dmesg log during a session with both processors working. I've added radeonfb to my kernel which wasn't in the other dmesg log (but this shouldn't matter). I haven't actually seen the problem again since adding radeonfb, but I've only booted a few times since then. I don't think there have been any other changes.

Comment 5 Daniel Drake (RETIRED) gentoo-dev

2006-10-23 17:12:02 UTC

Has this problem reappeared? You could try upgrading your BIOS to the latest version and booting with acpi=off

Comment 6 Daniel Drake (RETIRED) gentoo-dev

2006-10-23 17:13:38 UTC

Reproducing on the latest development kernel (currently 2.6.19-rc3) would also be wise

Comment 7 Christopher Head 2006-10-23 21:55:22 UTC

I've found a BIOS update. The problem hasn't appeared in a few boots, so it may be fixed now. I'll reopen the bug if it comes back. Thanks for your help and time.