From: Shaya Potter <spotter@yucs.org>
To: linux-kernel@vger.kernel.org
Subject: weird realtek gigabit ethernet issue
Date: Mon, 08 Dec 2008 00:56:38 -0500 [thread overview]
Message-ID: <493CB716.8070300@yucs.org> (raw)
[please cc me in any response as not subscribed]
I have an Asus M3A78-EM motherboard with a "Realtek Semiconductor Co.,
Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)"
(per lspci)
which is using the r8169 module on ubuntu intrepid (specifically ubuntu
kernel 2.6.27-9-generic)
kernel reports
RTL8168c/8111c at 0xf88be000, 00:22:15:a1:d2:41, XID 3c4000c0 IRQ 222
well, what's the issue, its going crazy on the dropped packets, even
when the only thing connected to it is is an ssh session.
namely ifconfig shows
eth0 Link encap:Ethernet HWaddr 00:22:15:a1:d2:41
inet addr:192.168.0.41 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::222:15ff:fea1:d241/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:499 errors:0 dropped:2867537736 overruns:0 frame:0
TX packets:538 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:38995 (38.9 KB) TX bytes:87571 (87.5 KB)
Interrupt:222 Base address:0xe000
and the dropped count keeps on cycling through its entire space rapidly.
it's running in gigabit mode
root@nas:/home/spotter# mii-tool
eth0: negotiated 1000baseT-FD flow-control, link ok
I have no idea why. never seen anything like this before. been
wondering what could be doing it.
in investigating the driver
/*
* The driver does not support incoming fragmented
* frames. They are seen as a symptom of over-mtu
* sized frames.
*/
if (unlikely(rtl8169_fragmented_frame(status))) {
dev->stats.rx_dropped++;
dev->stats.rx_length_errors++;
rtl8169_mark_to_asic(desc, tp->rx_buf_sz);
continue;
}
so it would appear to be some issue relating to fragmented frames.
However, based on the amount of packets received, it seems to be very
strange.
I would have thought maybe it had something to do with jumbo packets,
but all the machines on the net are using an mtu of 1500 currently.
anyways, any explanation, if its not a bug, would be appreciated.
next reply other threads:[~2008-12-08 6:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 5:56 Shaya Potter [this message]
2008-12-08 7:34 ` weird realtek gigabit ethernet issue Giangiacomo Mariotti
2008-12-08 14:58 ` Shaya Potter
2008-12-08 22:40 ` Francois Romieu
[not found] ` <2aac3c260812081519j4739af7cve93606a46c07b218@mail.gmail.com>
[not found] ` <20081208232425.GA8174@electric-eye.fr.zoreil.com>
[not found] ` <2aac3c260812091816n41afa4aex101569cdfab130ce@mail.gmail.com>
[not found] ` <20081210201818.GA30146@electric-eye.fr.zoreil.com>
[not found] ` <2aac3c260812102029p3da46d44h91eebcdbb4f1c5c0@mail.gmail.com>
[not found] ` <20081211082805.GA14963@electric-eye.fr.zoreil.com>
[not found] ` <2aac3c260812110128s10c71271nf497124bd3d05de0@mail.gmail.com>
2008-12-11 22:00 ` Francois Romieu
2008-12-12 9:20 ` Giangiacomo Mariotti
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=493CB716.8070300@yucs.org \
--to=spotter@yucs.org \
--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