[nos-bbs] nos-bbs Digest, Vol 64, Issue 7
ve1jot
ve1jot at eastlink.ca
Fri Nov 27 07:25:38 EST 2009
nos-bbs-request at tapr.org wrote:
> Send nos-bbs mailing list submissions to
> nos-bbs at tapr.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
> or, via email, send a message with subject or body 'help' to
> nos-bbs-request at tapr.org
>
> You can reach the person managing the list at
> nos-bbs-owner at tapr.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of nos-bbs digest..."
>
>
> Today's Topics:
>
> 1. Segmentation Fault (Raymond Quinn)
> 2. Re: Segmentation Fault (Jack)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 26 Nov 2009 21:26:38 -0800
> From: "Raymond Quinn" <w6ray at sbcglobal.net>
> Subject: [nos-bbs] Segmentation Fault
> To: "TAPR xNOS Mailing List" <nos-bbs at tapr.org>
> Message-ID: <IHENKOFEINFMLLPAHEDEAEBFJOAA.w6ray at sbcglobal.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I have had something crop up recently on a JNOS 2.0g Linux install. When I
> use "exit" to shut down the program, I get an error and a "Segmentation
> fault". Here is a recent occurrence:
>
> SP = bf3e4204, legal stack range [9d83750,9d88750)
> Stack violation,
> process timer
>
> SP = bf3e4044, legal stack range [9d83750,9d88750)
> Stack violation, process timer
> SP =
> bf3e3e84, legal stack range [9d83750,9d88750)
> Stack violation, process timer
> SP = bf3e3cc4, legal
> stack range [9d83750,9d88750)
> Stack violation, process timer
> SP = bf3e3b04, legal stack range
> [9d83750,9d88750)
>
> Stack violation, process timer
> SP = bf3e3944, legal stack range [9d83750,9d88750)
> Stack
> violation, process timer
> SP = bf3e3784, legal stack range [9d83750,9d88750)
> Segmentation fault
>
> There is much more and this is how it appears on the screen afterwards.
> Also, I have been making changes and restarting JNOS as I cannot access the
> computer terminal screen (as the computer is 1.5 hours drive away and at
> 7500 feet.. No snow yet...) I rebooted the computer on Tuesday due to the
> fact that each time I restarted it, the tun? Interface would increase in
> increments of one. For example, tun0, then tun1, etc., until tun7. Is there
> a fix for this or something I can do different?
>
> BTW, I have tried "screen" and each time I attach to the JNOS screen, the
> keyboard panic error occurs and it restarts again. It doesn't matter what my
> console settings are.
>
> Thanks!!
>
> 73 de Ray Quinn W6RAY
> Visalia, CA DM06
>
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 26 Nov 2009 22:47:23 -0800
> From: Jack <jeifer at cwo.com>
> Subject: Re: [nos-bbs] Segmentation Fault
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Message-ID: <4B0F75FB.2050108 at cwo.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> Ray,
>
> There is a fix for the segmentation crashs! I had the same
> problem and worked with Maiko (ve4klm) while he figured out
> the fix.
>
> The fix is a patch that has to be applied to the JNOS2g
> source code. I assume you compiled your own JNOS. If so,
> download and apply Maiko's patch-fix as directed on his
> website.
>
> http://www.langelaar.net/projects/jnos2
>
> I can't help you with the other issue regarding incrementing
> tunnel's (ie 'tun0', tun2..etc). Perhaps someone else on the
> list has some ideas and can help you.
>
> 73, Jack AA6HF
>
>
>
>
> Raymond Quinn wrote:
>
>> I have had something crop up recently on a JNOS 2.0g Linux install. When I
>> use "exit" to shut down the program, I get an error and a "Segmentation
>> fault". Here is a recent occurrence:
>>
>> SP = bf3e4204, legal stack range [9d83750,9d88750)
>> Stack violation,
>> process timer
>>
>> SP = bf3e4044, legal stack range [9d83750,9d88750)
>> Stack violation, process timer
>> SP =
>> bf3e3e84, legal stack range [9d83750,9d88750)
>> Stack violation, process timer
>> SP = bf3e3cc4, legal
>> stack range [9d83750,9d88750)
>> Stack violation, process timer
>> SP = bf3e3b04, legal stack range
>> [9d83750,9d88750)
>>
>> Stack violation, process timer
>> SP = bf3e3944, legal stack range [9d83750,9d88750)
>> Stack
>> violation, process timer
>> SP = bf3e3784, legal stack range [9d83750,9d88750)
>> Segmentation fault
>>
>> There is much more and this is how it appears on the screen afterwards.
>> Also, I have been making changes and restarting JNOS as I cannot access the
>> computer terminal screen (as the computer is 1.5 hours drive away and at
>> 7500 feet.. No snow yet...) I rebooted the computer on Tuesday due to the
>> fact that each time I restarted it, the tun? Interface would increase in
>> increments of one. For example, tun0, then tun1, etc., until tun7. Is there
>> a fix for this or something I can do different?
>>
>> BTW, I have tried "screen" and each time I attach to the JNOS screen, the
>> keyboard panic error occurs and it restarts again. It doesn't matter what my
>> console settings are.
>>
>> Thanks!!
>>
>> 73 de Ray Quinn W6RAY
>> Visalia, CA DM06
>>
>>
>>
>> _______________________________________________
>> nos-bbs mailing list
>> nos-bbs at tapr.org
>> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>>
>> .
>>
>>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
> End of nos-bbs Digest, Vol 64, Issue 7
> **************************************
>
>
I found with netrom that the same thing will occur (nr0, nr1, and up)
unless you
do a "rmmod netrom", then re-insert it each time, I'm not sure if tun is
a module, but
try removing and reinstalling it if it is?
Cheers,
John
(PS: perhaps ifdown then ifup on the tun iface might do it too?)
More information about the nos-bbs
mailing list