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]
Date:	Tue, 25 Sep 2012 07:40:17 +0000
From:	"Dmitry Kravkov" <dmitry@...adcom.com>
To:	"Jean-Michel Hautbois" <jhautbois@...il.com>
cc:	netdev <netdev@...r.kernel.org>,
	"Barak Witkowski" <barak@...adcom.com>,
	"Eilon Greenstein" <eilong@...adcom.com>,
	"davem@...emloft.net" <davem@...emloft.net>
Subject: RE: bnx2x: link detected up at startup even when it should be
 down

> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> On Behalf Of Dmitry Kravkov
> Sent: Friday, September 21, 2012 10:23 PM
> To: Jean-Michel Hautbois
> Cc: netdev; Barak Witkowski; Eilon Greenstein; davem@...emloft.net
> Subject: RE: bnx2x: link detected up at startup even when it should be down
> 
> Hi Jean,
> 
> Thank you for the info
> 
> > -----Original Message-----
> > From: Jean-Michel Hautbois [mailto:jhautbois@...il.com]
> > Sent: Friday, September 21, 2012 9:04 AM
> > To: Dmitry Kravkov
> > Cc: netdev; Barak Witkowski; Eilon Greenstein; davem@...emloft.net
> > Subject: Re: bnx2x: link detected up at startup even when it should be down
> >
> > I already did it twice. I think this is FW related and not only the
> > commit adding afex support. It may have solved a link issue (I am just
> > guessing, based on experiments) ?
> 
> FW replaced in this commit does not deal with link at all,
> 
> One is involved in link management is displayed using 'ethtool -i' - it comes with
> a card  and driver independent.
> 
> Is device configured for MF by the switch?
> Can you please share lspci output?
> 
> Other thing that can help in analysis is msglvl 0x4 for both situations
> 
We were unable to reproduce the issue on 3.2. Can you please provide logs from your setup?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ