[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAA85sZtGt0ZbhGY8+96G9TY+cE+tgmjb8rHmiGT9Js+ZbjKJeg@mail.gmail.com>
Date: Sat, 17 Oct 2020 00:39:11 +0200
From: Ian Kumlien <ian.kumlien@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: jeffrey.t.kirsher@...el.com,
intel-wired-lan <intel-wired-lan@...ts.osuosl.org>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: ixgbe - only presenting one out of four interfaces on 5.9
On Fri, Oct 16, 2020 at 9:21 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Fri, 16 Oct 2020 11:35:15 +0200 Ian Kumlien wrote:
> > Adding netdev, someone might have a clue of what to look at...
> >
> > On Mon, Oct 12, 2020 at 9:20 PM Ian Kumlien <ian.kumlien@...il.com> wrote:
> > >
> > > Hi,
> > >
> > > I was really surprised when i rebooted my firewall and there was
> > > network issues, I was even more surprised when
> > > only one of the four ports of my ixbe (x553) nic was available when booted.
>
> Just to be sure you mean that the 3 devices are not present in ip link
> show?
or ifconfig or /proc etc etc, so yes
> > > You can actually see it dmesg... And i tried some basic looking at
> > > changes to see if it was obvious.... but..
>
> Showing a full dmesg may be helpful, but looking at what you posted it
> seems like the driver gets past the point where netdev gets registered,
> so the only thing that could fail after that point AFIACT is
> mdiobus_register(). Could be some breakage in MDIO.
Humm... interesting, will have a look at it
> Any chance you could fire up perf, bpftrace and install a kretprobe to
> see what mdiobus_register() returns? You can rebind the device to the
> driver through sysfs.
Do you need a difference between the kernels?
Powered by blists - more mailing lists