From: Petru Paler <ppetru@ppetru.net>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-pre3+zerocopy: weird messages
Date: Sun, 14 Jan 2001 13:28:45 +0200 [thread overview]
Message-ID: <20010114132845.F1394@ppetru.net> (raw)
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>
In-Reply-To: <14945.34414.185794.396720@pizda.ninka.net>; from davem@redhat.com on Sun, Jan 14, 2001 at 02:58:54AM -0800
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.
> 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 actual patch :)
--
Petru Paler, mailto:ppetru@ppetru.net
http://www.ppetru.net - ICQ: 41817235
-
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 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-14 10:11 2.4.0-pre3+zerocopy: weird messages 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 [this message]
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
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=20010114132845.F1394@ppetru.net \
--to=ppetru@ppetru.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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