[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c7286c2b-09de-1221-303a-0aed3ed77c21@mellanox.com>
Date: Sun, 8 Oct 2017 10:43:08 +0300
From: Arkadi Sharshevsky <arkadis@...lanox.com>
To: David Ahern <dsa@...ulusnetworks.com>,
Jiri Pirko <jiri@...lanox.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: devlink dump of mlxsw_adj table triggers a panic
On 10/05/2017 02:57 AM, David Ahern wrote:
> The following devlink command on a 2700 triggers a panic every time.
> Kernel is net-next at 26873308b21654b6e0785b9f9e2c5414d37a4c4c
>
> $ devlink dpipe table dump pci/0000:03:00.0 name mlxsw_adj
> devlink answers: No buffer space available
> <hang>
>
> I have seen several different stack traces and varying amounts of EMAD
> errors on console:
>
> [ 77.453364] mlxsw_spectrum 0000:03:00.0: EMAD reg access failed
> (tid=64c24a400003688,reg_id=200b(sfn),type=query,status=0(operation
> performed))
> [ 77.466568] mlxsw_spectrum 0000:03:00.0: Failed to get FDB notifications
>
> If it does not reproduce for you let me know and I'll grab a trace.
>
> David
>
Thanks, will check it out. How many nexthops groups & overall number of
nexthops you configured?
Thanks,
Arkadi
Powered by blists - more mailing lists