[Asterisk-bsd] FBSD port: Hard lockup of machine at exit/restart of asterisk

[Charles A.Newcomer]

Let me post this again.
I think this will solve all of the hard lockups.

Greetings:

It looks like there is a bug in the zaptel driver from 
zaptel-freebsd-0.8.

It manifest itself when the zt_chan_read call is interrupted. (To 
reproduce
run zttest and hit ^C).  I first noticed it when doing a STOP NOW.

Changing the schluffen routine as follows fixes the problem:

> static int schluffen(void *q)
> {
>    int rc;
>
>         switch (rc=tsleep(q, PZERO | PCATCH, "schluffen", 0)) {
>            case    EINTR:
>            case ERESTART: return(rc);
>         }
>         return(0);
> }
>


This allows the for (;;) loop to exit after an interrupt.


Thanks,
/can


On Feb 3, 2005, at 3:45 PM, Jerry Bednyak wrote:

> I'm having the same problem. I did notice, however,
> that disabling all the musiconhold classes via
> musiconhold.conf will allow a clean shutdown without
> hanging the computer. Maybe that will spawn some ideas
> as to the problem. Using FreeBSD 5.3 w/ Zaptel,
> Asterisk 1.0.3
>
> Jerry
>
> ----- Original Message -----
> From: "Vahan Yerkanian" <vahan at arminco.com>
> To: "Asterisk on BSD discussion" <asterisk-bsd at
> lists.digium.com>
> Sent: Sunday, January 16, 2005 3:18 AM
> Subject: Re: [Asterisk-bsd] FreeBSD hang up when
> exiting *
>
>
>> Same thing here,
>>
>> Try to unload zaptel drivers and you'll see the
> problem go. We need
>> newer drivers in ports for sure.
>>
>> Kavit Munshi wrote:
>>> I am getting a very strange error on FreeBSD 5.3
> STABLE. I am using
>>> asterisk 1.0.3 and the zaptel-bsd drivers from the
> svn trunk. Asterisk
>>> performs just fine. No issues whatsoever. The
> problem arises when I try
>>> to exit asterisk in any fashion, stop now, stop
> when convenient, hitting
>>> CTRL-C, using kill -9 or kill all; it freezes the
> entire operating
>>> system over. Its like getting the blue screen of
> death on windows. No
>>> keys work and I have to reset the machine manually.
>>>
>>> Now the instresting bit is, after rebooting i
> examine the log files and
>>> i get no log messages pertaining to a crash or any
> kernel messages which
>>> give a clue.
>>>
>>> This is really weird as asterisk performs very
> nicely and doesnt give
>>> any issues with memory load or interrupts. It only
> has problems when you
>>> try to exit it.
>>>
>>> I will appreciate any help.
>>>
>>> regards
>>>
>>> Kavit
>>> _______________________________________________
>>> Asterisk-BSD mailing list
>>> Asterisk-BSD at lists.digium.com
>>>
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>>>
>>
>
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>


On Mar 19, 2005, at 7:33 PM, Kim Culhan wrote:

> On Sat, March 19, 2005 8:05 pm, Mark Radabaugh said:
>
>>
>> What are you running on?   I have a AMD in a Asus A7N8X motherboard
>> (NVidia chipset, integrated NVidia sound).  I'm thinking the lockup
>> is really a kernel bug with this hardware related to the soundcard.
>
> You may be onto something there, this is the same motherboard
>
>> I agree with your statement regarding the surprise at seeing
>> a FreeBSDbox lock up - in many years of running BSD on lots of
>> different machines I don't think I have ever seen a kernel freeze.
>> At the same time I have never had a reason to run sound - all of
>> our machines are servers.
>>
>> I'm going to do a little more investigating with mpg123 without
>> Asterisk running - I'll let you know what I find.
>
> Thats great, anyone else seeing this?
>
> -kim
>
>
>
> 		
> __________________________________
> Do you Yahoo!?
> Yahoo! Small Business - Try our new resources site!
> http://smallbusiness.yahoo.com/resources/
> _______________________________________________
> Asterisk-BSD mailing list
> Asterisk-BSD at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-bsd
>