[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 4 Apr 2017 22:51:11 +0000
From: "Williams, Mitch A" <mitch.a.williams@...el.com>
To: 'Stefan Assmann' <sassmann@...nic.de>,
Or Gerlitz <gerlitz.or@...il.com>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
Linux Netdev List <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
Subject: RE: [PATCH] i40e: limit client interface to X722 hardware
> -----Original Message-----
> From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org] On
> Behalf Of Stefan Assmann
> Sent: Tuesday, April 04, 2017 12:52 PM
> To: Or Gerlitz <gerlitz.or@...il.com>
> Cc: intel-wired-lan@...ts.osuosl.org; Linux Netdev List
> <netdev@...r.kernel.org>; David Miller <davem@...emloft.net>; Kirsher,
> Jeffrey T <jeffrey.t.kirsher@...el.com>
> Subject: Re: [PATCH] i40e: limit client interface to X722 hardware
>
> On 04.04.2017 18:56, Or Gerlitz wrote:
> > On Tue, Apr 4, 2017 at 5:34 PM, Stefan Assmann <sassmann@...nic.de> wrote:
> >> The client interface is meant for X722 iWARP support. Modprobing i40iw
> >> on systems with X710/XL710 NICs currently may crash the system.
> >
> > just curious may or crash? and why?
>
> The backtrace I got was not really conclusive. The code is not meant to
> be run on that hardware so I didn't bother to dig deeper.
>
> Stefan
The i40iw module can't easily determine which hardware its loaded upon. So it assumes that we (i40e, that is) have handed it a handle to valid hardware. When the interface is opened, it starts reading and writing registers that are nonexistent on X710/XL710.
-Mitch
Powered by blists - more mailing lists