Re: [Aprsd-users] Killer packets??

[Steve D. <k4...@ta...>]

On 12/28/01 4:12 PM Brian D Heaton (bdh...@c4...) wrote:

>	I'm assuming you're current on all the RH patches.  I'd also
>download/compile the newest 2.4.17 kernel (2.4.16 would work too). 
>There have been some major changes to the VM subsystem since 2.4.7 and
>it will remove some areas of concern.  2.4.16/17 also has the ext3
>patches integrated into the kernel so if you've got ext3 filesystems you
>won't have to add the patch.  As a side benefit you can tweak the kernel
>for your setup.  The RH stock kernels have so much stuff compiled in (or
>in modules) that it can cause some problems.
>
>	Give that a shot and let me know if I can be of any assistance.
>
Actually I've given up, now that I've been pointed to aprsd.pl, so far it 
is much more stable.

Just to be totally clear. This is not a new problem, there is a 
concurrency issue, it seems the higher the performance of the system (and 
especially going to multiple processors) the greater the likelihood of it 
occuring. There is some other trigger factor I don't understand, but as 
far as I can tell it isn't specific data on the stream.

I don't believe this is a kernel issue, it has been present in every 
kernel I've used going back to 2.0.something before I even started findU. 
I've spent countless hours trying to isolate something that could 
consistently reproduce it or find some way to work around it. I can't 
bring down the production machine for findu every time a new kernel comes 
out in the vague hope that that will magically fix the problem. For 
production machines staying a bit behind the bleeding edge is often the 
safest course of action, not to mention the most efficient. 

I want to spend my time working on findU, not administering and 
configuring Linux.

Steve K4HG