[eepro100] KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1463)

Wei Keong chooweikeong@pacific.net.sg
Sun Apr 28 22:12:01 2002


>> I've another server down with the same rx buffer problem again. The funny
>> thing is both servers were down in the morning (5-6 am) where processing
>> is the lowest.

>Do you have any cron jobs scheduled for then?
>Check /etc/cron.daily and /etc/cron.weekly

The servers will run a cron to compress and send a log file (~100 MB) to log
cruncher. I doubt this will take up all the memory. However, there is a
'sleep 3600' in the cron job... will this cause some trouble?

>> ./bdflush
>> 10 0 0 0 100 3000 60 0 0

>Try
>echo "100 500 200" > /proc/sys/vm/bdflush

My current bdflush looks like this "40      0       0       0       500
3000    60      0       0". According to the doc (below), changing it to
"100 500 200" would break the bdflush, wouldn't it?

Donald, please advise.

Thanks,
Wei Keong


>From linux/fs/buffer.c:
--------------------------------------------------------------
union bdflush_param {
        struct {
                int nfract;     /* Percentage of buffer cache dirty to
                                   activate bdflush */
                int dummy1;     /* old "ndirty" */
                int dummy2;     /* old "nrefill" */
                int dummy3;     /* unused */
                int interval;   /* jiffies delay between kupdate flushes */
                int age_buffer; /* Time for normal buffer to age */
                int nfract_sync;/* Percentage of buffer cache dirty to
                                   activate bdflush synchronously */
                int dummy4;     /* unused */
                int dummy5;     /* unused */
        } b_un;
        unsigned int data[N_PARAM];
} bdf_prm = {{30, 64, 64, 256, 5*HZ, 30*HZ, 60, 0, 0}};
--------------------------------------------------------------