From: Francois Romieu <romieu@fr.zoreil.com>
To: Craig Small <csmall@enc.com.au>
Cc: Realtek linux nic maintainers <nic_swsd@realtek.com>,
netdev@vger.kernel.org
Subject: Re: r8169 won't transmit with 3.12
Date: Thu, 23 Jan 2014 00:31:35 +0100 [thread overview]
Message-ID: <20140122233135.GA800@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20140122004119.GA28174@enc.com.au>
Craig Small <csmall@enc.com.au> :
> On Wed, Jan 22, 2014 at 12:36:30AM +0100, Francois Romieu wrote:
> > You may check that the onboard nic device does not even work when the
> > extra PCI-e card aren't plugged.
> It definitely doesn't. I've tried with only the onboard device
> and no other NIC device (r8169 or not) installed and its the same
> problem.
Should I understand that the LOM fails on Linux with a naked motherboard ?
> > A complete dmesg including the XID lines that the r8169 driver prints
> > would be welcome.
> See attached text file. I'm not sure why I get so many interface up
> messages.
Please check if runtime resume is disabled (/sys/bus/pci/devices/.../power/control
should be 'on'). If so and you do not see many netdev watchdog messages either,
these could be real link status change events.
> This is for the two NIC cards. I can pull them out and go back to the
> onboard one if you like.
Please do (and send a complete dmesg).
Your previous posting suggests that the LOM board is a 8168b but I haven't
seen its XID.
It could help to check the add-on 8168c in a different computer whose
motherboard does not include any networking chipset from Realtek (nor
any bios that could confuse different revisions of those).
Please don't switch between the r8168 and the r8169 modules at runtime.
I saw it in your dmesg and I won't claim it's supported.
I'll be out for work during two days.
Thanks.
--
Ueimor
next prev parent reply other threads:[~2014-01-22 23:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 0:06 r8169 won't transmit with 3.12 Craig Small
2014-01-21 23:36 ` Francois Romieu
2014-01-22 0:41 ` Craig Small
2014-01-22 23:31 ` Francois Romieu [this message]
2014-01-23 7:57 ` Craig Small
2014-01-24 0:25 ` Francois Romieu
2014-01-25 0:59 ` Craig Small
2014-01-22 4:00 ` Craig Small
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=20140122233135.GA800@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=csmall@enc.com.au \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
/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).