| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [TG3]: About hw coalescing infrastructure. |
| From: | Eric Dumazet <dada1@xxxxxxxxxxxxx> |
| Date: | Mon, 04 Jul 2005 23:39:35 +0200 |
| Cc: | mchan@xxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <20050704.142604.18592223.davem@xxxxxxxxxxxxx> |
| References: | <42B982D4.9040704@xxxxxxxxxxxxx> <1119467012.5325.15.camel@rh4> <42C9A884.1030906@xxxxxxxxxxxxx> <20050704.142604.18592223.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0 (Windows/20041206) |
David S. Miller a écrit : From: Eric Dumazet <dada1@xxxxxxxxxxxxx> Date: Mon, 04 Jul 2005 23:22:12 +0200But it seems something is wrong because when network load becomes high I get : Jul 4 23:01:19 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 4 23:01:19 dada1 kernel: tg3: eth0: transmit timed out, resetting Jul 4 23:01:24 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 4 23:01:24 dada1 kernel: tg3: eth0: transmit timed out, resetting Jul 4 23:01:29 dada1 kernel: NETDEV WATCHDOG: eth0: transmit timed outDoes this happen without changing the coalescing settings at all? Not easy to answer because I have to rebuild a kernel and reboot. Will do that shortly. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [TG3]: About hw coalescing infrastructure., David S. Miller |
|---|---|
| Next by Date: | Re: [TG3]: About hw coalescing infrastructure., David S. Miller |
| Previous by Thread: | Re: [TG3]: About hw coalescing infrastructure., David S. Miller |
| Next by Thread: | Re: [TG3]: About hw coalescing infrastructure., David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |