From: Dirk Behme <dirk.behme@googlemail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-rt-users@vger.kernel.org
Subject: Ethernet transmit timeouts, was: v2.6.19-rt6, yum/rpm
Date: Fri, 08 Dec 2006 20:40:54 +0100 [thread overview]
Message-ID: <4579BFC6.6000605@gmail.com> (raw)
In-Reply-To: <20061205171114.GA25926@elte.hu>
Ingo Molnar wrote:
> this is a fixes-only release. Changes since -rt1:
...
> - e1000: update to driver 7.3.15-k2 to fix latency problem
Any hint what the "latency problem" was here?
On ARM926 with patch-2.6.19-rt10 we use SMC91C94 ethernet
(smc91x.c). With rt10 applied we get NETDEV WATCHDOG
transmit timouts (see below) while using NFS. We don't get
them without rt patch.
Dirk
Btw: Any idea why /proc/interrupts doesn't look like Figure
8 of http://rt.wiki.kernel.org/index.php/RT_PREEMPT_HOWTO ?
The [........N/ 0] info is missing here.
eth0: SMC91C94 (rev 9) at c2850300 IRQ 160 [nowait]
eth0: Ethernet addr: 00:0e:99:02:02:42
# cat /proc/interrupts
CPU0
...
93: 0 MPU DMA
94: 0 MPU DMA
160: 28 GPIO eth0
164: 1 GPIO spi2.0
197: 0 GPIO serial wakeup
...
# madplay /mnt/nfs/foo.mp3
...
NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server 192.0.0.1 not responding, still trying
nfs: server 192.0.0.1 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server 192.0.0.1 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
nfs: server 192.0.0.1 not responding, still trying
nfs: server 192.0.0.1 not responding, still trying
nfs: server 192.0.0.1 not responding, still trying
NETDEV WATCHDOG: eth0: transmit timed out
next prev parent reply other threads:[~2006-12-08 19:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 17:11 v2.6.19-rt6, yum/rpm Ingo Molnar
2006-12-07 11:33 ` K.R. Foley
2006-12-07 12:13 ` Ingo Molnar
2006-12-07 15:54 ` K.R. Foley
2006-12-07 16:57 ` Ingo Molnar
2006-12-07 19:40 ` K.R. Foley
2006-12-07 20:04 ` Ingo Molnar
2006-12-07 20:45 ` Fernando Lopez-Lezcano
2006-12-07 20:58 ` Ingo Molnar
2006-12-07 21:07 ` Fernando Lopez-Lezcano
2006-12-07 21:42 ` Fernando Lopez-Lezcano
2006-12-07 21:20 ` Arjan van de Ven
2006-12-07 21:44 ` Ingo Molnar
2006-12-08 19:40 ` Dirk Behme [this message]
2006-12-08 20:15 ` Ethernet transmit timeouts, was: " Thomas Gleixner
2006-12-09 7:53 ` Ethernet transmit timeouts Dirk Behme
2006-12-10 8:27 ` Ingo Molnar
2006-12-09 4:26 ` Ethernet transmit timeouts, was: v2.6.19-rt6, yum/rpm Bruce Ashfield
2006-12-15 16:18 ` Sergei Shtylyov
2006-12-15 16:19 ` Ingo Molnar
2007-02-01 15:52 ` Sergei Shtylyov
2007-02-01 17:38 ` Ingo Molnar
2007-02-01 17:49 ` Ingo Molnar
2007-02-01 18:01 ` Sergei Shtylyov
2007-03-07 14:55 ` Sergei Shtylyov
2007-03-07 14:55 ` Sergei Shtylyov
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=4579BFC6.6000605@gmail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-rt-users@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.