From: David Dillow <dave@thedillows.org>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: Francois Romieu <romieu@fr.zoreil.com>, linux-kernel@vger.kernel.org
Subject: Re: Realtek 8168D: no active link (2.6.29.2)
Date: Thu, 14 May 2009 13:45:33 -0400 [thread overview]
Message-ID: <1242323133.32579.4.camel@lap75545.ornl.gov> (raw)
In-Reply-To: <200905141208.n4EC8xh3017350@mercury.physics.adelaide.edu.au>
On Thu, 2009-05-14 at 21:38 +0930, Jonathan Woithe wrote:
> Hi again
>
> Following up on my previous email, it seems that the stock kernel r8169
> driver is now working with the card in this machine ever since I tried the
> Realtek driver version 8.012.00. It's almost as if the Realtek driver
> "unlocked" something on the chip (eg: activated the PHY), the status of
> which is remembered across reboots and hard powercycles.
It's worth noting that a power cycle may not clear everything out, as
there is likely standby power being supplied even with you have the
machine off. You can be sure by disconnecting the mains power to the
power supply for 30 seconds or so -- I've seen some motherboards with
large caps that take a while to drain.
It would be interesting to see if your problems come back after doing
this. Also, if you have another machine on the gigabit network, it would
be interesting to do 'nc -l 9000 > /dev/null' and 'nc target 9000
< /dev/zero' on the other and see if a ping between the machine
eventually stops working. This reliably hangs my 8168d card at home, but
it comes back with an ifdown/ifup sequence.
Dave
next prev parent reply other threads:[~2009-05-14 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-09 14:03 Jonathan Woithe
2009-05-13 22:04 ` Francois Romieu
2009-05-14 11:49 ` Jonathan Woithe
2009-05-14 12:08 ` Jonathan Woithe
2009-05-14 17:45 ` David Dillow [this message]
2009-05-14 23:22 ` Jonathan Woithe
2009-05-17 21:57 ` Francois Romieu
2009-05-17 22:22 ` David Dillow
2009-05-18 0:17 ` Jonathan Woithe
2009-05-18 22:17 ` Francois Romieu
2009-05-18 23:43 ` Jonathan Woithe
2009-05-19 21:32 ` Francois Romieu
2009-05-22 7:18 ` Jonathan Woithe
2009-05-25 10:14 ` Jonathan Woithe
2009-05-27 12:27 ` Benny Amorsen
2009-05-28 0:09 ` Jonathan Woithe
2009-05-28 8:40 ` Benny Amorsen
2009-05-28 13:15 ` Jonathan Woithe
2009-05-18 12:39 ` Jonathan Woithe
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=1242323133.32579.4.camel@lap75545.ornl.gov \
--to=dave@thedillows.org \
--cc=jwoithe@physics.adelaide.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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
all inboxes | Powered by JetHome®