linux-kernel - Re: Realtek 8168D: no active link (2.6.29.2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <1242323133.32579.4.camel@lap75545.ornl.gov>
Date:	Thu, 14 May 2009 13:45:33 -0400
From:	David Dillow <dave@...dillows.org>
To:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>
Cc:	Francois Romieu <romieu@...zoreil.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Realtek 8168D: no active link (2.6.29.2)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/