netdev - RE: bnx2x - odd behaviour

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: <MN2PR18MB2528B4C3200127735D51C7B9D3250@MN2PR18MB2528.namprd18.prod.outlook.com>
Date:   Wed, 17 Apr 2019 13:05:23 +0000
From:   Sudarsana Reddy Kalluru <skalluru@...vell.com>
To:     Ian Kumlien <ian.kumlien@...il.com>
CC:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        Ariel Elior <aelior@...vell.com>,
        Ameen Rahman <arahman@...vell.com>
Subject: RE: bnx2x - odd behaviour

> -----Original Message-----
> From: Ian Kumlien <ian.kumlien@...il.com>
> Sent: Wednesday, April 17, 2019 4:32 PM
> To: Sudarsana Reddy Kalluru <skalluru@...vell.com>
> Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>; Ariel Elior
> <aelior@...vell.com>; Ameen Rahman <arahman@...vell.com>
> Subject: Re: bnx2x - odd behaviour
> 
> On Wed, Apr 17, 2019 at 9:58 AM Sudarsana Reddy Kalluru
> <skalluru@...vell.com> wrote:
> >
> > +Ameen
> >
> > Ian,
> >     We couldn't find the root-cause from the logs/register-dump.
> > Could you please load the driver with link-debugs enabled, i.e., modprobe
> bnx2x debug=0x4 or 'ethtool -s <interface> msglvl 0x4'. And collect the
> complete kernel logs and the register-dump(collected before performing
> ifconfig-down). Please also provide the output of "ethtool -i <interface>".
> 
> I'll try, this is a production system...
> 
> Could it be related to the gro changes for UDP that was done in 5.x?
>
Thanks for your help. I'm not sure if this is related to gro, link related code is handled by different component [management firmware (mfw)]. May be the complete logs/register-dump provide some additional pointers. There were some fixes in the newer version of mfw, getting the mfw version on the chip would help (ethtool -i <interface> provides mfw/boot-code version).
 
> > Thanks,
> > Sudarsana
> > > -----Original Message-----
> > > From: Ian Kumlien <ian.kumlien@...il.com>
> > > Sent: Friday, April 12, 2019 4:39 PM
> > > To: Sudarsana Reddy Kalluru <skalluru@...vell.com>
> > > Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>; Ariel
> > > Elior <aelior@...vell.com>
> > > Subject: Re: bnx2x - odd behaviour
> > >
> > > On Fri, Apr 12, 2019 at 12:53 PM Sudarsana Reddy Kalluru
> > > <skalluru@...vell.com> wrote:
> > > >
> > > > Hi Ian,
> > > >    Thanks for your info/help. There's not much info in the logs
> > > > (e.g., FW
> > > traces, calltraces). Will contact our firmware team on the
> > > register-dump analysis and provide you the update.
> > >
> > > Thank you =)
> > >
> > > > Thanks,
> > > > Sudarsana
> > > > > -----Original Message-----
> > > > > From: Ian Kumlien <ian.kumlien@...il.com>
> > > > > Sent: Friday, April 12, 2019 2:44 PM
> > > > > To: Sudarsana Reddy Kalluru <skalluru@...vell.com>
> > > > > Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>;
> > > > > Ariel Elior <aelior@...vell.com>
> > > > > Subject: Re: bnx2x - odd behaviour
> > > > >
> > > > > Finally!
> > > > >
> > > > > Just had a machine with the same issue!
> > > > >
> > > > > On Thu, Apr 11, 2019 at 10:56 AM Ian Kumlien
> > > > > <ian.kumlien@...il.com>
> > > > > wrote:
> > > > > >
> > > > > > On Thu, Apr 4, 2019 at 4:27 PM Sudarsana Reddy Kalluru
> > > > > > <skalluru@...vell.com> wrote:
> > > > > > >
> > > > > > > Hi,
> > > > > > >    We are not aware of this issue. Please collect the
> > > > > > > register dump i.e.,
> > > > > "ethtool -d <interface>" output when this issue happens (before
> > > > > performing
> > > > > link-flap) and share it for the analysis.
> > > > >
> > > > > Sent the dump separately :)