[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACKFLim=ENcZMk+8UUwg87PPdu6zDC1Ld5b54Pp+_WSow9g_Og@mail.gmail.com>
Date: Mon, 10 Jan 2022 13:15:34 -0800
From: Michael Chan <michael.chan@...adcom.com>
To: Vijay Balakrishna <vijayb@...ux.microsoft.com>
Cc: Netdev <netdev@...r.kernel.org>
Subject: Re: [bnxt] Error: Unable to read VPD
On Mon, Jan 10, 2022 at 1:02 PM Vijay Balakrishna
<vijayb@...ux.microsoft.com> wrote:
>
>
> Since moving to 5.10 from 5.4 we are seeing
>
> > Jan 01 00:00:01 localhost kernel: bnxt_en 0008:01:00.0 (unnamed net_device) (uninitialized): Unable to read VPD
> >
> > Jan 01 00:00:01 localhost kernel: bnxt_en 0008:01:00.1 (unnamed net_device) (uninitialized): Unable to read VPD
>
> these appear to be harmless and introduced by
>
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a0d0fd70fed5cc4f1e2dd98b801be63b07b4d6ac
> Does "Unable to read VPD" need to be an error or can it be a warning
> (netdev_warn)?
>
We can change these to warnings. Thanks.
Powered by blists - more mailing lists