-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Watts wrote:
>
>
>>Viestissä Tiistai 3. Kesäkuuta 2003 19:11, Jan Ciger kirjoitti:
>>
>>>On Tuesday 03 June 2003 15:57, Mark Watts wrote:
>>>
>>>>Two questions:
>>>>
>>>>1) Does any Mandrake kernel support Hyperthreading Xeons?
>>>
>>>Cooker and 9.1 do - at least my dual Xeon thinks so :-) It works fine,
>>>without any problems, it looks as if I had 4 CPUs instead of just two -
>>>just as any other SMP setup.
>>>
>>>
>>>>b) Is there a fix for the IRQ Routing issues with 2.4.x on SMP boxes?
>>>
>>>No idea, but would be nice though
>>>
>>>Jan
>>
>>AFAIK it was fixed in  16mdk ...
>>
>>Thomas
>
>
> Interesting - I compiled 2.4.21-1rc1.1 today and neither irq routing or
> hyperthreading were working.
>
> 2.4.21-rc6-ac2 fixed the irq issue but I still don't get hyperthreading.
>
> I'm beginning to think its an issue with the ServerWorks chipset I'm
running.

Hmmm, we just got a Dell 1600SC with single 2GHz Xeon HT, and it shows
only one CPU (in /proc/cpuinfo) when booted on the current updated smp
kernel. Should /proc/cpuinfo show twice the number of instlled
processors if HT works?

Mark, did you resolve this?

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+82jhrJK6UGDSBKcRAgPvAJ9WbzBzPT7EnGwOh4ZVndLykrp8lACgrwbv
tIxRzJTdRl+cDzkOd8MSxCM=
=JhKy
-----END PGP SIGNATURE-----

******************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
******************************************************************

Reply via email to