On Sun, Jan 14, 2001 at 05:21:33AM -0800, David S. Miller wrote:
> Petru Paler writes:
> > Got more "udp v4 hw csum failure" messages but still no "UDP packet
> > with bad csum was fragmented".
>
> OK, last experiment :-) Add this patch, and watch to see if
> the UDP "InErrors" field in /proc/
On Sun, Jan 14, 2001 at 05:21:33AM -0800, David S. Miller wrote:
> Petru Paler writes:
> > Got more "udp v4 hw csum failure" messages but still no "UDP packet
> > with bad csum was fragmented".
>
> OK, last experiment :-) Add this patch, and watch to see if
> the UDP "InErrors" field in /proc/
Petru Paler writes:
> Got more "udp v4 hw csum failure" messages but still no "UDP packet
> with bad csum was fragmented".
OK, last experiment :-) Add this patch, and watch to see if
the UDP "InErrors" field in /proc/net/snmp has a non-zero value after
letting it run for a while. Thanks.
--
On Sun, Jan 14, 2001 at 02:10:03PM +0200, Petru Paler wrote:
> On Sun, Jan 14, 2001 at 03:32:40AM -0800, David S. Miller wrote:
> > Petru Paler writes:
> > > > Oh, I think I know why this happens. Can you add this patch, and next
> > > > time the UDP bad csum message appears, tell me if it says
On Sun, Jan 14, 2001 at 03:32:40AM -0800, David S. Miller wrote:
> Petru Paler writes:
> > > Oh, I think I know why this happens. Can you add this patch, and next
> > > time the UDP bad csum message appears, tell me if it says "UDP packet
> > > with bad csum was fragmented." in the next line o
Petru Paler writes:
> > Oh, I think I know why this happens. Can you add this patch, and next
> > time the UDP bad csum message appears, tell me if it says "UDP packet
> > with bad csum was fragmented." in the next line of your syslog
> > messages? Thanks.
>
> Sure, but I also need the a
On Sun, Jan 14, 2001 at 02:58:54AM -0800, David S. Miller wrote:
> Petru Paler writes:
> > Ok. Should I keep reporting new syslog messages as they appear ?
>
> Not the "Undo ***" and "Disorder ***" ones".
Ok.
> But this one is curious:
>
> > udp v4 hw csum failure.
Petru Paler writes:
> Ok. Should I keep reporting new syslog messages as they appear ?
Not the "Undo ***" and "Disorder ***" ones".
But this one is curious:
> udp v4 hw csum failure.
>
Oh, I think I know why this happens. C
On Sun, Jan 14, 2001 at 02:33:26AM -0800, David S. Miller wrote:
> Petru Paler writes:
> > I get messages in syslog looking like:
> >
> > Undo loss 192.147.174.183/59953 c2 l0 ss2/65535 p0
> > Undo loss 63.148.232.53/4423 c2 l0 ss2/2 p0
> > Undo loss 204.253.105.63/25 c2 l0 ss2/2 p0
>
> The
Petru Paler writes:
> I get messages in syslog looking like:
>
> Undo loss 192.147.174.183/59953 c2 l0 ss2/65535 p0
> Undo loss 63.148.232.53/4423 c2 l0 ss2/2 p0
> Undo loss 204.253.105.63/25 c2 l0 ss2/2 p0
These are normal, if they annoy you please change FASTRETRANS_DEBUG
back to "1" in
I get messages in syslog looking like:
Undo loss 192.147.174.183/59953 c2 l0 ss2/65535 p0
Undo loss 63.148.232.53/4423 c2 l0 ss2/2 p0
Undo loss 204.253.105.63/25 c2 l0 ss2/2 p0
This is on a dual UltraSPARC box with a Happy Meal network
card. I don
11 matches
Mail list logo
