Hello Richard

I'll give this a go, 
after my current test trying to overcome my ax25 stack hangup. Currently
following the email message 8 July 2000 'kernels mkiss bug' commenting
out a line in mkiss.c related to flexnet crc frame
System as been running 12 days 15 hours (longest non failure uptime
since December 1999) so far with out one of the ports locking up (ax25
process) as detailed in my earlier messages.

If this gets to 20 days, I'll compile the kernel with rose support (not
loading the module) as you suggest, and report back.

de Paul g4apl

In message <00080623475207.00810@pa3gcu>, Richard Adams
<[EMAIL PROTECTED]> writes
>Hello All.
>
>They say the person who keeps at it wins, well this is true.
>
>Some of you will remember a while ago a few messages about Linux node
>exiting with a segfault and an Oops in the logfile, well i think i may have
>found the answer, NOTE, i said think, maybe Tomi could check what i have to
>say.
>
>The problem kernel was "without" rose support, all other ax25 stuff was
>compiled as modules. All the utilitys AFAIK were compiled against the
>kernel without rose support. However i said yes to rose support in Linux
>node. (0.0.3)
>ax25-apps-0.0.4
>ax25-tools-0.0.5 6 was tryed as well same result.
>
>Using the bad kernel I first installed AWZ node to see if there was any
>differeance, there was, i could get a node list all 800+ nodes no problem,
>node-0.3.0 would segfault) it was just the "r"outes command which caused
>AWZnode to fail with a seg fault.
>netstat --ax25 still caused an oops 
>I then installed the new kernel and new modules with of course rose
>support as a module, rose is not loaded however but the oops'en are gone
>and netstat --ax25 works.
>
>Maybe the other 2 stn's that reported a problem (i think both were G stn's)
>try what i have explained.???
>
>Tomi, could you look into this, ?? if you need any more info please ask, i
>know its a lot to ask of you, but at least the oops'en have gone, just what
>does this have to do with rose.?? a depenency problem.???
>

-- 
[EMAIL PROTECTED]

Reply via email to