From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751824AbcEJFhw (ORCPT ); Tue, 10 May 2016 01:37:52 -0400 Received: from mail-bn1on0115.outbound.protection.outlook.com ([157.56.110.115]:16288 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751249AbcEJFhu convert rfc822-to-8bit (ORCPT ); Tue, 10 May 2016 01:37:50 -0400 X-Greylist: delayed 905 seconds by postgrey-1.27 at vger.kernel.org; Tue, 10 May 2016 01:37:49 EDT From: Yuval Mintz To: "Elliott, Robert (Persistent Memory)" CC: netdev , linux-kernel , Ariel Elior , "David Miller" Subject: RE: bnx2x in 4.6rc7 with FW 7.13.1.0 not present Thread-Topic: bnx2x in 4.6rc7 with FW 7.13.1.0 not present Thread-Index: AdGqLjvSX3PVhHfQS9i81PtRw9MX1wATO8cQ Date: Tue, 10 May 2016 05:22:38 +0000 Message-ID: References: <94D0CD8314A33A4D9D801C0FE68B4029639613DA@G4W3202.americas.hpqcorp.net> In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B4029639613DA@G4W3202.americas.hpqcorp.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: hpe.com; dkim=none (message not signed) header.d=none;hpe.com; dmarc=none action=none header.from=qlogic.com; x-originating-ip: [31.168.140.228] x-ld-processed: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba,ExtAddr,ExtAddr x-ms-office365-filtering-correlation-id: 70039b72-5ea7-410b-3be8-08d378931a5d x-microsoft-exchange-diagnostics: 1;CO2PR11MB0086;5:jr5wIFnUkuG4G6PwqsSuOpvPHizhUqnMc5vmUjJWN3QlJWgfBt3/dSX3PoAd9Kq0sb6W+bDn/WkkJzM9tQ5va4oKOsKgdHi+Mge4wFr4pQvBrUdlb1gIR5AGqa34/ssmV8ZsX4Knytp5KS9EAUYalQ==;24:017fPuVqTetJ6b/PyKaeIPxeTjKH3MAGXLTI3QEhyHHgToOz/p2yWfeIs6KpFAj0D/vOkoLJUXAn2Yh0ACLWspp2i9C39Y3PCtn3E9MyOD4=;7:61SkotpRpSSIkXs80osqN2CGSPh1ZVj12IasB8q4yPelClLcuoqvon4cgBgYJGL64+zVlbqoiN9xzio6nyrFfFiZFieOVWZw/zrq8XnYHBEMBewj9iczsBcOe1e+thvp9GyYB0i/9w422YLSNydQbA2mZ6L6Ag5inL39fRyxwzVL9lRzltUA7pgLSyBsNWHr;20:IwhDBxwuJsH+W23cqzwctUt5ehCZRpJCahjugmgvAVarMiwE2dQXYOSQO2/qaMz+s42Ey+dSHqyDiIwHkkhoReT6Mbu0dYgtZ9aeSoSumLqaCHDJMsJPR3uvRP8sbyVHIZgG38AWNY/ImPz89eqw3BoIVmfaDQmeYvCsVIglKbM= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO2PR11MB0086; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046);SRVR:CO2PR11MB0086;BCL:0;PCL:0;RULEID:;SRVR:CO2PR11MB0086; x-forefront-prvs: 0938781D02 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(122556002)(99286002)(6116002)(92566002)(5002640100001)(102836003)(3846002)(586003)(1220700001)(5003600100002)(81166005)(2950100001)(2900100001)(2906002)(87936001)(77096005)(76576001)(86362001)(3280700002)(3660700001)(66066001)(50986999)(74316001)(76176999)(54356999)(33656002)(10400500002)(5008740100001)(8936002)(110136002)(5004730100002)(9686002)(189998001)(4326007);DIR:OUT;SFP:1102;SCL:1;SRVR:CO2PR11MB0086;H:CO2PR11MB0088.namprd11.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginatorOrg: qlogic.com X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2016 05:22:38.6121 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR11MB0086 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Upgrading a system from kernel 4.2 to 4.6rc7, there is an extra 2 minute delay > while booting due to these problems: > > [ 47.977221] bnx2x 0000:04:00.1: Direct firmware load for bnx2x/bnx2x-e2- > 7.13.1.0.fw failed with error -2 ... > Could the driver fall back to an older firmware version more gracefully? No. The internal FW isn't necessarily backward compatible [there are some Compatibility in fastpath in order to support VFs, but not in general]. Doing what you ask would means filling the driver with a lot of legacy code for older FWs, adding per-FW version HSI files, etc. So in short - if you've installed a fresh kernel on top of an existing distro that lacked the latest firmware in its filesystem, getting that missing .bin file from linux-firmware is the way to go. Cheers, Yuval