From: Corinna Vinschen <vinschen@redhat.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, jesse.brandeburg@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net] igb: clean up in all error paths when enabling SR-IOV
Date: Thu, 31 Aug 2023 10:10:11 +0200 [thread overview]
Message-ID: <ZPBK46hxIJCmuKtr@calimero.vinschen.de> (raw)
In-Reply-To: <c9bc7c2a-622f-5d82-69e8-2d24ba3875fa@intel.com>
On Aug 29 16:09, Tony Nguyen wrote:
> On 8/24/2023 6:07 AM, Corinna Vinschen wrote:
> > Question to the Intel folks:
> >
> > On Aug 24 11:16, Corinna Vinschen wrote:
> > > After commit 50f303496d92 ("igb: Enable SR-IOV after reinit"), removing
> > > the igb module could hang or crash (depending on the machine) when the
> > > module has been loaded with the max_vfs parameter set to some value != 0.
> > >
> > > In case of one test machine with a dual port 82580, this hang occured:
> > > [...]
> > > The reproducer was a simple script:
> > >
> > > #!/bin/sh
> > > for i in `seq 1 5`; do
> > > modprobe -rv igb
> > > modprobe -v igb max_vfs=1
> > > sleep 1
> > > modprobe -rv igb
> > > done
> > >
> > > It turned out that this could only be reproduce on 82580 (quad and
> > > dual-port), but not on 82576, i350 and i210. Further debugging showed
> > > that igb_enable_sriov()'s call to pci_enable_sriov() is failing, because
> > > dev->is_physfn is 0 on 82580.
> >
> > Along these lines, isn't the first and foremost bug that igb_enable_sriov()
> > has been called for this NIC at all? In terms of patches, shouldn't the
> > guard expression in igb_probe_vfs()
> >
> > /* Virtualization features not supported on i210 family. */
> > if ((hw->mac.type == e1000_i210) || (hw->mac.type == e1000_i211))
> > return;
> >
> > get changed to:
> >
> > /* Virtualization features not supported on i210 and 82580 family. */
> > if ((hw->mac.type == e1000_i210) || (hw->mac.type == e1000_i211) ||
> > (hw->mac.type == e1000_82580))
> > return;
>
> Hi Corinna,
>
> Adding 82580 to this seems like a good change; did you want to submit a
> patch to do this?
Hi Tony,
sure, I just sent the patch.
Thanks,
Corinna
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-08-31 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 9:16 [Intel-wired-lan] [PATCH net] igb: clean up in all error paths when enabling SR-IOV Corinna Vinschen
2023-08-24 11:02 ` Akihiko Odaki
2023-08-24 13:07 ` Corinna Vinschen
2023-08-29 23:09 ` Tony Nguyen
2023-08-31 8:10 ` Corinna Vinschen [this message]
2023-09-11 8:02 ` Romanowski, Rafal
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=ZPBK46hxIJCmuKtr@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox