I believe this is related to the load, there are always calls in our test.
Attached is a part of /var/log/messages file with SysRq memory info - in
case you can see something in it. The box was rebooted 06-16 17:08 and
the problem occurred 06-17 11:36.
Thank you.
Alex Zarubin
-----Original Message-----
From: Mark Spencer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 17, 2003 6:58 AM
To: '[EMAIL PROTECTED]'
Subject: RE: [Asterisk-Users] Dual T400P, SMP, performance issues
> As far as SMP and single T400P - we'll try and report the results
> but the idea was to go with as high density as possible ...
Right, I'm just trying to narrow down the problem. I'm theorizing that
the problem is some sort of spinlock deadlock. Does it only occur if
there is activity or even if the lines are up but no calls taking place?
> What do you think of using hyperthreading - should we enable or disable it
> for the box running asterisk?
We use hyperthreading but have not run tests longer than a few hours on
those machines.
> What about -DCONFIG_ZAPTEL_WATCHDOG ? Can it help and how to use it?
k
Likely will make no difference in this situation.
Mark
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
mes_ast.gz
Description: Binary data
