Re: Upgrade to 2.6.15-1-k7 kernel --> "eth0: Corrupted packet received..." in syslog.

[Adam Funk <a24061@yahoo.com>]

On 2006-02-27, Adam Funk <a24061@yahoo.com> wrote:
> Last night I upgraded from 2.6.8-2-k7 to 2.6.15-1-k7.  Now I'm getting
> the following about 24 times an hour in /var/log/syslog:
>
> kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee.

Now I'm convinced this is connected with the problems I've been having
(on and off) with fetchnews, since the "Corrupted packet" messages are
interspersed with fetchnews messages, for example:

Feb 28 12:53:01 garcia fetchnews[25101]: leafnode 1.11.4: verbosity level is 0, debugmode is 0
Feb 28 12:53:08 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee.
Feb 28 12:53:46 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee.
Feb 28 12:54:27 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee.
Feb 28 12:54:48 garcia fetchnews[25101]: < (ERROR: timeout - no response in 100 s)
Feb 28 12:54:48 garcia fetchnews[25101]: Server disconnection or timeout before article could be retrieved #2
Feb 28 12:54:48 garcia fetchnews[25101]: Warning: aborting fetch from news.individual.net due to previous condition.
Feb 28 12:54:49 garcia kernel: eth0: Corrupted packet received, buffer status = 0x90c005ee.
Feb 28 12:56:29 garcia fetchnews[25101]: < (ERROR: timeout - no response in 100 s)
Feb 28 12:56:29 garcia fetchnews[25101]: Server disconnection or timeout before article could be retrieved #1
Feb 28 12:56:29 garcia fetchnews[25101]: Warning: aborting fetch from text.news.blueyonder.co.uk due to previous condition.

Any ideas?