Hi,
> -Original Message-
> I get seg. fault with my * box. at the crash time i had about 35
> Bridged Channel.
> i have:
> - dual xeon box (3.2Ghz)
> - 2Gb of memory
> - E7501 chipset motherboard.
> - U320 scsi disks
> - intel Gb ethernet device.
> - i only use sip for clients (no fxs in
I'm using FC2. but with a fresh 2.6.9 kernel downloaded from kernel.org.
I've recently upgraded my Glibc to glibc-2.3.3-27.1.
I'm also using ECC Reg Memory.
and this is my Xeon CPU info: (HyperThreading is ON)
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model :
[EMAIL PROTECTED] wrote:
> - dual xeon box (3.2Ghz)
> - 2Gb of memory
> - E7501 chipset motherboard.
> - U320 scsi disks
> - intel Gb ethernet device.
> - i only use sip for clients (no fxs in box)
> - TE405P for fxo (with 4 atran TA750).
> - ulaw is used as codec and echo cancellationo is enabled
I got another crash... the core dumped file shows that the
crash has been occurred at the same point as the previous crash.
Program terminated with signal 11, Segmentation fault.
#0 0xb7fbbce4 in ?? ()
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
> I have seen lots of this kind of problems before. We
> had lots of stability problems with GNUgk on Debian
> Woody.
is there any relation between * and GNUgk?
thanks
Paradise Dove
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium
> Hmm without knowing anything else about your specific situation: A signal 11
> most often is caused by a hardware malfunction, for instance a rotten bit in
> your memory or something.Any chance you could do some heavy diagnostics on
> that machine ?
I've just seen a new update of my M.B. Bios,
d