From: Lance Lassetter <lancelassetter@gmail.com>
To: netdev@vger.kernel.org
Subject: r8169 with 3.9.0-rc9
Date: Fri, 26 Apr 2013 08:23:02 -0500 [thread overview]
Message-ID: <20130426132254.GA22821@gmail.com> (raw)
hello,
i've exhausted my efforts to resolve this so i am sending you this email in hopes you might shed some light on the problem.
i have an onboard r8169 and a secondary pcie r8169 chipset gigabit ethernet adapters.
the link keeps sputtering with constant kernel messages (dmesg) of "link up link down"
the variant of linux is fedora 18 with testing branch enabled and fedora "vanilla" kernel with minimal fedora patchset taken from fedora vanilla kernel repos as instructed on the fedora wiki.
the reason for the development kernel is i hoped with this, this problem would be resolved.
dmesg looks like:
[52857.473520] r8169 0000:03:00.0 p10p1: link down
[52859.763261] r8169 0000:03:00.0 p10p1: link up
[52859.771250] r8169 0000:04:09.0 p8p1: link up
[52917.512992] r8169 0000:04:09.0 p8p1: link down
[52917.534918] r8169 0000:03:00.0 p10p1: link down
[52919.846520] r8169 0000:04:09.0 p8p1: link up
[52919.850411] r8169 0000:03:00.0 p10p1: link up
[53977.329829] r8169 0000:03:00.0 p10p1: link down
[53979.798396] r8169 0000:03:00.0 p10p1: link up
[54087.331434] r8169 0000:03:00.0 p10p1: link down
[54089.730198] r8169 0000:03:00.0 p10p1: link up
etc....
the box serves as a network router so it is causing abundant network traffic problems.
any debugging i could help you with, please let me know. also if there is a possible solution, please let me know.
kind regards and i wish you the best,
lance lassetter
next reply other threads:[~2013-04-26 13:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 13:23 Lance Lassetter [this message]
2013-04-26 20:50 ` r8169 with 3.9.0-rc9 Francois Romieu
2013-04-27 4:12 ` Lance Lassetter
2013-04-28 1:12 ` Lance Lassetter
2013-05-01 10:07 ` Lance Lassetter
2013-05-01 12:15 ` Francois Romieu
2013-05-01 21:28 ` Lance Lassetter
2013-05-01 22:31 ` Francois Romieu
2013-05-02 2:18 ` Lance Lassetter
2013-05-02 22:18 ` Francois Romieu
2013-05-03 4:24 ` Lance Lassetter
2013-05-05 15:17 ` Lance Lassetter
2013-05-05 16:02 ` Lance Lassetter
2013-05-05 19:33 ` Francois Romieu
2013-05-09 17:14 ` Lance Lassetter
2013-05-09 17:50 ` Lance Lassetter
2013-05-10 19:02 ` Lance Lassetter
2013-05-14 3:04 ` Lance Lassetter
2013-05-17 14:35 ` Lance Lassetter
2013-05-24 4:45 ` Lance Lassetter
2013-06-04 2:16 ` Lance Lassetter
2013-05-02 2:23 ` Lance Lassetter
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=20130426132254.GA22821@gmail.com \
--to=lancelassetter@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).