Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Chase Venters
> Complete 'dmesg' please. See below. Thanks, Chase Linux version 2.6.13 ([EMAIL PROTECTED]) (gcc version 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) #2 SMP Sun Aug 28 23:54:34 CDT 2005 BIOS-provided physical RAM map: BIOS-e820: - 000

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Mws
Pallipadi, Venkatesh wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chase Venters Sent: Monday, August 29, 2005 9:04 PM To: linux-kernel@vger.kernel.org Subject: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13 Gree

RE: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Pallipadi, Venkatesh
>-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Chase Venters >Sent: Monday, August 29, 2005 9:04 PM >To: linux-kernel@vger.kernel.org >Subject: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13 > >G

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Ralf Hildebrandt
* Ralf Hildebrandt <[EMAIL PROTECTED]>: > * Chase Venters <[EMAIL PROTECTED]>: > > > > CONFIG_MPENTIUM4, CONFIG_SMP and CONFIG_SCHED_SMT enabled? > > > > Yes in all three regards. > > Same here. Dual-Xeon 2.8Ghz, only 2 CPUs are being displayed. After activating ACPI and power Management, HT wo

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Ralf Hildebrandt
* Chase Venters <[EMAIL PROTECTED]>: > > CONFIG_MPENTIUM4, CONFIG_SMP and CONFIG_SCHED_SMT enabled? > > Yes in all three regards. Same here. Dual-Xeon 2.8Ghz, only 2 CPUs are being displayed. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin Ber

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Chase Venters
> I needed CONFIG_PM=y and CONFIG_ACPI=y to get ht working on 2.6.13. CONFIG_ACPI and CONFIG_PM are enabled here. Thanks, Chase Venters - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kerne

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Chase Venters
On Tuesday 30 August 2005 07:06 am, you wrote: > On 8/30/05, Chase Venters <[EMAIL PROTECTED]> wrote: > > Greetings kind hackers... > > I recently switched to 2.6.13 on my desktop. I noticed that the > > second "CPU" (is there a better term to use in this HyperThreading > > scenario?) that

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread linux-os \(Dick Johnson\)
On Tue, 30 Aug 2005, Jesper Juhl wrote: > On 8/30/05, Chase Venters <[EMAIL PROTECTED]> wrote: >> Greetings kind hackers... >> I recently switched to 2.6.13 on my desktop. I noticed that the >> second >> "CPU" (is there a better term to use in this HyperThreading scenario?) that >> used

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Philippe Elie
On Mon, 29 Aug 2005 at 23:03 +, Chase Venters wrote: > Greetings kind hackers... > I recently switched to 2.6.13 on my desktop. I noticed that the second > "CPU" (is there a better term to use in this HyperThreading scenario?) that > used to be listed in /proc/cpuinfo is no longer pres

Re: Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-30 Thread Jesper Juhl
On 8/30/05, Chase Venters <[EMAIL PROTECTED]> wrote: > Greetings kind hackers... > I recently switched to 2.6.13 on my desktop. I noticed that the second > "CPU" (is there a better term to use in this HyperThreading scenario?) that > used to be listed in /proc/cpuinfo is no longer present.

Second "CPU" of 1-core HyperThreading CPU not found in 2.6.13

2005-08-29 Thread Chase Venters
Greetings kind hackers... I recently switched to 2.6.13 on my desktop. I noticed that the second "CPU" (is there a better term to use in this HyperThreading scenario?) that used to be listed in /proc/cpuinfo is no longer present. Browsing over the archives, it appears as if someone else