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] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.01.1301100231320.29960@nerf07.vanv.qr>
Date:	Thu, 10 Jan 2013 02:52:24 +0100 (CET)
From:	Jan Engelhardt <jengelh@...i.de>
To:	Julian Calaby <julian.calaby@...il.com>
cc:	Linux Networking Developer Mailing List <netdev@...r.kernel.org>,
	sparclinux@...r.kernel.org
Subject: Re: niu interface automatically goes up then down


On Thursday 2013-01-10 02:27, Julian Calaby wrote:
>
>> The issue is not pressing, since it's just service processors
>> which are connected.
>
>Ok, I'm guessing that this is production so heavy debugging isn't
>going to happen.

No production, free to toy.

>I'm out of ideas. Tag?

Here is a fun fact. If I disable autonegotiation (via ethtool) on the 
link on the niu side, the remote side will deassert the carrier and 
won't return it until autoneg is turned on again.

In fact, if I do `ethtool -s eth7 autoneg off; ethtool -s eth7 autoneg 
on;`, it will take a good exact second (~1.000400 s) for the HW to 
reestablish an autonegotiated link. This delay is of the same magnitude 
and value as when the link bounces on its own.
Hypothesis: maybe the niu HW drops autoneg for a splitsecond (or it 
gets lost due to some other reason), causing the observed bounces.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ