From: Ian Kumlien <pomac@vapor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [netdev watchdog/b44] is something broken? (problem somewhat found)
Date: Tue, 22 Jun 2004 16:16:46 +0200 [thread overview]
Message-ID: <1087913806.2971.155.camel@big> (raw)
[-- Attachment #1: Type: text/plain, Size: 472 bytes --]
Hi,
I just did a new observation, this only seems to happen with udp
packets...
Ie, i'm now transferring with ftp instead of nfs and it doesn't die.
if a udp packet is delayed and not sent, shouldn't it just be dropped?
I mean instead of restarting the network card?
Esp when it can kill a alta card after a while (ie reboot == only option
since it just refuses to go online again.)
--
Ian Kumlien <pomac () vapor ! com> -- http://pomac.netswarm.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-06-22 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1087913806.2971.155.camel@big \
--to=pomac@vapor.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