Re: [Asterisk-Users] Strange Crash

2005-01-31 Thread timebandit001
> memtest86 is a nice tool and if you go to their site(http://memtest86.com),
> they have an ISO bootable image there also.
Knoppix also can be used to test memory

On the boot prompt just type "memtest" and it will start the test

HTH
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Strange Crash

2005-01-31 Thread Lyle Giese
memtest86 is a nice tool and if you go to their site(http://memtest86.com),
they have an ISO bootable image there also.

Lyle
- Original Message -
From: "Adam Goryachev" <[EMAIL PROTECTED]>
To: "Asterisk Users Mailing List - Non-Commercial Discussion"

Sent: Monday, January 31, 2005 4:26 AM
Subject: Re: [Asterisk-Users] Strange Crash


> On Sun, 2005-01-30 at 03:11 -0600, Steven Critchfield wrote:
> > On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> > > hi,
> > >
> > > just got an strange crash, and don't know what could cause this type
of crashs
> > > - hardware failure
> > > - memory
> > > - cpu
> > > ?
> > > i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no
patch).
> > > * version is latest CVS HEAD.
> > >
> > > thanks
> > >
> > > Program terminated with signal 11, Segmentation fault.
> > > Cannot access memory at address 0xb80014bc
> >
> > Seg faults can be faulty memory, overheated CPU, but usually it is an
> > error in programming.
> >
> > > #0  0xb7fbbce4 in ?? ()
> > >
> > > (gdb) bt
> > > #0  0xb7fbbce4 in ?? ()
> > > #1  0x080d425d in _IO_stdin_used ()
> > > #2  0x in ?? ()
> >
> > Next time provide the asterisk binary along with the core file to gdb so
> > you can get symbol names and line numbers.
> >
>
> I always though sig11 was a memory error... eg, faulty memory. At least,
> when compiling on a machine with bad memory, I always got sig11's in
> different/random places sometimes it would compile, and then crash
> later too :)
>
> I'd suggest you try and get around an hour to boot memtest, and see how
> it goes. (From another thread, this is one very nice reason to have a
> gentoo CD, it comes with bootable memtest. I wish debian would do that
> too)...
>
> Regards,
> Adam
>
> --
>  --
> Adam Goryachev
> Website Managers
> Ph:  +61 2 8304 [EMAIL PROTECTED]
> Fax: +61 2 9345 4396www.websitemanagers.com.au
>
> ___
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>http://lists.digium.com/mailman/listinfo/asterisk-users
>

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Strange Crash

2005-01-31 Thread Adam Goryachev
On Sun, 2005-01-30 at 03:11 -0600, Steven Critchfield wrote:
> On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> > hi,
> > 
> > just got an strange crash, and don't know what could cause this type of 
> > crashs
> > - hardware failure
> > - memory 
> > - cpu
> > ?
> > i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no patch).
> > * version is latest CVS HEAD.
> > 
> > thanks
> > 
> > Program terminated with signal 11, Segmentation fault.
> > Cannot access memory at address 0xb80014bc
> 
> Seg faults can be faulty memory, overheated CPU, but usually it is an
> error in programming. 
> 
> > #0  0xb7fbbce4 in ?? ()
> > 
> > (gdb) bt
> > #0  0xb7fbbce4 in ?? ()
> > #1  0x080d425d in _IO_stdin_used ()
> > #2  0x in ?? ()
> 
> Next time provide the asterisk binary along with the core file to gdb so
> you can get symbol names and line numbers. 
> 

I always though sig11 was a memory error... eg, faulty memory. At least,
when compiling on a machine with bad memory, I always got sig11's in
different/random places sometimes it would compile, and then crash
later too :)

I'd suggest you try and get around an hour to boot memtest, and see how
it goes. (From another thread, this is one very nice reason to have a
gentoo CD, it comes with bootable memtest. I wish debian would do that
too)...

Regards,
Adam

-- 
 -- 
Adam Goryachev
Website Managers
Ph:  +61 2 8304 [EMAIL PROTECTED]
Fax: +61 2 9345 4396www.websitemanagers.com.au

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Strange Crash

2005-01-30 Thread Paradise Dove
the same result!


On Sun, 30 Jan 2005 03:24:38 -0600, Steven Critchfield
<[EMAIL PROTECTED]> wrote:
> On Sun, 2005-01-30 at 12:46 +0330, Paradise Dove wrote:
> > this is what i've typed to get the crash info:
> >
> > gdb /usr/sbin/asterisk --core=/core.3673
> 
> Not sure if that is wrong, but I also see from the gdb man page that you
> should be able to start it by
> 
> gdb /usr/sbin/asterisk /core.3673
> 
> 
> > On Sun, 30 Jan 2005 03:11:24 -0600, Steven Critchfield
> > <[EMAIL PROTECTED]> wrote:
> > > On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> > > > hi,
> > > >
> > > > just got an strange crash, and don't know what could cause this type of 
> > > > crashs
> > > > - hardware failure
> > > > - memory
> > > > - cpu
> > > > ?
> > > > i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no 
> > > > patch).
> > > > * version is latest CVS HEAD.
> > > >
> > > > thanks
> > > >
> > > > Program terminated with signal 11, Segmentation fault.
> > > > Cannot access memory at address 0xb80014bc
> > >
> > > Seg faults can be faulty memory, overheated CPU, but usually it is an
> > > error in programming.
> > >
> > > > #0  0xb7fbbce4 in ?? ()
> > > >
> > > > (gdb) bt
> > > > #0  0xb7fbbce4 in ?? ()
> > > > #1  0x080d425d in _IO_stdin_used ()
> > > > #2  0x in ?? ()
> > >
> > > Next time provide the asterisk binary along with the core file to gdb so
> > > you can get symbol names and line numbers.
> > >
> --
> Steven Critchfield <[EMAIL PROTECTED]>
> 
>
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Strange Crash

2005-01-30 Thread Steven Critchfield
On Sun, 2005-01-30 at 12:46 +0330, Paradise Dove wrote:
> this is what i've typed to get the crash info:
> 
> gdb /usr/sbin/asterisk --core=/core.3673

Not sure if that is wrong, but I also see from the gdb man page that you
should be able to start it by

gdb /usr/sbin/asterisk /core.3673



> On Sun, 30 Jan 2005 03:11:24 -0600, Steven Critchfield
> <[EMAIL PROTECTED]> wrote:
> > On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> > > hi,
> > >
> > > just got an strange crash, and don't know what could cause this type of 
> > > crashs
> > > - hardware failure
> > > - memory
> > > - cpu
> > > ?
> > > i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no 
> > > patch).
> > > * version is latest CVS HEAD.
> > >
> > > thanks
> > >
> > > Program terminated with signal 11, Segmentation fault.
> > > Cannot access memory at address 0xb80014bc
> > 
> > Seg faults can be faulty memory, overheated CPU, but usually it is an
> > error in programming.
> > 
> > > #0  0xb7fbbce4 in ?? ()
> > >
> > > (gdb) bt
> > > #0  0xb7fbbce4 in ?? ()
> > > #1  0x080d425d in _IO_stdin_used ()
> > > #2  0x in ?? ()
> > 
> > Next time provide the asterisk binary along with the core file to gdb so
> > you can get symbol names and line numbers.
> > 
-- 
Steven Critchfield <[EMAIL PROTECTED]>

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Strange Crash

2005-01-30 Thread Paradise Dove
this is what i've typed to get the crash info:

gdb /usr/sbin/asterisk --core=/core.3673

is it wrong?


On Sun, 30 Jan 2005 03:11:24 -0600, Steven Critchfield
<[EMAIL PROTECTED]> wrote:
> On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> > hi,
> >
> > just got an strange crash, and don't know what could cause this type of 
> > crashs
> > - hardware failure
> > - memory
> > - cpu
> > ?
> > i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no patch).
> > * version is latest CVS HEAD.
> >
> > thanks
> >
> > Program terminated with signal 11, Segmentation fault.
> > Cannot access memory at address 0xb80014bc
> 
> Seg faults can be faulty memory, overheated CPU, but usually it is an
> error in programming.
> 
> > #0  0xb7fbbce4 in ?? ()
> >
> > (gdb) bt
> > #0  0xb7fbbce4 in ?? ()
> > #1  0x080d425d in _IO_stdin_used ()
> > #2  0x in ?? ()
> 
> Next time provide the asterisk binary along with the core file to gdb so
> you can get symbol names and line numbers.
> 
> --
> Steven Critchfield <[EMAIL PROTECTED]>
> 
>
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: [Asterisk-Users] Strange Crash

2005-01-30 Thread Steven Critchfield
On Sun, 2005-01-30 at 12:31 +0330, Paradise Dove wrote:
> hi,
> 
> just got an strange crash, and don't know what could cause this type of crashs
> - hardware failure
> - memory 
> - cpu
> ?
> i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no patch).
> * version is latest CVS HEAD.
> 
> thanks
> 
> Program terminated with signal 11, Segmentation fault.
> Cannot access memory at address 0xb80014bc

Seg faults can be faulty memory, overheated CPU, but usually it is an
error in programming. 

> #0  0xb7fbbce4 in ?? ()
> 
> (gdb) bt
> #0  0xb7fbbce4 in ?? ()
> #1  0x080d425d in _IO_stdin_used ()
> #2  0x in ?? ()

Next time provide the asterisk binary along with the core file to gdb so
you can get symbol names and line numbers. 

-- 
Steven Critchfield <[EMAIL PROTECTED]>

___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


[Asterisk-Users] Strange Crash

2005-01-30 Thread Paradise Dove
hi,

just got an strange crash, and don't know what could cause this type of crashs
- hardware failure
- memory 
- cpu
?
i have 1xTE405P installed with 4xTA750. using fresh kernel 2.6.9 (no patch).
* version is latest CVS HEAD.

thanks

Program terminated with signal 11, Segmentation fault.
Cannot access memory at address 0xb80014bc
#0  0xb7fbbce4 in ?? ()

(gdb) bt
#0  0xb7fbbce4 in ?? ()
#1  0x080d425d in _IO_stdin_used ()
#2  0x in ?? ()
___
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users