From: Stefan Assmann <sassmann@kpanic.de>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: intel-wired-lan@lists.osuosl.org,
Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: [PATCH] i40e: limit client interface to X722 hardware
Date: Tue, 4 Apr 2017 21:51:51 +0200 [thread overview]
Message-ID: <b28317c2-fa35-2ee1-7bf2-c3ca7d24677b@kpanic.de> (raw)
In-Reply-To: <CAJ3xEMjvmXTAyLP2-BwHRj59uQeCNXA7XSX7kTA=8TmwwmzRkw@mail.gmail.com>
On 04.04.2017 18:56, Or Gerlitz wrote:
> On Tue, Apr 4, 2017 at 5:34 PM, Stefan Assmann <sassmann@kpanic.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
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Assmann <sassmann@kpanic.de>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] i40e: limit client interface to X722 hardware
Date: Tue, 4 Apr 2017 21:51:51 +0200 [thread overview]
Message-ID: <b28317c2-fa35-2ee1-7bf2-c3ca7d24677b@kpanic.de> (raw)
In-Reply-To: <CAJ3xEMjvmXTAyLP2-BwHRj59uQeCNXA7XSX7kTA=8TmwwmzRkw@mail.gmail.com>
On 04.04.2017 18:56, Or Gerlitz wrote:
> On Tue, Apr 4, 2017 at 5:34 PM, Stefan Assmann <sassmann@kpanic.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
next prev parent reply other threads:[~2017-04-04 19:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 14:34 [PATCH] i40e: limit client interface to X722 hardware Stefan Assmann
2017-04-04 14:34 ` [Intel-wired-lan] " Stefan Assmann
2017-04-04 16:33 ` Williams, Mitch A
2017-04-04 16:33 ` [Intel-wired-lan] " Williams, Mitch A
2017-04-04 16:56 ` Or Gerlitz
2017-04-04 16:56 ` [Intel-wired-lan] " Or Gerlitz
2017-04-04 19:51 ` Stefan Assmann [this message]
2017-04-04 19:51 ` Stefan Assmann
2017-04-04 22:51 ` Williams, Mitch A
2017-04-04 22:51 ` [Intel-wired-lan] " Williams, Mitch A
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b28317c2-fa35-2ee1-7bf2-c3ca7d24677b@kpanic.de \
--to=sassmann@kpanic.de \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.