From: "David S. Miller" <davem@redhat.com>
To: Petru Paler <ppetru@ppetru.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-pre3+zerocopy: weird messages
Date: Sun, 14 Jan 2001 05:21:33 -0800 (PST) [thread overview]
Message-ID: <14945.42973.905573.579075@pizda.ninka.net> (raw)
In-Reply-To: <20010114151257.J1394@ppetru.net>
In-Reply-To: <20010114121105.B1394@ppetru.net> <14945.32886.671619.99921@pizda.ninka.net> <20010114124549.D1394@ppetru.net> <14945.34414.185794.396720@pizda.ninka.net> <20010114132845.F1394@ppetru.net> <14945.36440.59585.376942@pizda.ninka.net> <20010114141003.G1394@ppetru.net> <20010114151257.J1394@ppetru.net>
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.
--- drivers/net/sunhme.c.~1~ Wed Dec 13 10:31:46 2000
+++ drivers/net/sunhme.c Sun Jan 14 05:19:09 2001
@@ -2109,11 +2109,11 @@
skb = copy_skb;
}
-
+#if 0
/* This card is _fucking_ hot... */
skb->csum = (csum ^ 0xffff);
skb->ip_summed = CHECKSUM_HW;
-
+#endif
RXD(("len=%d csum=%4x]", len, csum));
skb->protocol = eth_type_trans(skb, dev);
netif_rx(skb);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-14 13:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-14 10:11 Petru Paler
2001-01-14 10:33 ` David S. Miller
2001-01-14 10:45 ` Petru Paler
2001-01-14 10:58 ` David S. Miller
2001-01-14 11:28 ` Petru Paler
2001-01-14 11:32 ` David S. Miller
2001-01-14 12:10 ` Petru Paler
2001-01-14 13:12 ` Petru Paler
2001-01-14 13:21 ` David S. Miller [this message]
2001-01-14 18:08 ` Petru Paler
2001-01-15 5:20 ` Petru Paler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14945.42973.905573.579075@pizda.ninka.net \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ppetru@ppetru.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®