Just noticed one more thing... it appears to be Apache causing the super
high load (among other programs running) when SMP is compiled into the
kernel, and with a bunch of errors in syslog:

[Wed Dec 17 02:27:37 2003] [notice] child pid xxxxxx exit signal
Segmentation fault (11)

(and a whole bunch of these errors, like 50 lines)

I did a search and someone said it has to do with Apache requesting memory
that it doesn't own or something:
http://lists.debian.org/debian-apache/2002/debian-apache-200207/msg00005.html

but that doesn't really help in this case, unless you guys can think of a
different angle on this?


----- Original Message ----- 
From: "Jason Lim" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 16, 2003 11:23 PM
Subject: Intel Hyperthreading problem on server?


> Hi All...
>
> Do you guys know anything about a problem with Intel Hyperthreading (eg.
> on the Intel 2.4Ghz HT-enabled processor) that would cause the load
> average to jump to over 200?
>
> Here is the log line:
>
> Dec 16 22:48:17 be watchdog[250]: loadavg 203 101 40 is higher than the
> given threshold 200 150 100!
>
> (then it reboots)
>
> This happened on the 2.4.22 kernel, and now I tried it with the 2.4.23
> kernel, and it has the same problem.
>
> When the kernel is compiled WITHOUT SMP support, the kernel works fine,
> and it can have uptimes of months without any problem. But when SMP is
> compiled in, and the HT processor is correctly identified (and top can
see
> CPU0 and CPU1), then it only takes about an hour or two of operation
> before the load average jumps like that. Note that this is with Debian
> woody/stable, and with a clean kernel.org kernel.
>
> Do you guys know anything about this, or have any ideas where I should
> look? Is there something in Woody that isn't friendly with SMP or
perhaps
> HyperThreading processors?
>
> Thanks in advance.
>
> Sincerely,
> Jas
>
>
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to