From: Ian Kumlien <pomac@vapor.com>
To: Andre Tomt <andre@tomt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [sundance] Known problems?
Date: Sat, 19 Jun 2004 18:56:31 +0200 [thread overview]
Message-ID: <1087664191.2971.66.camel@big> (raw)
In-Reply-To: <40D46220.9030806@tomt.net>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
On Sat, 2004-06-19 at 17:56, Andre Tomt wrote:
> If you don't know what it is, you most likely aren't using it. I'm not
> avare of any distributions having it applied. It's used for combinding
> several network packet queues into one for example.
RX packets:26633293 errors:0 dropped:672 overruns:0 frame:0
TX packets:10031287 errors:132 dropped:3960 overruns:0
carrier:0
To my knowledge all those drops was yesterday during a 2 hour period..
This is a local switched lan with flowcontrol enabled.
Couldn't this be tx getting nuts due to delays that rx packets causes?
Thus:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, TxStatus 00 TxFrameId 14, resetting...
Anyways, something is wrong... but i assume it could be pci related:
5: 43355556 XT-PIC eth0
10: 19987656 XT-PIC aic7xxx, eth3
---
LOC: 143364244
ERR: 406517
---
Any clues?
--
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 --]
prev parent reply other threads:[~2004-06-19 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 13:05 [sundance] Known problems? Ian Kumlien
2004-06-19 13:22 ` Andre Tomt
2004-06-19 13:31 ` Ian Kumlien
2004-06-19 15:56 ` Andre Tomt
2004-06-19 16:08 ` Ian Kumlien
2004-06-19 16:56 ` Ian Kumlien [this message]
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=1087664191.2971.66.camel@big \
--to=pomac@vapor.com \
--cc=andre@tomt.net \
--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