[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <81D78EA7F834FA4C83B64260D494C859087192AE@avmb3.qlogic.org>
Date: Mon, 21 Sep 2015 10:43:16 +0000
From: Ariel Elior <Ariel.Elior@...gic.com>
To: Nikola Ciprich <nikola.ciprich@...uxbox.cz>
CC: netdev <netdev@...r.kernel.org>,
"nik@...uxbox.cz" <nik@...uxbox.cz>
Subject: RE: bnx2x - occasional high packet loss (on LAN)
> -----Original Message-----
> From: Nikola Ciprich [mailto:nikola.ciprich@...uxbox.cz]
> Sent: Monday, September 21, 2015 1:32 PM
> To: Ariel Elior <Ariel.Elior@...gic.com>
> Cc: netdev <netdev@...r.kernel.org>; nik@...uxbox.cz
> Subject: Re: bnx2x - occasional high packet loss (on LAN)
>
> Hello Ariel,
>
> after few days of torturing NICs with flood pings, card
> seems to have given up with lots of errors..
>
> I've uploaded new kernel log here:
>
> http://nik.lbox.cz/download/dmesg.txt
>
> Will this help?
>
> I still have it in this hung state now, in case I could provide
> more info for diagnostics..
>
> however please note this can be different problem then I was reporting
> originaly, since I only had high packet loss, while now whole card
> seems to be blocked.. but maybe it just is worse case of the same
> problem?
Hi Nikola,
Seems like the link below is the same file you shared before - I don't see any errors there.
Two things you can collect for me to help debug this issue:
1.
Output of ethtool -d eth1 after problem occurs (redirect to a file)
2.
dmesg after enabling link related debug messages. Use
modprobe bnx2x debug=0x4
Or
ethtool -s eth1 msglvl 0x4
to enable these prints.
This holds for both of your problems (unless it is the same issue).
Thanks,
Ariel
--
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