All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: <linux-acpi@vger.kernel.org>, <netdev@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: Oops in during sriov_enable with ixgbe driver
Date: Thu, 30 Sep 2021 19:38:37 +0200	[thread overview]
Message-ID: <b9e461a5-75de-6f45-1709-d9573492f7ac@intel.com> (raw)
In-Reply-To: <5ea40608-388e-1137-9b86-85aad1cad6f6@intel.com>

On 9/30/2021 7:31 PM, Jesse Brandeburg wrote:
> On 9/28/2021 4:56 AM, Niklas Schnelle wrote:
>> Hi Jesse, Hi Tony,
>>
>> Since v5.15-rc1 I've been having problems with enabling SR-IOV VFs on
>> my private workstation with an Intel 82599 NIC with the ixgbe driver. I
>> haven't had time to bisect or look closer but since it still happens on
>> v5.15-rc3 I wanted to at least check if you're aware of the problem as
>> I couldn't find anything on the web.
> We haven't heard anything of this problem.
>
>
>> I get below Oops when trying "echo 2 > /sys/bus/pci/.../sriov_numvfs"
>> and suspect that the earlier ACPI messages could have something to do
>> with that, absolutely not an ACPI expert though. If there is a need I
>> could do a bisect.
> Hi Niklas, thanks for the report, I added the Intel Driver's list for
> more exposure.
>
> I asked the developers working on that driver to take a look and they
> tried to reproduce, and were unable to do so. This might be related to
> your platform, which strongly suggests that the ACPI stuff may be related.
>
> We have tried to reproduce but everything works fine no call trace in
> scenario with creating VF.
>
> This is good in that it doesn't seem to be a general failure, you may
> want to file a kernel bugzilla (bugzilla.kernel.org) to track the issue,
> and I hope that @Rafael might have some insight.
>
> This issue may be related to changes in acpi_pci_find_companion,
> but as I say, we are not able to reproduce this.
>
> commit 59dc33252ee777e02332774fbdf3381b1d5d5f5d
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date:   Tue Aug 24 16:43:55 2021 +0200
>      PCI: VMD: ACPI: Make ACPI companion lookup work for VMD bus

This change doesn't affect any devices beyond the ones on the VMD bus.


> At this point maybe a bisect would be helpful, since this seems to be a
> corner case that we used to handle but no longer do.
>
> Thanks!
> Jesse



WARNING: multiple messages have this Message-ID (diff)
From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] Oops in during sriov_enable with ixgbe driver
Date: Thu, 30 Sep 2021 19:38:37 +0200	[thread overview]
Message-ID: <b9e461a5-75de-6f45-1709-d9573492f7ac@intel.com> (raw)
In-Reply-To: <5ea40608-388e-1137-9b86-85aad1cad6f6@intel.com>

On 9/30/2021 7:31 PM, Jesse Brandeburg wrote:
> On 9/28/2021 4:56 AM, Niklas Schnelle wrote:
>> Hi Jesse, Hi Tony,
>>
>> Since v5.15-rc1 I've been having problems with enabling SR-IOV VFs on
>> my private workstation with an Intel 82599 NIC with the ixgbe driver. I
>> haven't had time to bisect or look closer but since it still happens on
>> v5.15-rc3 I wanted to at least check if you're aware of the problem as
>> I couldn't find anything on the web.
> We haven't heard anything of this problem.
>
>
>> I get below Oops when trying "echo 2 > /sys/bus/pci/.../sriov_numvfs"
>> and suspect that the earlier ACPI messages could have something to do
>> with that, absolutely not an ACPI expert though. If there is a need I
>> could do a bisect.
> Hi Niklas, thanks for the report, I added the Intel Driver's list for
> more exposure.
>
> I asked the developers working on that driver to take a look and they
> tried to reproduce, and were unable to do so. This might be related to
> your platform, which strongly suggests that the ACPI stuff may be related.
>
> We have tried to reproduce but everything works fine no call trace in
> scenario with creating VF.
>
> This is good in that it doesn't seem to be a general failure, you may
> want to file a kernel bugzilla (bugzilla.kernel.org) to track the issue,
> and I hope that @Rafael might have some insight.
>
> This issue may be related to changes in acpi_pci_find_companion,
> but as I say, we are not able to reproduce this.
>
> commit 59dc33252ee777e02332774fbdf3381b1d5d5f5d
> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Date:   Tue Aug 24 16:43:55 2021 +0200
>      PCI: VMD: ACPI: Make ACPI companion lookup work for VMD bus

This change doesn't affect any devices beyond the ones on the VMD bus.


> At this point maybe a bisect would be helpful, since this seems to be a
> corner case that we used to handle but no longer do.
>
> Thanks!
> Jesse



  reply	other threads:[~2021-09-30 17:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 11:56 Oops in during sriov_enable with ixgbe driver Niklas Schnelle
2021-09-30 17:31 ` Jesse Brandeburg
2021-09-30 17:31   ` [Intel-wired-lan] " Jesse Brandeburg
2021-09-30 17:38   ` Rafael J. Wysocki [this message]
2021-09-30 17:38     ` Rafael J. Wysocki
2021-09-30 18:20     ` Rafael J. Wysocki
2021-09-30 18:20       ` [Intel-wired-lan] " Rafael J. Wysocki
2021-09-30 18:37       ` Rafael J. Wysocki
2021-09-30 18:37         ` [Intel-wired-lan] " Rafael J. Wysocki
2021-10-01  8:23         ` Niklas Schnelle
2021-10-01  8:23           ` [Intel-wired-lan] " Niklas Schnelle
2021-10-01 13:21           ` Rafael J. Wysocki
2021-10-01 13:21             ` [Intel-wired-lan] " Rafael J. Wysocki

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=b9e461a5-75de-6f45-1709-d9573492f7ac@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=schnelle@linux.ibm.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 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.