On Tue, 2023-01-03 at 11:37 -0600, Dave Chiluk wrote: > On Thu, Dec 1, 2022 at 5:33 AM Coelho, Luciano <luciano.coelho@xxxxxxxxx> wrote: > > > > On Thu, 2022-12-01 at 11:14 +0100, Thorsten Leemhuis wrote: > > > Hi, this is your Linux kernel regression tracker. > > > > > > Luca, I noticed a regression report in bugzilla where I'd like your > > > advice on. To quote https://bugzilla.kernel.org/show_bug.cgi?id=216753 > > > > Hi Thorsten wearing-the-regression-hat, 🙂 > > > > I'm not the maintainer of iwlwifi anymore, so I'm adding the new > > maintainer here, Gregory Greenman. > > > > Gregory, can you take a look? > > > > @Gregory Greenman as I'm sure this got buried over the holidays, can > you take a look at this and advise? This is definitely a regression, > but I don't think a lot of people are noticing it or don't yet have > 6ghz access points. I can write up a patch removing the offending > commit (698b166ed), or I can add an iwlwifi option to ignore the 6e > ACPI bit. Which would you prefer? > > Dell has been of little help which I pretty much expected. > > @Luciano, as you were the author of the original change, and I'm not > familiar enough with ACPI, is the below code reading the enable bits > from the BIOS ACPI table or is this somehow coming out of the network > card through some UEFI extensions? I'm trying to figure out which of > Dell or Intel need to update their firmware? I think some Lenovo's > have similar problems, so I suspect it's a BIOS ACPI table problem. > > ret = iwl_acpi_get_dsm_u32(mvm->fwrt.dev, 0, > DSM_FUNC_ENABLE_6E, > &iwl_guid, &value); Dave, this code was added there for a reason. But as I said, I'm not working with WiFi anymore, so I raised the question internally and Gregory or someone else will respond to you with the details soon. -- Cheers, Luca.
