netdev - RE: [PATCH iwl-next v2] ice: Print NIC FW version during init

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 linux-cve-announce 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]

Message-ID: <BY5PR11MB4257E2D47667F2108BEDBE0F9682A@BY5PR11MB4257.namprd11.prod.outlook.com>
Date: Thu, 30 Nov 2023 17:08:06 +0000
From: "Bahadur, Sachin" <sachin.bahadur@...el.com>
To: Andrew Lunn <andrew@...n.ch>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH iwl-next v2] ice: Print NIC FW version during init



> From: Andrew Lunn <andrew@...n.ch>
> Sent: Thursday, November 30, 2023 7:57 AM
> To: Bahadur, Sachin <sachin.bahadur@...el.com>
> Cc: intel-wired-lan@...ts.osuosl.org; netdev@...r.kernel.org
> Subject: Re: [PATCH iwl-next v2] ice: Print NIC FW version during init
> 
> On Wed, Nov 29, 2023 at 09:56:04AM -0800, Sachin Bahadur wrote:
> > Print NIC FW version during PF initialization. FW version in dmesg is
> > used to identify and isolate issues. Particularly useful when dmesg is
> > read after reboot.
> >
> > Example log from dmesg:
> > ice 0000:ca:00.0: fw 6.2.9 api 1.7.9 nvm 3.32 0x8000d83e 1.3146.0
> >
> > Reviewed-by: Paul Menzel <pmenzel@...gen.mpg.de>
> > Reviewed-by: Pawel Kaminski <pawel.kaminski@...el.com>
> > Signed-off-by: Sachin Bahadur <sachin.bahadur@...el.com>
> 
> Is this information available via devlink info?
> It has a section to report firmware version.
> 
>    Andrew


Yes, this info is available via the "devlink dev info" command. 
Adding this info in dmesg ensures the version information is
available when someone is looking at the dmesg log to debug an issue.