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  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:   Fri, 17 Jan 2020 11:04:40 -0500
From:   Marc Smith <msmith626@...il.com>
To:     Michael Chan <michael.chan@...adcom.com>
Cc:     Netdev <netdev@...r.kernel.org>
Subject: Re: 5.4.12 bnxt_en: Unable do read adapter's DSN

On Thu, Jan 16, 2020 at 5:19 PM Michael Chan <michael.chan@...adcom.com> wrote:
>
> On Thu, Jan 16, 2020 at 2:08 PM Marc Smith <msmith626@...il.com> wrote:
> >
> > Hi,
> >
> > I'm using the 'bnxt_en' driver with vanilla Linux 5.4.12. I have a
> > Broadcom P225p 10/25 GbE adapter. I previously used this adapter with
> > Linux 4.14.120 with no issues. Now with 5.4.12 I observe the following
> > kernel messages during initialization:
> > ...
> > [    2.605878] Broadcom NetXtreme-C/E driver bnxt_en v1.10.0
> > [    2.618302] bnxt_en 0000:00:03.0 (unnamed net_device)
> > (uninitialized): Unable do read adapter's DSN
> > [    2.622295] bnxt_en: probe of 0000:00:03.0 failed with error -95
> > [    2.632808] bnxt_en 0000:00:0a.0 (unnamed net_device)
> > (uninitialized): Unable do read adapter's DSN
> > [    2.637043] bnxt_en: probe of 0000:00:0a.0 failed with error -95
> > ...
>
> I have received a similar report about this issue recently.  I believe
> some kernels are not configured to read extended configuration space
> and so the driver's call to read the DSN would fail on such a kernel.
> This failure should not be considered a fatal error and the driver
> should continue to load.  I will send out a driver patch to fix this
> very shortly.

Thanks Michael for providing a patch so quickly! I'll try the patches
you posted in just a bit.

I'm curious though about your comment: Is there in a fact a kernel
config option I can enable for "extended configuration space support"?
I looked through the PCI support options in the kernel config menu on
5.4.x but nothing jumped out at me that sounded similar to this.

--Marc


>
> Thanks.

Powered by blists - more mailing lists