pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

Hello,

some variants of Dell XPS 13 9310 model have a QCA6390 device and I was 
trying to make it work using the  ath.git master branch (tag 
ath-202010011934).

Unfortunatly, I get the following error messages when loading the module:

> [  672.277726] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support is 
> experimental!
> [  672.277925] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem 
> 0x8c300000-0x8c3fffff 64bit]
> [  672.278020] ath11k_pci 0000:56:00.0: failed to get 32 MSI vectors, 
> only -28 available
> [  672.278024] ath11k_pci 0000:56:00.0: failed to enable msi: -28
> [  672.278144] ath11k_pci: probe of 0000:56:00.0 failed with error -28

-28 seems to reference ENOSPC, which seems to be related to the minimum 
number of vectors not beeing available. lspci output is

> 56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>     Subsystem: Rivet Networks Device a501
>     Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>     Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
>     Capabilities: [40] Power Management version 3
>         Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
> PME(D0+,D1-,D2-,D3hot+,D3cold+)
>         Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
>     Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit-
>         Address: fee01004  Data: 40ef
>         Masking: 00000000  Pending: 00000000
>     Capabilities: [70] Express (v2) Endpoint, MSI 00
>         DevCap:    MaxPayload 128 bytes, PhantFunc 0, Latency L0s 
> unlimited, L1 unlimited
>             ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- 
> SlotPowerLimit 10.000W
>         DevCtl:    CorrErr- NonFatalErr- FatalErr- UnsupReq-
>             RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
>             MaxPayload 128 bytes, MaxReadReq 512 bytes
>         DevSta:    CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ 
> TransPend-
>         LnkCap:    Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit 
> Latency L0s <1us, L1 <64us
>             ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
>         LnkCtl:    ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
>             ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
>         LnkSta:    Speed 5GT/s (downgraded), Width x1 (ok)
>             TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
>         DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, 
> NROPrPrP-, LTR+
>              10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, 
> EETLPPrefix-
>              EmergencyPowerReduction Not Supported, 
> EmergencyPowerReductionInit-
>              FRS-, TPHComp+, ExtTPHComp-
>              AtomicOpsCap: 32bit- 64bit- 128bitCAS-
>         DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
> OBFF Disabled
>              AtomicOpsCtl: ReqEn-
>         LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
>              Transmit Margin: Normal Operating Range, 
> EnterModifiedCompliance- ComplianceSOS-
>              Compliance De-emphasis: -6dB
>         LnkSta2: Current De-emphasis Level: -6dB, 
> EqualizationComplete-, EqualizationPhase1-
>              EqualizationPhase2-, EqualizationPhase3-, 
> LinkEqualizationRequest-
>     Capabilities: [100 v2] Advanced Error Reporting
>         UESta:    DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>         UEMsk:    DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
>         UESvrt:    DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- 
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
>         CESta:    RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
> AdvNonFatalErr+
>         CEMsk:    RxErr- BadTLP- BadDLLP- Rollover- Timeout- 
> AdvNonFatalErr+
>         AERCap:    First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- 
> ECRCChkCap+ ECRCChkEn-
>             MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
>         HeaderLog: 00000000 00000000 00000000 00000000
>     Capabilities: [148 v1] Secondary PCI Express
>         LnkCtl3: LnkEquIntrruptEn-, PerformEqu-
>         LaneErrStat: 0
>     Capabilities: [158 v1] Transaction Processing Hints
>         No steering table available
>     Capabilities: [1e4 v1] Latency Tolerance Reporting
>         Max snoop latency: 3145728ns
>         Max no snoop latency: 3145728ns
>     Capabilities: [1ec v1] L1 PM Substates
>         L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ 
> L1_PM_Substates+
>               PortCommonModeRestoreTime=70us PortTPowerOnTime=0us
>         L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
>                T_CommonMode=0us LTR1.2_Threshold=81920ns
>         L1SubCtl2: T_PwrOn=44us
>     Kernel modules: ath11k_pci
It there anything in my side I can to to fix the vector allocation or is 
the XPS 13 9310 just not supported? Bluetooth works with this kernel 
version, only Wifi fails.

Best,

Thomas


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Krause <thomaskrause@posteo.de> writes:

> some variants of Dell XPS 13 9310 model have a QCA6390 device 

Do you happen to know which models exacly have it? I'm trying to find a
reasonably priced laptop with QCA6390 from Finland or EU, no luck yet.
Apparently there was a certain Dell XPS 15 9500 model but it was almost
4k EUR.

> and I was trying to make it work using the  ath.git master branch (tag
> ath-202010011934).
>
> Unfortunatly, I get the following error messages when loading the module:
>
>> [  672.277726] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support
>> is experimental!
>> [  672.277925] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem
>> 0x8c300000-0x8c3fffff 64bit]
>> [  672.278020] ath11k_pci 0000:56:00.0: failed to get 32 MSI
>> vectors, only -28 available
>> [  672.278024] ath11k_pci 0000:56:00.0: failed to enable msi: -28
>> [  672.278144] ath11k_pci: probe of 0000:56:00.0 failed with error -28
>
> -28 seems to reference ENOSPC, which seems to be related to the
> minimum number of vectors not beeing available.

I had the same problem as well back in the days, for me enabling
CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
mention that in the ath11k warning above :)

-- 
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

Am 19.10.20 um 10:09 schrieb Kalle Valo:
>> some variants of Dell XPS 13 9310 model have a QCA6390 device
> Do you happen to know which models exacly have it? I'm trying to find a
> reasonably priced laptop with QCA6390 from Finland or EU, no luck yet.
> Apparently there was a certain Dell XPS 15 9500 model but it was almost
> 4k EUR.
Dell at least sold the XPS 13 9310 with 32 GB RAM in Germany 
(https://www.dell.com/de-de/shop/laptops/neu-xps-13/spd/xps-13-9310-laptop/cn93212) 
with the QCA6390 device. With around 2300 EUR, this offer is still 
expensive but it's less than the 4000. In the delivery notes they called 
the Wi-Fi card "Killer Wi-Fi 6 AX500-DBS (2 x 2)" (part number 555-BFPF) 
but in the current version of the linked listing this is now "Killer 
Wifi 7 AX500". I'm not sure if the "DBS" part has anything to say.
>
> I had the same problem as well back in the days, for me enabling
> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
> mention that in the ath11k warning above :)

CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card is behind a PCI bridge which is also disabled, could this be a problem?

00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 123
	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c300000-8c3fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: Dell Device 0991
	Capabilities: [a0] Power Management version 3
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [220] Access Control Services
	Capabilities: [150] Precision Time Measurement
	Capabilities: [200] L1 PM Substates
	Capabilities: [a00] Downstream Port Containment
	Kernel driver in use: pcieport




-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Krause <thomaskrause@posteo.de> writes:

> Am 19.10.20 um 10:09 schrieb Kalle Valo:
>>> some variants of Dell XPS 13 9310 model have a QCA6390 device
>> Do you happen to know which models exacly have it? I'm trying to find a
>> reasonably priced laptop with QCA6390 from Finland or EU, no luck yet.
>> Apparently there was a certain Dell XPS 15 9500 model but it was almost
>> 4k EUR.
>
> Dell at least sold the XPS 13 9310 with 32 GB RAM in Germany
> (https://www.dell.com/de-de/shop/laptops/neu-xps-13/spd/xps-13-9310-laptop/cn93212)
> with the QCA6390 device. With around 2300 EUR, this offer is still
> expensive but it's less than the 4000. In the delivery notes they
> called the Wi-Fi card "Killer Wi-Fi 6 AX500-DBS (2 x 2)" (part number
> 555-BFPF) but in the current version of the linked listing this is now
> "Killer Wifi 7 AX500". I'm not sure if the "DBS" part has anything to
> say.

Yeah, that's more reasonable price for a laptop. Thanks, this is very
good info. I'll try to find one from Finland.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

+ linux-wireless, linux-pci, devin

Thomas Krause <thomaskrause@posteo.de> writes:

>> I had the same problem as well back in the days, for me enabling
>> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> mention that in the ath11k warning above :)
>
> CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
> is behind a PCI bridge which is also disabled, could this be a
> problem?
>
> 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
> [Normal decode])
> 	Flags: bus master, fast devsel, latency 0, IRQ 123
> 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> 	I/O behind bridge: [disabled]
> 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> 	Prefetchable memory behind bridge: [disabled]
> 	Capabilities: [40] Express Root Port (Slot+), MSI 00
> 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
> 	Capabilities: [90] Subsystem: Dell Device 0991
> 	Capabilities: [a0] Power Management version 3
> 	Capabilities: [100] Advanced Error Reporting
> 	Capabilities: [220] Access Control Services
> 	Capabilities: [150] Precision Time Measurement
> 	Capabilities: [200] L1 PM Substates
> 	Capabilities: [a00] Downstream Port Containment
> 	Kernel driver in use: pcieport

I don't know enough about PCI to say if the bridge is a problem or not.
I'm adding linux-wireless and linux-pci in someone can help. Also Devin
seems to have a similar problem.

To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
PCI device where he is not having enough MSI vectors. ath11k needs 32
vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
for ath11k and introduced in v5.10-rc1. The irq allocation code is in
drivers/net/wireless/ath/ath11k/pci.c. [2]

Can PCI folks help, what could cause this and how to debug it further?

I would first try with a full distro kernel config, just in case there's
some another important kernel config missing.

[1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html

[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath11k/pci.c#n633

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

+ linux-wireless, linux-pci, devin

Thomas Krause <thomaskrause@posteo.de> writes:

>> I had the same problem as well back in the days, for me enabling
>> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> mention that in the ath11k warning above :)
>
> CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
> is behind a PCI bridge which is also disabled, could this be a
> problem?
>
> 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
> [Normal decode])
> 	Flags: bus master, fast devsel, latency 0, IRQ 123
> 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> 	I/O behind bridge: [disabled]
> 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> 	Prefetchable memory behind bridge: [disabled]
> 	Capabilities: [40] Express Root Port (Slot+), MSI 00
> 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
> 	Capabilities: [90] Subsystem: Dell Device 0991
> 	Capabilities: [a0] Power Management version 3
> 	Capabilities: [100] Advanced Error Reporting
> 	Capabilities: [220] Access Control Services
> 	Capabilities: [150] Precision Time Measurement
> 	Capabilities: [200] L1 PM Substates
> 	Capabilities: [a00] Downstream Port Containment
> 	Kernel driver in use: pcieport

I don't know enough about PCI to say if the bridge is a problem or not.
I'm adding linux-wireless and linux-pci in someone can help. Also Devin
seems to have a similar problem.

To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
PCI device where he is not having enough MSI vectors. ath11k needs 32
vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
for ath11k and introduced in v5.10-rc1. The irq allocation code is in
drivers/net/wireless/ath/ath11k/pci.c. [2]

Can PCI folks help, what could cause this and how to debug it further?

I would first try with a full distro kernel config, just in case there's
some another important kernel config missing.

[1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html

[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath11k/pci.c#n633

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Bjorn Helgaas]

[+cc Govind, author of 5697a564d369 ("ath11k: pci: add MSI config
initialisation")]

On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
> + linux-wireless, linux-pci, devin
> 
> Thomas Krause <thomaskrause@posteo.de> writes:
> 
> >> I had the same problem as well back in the days, for me enabling
> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
> >> mention that in the ath11k warning above :)
> >
> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
> > is behind a PCI bridge which is also disabled, could this be a
> > problem?
> >
> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
> > [Normal decode])
> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> > 	I/O behind bridge: [disabled]
> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> > 	Prefetchable memory behind bridge: [disabled]
> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
> > 	Capabilities: [90] Subsystem: Dell Device 0991
> > 	Capabilities: [a0] Power Management version 3
> > 	Capabilities: [100] Advanced Error Reporting
> > 	Capabilities: [220] Access Control Services
> > 	Capabilities: [150] Precision Time Measurement
> > 	Capabilities: [200] L1 PM Substates
> > 	Capabilities: [a00] Downstream Port Containment
> > 	Kernel driver in use: pcieport
> 
> I don't know enough about PCI to say if the bridge is a problem or not.

I don't think the bridge is an issue here.  AFAICT the bridge's I/O
and prefetchable memory windows are disabled, but the non-prefetchable
window *is* enabled and contains the space consumed by the ath11k
device:

  00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
	Memory behind bridge: 8c300000-8c3fffff [size=1M]
  56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
     Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]

> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
> PCI device where he is not having enough MSI vectors. ath11k needs 32
> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
> drivers/net/wireless/ath/ath11k/pci.c. [2]

This code is needlessly complicated.  If you absolutely need
msi_config.total_vectors and can't settle for any less, you can do
this:

  num_vectors = pci_alloc_irq_vectors(ab_pci->pdev,
                                      msi_config.total_vectors,
                                      msi_config.total_vectors,
                                      PCI_IRQ_MSI);

  if (num_vectors < 0) {
    ath11k_err(ab, "failed to get %d MSI vectors (%d)\n",
               msi_config.total_vectors, num_vectors);
    return num_vectors;
  }

But it seems a little greedy if the device can't operate at all unless
it gets 32 vectors.  Are you sure that's a hard requirement?  Most
devices can work with fewer vectors, even if it reduces performance.

> I would first try with a full distro kernel config, just in case there's
> some another important kernel config missing.
> 
> [1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html

Tangent: have you considered getting this list archived on
https://lore.kernel.org/lists.html?

> [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath11k/pci.c#n633
> 
> -- 
> https://patchwork.kernel.org/project/linux-wireless/list/
> 
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Bjorn Helgaas]

[+cc Govind, author of 5697a564d369 ("ath11k: pci: add MSI config
initialisation")]

On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
> + linux-wireless, linux-pci, devin
> 
> Thomas Krause <thomaskrause@posteo.de> writes:
> 
> >> I had the same problem as well back in the days, for me enabling
> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
> >> mention that in the ath11k warning above :)
> >
> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
> > is behind a PCI bridge which is also disabled, could this be a
> > problem?
> >
> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
> > [Normal decode])
> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> > 	I/O behind bridge: [disabled]
> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> > 	Prefetchable memory behind bridge: [disabled]
> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
> > 	Capabilities: [90] Subsystem: Dell Device 0991
> > 	Capabilities: [a0] Power Management version 3
> > 	Capabilities: [100] Advanced Error Reporting
> > 	Capabilities: [220] Access Control Services
> > 	Capabilities: [150] Precision Time Measurement
> > 	Capabilities: [200] L1 PM Substates
> > 	Capabilities: [a00] Downstream Port Containment
> > 	Kernel driver in use: pcieport
> 
> I don't know enough about PCI to say if the bridge is a problem or not.

I don't think the bridge is an issue here.  AFAICT the bridge's I/O
and prefetchable memory windows are disabled, but the non-prefetchable
window *is* enabled and contains the space consumed by the ath11k
device:

  00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
	Memory behind bridge: 8c300000-8c3fffff [size=1M]
  56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
     Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]

> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
> PCI device where he is not having enough MSI vectors. ath11k needs 32
> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
> drivers/net/wireless/ath/ath11k/pci.c. [2]

This code is needlessly complicated.  If you absolutely need
msi_config.total_vectors and can't settle for any less, you can do
this:

  num_vectors = pci_alloc_irq_vectors(ab_pci->pdev,
                                      msi_config.total_vectors,
                                      msi_config.total_vectors,
                                      PCI_IRQ_MSI);

  if (num_vectors < 0) {
    ath11k_err(ab, "failed to get %d MSI vectors (%d)\n",
               msi_config.total_vectors, num_vectors);
    return num_vectors;
  }

But it seems a little greedy if the device can't operate at all unless
it gets 32 vectors.  Are you sure that's a hard requirement?  Most
devices can work with fewer vectors, even if it reduces performance.

> I would first try with a full distro kernel config, just in case there's
> some another important kernel config missing.
> 
> [1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html

Tangent: have you considered getting this list archived on
https://lore.kernel.org/lists.html?

> [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath11k/pci.c#n633
> 
> -- 
> https://patchwork.kernel.org/project/linux-wireless/list/
> 
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Carl Huang]

On 2020-11-03 04:57, Bjorn Helgaas wrote:
> [+cc Govind, author of 5697a564d369 ("ath11k: pci: add MSI config
> initialisation")]
> 
> On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
>> + linux-wireless, linux-pci, devin
>> 
>> Thomas Krause <thomaskrause@posteo.de> writes:
>> 
>> >> I had the same problem as well back in the days, for me enabling
>> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> >> mention that in the ath11k warning above :)
>> >
>> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
>> > is behind a PCI bridge which is also disabled, could this be a
>> > problem?
>> >
>> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
>> > [Normal decode])
>> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
>> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
>> > 	I/O behind bridge: [disabled]
>> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>> > 	Prefetchable memory behind bridge: [disabled]
>> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
>> > 	Capabilities: [90] Subsystem: Dell Device 0991
>> > 	Capabilities: [a0] Power Management version 3
>> > 	Capabilities: [100] Advanced Error Reporting
>> > 	Capabilities: [220] Access Control Services
>> > 	Capabilities: [150] Precision Time Measurement
>> > 	Capabilities: [200] L1 PM Substates
>> > 	Capabilities: [a00] Downstream Port Containment
>> > 	Kernel driver in use: pcieport
>> 
>> I don't know enough about PCI to say if the bridge is a problem or 
>> not.
> 
> I don't think the bridge is an issue here.  AFAICT the bridge's I/O
> and prefetchable memory windows are disabled, but the non-prefetchable
> window *is* enabled and contains the space consumed by the ath11k
> device:
> 
>   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
> 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
> 

Have you enabled VT-d from BIOS? This is required at least on some old 
laptops.


>> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
>> PCI device where he is not having enough MSI vectors. ath11k needs 32
>> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is 
>> new
>> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
>> drivers/net/wireless/ath/ath11k/pci.c. [2]
> 
> This code is needlessly complicated.  If you absolutely need
> msi_config.total_vectors and can't settle for any less, you can do
> this:
> 
>   num_vectors = pci_alloc_irq_vectors(ab_pci->pdev,
>                                       msi_config.total_vectors,
>                                       msi_config.total_vectors,
>                                       PCI_IRQ_MSI);
> 
>   if (num_vectors < 0) {
>     ath11k_err(ab, "failed to get %d MSI vectors (%d)\n",
>                msi_config.total_vectors, num_vectors);
>     return num_vectors;
>   }
> 
> But it seems a little greedy if the device can't operate at all unless
> it gets 32 vectors.  Are you sure that's a hard requirement?  Most
> devices can work with fewer vectors, even if it reduces performance.
> 
>> I would first try with a full distro kernel config, just in case 
>> there's
>> some another important kernel config missing.
>> 
>> [1] 
>> http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html
> 
> Tangent: have you considered getting this list archived on
> https://lore.kernel.org/lists.html?
> 
>> [2] 
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath11k/pci.c#n633
>> 
>> --
>> https://patchwork.kernel.org/project/linux-wireless/list/
>> 
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Carl Huang]

On 2020-11-03 04:57, Bjorn Helgaas wrote:
> [+cc Govind, author of 5697a564d369 ("ath11k: pci: add MSI config
> initialisation")]
> 
> On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
>> + linux-wireless, linux-pci, devin
>> 
>> Thomas Krause <thomaskrause@posteo.de> writes:
>> 
>> >> I had the same problem as well back in the days, for me enabling
>> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> >> mention that in the ath11k warning above :)
>> >
>> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
>> > is behind a PCI bridge which is also disabled, could this be a
>> > problem?
>> >
>> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
>> > [Normal decode])
>> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
>> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
>> > 	I/O behind bridge: [disabled]
>> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>> > 	Prefetchable memory behind bridge: [disabled]
>> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
>> > 	Capabilities: [90] Subsystem: Dell Device 0991
>> > 	Capabilities: [a0] Power Management version 3
>> > 	Capabilities: [100] Advanced Error Reporting
>> > 	Capabilities: [220] Access Control Services
>> > 	Capabilities: [150] Precision Time Measurement
>> > 	Capabilities: [200] L1 PM Substates
>> > 	Capabilities: [a00] Downstream Port Containment
>> > 	Kernel driver in use: pcieport
>> 
>> I don't know enough about PCI to say if the bridge is a problem or 
>> not.
> 
> I don't think the bridge is an issue here.  AFAICT the bridge's I/O
> and prefetchable memory windows are disabled, but the non-prefetchable
> window *is* enabled and contains the space consumed by the ath11k
> device:
> 
>   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
> 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
> 

Have you enabled VT-d from BIOS? This is required at least on some old 
laptops.


>> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
>> PCI device where he is not having enough MSI vectors. ath11k needs 32
>> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is 
>> new
>> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
>> drivers/net/wireless/ath/ath11k/pci.c. [2]
> 
> This code is needlessly complicated.  If you absolutely need
> msi_config.total_vectors and can't settle for any less, you can do
> this:
> 
>   num_vectors = pci_alloc_irq_vectors(ab_pci->pdev,
>                                       msi_config.total_vectors,
>                                       msi_config.total_vectors,
>                                       PCI_IRQ_MSI);
> 
>   if (num_vectors < 0) {
>     ath11k_err(ab, "failed to get %d MSI vectors (%d)\n",
>                msi_config.total_vectors, num_vectors);
>     return num_vectors;
>   }
> 
> But it seems a little greedy if the device can't operate at all unless
> it gets 32 vectors.  Are you sure that's a hard requirement?  Most
> devices can work with fewer vectors, even if it reduces performance.
> 
>> I would first try with a full distro kernel config, just in case 
>> there's
>> some another important kernel config missing.
>> 
>> [1] 
>> http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html
> 
> Tangent: have you considered getting this list archived on
> https://lore.kernel.org/lists.html?
> 
>> [2] 
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath11k/pci.c#n633
>> 
>> --
>> https://patchwork.kernel.org/project/linux-wireless/list/
>> 
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Bjorn Helgaas <helgaas@kernel.org> writes:

> [+cc Govind, author of 5697a564d369 ("ath11k: pci: add MSI config
> initialisation")]
>
> On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
>> + linux-wireless, linux-pci, devin
>> 
>> Thomas Krause <thomaskrause@posteo.de> writes:
>> 
>> >> I had the same problem as well back in the days, for me enabling
>> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> >> mention that in the ath11k warning above :)
>> >
>> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
>> > is behind a PCI bridge which is also disabled, could this be a
>> > problem?
>> >
>> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
>> > [Normal decode])
>> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
>> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
>> > 	I/O behind bridge: [disabled]
>> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>> > 	Prefetchable memory behind bridge: [disabled]
>> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
>> > 	Capabilities: [90] Subsystem: Dell Device 0991
>> > 	Capabilities: [a0] Power Management version 3
>> > 	Capabilities: [100] Advanced Error Reporting
>> > 	Capabilities: [220] Access Control Services
>> > 	Capabilities: [150] Precision Time Measurement
>> > 	Capabilities: [200] L1 PM Substates
>> > 	Capabilities: [a00] Downstream Port Containment
>> > 	Kernel driver in use: pcieport
>> 
>> I don't know enough about PCI to say if the bridge is a problem or not.
>
> I don't think the bridge is an issue here.  AFAICT the bridge's I/O
> and prefetchable memory windows are disabled, but the non-prefetchable
> window *is* enabled and contains the space consumed by the ath11k
> device:
>
>   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
> 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]

Good to know that the bridge shouldn't be the problem. Do you have any
ideas how to make more vectors available to ath11k, besides
CONFIG_IRQ_REMAP? Because QCA6390 works in Windows I doubt this is a
hardware problem.

>> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
>> PCI device where he is not having enough MSI vectors. ath11k needs 32
>> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
>> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
>> drivers/net/wireless/ath/ath11k/pci.c. [2]
>
> This code is needlessly complicated.  If you absolutely need
> msi_config.total_vectors and can't settle for any less, you can do
> this:
>
>   num_vectors = pci_alloc_irq_vectors(ab_pci->pdev,
>                                       msi_config.total_vectors,
>                                       msi_config.total_vectors,
>                                       PCI_IRQ_MSI);
>
>   if (num_vectors < 0) {
>     ath11k_err(ab, "failed to get %d MSI vectors (%d)\n",
>                msi_config.total_vectors, num_vectors);
>     return num_vectors;
>   }

True, this should be cleaned up. But of course this won't solve the
actual problem.

> But it seems a little greedy if the device can't operate at all unless
> it gets 32 vectors.  Are you sure that's a hard requirement?  Most
> devices can work with fewer vectors, even if it reduces performance.

This was my first reaction as well when I saw the code for the first
time. And the reply I got is that the firmware needs all 32 vectors, it
won't work with less.

>> I would first try with a full distro kernel config, just in case there's
>> some another important kernel config missing.
>> 
>> [1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html
>
> Tangent: have you considered getting this list archived on
> https://lore.kernel.org/lists.html?

Good point, actually I have not. I'll add both ath10k and ath11k lists
to lore. It's even more important now that lists.infradead.org had a
hard drive crash and lost years of archives.

Thanks for the help!

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Bjorn Helgaas <helgaas@kernel.org> writes:

> [+cc Govind, author of 5697a564d369 ("ath11k: pci: add MSI config
> initialisation")]
>
> On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
>> + linux-wireless, linux-pci, devin
>> 
>> Thomas Krause <thomaskrause@posteo.de> writes:
>> 
>> >> I had the same problem as well back in the days, for me enabling
>> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> >> mention that in the ath11k warning above :)
>> >
>> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
>> > is behind a PCI bridge which is also disabled, could this be a
>> > problem?
>> >
>> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
>> > [Normal decode])
>> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
>> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
>> > 	I/O behind bridge: [disabled]
>> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>> > 	Prefetchable memory behind bridge: [disabled]
>> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
>> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
>> > 	Capabilities: [90] Subsystem: Dell Device 0991
>> > 	Capabilities: [a0] Power Management version 3
>> > 	Capabilities: [100] Advanced Error Reporting
>> > 	Capabilities: [220] Access Control Services
>> > 	Capabilities: [150] Precision Time Measurement
>> > 	Capabilities: [200] L1 PM Substates
>> > 	Capabilities: [a00] Downstream Port Containment
>> > 	Kernel driver in use: pcieport
>> 
>> I don't know enough about PCI to say if the bridge is a problem or not.
>
> I don't think the bridge is an issue here.  AFAICT the bridge's I/O
> and prefetchable memory windows are disabled, but the non-prefetchable
> window *is* enabled and contains the space consumed by the ath11k
> device:
>
>   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
> 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]

Good to know that the bridge shouldn't be the problem. Do you have any
ideas how to make more vectors available to ath11k, besides
CONFIG_IRQ_REMAP? Because QCA6390 works in Windows I doubt this is a
hardware problem.

>> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
>> PCI device where he is not having enough MSI vectors. ath11k needs 32
>> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
>> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
>> drivers/net/wireless/ath/ath11k/pci.c. [2]
>
> This code is needlessly complicated.  If you absolutely need
> msi_config.total_vectors and can't settle for any less, you can do
> this:
>
>   num_vectors = pci_alloc_irq_vectors(ab_pci->pdev,
>                                       msi_config.total_vectors,
>                                       msi_config.total_vectors,
>                                       PCI_IRQ_MSI);
>
>   if (num_vectors < 0) {
>     ath11k_err(ab, "failed to get %d MSI vectors (%d)\n",
>                msi_config.total_vectors, num_vectors);
>     return num_vectors;
>   }

True, this should be cleaned up. But of course this won't solve the
actual problem.

> But it seems a little greedy if the device can't operate at all unless
> it gets 32 vectors.  Are you sure that's a hard requirement?  Most
> devices can work with fewer vectors, even if it reduces performance.

This was my first reaction as well when I saw the code for the first
time. And the reply I got is that the firmware needs all 32 vectors, it
won't work with less.

>> I would first try with a full distro kernel config, just in case there's
>> some another important kernel config missing.
>> 
>> [1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html
>
> Tangent: have you considered getting this list archived on
> https://lore.kernel.org/lists.html?

Good point, actually I have not. I'll add both ath10k and ath11k lists
to lore. It's even more important now that lists.infradead.org had a
hard drive crash and lost years of archives.

Thanks for the help!

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Devin Bayer]

On 02/11/2020 21.57, Bjorn Helgaas wrote:
>>>
>>> CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
>>> is behind a PCI bridge which is also disabled, could this be a
>>> problem?

Just to provide another case, I have the same issue with this driver.

CONFIG_IRQ_REMAP=y and doesn't have any effect.

I'm unsure if the issue could be my system (Atom / Intel J1900) or the
that I'm using a slightly different card. Is there anyway to tell from the
lspci output? Here is what I guess is most relevant:

00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) (prog-if 00 [Normal decode])
        Memory behind bridge: d0000000-d0ffffff [size=16M]
        Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee08004  Data: 4021

03:00.0 Unassigned class [ff00]: Qualcomm Device 1101
        Subsystem: Qualcomm Device 0108
        Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=16M]
        Capabilities: [50] MSI: Enable+ Count=1/32 Maskable+ 64bit-
                Address: fee01004  Data: 40ef
                Masking: ffffffff  Pending: 00000000
        Capabilities: [70] Express (v2) Endpoint, MSI 00

Thanks,
Devin

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Devin Bayer]

On 02/11/2020 21.57, Bjorn Helgaas wrote:
>>>
>>> CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
>>> is behind a PCI bridge which is also disabled, could this be a
>>> problem?

Just to provide another case, I have the same issue with this driver.

CONFIG_IRQ_REMAP=y and doesn't have any effect.

I'm unsure if the issue could be my system (Atom / Intel J1900) or the
that I'm using a slightly different card. Is there anyway to tell from the
lspci output? Here is what I guess is most relevant:

00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 0e) (prog-if 00 [Normal decode])
        Memory behind bridge: d0000000-d0ffffff [size=16M]
        Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee08004  Data: 4021

03:00.0 Unassigned class [ff00]: Qualcomm Device 1101
        Subsystem: Qualcomm Device 0108
        Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=16M]
        Capabilities: [50] MSI: Enable+ Count=1/32 Maskable+ 64bit-
                Address: fee01004  Data: 40ef
                Masking: ffffffff  Pending: 00000000
        Capabilities: [70] Express (v2) Endpoint, MSI 00

Thanks,
Devin

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Bjorn Helgaas]

[+cc Thomas, Christoph for question about not enough MSI IRQ vectors]

On Tue, Nov 03, 2020 at 08:49:06AM +0200, Kalle Valo wrote:
> Bjorn Helgaas <helgaas@kernel.org> writes:
> > On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
> >> + linux-wireless, linux-pci, devin
> >> 
> >> Thomas Krause <thomaskrause@posteo.de> writes:
> >> 
> >> >> I had the same problem as well back in the days, for me enabling
> >> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
> >> >> mention that in the ath11k warning above :)
> >> >
> >> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
> >> > is behind a PCI bridge which is also disabled, could this be a
> >> > problem?
> >> >
> >> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
> >> > [Normal decode])
> >> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
> >> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> >> > 	I/O behind bridge: [disabled]
> >> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> >> > 	Prefetchable memory behind bridge: [disabled]
> >> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
> >> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
> >> > 	Capabilities: [90] Subsystem: Dell Device 0991
> >> > 	Capabilities: [a0] Power Management version 3
> >> > 	Capabilities: [100] Advanced Error Reporting
> >> > 	Capabilities: [220] Access Control Services
> >> > 	Capabilities: [150] Precision Time Measurement
> >> > 	Capabilities: [200] L1 PM Substates
> >> > 	Capabilities: [a00] Downstream Port Containment
> >> > 	Kernel driver in use: pcieport
> >> 
> >> I don't know enough about PCI to say if the bridge is a problem or not.
> >
> > I don't think the bridge is an issue here.  AFAICT the bridge's I/O
> > and prefetchable memory windows are disabled, but the non-prefetchable
> > window *is* enabled and contains the space consumed by the ath11k
> > device:
> >
> >   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> >   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
> >      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
> 
> Good to know that the bridge shouldn't be the problem. Do you have any
> ideas how to make more vectors available to ath11k, besides
> CONFIG_IRQ_REMAP? Because QCA6390 works in Windows I doubt this is a
> hardware problem.
> 
> >> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
> >> PCI device where he is not having enough MSI vectors. ath11k needs 32
> >> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
> >> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
> >> drivers/net/wireless/ath/ath11k/pci.c. [2]

> > But it seems a little greedy if the device can't operate at all unless
> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
> > devices can work with fewer vectors, even if it reduces performance.
> 
> This was my first reaction as well when I saw the code for the first
> time. And the reply I got is that the firmware needs all 32 vectors, it
> won't work with less.

I do see a couple other drivers that are completely inflexible (they
request min==max).  But I don't know the system constraint you're
hitting.  CC'd Thomas & Christoph in case they have time to give us a
hint.

> >> I would first try with a full distro kernel config, just in case there's
> >> some another important kernel config missing.
> >> 
> >> [1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html
> >
> > Tangent: have you considered getting this list archived on
> > https://lore.kernel.org/lists.html?
> 
> Good point, actually I have not. I'll add both ath10k and ath11k lists
> to lore. It's even more important now that lists.infradead.org had a
> hard drive crash and lost years of archives.

Or you could just add linux-wireless, e.g.,

  L:      ath11k@lists.infradead.org
  L:      linux-wireless@vger.kernel.org

or even consider moving from ath10k and ath11k to
linux-wireless@vger.kernel.org.  I think there's some value in
consolidating low-volume lists.  It looks like ath11k had < 90
messages for all of October.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Bjorn Helgaas]

[+cc Thomas, Christoph for question about not enough MSI IRQ vectors]

On Tue, Nov 03, 2020 at 08:49:06AM +0200, Kalle Valo wrote:
> Bjorn Helgaas <helgaas@kernel.org> writes:
> > On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
> >> + linux-wireless, linux-pci, devin
> >> 
> >> Thomas Krause <thomaskrause@posteo.de> writes:
> >> 
> >> >> I had the same problem as well back in the days, for me enabling
> >> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
> >> >> mention that in the ath11k warning above :)
> >> >
> >> > CONFIG_IRQ_REMAP did not do the trick. I noticed that the Wi-Fi card
> >> > is behind a PCI bridge which is also disabled, could this be a
> >> > problem?
> >> >
> >> > 00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00
> >> > [Normal decode])
> >> > 	Flags: bus master, fast devsel, latency 0, IRQ 123
> >> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> >> > 	I/O behind bridge: [disabled]
> >> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> >> > 	Prefetchable memory behind bridge: [disabled]
> >> > 	Capabilities: [40] Express Root Port (Slot+), MSI 00
> >> > 	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
> >> > 	Capabilities: [90] Subsystem: Dell Device 0991
> >> > 	Capabilities: [a0] Power Management version 3
> >> > 	Capabilities: [100] Advanced Error Reporting
> >> > 	Capabilities: [220] Access Control Services
> >> > 	Capabilities: [150] Precision Time Measurement
> >> > 	Capabilities: [200] L1 PM Substates
> >> > 	Capabilities: [a00] Downstream Port Containment
> >> > 	Kernel driver in use: pcieport
> >> 
> >> I don't know enough about PCI to say if the bridge is a problem or not.
> >
> > I don't think the bridge is an issue here.  AFAICT the bridge's I/O
> > and prefetchable memory windows are disabled, but the non-prefetchable
> > window *is* enabled and contains the space consumed by the ath11k
> > device:
> >
> >   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
> >   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
> >      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
> 
> Good to know that the bridge shouldn't be the problem. Do you have any
> ideas how to make more vectors available to ath11k, besides
> CONFIG_IRQ_REMAP? Because QCA6390 works in Windows I doubt this is a
> hardware problem.
> 
> >> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
> >> PCI device where he is not having enough MSI vectors. ath11k needs 32
> >> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
> >> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
> >> drivers/net/wireless/ath/ath11k/pci.c. [2]

> > But it seems a little greedy if the device can't operate at all unless
> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
> > devices can work with fewer vectors, even if it reduces performance.
> 
> This was my first reaction as well when I saw the code for the first
> time. And the reply I got is that the firmware needs all 32 vectors, it
> won't work with less.

I do see a couple other drivers that are completely inflexible (they
request min==max).  But I don't know the system constraint you're
hitting.  CC'd Thomas & Christoph in case they have time to give us a
hint.

> >> I would first try with a full distro kernel config, just in case there's
> >> some another important kernel config missing.
> >> 
> >> [1] http://lists.infradead.org/pipermail/ath11k/2020-October/000466.html
> >
> > Tangent: have you considered getting this list archived on
> > https://lore.kernel.org/lists.html?
> 
> Good point, actually I have not. I'll add both ath10k and ath11k lists
> to lore. It's even more important now that lists.infradead.org had a
> hard drive crash and lost years of archives.

Or you could just add linux-wireless, e.g.,

  L:      ath11k@lists.infradead.org
  L:      linux-wireless@vger.kernel.org

or even consider moving from ath10k and ath11k to
linux-wireless@vger.kernel.org.  I think there's some value in
consolidating low-volume lists.  It looks like ath11k had < 90
messages for all of October.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
> On Tue, Nov 03, 2020 at 08:49:06AM +0200, Kalle Valo wrote:
>> Bjorn Helgaas <helgaas@kernel.org> writes:
>> > On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
>> >> Thomas Krause <thomaskrause@posteo.de> writes:
>> >> 
>> >> >> I had the same problem as well back in the days, for me enabling
>> >> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> >> >> mention that in the ath11k warning above :)

Interrupt remapping only helps when the device supports only MSI (not
MSI-X) because x86 (kernel) does not support multiple MSI interrupts
without remapping.

So if only MSI is available then you get exactly _one_ MSI vector
without remapping.

>> >> > CONFIG_IRQ_REMAP did not do the trick.

The config alone does not help. The hardware has to support it and the
BIOS has to enable it.

Check the BIOS for a switch which is named 'VT-d' or such. It might
depend on 'Intel Virtualization Technology' or such.

>> >   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
>> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
>> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>> >   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>> >      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]

So I grabbed the PCI info from the link and it has:

     Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit-

So no MSI-X, ergo only one MSI interrupt without remapping.
 
>> >> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
>> >> PCI device where he is not having enough MSI vectors. ath11k needs 32
>> >> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
>> >> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
>> >> drivers/net/wireless/ath/ath11k/pci.c. [2]
>
>> > But it seems a little greedy if the device can't operate at all unless
>> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
>> > devices can work with fewer vectors, even if it reduces performance.

Right, even most high end network cards work with one interrupt.

>> This was my first reaction as well when I saw the code for the first
>> time. And the reply I got is that the firmware needs all 32 vectors, it
>> won't work with less.

Great design.

> I do see a couple other drivers that are completely inflexible (they
> request min==max).  But I don't know the system constraint you're
> hitting.  CC'd Thomas & Christoph in case they have time to give us a
> hint.

Can I have a full dmesg please?

Please enable CONFIG_IRQ_REMAP and CONFIG_INTEL_IOMMU (not strictly
required, but it's a Dell BIOS after all). Also set
CONFIG_INTEL_IOMMU_DEFAULT_ON.

Or simply try a distro kernel.

Thanks,

        tglx

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
> On Tue, Nov 03, 2020 at 08:49:06AM +0200, Kalle Valo wrote:
>> Bjorn Helgaas <helgaas@kernel.org> writes:
>> > On Mon, Nov 02, 2020 at 08:49:51PM +0200, Kalle Valo wrote:
>> >> Thomas Krause <thomaskrause@posteo.de> writes:
>> >> 
>> >> >> I had the same problem as well back in the days, for me enabling
>> >> >> CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
>> >> >> mention that in the ath11k warning above :)

Interrupt remapping only helps when the device supports only MSI (not
MSI-X) because x86 (kernel) does not support multiple MSI interrupts
without remapping.

So if only MSI is available then you get exactly _one_ MSI vector
without remapping.

>> >> > CONFIG_IRQ_REMAP did not do the trick.

The config alone does not help. The hardware has to support it and the
BIOS has to enable it.

Check the BIOS for a switch which is named 'VT-d' or such. It might
depend on 'Intel Virtualization Technology' or such.

>> >   00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20)
>> > 	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
>> > 	Memory behind bridge: 8c300000-8c3fffff [size=1M]
>> >   56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
>> >      Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]

So I grabbed the PCI info from the link and it has:

     Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit-

So no MSI-X, ergo only one MSI interrupt without remapping.
 
>> >> To summarise: Thomas is reporting[1] a problem with ath11k on QCA6390
>> >> PCI device where he is not having enough MSI vectors. ath11k needs 32
>> >> vectors but pci_alloc_irq_vectors() returns -ENOSPC. PCI support is new
>> >> for ath11k and introduced in v5.10-rc1. The irq allocation code is in
>> >> drivers/net/wireless/ath/ath11k/pci.c. [2]
>
>> > But it seems a little greedy if the device can't operate at all unless
>> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
>> > devices can work with fewer vectors, even if it reduces performance.

Right, even most high end network cards work with one interrupt.

>> This was my first reaction as well when I saw the code for the first
>> time. And the reply I got is that the firmware needs all 32 vectors, it
>> won't work with less.

Great design.

> I do see a couple other drivers that are completely inflexible (they
> request min==max).  But I don't know the system constraint you're
> hitting.  CC'd Thomas & Christoph in case they have time to give us a
> hint.

Can I have a full dmesg please?

Please enable CONFIG_IRQ_REMAP and CONFIG_INTEL_IOMMU (not strictly
required, but it's a Dell BIOS after all). Also set
CONFIG_INTEL_IOMMU_DEFAULT_ON.

Or simply try a distro kernel.

Thanks,

        tglx

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Tue, Nov 03 2020 at 22:08, Thomas Gleixner wrote:
> On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
>>> > But it seems a little greedy if the device can't operate at all unless
>>> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
>>> > devices can work with fewer vectors, even if it reduces performance.
>
> Right, even most high end network cards work with one interrupt.
>
>>> This was my first reaction as well when I saw the code for the first
>>> time. And the reply I got is that the firmware needs all 32 vectors, it
>>> won't work with less.
>
> Great design.

Just to put more information to this:

Enforcing 32 vectors with MSI is beyond silly. Due to the limitations of
MSI all of these vectors will be affine to a single CPU unless irq
remapping is available and enabled.

So if irq remapping is not enabled, then what are the 32 vectors buying?
Exactly nothing because they just compete to be handled on the very same
CPU. If the design requires more than one vector, then this should be
done with MSI-X (which allows individual affinities and individual
masking).

That's known for 20 years and MSI-X exists for exactly that reason. But
hardware people still insist on implementing MSI (probably because it
saves 0.002$ per chip).

But there is also the firmware side. Enforcing the availability of 32
vectors on MSI is silly to begin with as explained above, but it's also
silly given the constraints of the x86 vector space. It takes just 6
devices having the same 32 vector requirement to exhaust it. Oh well...

Thanks,

        tglx

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Tue, Nov 03 2020 at 22:08, Thomas Gleixner wrote:
> On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
>>> > But it seems a little greedy if the device can't operate at all unless
>>> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
>>> > devices can work with fewer vectors, even if it reduces performance.
>
> Right, even most high end network cards work with one interrupt.
>
>>> This was my first reaction as well when I saw the code for the first
>>> time. And the reply I got is that the firmware needs all 32 vectors, it
>>> won't work with less.
>
> Great design.

Just to put more information to this:

Enforcing 32 vectors with MSI is beyond silly. Due to the limitations of
MSI all of these vectors will be affine to a single CPU unless irq
remapping is available and enabled.

So if irq remapping is not enabled, then what are the 32 vectors buying?
Exactly nothing because they just compete to be handled on the very same
CPU. If the design requires more than one vector, then this should be
done with MSI-X (which allows individual affinities and individual
masking).

That's known for 20 years and MSI-X exists for exactly that reason. But
hardware people still insist on implementing MSI (probably because it
saves 0.002$ per chip).

But there is also the firmware side. Enforcing the availability of 32
vectors on MSI is silly to begin with as explained above, but it's also
silly given the constraints of the x86 vector space. It takes just 6
devices having the same 32 vector requirement to exhaust it. Oh well...

Thanks,

        tglx









-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]


> Can I have a full dmesg please?
>
> Please enable CONFIG_IRQ_REMAP and CONFIG_INTEL_IOMMU (not strictly
> required, but it's a Dell BIOS after all). Also set
> CONFIG_INTEL_IOMMU_DEFAULT_ON.

I attached a full dmesg with the latest ath11k master and the 
configuration enabled. VT-d was enabled in BIOS. Most options have been 
already been present in the previous attempts (copied from the distro 
config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
hope this helps, if there is more I can do to debug it on my side I'm 
happy to do so.


[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 83128 bytes --]

[    0.000000] Linux version 5.10.0-rc1-wt-ath+ (thomas@tk-9310) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #1 SMP Wed Nov 4 12:19:14 CET 2020
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-rc1-wt-ath+ root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000]   zhaoxin   Shanghai  
[    0.000000] x86/split lock detection: warning about user-space split_locks
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
[    0.000000] x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
[    0.000000] x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
[    0.000000] x86/fpu: xstate_offset[9]: 2432, xstate_sizes[9]:    8
[    0.000000] x86/fpu: Enabled xstate features 0x2e7, context size is 2440 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005f72afff] usable
[    0.000000] BIOS-e820: [mem 0x000000005f72b000-0x0000000063510fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000063511000-0x0000000063d71fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000063d72000-0x0000000063ffefff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000063fff000-0x0000000063ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000064000000-0x0000000067ffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000068600000-0x00000000687fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000069000000-0x00000000707fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000088f7fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.70 by Dell
[    0.000000] efi: ACPI=0x63ffe000 ACPI 2.0=0x63ffe014 SMBIOS=0x5fdd7000 TPMFinalLog=0x63cd8000 ESRT=0x5fcecd18 MEMATTR=0x588b3018 RNG=0x5fcf0f98 TPMEventLog=0x5ad43018 
[    0.000000] efi: seeding entropy pool
[    0.000000] random: fast init done
[    0.000000] SMBIOS 3.2 present.
[    0.000000] DMI: Dell Inc. XPS 13 9310/0F7M4C, BIOS 1.1.1 10/05/2020
[    0.000000] tsc: Detected 2800.000 MHz processor
[    0.000000] tsc: Detected 2803.200 MHz TSC
[    0.000004] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000005] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000009] last_pfn = 0x88f800 max_arch_pfn = 0x400000000
[    0.000011] MTRR default type: write-back
[    0.000011] MTRR fixed ranges enabled:
[    0.000012]   00000-9FFFF write-back
[    0.000012]   A0000-BFFFF uncachable
[    0.000013]   C0000-FFFFF write-protect
[    0.000013] MTRR variable ranges enabled:
[    0.000014]   0 base 0080000000 mask 7F80000000 uncachable
[    0.000015]   1 base 0070000000 mask 7FF0000000 uncachable
[    0.000015]   2 base 006C000000 mask 7FFC000000 uncachable
[    0.000016]   3 base 2000000000 mask 6000000000 uncachable
[    0.000016]   4 base 1000000000 mask 7000000000 uncachable
[    0.000016]   5 base 4000000000 mask 4000000000 uncachable
[    0.000017]   6 disabled
[    0.000017]   7 disabled
[    0.000017]   8 disabled
[    0.000018]   9 disabled
[    0.000450] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.000802] last_pfn = 0x64000 max_arch_pfn = 0x400000000
[    0.007947] esrt: Reserving ESRT space from 0x000000005fcecd18 to 0x000000005fcecda0.
[    0.007956] check: Scanning 1 areas for low memory corruption
[    0.007960] Using GB pages for direct mapping
[    0.008076] Secure boot disabled
[    0.008076] RAMDISK: [mem 0x22f82000-0x28496fff]
[    0.008091] ACPI: Early table checksum verification disabled
[    0.008094] ACPI: RSDP 0x0000000063FFE014 000024 (v02 DELL  )
[    0.008097] ACPI: XSDT 0x0000000063F79188 00010C (v01 DELL   Dell Inc 00000002      01000013)
[    0.008102] ACPI: FACP 0x0000000063FF5000 000114 (v06 DELL   Dell Inc 00000002      01000013)
[    0.008106] ACPI: DSDT 0x0000000063F98000 05903E (v02 DELL   Dell Inc 00000002      01000013)
[    0.008108] ACPI: FACS 0x0000000063D1B000 000040
[    0.008110] ACPI: SSDT 0x0000000063FFA000 00255D (v02 CpuRef CpuSsdt  00003000 INTL 20191018)
[    0.008112] ACPI: SSDT 0x0000000063FF6000 0038E4 (v02 DptfTb DptfTabl 00001000 INTL 20191018)
[    0.008114] ACPI: HPET 0x0000000063FF4000 000038 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008116] ACPI: APIC 0x0000000063FF3000 00012C (v04 DELL   Dell Inc 00000002      01000013)
[    0.008118] ACPI: MCFG 0x0000000063FF2000 00003C (v01 DELL   Dell Inc 00000002      01000013)
[    0.008120] ACPI: SSDT 0x0000000063F97000 000D01 (v02 DELL   DellRtd3 00001000 INTL 20191018)
[    0.008121] ACPI: NHLT 0x0000000063F95000 001B54 (v00 DELL   Dell Inc 00000002      01000013)
[    0.008123] ACPI: SSDT 0x0000000063F92000 002BB5 (v02 SaSsdt SaSsdt   00003000 INTL 20191018)
[    0.008125] ACPI: SSDT 0x0000000063F90000 0012AA (v02 INTEL  IgfxSsdt 00003000 INTL 20191018)
[    0.008127] ACPI: SSDT 0x0000000063F84000 00B192 (v02 INTEL  TcssSsdt 00001000 INTL 20191018)
[    0.008129] ACPI: SSDT 0x0000000063F83000 000CD2 (v02 DELL   UsbCTabl 00001000 INTL 20191018)
[    0.008131] ACPI: LPIT 0x0000000063F82000 0000CC (v01 DELL   Dell Inc 00000002      01000013)
[    0.008133] ACPI: WSMT 0x0000000063F81000 000028 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008135] ACPI: SSDT 0x0000000063F80000 000B75 (v02 DELL   PtidDevc 00001000 INTL 20191018)
[    0.008137] ACPI: SSDT 0x0000000063F7F000 00012A (v02 DELL   TbtTypeC 00000000 INTL 20191018)
[    0.008139] ACPI: DBGP 0x0000000063F7E000 000034 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008141] ACPI: DBG2 0x0000000063F7D000 000054 (v00 DELL   Dell Inc 00000002      01000013)
[    0.008143] ACPI: SLIC 0x0000000063F7C000 000176 (v03 DELL   CBX3     06222004 MSFT 00010013)
[    0.008144] ACPI: BOOT 0x0000000063F7B000 000028 (v01 DELL   CBX3     00000002      01000013)
[    0.008146] ACPI: SSDT 0x0000000063F7A000 00060E (v02 DELL   Tpm2Tabl 00001000 INTL 20191018)
[    0.008148] ACPI: TPM2 0x0000000063FFD000 00004C (v04 DELL   Dell Inc 00000002      01000013)
[    0.008150] ACPI: MSDM 0x0000000063F78000 000055 (v03 DELL   CBX3     06222004 AMI  00010013)
[    0.008152] ACPI: DMAR 0x0000000063F77000 0000A8 (v02 INTEL  Dell Inc 00000002      01000013)
[    0.008154] ACPI: SSDT 0x0000000063F76000 000841 (v02 DELL   xh_Dell_ 00000000 INTL 20191018)
[    0.008156] ACPI: SSDT 0x0000000063F75000 000144 (v02 Intel  ADebTabl 00001000 INTL 20191018)
[    0.008158] ACPI: PTDT 0x0000000063F74000 000D44 (v00 DELL   Dell Inc 00000005 MSFT 0100000D)
[    0.008160] ACPI: BGRT 0x0000000063F73000 000038 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008162] ACPI: FPDT 0x0000000063F72000 000034 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008168] ACPI: Local APIC address 0xfee00000
[    0.008441] No NUMA configuration found
[    0.008441] Faking a node at [mem 0x0000000000000000-0x000000088f7fffff]
[    0.008447] NODE_DATA(0) allocated [mem 0x88f7d6000-0x88f7fffff]
[    0.008637] Zone ranges:
[    0.008638]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.008638]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.008639]   Normal   [mem 0x0000000100000000-0x000000088f7fffff]
[    0.008640]   Device   empty
[    0.008641] Movable zone start for each node
[    0.008643] Early memory node ranges
[    0.008643]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.008644]   node   0: [mem 0x0000000000100000-0x000000005f72afff]
[    0.008644]   node   0: [mem 0x0000000063fff000-0x0000000063ffffff]
[    0.008645]   node   0: [mem 0x0000000100000000-0x000000088f7fffff]
[    0.008929] Zeroed struct page in unavailable ranges: 37174 pages
[    0.008931] Initmem setup node 0 [mem 0x0000000000001000-0x000000088f7fffff]
[    0.008932] On node 0 totalpages: 8318666
[    0.008933]   DMA zone: 64 pages used for memmap
[    0.008933]   DMA zone: 22 pages reserved
[    0.008934]   DMA zone: 3998 pages, LIFO batch:0
[    0.008957]   DMA32 zone: 6045 pages used for memmap
[    0.008958]   DMA32 zone: 386860 pages, LIFO batch:63
[    0.010805]   Normal zone: 123872 pages used for memmap
[    0.010805]   Normal zone: 7927808 pages, LIFO batch:63
[    0.046187] Reserving Intel graphics memory at [mem 0x6c800000-0x707fffff]
[    0.046975] ACPI: PM-Timer IO Port: 0x1808
[    0.046976] ACPI: Local APIC address 0xfee00000
[    0.046981] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.046982] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.046982] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.046982] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.046983] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.046983] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.046983] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.046984] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.046984] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
[    0.046984] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
[    0.046985] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
[    0.046985] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
[    0.046985] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
[    0.046986] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
[    0.046986] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
[    0.046986] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
[    0.047022] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[    0.047023] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.047024] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.047025] ACPI: IRQ0 used by override.
[    0.047026] ACPI: IRQ9 used by override.
[    0.047027] Using ACPI (MADT) for SMP configuration information
[    0.047028] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.047033] e820: update [mem 0x5ad50000-0x5ad6dfff] usable ==> reserved
[    0.047038] TSC deadline timer available
[    0.047038] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[    0.047046] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.047047] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
[    0.047047] PM: hibernation: Registered nosave memory: [mem 0x5ad50000-0x5ad6dfff]
[    0.047048] PM: hibernation: Registered nosave memory: [mem 0x5f72b000-0x63510fff]
[    0.047049] PM: hibernation: Registered nosave memory: [mem 0x63511000-0x63d71fff]
[    0.047049] PM: hibernation: Registered nosave memory: [mem 0x63d72000-0x63ffefff]
[    0.047050] PM: hibernation: Registered nosave memory: [mem 0x64000000-0x67ffffff]
[    0.047050] PM: hibernation: Registered nosave memory: [mem 0x68000000-0x685fffff]
[    0.047050] PM: hibernation: Registered nosave memory: [mem 0x68600000-0x687fffff]
[    0.047051] PM: hibernation: Registered nosave memory: [mem 0x68800000-0x68ffffff]
[    0.047051] PM: hibernation: Registered nosave memory: [mem 0x69000000-0x707fffff]
[    0.047051] PM: hibernation: Registered nosave memory: [mem 0x70800000-0xbfffffff]
[    0.047052] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xcfffffff]
[    0.047052] PM: hibernation: Registered nosave memory: [mem 0xd0000000-0xfed1ffff]
[    0.047052] PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xfed7ffff]
[    0.047053] PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfeffffff]
[    0.047053] PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
[    0.047054] [mem 0x70800000-0xbfffffff] available for PCI devices
[    0.047055] Booting paravirtualized kernel on bare hardware
[    0.047056] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.047060] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
[    0.047164] percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144
[    0.047167] pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152
[    0.047168] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
[    0.047182] Built 1 zonelists, mobility grouping on.  Total pages: 8188663
[    0.047183] Policy zone: Normal
[    0.047183] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-rc1-wt-ath+ root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
[    0.048019] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[    0.048423] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.048474] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!
               BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version: 
[    0.091268] Memory: 32407176K/33274664K available (14345K kernel code, 3506K rwdata, 5212K rodata, 2636K init, 6000K bss, 867228K reserved, 0K cma-reserved)
[    0.091273] random: get_random_u64 called from __kmem_cache_create+0x2d/0x540 with crng_init=1
[    0.091351] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.091358] ftrace: allocating 46263 entries in 181 pages
[    0.100864] ftrace: allocated 181 pages with 5 groups
[    0.100940] rcu: Hierarchical RCU implementation.
[    0.100941] rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
[    0.100942] 	Rude variant of Tasks RCU enabled.
[    0.100942] 	Tracing variant of Tasks RCU enabled.
[    0.100943] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.100943] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.102847] NR_IRQS: 524544, nr_irqs: 2048, preallocated irqs: 16
[    0.103281] random: crng done (trusting CPU's manufacturer)
[    0.103295] Console: colour dummy device 80x25
[    0.103303] printk: console [tty0] enabled
[    0.103314] ACPI: Core revision 20200925
[    0.103583] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 99544814920 ns
[    0.103691] APIC: Switch to symmetric I/O mode setup
[    0.103693] DMAR: Host address width 39
[    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 69e2ff0505e
[    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
[    0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
[    0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
[    0.103707] DMAR: Parse DMAR table failure.
[    0.104980] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.109990] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.127643] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x28680fa287f, max_idle_ns: 440795281151 ns
[    0.127646] Calibrating delay loop (skipped), value calculated using timer frequency.. 5606.40 BogoMIPS (lpj=11212800)
[    0.127648] pid_max: default: 32768 minimum: 301
[    0.129518] LSM: Security Framework initializing
[    0.129527] Yama: becoming mindful.
[    0.129556] AppArmor: AppArmor initialized
[    0.129625] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.129682] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.129857] x86/cpu: User Mode Instruction Prevention (UMIP) activated
[    0.129885] mce: CPU0: Thermal monitoring enabled (TM1)
[    0.129950] process: using mwait in idle threads
[    0.129951] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.129952] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.129954] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.129955] Spectre V2 : Mitigation: Enhanced IBRS
[    0.129955] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.129957] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.129957] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.130177] Freeing SMP alternatives memory: 40K
[    0.131733] smpboot: CPU0: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (family: 0x6, model: 0x8c, stepping: 0x1)
[    0.131801] Performance Events: PEBS fmt4+-baseline, Icelake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.131808] ... version:                5
[    0.131808] ... bit width:              48
[    0.131808] ... generic registers:      8
[    0.131809] ... value mask:             0000ffffffffffff
[    0.131809] ... max period:             00007fffffffffff
[    0.131809] ... fixed-purpose events:   4
[    0.131810] ... event mask:             0001000f000000ff
[    0.131857] rcu: Hierarchical SRCU implementation.
[    0.132296] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.132345] smp: Bringing up secondary CPUs ...
[    0.132390] x86: Booting SMP configuration:
[    0.132391] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
[    0.141093] smp: Brought up 1 node, 8 CPUs
[    0.141093] smpboot: Max logical packages: 1
[    0.141093] smpboot: Total of 8 processors activated (44851.20 BogoMIPS)
[    0.144518] devtmpfs: initialized
[    0.144518] x86/mm: Memory block size: 128MB
[    0.144701] PM: Registering ACPI NVS region [mem 0x63511000-0x63d71fff] (8785920 bytes)
[    0.144701] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.144701] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[    0.144701] pinctrl core: initialized pinctrl subsystem
[    0.144701] PM: RTC time: 12:34:09, date: 2020-11-04
[    0.144701] NET: Registered protocol family 16
[    0.144701] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
[    0.144701] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.144723] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.144728] audit: initializing netlink subsys (disabled)
[    0.144733] audit: type=2000 audit(1604493249.040:1): state=initialized audit_enabled=0 res=1
[    0.144733] thermal_sys: Registered thermal governor 'fair_share'
[    0.144733] thermal_sys: Registered thermal governor 'bang_bang'
[    0.144733] thermal_sys: Registered thermal governor 'step_wise'
[    0.144733] thermal_sys: Registered thermal governor 'user_space'
[    0.144733] thermal_sys: Registered thermal governor 'power_allocator'
[    0.144733] EISA bus registered
[    0.144733] cpuidle: using governor ladder
[    0.144733] cpuidle: using governor menu
[    0.144733] Simple Boot Flag at 0x47 set to 0x80
[    0.144733] ACPI: bus type PCI registered
[    0.144733] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.144733] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xc0000000-0xcfffffff] (base 0xc0000000)
[    0.144733] PCI: MMCONFIG at [mem 0xc0000000-0xcfffffff] reserved in E820
[    0.144733] PCI: Using configuration type 1 for base access
[    0.147650] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.148275] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.148275] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.148275] ACPI: Added _OSI(Module Device)
[    0.148275] ACPI: Added _OSI(Processor Device)
[    0.148275] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.148275] ACPI: Added _OSI(Processor Aggregator Device)
[    0.148275] ACPI: Added _OSI(Linux-Dell-Video)
[    0.148275] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.148275] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.202420] ACPI: 13 ACPI AML tables successfully acquired and loaded
[    0.215261] ACPI: Dynamic OEM Table Load:
[    0.215268] ACPI: SSDT 0xFFFF934700DF7E00 0001CB (v02 PmRef  Cpu0Psd  00003000 INTL 20191018)
[    0.216201] ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
[    0.218127] ACPI: Dynamic OEM Table Load:
[    0.218131] ACPI: SSDT 0xFFFF934700DB5400 000394 (v02 PmRef  Cpu0Cst  00003001 INTL 20191018)
[    0.219215] ACPI: Dynamic OEM Table Load:
[    0.219219] ACPI: SSDT 0xFFFF9347015C6800 000647 (v02 PmRef  Cpu0Ist  00003000 INTL 20191018)
[    0.220376] ACPI: Dynamic OEM Table Load:
[    0.220380] ACPI: SSDT 0xFFFF934700DB6C00 000266 (v02 PmRef  Cpu0Hwp  00003000 INTL 20191018)
[    0.221595] ACPI: Dynamic OEM Table Load:
[    0.221599] ACPI: SSDT 0xFFFF93470013A000 0008E7 (v02 PmRef  ApIst    00003000 INTL 20191018)
[    0.222798] ACPI: Dynamic OEM Table Load:
[    0.222801] ACPI: SSDT 0xFFFF9347015C3000 00048A (v02 PmRef  ApHwp    00003000 INTL 20191018)
[    0.223913] ACPI: Dynamic OEM Table Load:
[    0.223916] ACPI: SSDT 0xFFFF9347015C4000 0004D2 (v02 PmRef  ApPsd    00003000 INTL 20191018)
[    0.225037] ACPI: Dynamic OEM Table Load:
[    0.225040] ACPI: SSDT 0xFFFF9347015C7000 00048A (v02 PmRef  ApCst    00003000 INTL 20191018)
[    0.229625] ACPI: EC: EC started
[    0.229625] ACPI: EC: interrupt blocked
[    0.232144] ACPI: EC: EC_CMD/EC_SC=0x934, EC_DATA=0x930
[    0.232145] ACPI: \_SB_.PC00.LPCB.ECDV: Boot DSDT EC used to handle transactions
[    0.232145] ACPI: Interpreter enabled
[    0.232186] ACPI: (supports S0 S4 S5)
[    0.232187] ACPI: Using IOAPIC for interrupt routing
[    0.232222] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.233868] ACPI: Enabled 8 GPEs in block 00 to 7F
[    0.239996] ACPI: Power Resource [WRST] (on)
[    0.240014] ACPI: Power Resource [DRST] (on)
[    0.245952] ACPI: Power Resource [V0PR] (on)
[    0.246062] ACPI: Power Resource [V1PR] (on)
[    0.246166] ACPI: Power Resource [V2PR] (on)
[    0.249717] ACPI: Power Resource [WRST] (on)
[    0.257257] ACPI: Power Resource [TBT0] (on)
[    0.257292] ACPI: Power Resource [TBT1] (on)
[    0.257319] ACPI: Power Resource [D3C] (on)
[    0.497199] ACPI: Power Resource [PIN] (off)
[    0.497496] ACPI: PCI Root Bridge [PC00] (domain 0000 [bus 00-fe])
[    0.497500] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.499133] acpi PNP0A08:00: _OSC: platform does not support [AER]
[    0.502179] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability LTR]
[    0.505031] PCI host bridge to bus 0000:00
[    0.505032] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.505033] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.505033] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.505034] pci_bus 0000:00: root bus resource [mem 0x70800000-0xbfffffff window]
[    0.505034] pci_bus 0000:00: root bus resource [mem 0x4000000000-0x7fffffffff window]
[    0.505035] pci_bus 0000:00: root bus resource [bus 00-fe]
[    0.505059] pci 0000:00:00.0: [8086:9a14] type 00 class 0x060000
[    0.506292] pci 0000:00:02.0: [8086:9a49] type 00 class 0x030000
[    0.506300] pci 0000:00:02.0: reg 0x10: [mem 0x603c000000-0x603cffffff 64bit]
[    0.506304] pci 0000:00:02.0: reg 0x18: [mem 0x4000000000-0x400fffffff 64bit pref]
[    0.506307] pci 0000:00:02.0: reg 0x20: [io  0x3000-0x303f]
[    0.506320] pci 0000:00:02.0: BAR 2: assigned to efifb
[    0.506321] pci 0000:00:02.0: DMAR: Skip IOMMU disabling for graphics
[    0.506344] pci 0000:00:02.0: reg 0x344: [mem 0x00000000-0x00ffffff 64bit]
[    0.506345] pci 0000:00:02.0: VF(n) BAR0 space: [mem 0x00000000-0x06ffffff 64bit] (contains BAR0 for 7 VFs)
[    0.506349] pci 0000:00:02.0: reg 0x34c: [mem 0x00000000-0x1fffffff 64bit pref]
[    0.506349] pci 0000:00:02.0: VF(n) BAR2 space: [mem 0x00000000-0xdfffffff 64bit pref] (contains BAR2 for 7 VFs)
[    0.507214] pci 0000:00:04.0: [8086:9a03] type 00 class 0x118000
[    0.507229] pci 0000:00:04.0: reg 0x10: [mem 0x603d180000-0x603d19ffff 64bit]
[    0.508179] pci 0000:00:06.0: [8086:9a09] type 01 class 0x060400
[    0.508267] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
[    0.508302] pci 0000:00:06.0: PTM enabled (root), 4ns granularity
[    0.509228] pci 0000:00:07.0: [8086:9a23] type 01 class 0x060400
[    0.510098] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[    0.510119] pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
[    0.510126] fbcon: Taking over console
[    0.510230] pci 0000:00:07.2: [8086:9a27] type 01 class 0x060400
[    0.511100] pci 0000:00:07.2: PME# supported from D0 D3hot D3cold
[    0.511121] pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
[    0.511234] pci 0000:00:0a.0: [8086:9a0d] type 00 class 0x118000
[    0.511240] pci 0000:00:0a.0: reg 0x10: [mem 0x603d1d0000-0x603d1d7fff 64bit]
[    0.511259] pci 0000:00:0a.0: enabling Extended Tags
[    0.512127] pci 0000:00:0d.0: [8086:9a13] type 00 class 0x0c0330
[    0.512139] pci 0000:00:0d.0: reg 0x10: [mem 0x603d1c0000-0x603d1cffff 64bit]
[    0.512192] pci 0000:00:0d.0: PME# supported from D3hot D3cold
[    0.513071] pci 0000:00:0d.2: [8086:9a1b] type 00 class 0x0c0340
[    0.513081] pci 0000:00:0d.2: reg 0x10: [mem 0x603d140000-0x603d17ffff 64bit]
[    0.513088] pci 0000:00:0d.2: reg 0x18: [mem 0x603d1e9000-0x603d1e9fff 64bit]
[    0.513123] pci 0000:00:0d.2: supports D1 D2
[    0.513123] pci 0000:00:0d.2: PME# supported from D0 D1 D2 D3hot D3cold
[    0.513966] pci 0000:00:0d.3: [8086:9a1d] type 00 class 0x0c0340
[    0.513976] pci 0000:00:0d.3: reg 0x10: [mem 0x603d100000-0x603d13ffff 64bit]
[    0.513983] pci 0000:00:0d.3: reg 0x18: [mem 0x603d1e8000-0x603d1e8fff 64bit]
[    0.514016] pci 0000:00:0d.3: supports D1 D2
[    0.514017] pci 0000:00:0d.3: PME# supported from D0 D1 D2 D3hot D3cold
[    0.514894] pci 0000:00:12.0: [8086:a0fc] type 00 class 0x070000
[    0.514915] pci 0000:00:12.0: reg 0x10: [mem 0x603d1b0000-0x603d1bffff 64bit]
[    0.514986] pci 0000:00:12.0: PME# supported from D0 D3hot
[    0.515927] pci 0000:00:14.0: [8086:a0ed] type 00 class 0x0c0330
[    0.515948] pci 0000:00:14.0: reg 0x10: [mem 0x603d1a0000-0x603d1affff 64bit]
[    0.516033] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.516924] pci 0000:00:14.2: [8086:a0ef] type 00 class 0x050000
[    0.516943] pci 0000:00:14.2: reg 0x10: [mem 0x603d1dc000-0x603d1dffff 64bit]
[    0.516956] pci 0000:00:14.2: reg 0x18: [mem 0x603d1e7000-0x603d1e7fff 64bit]
[    0.517907] pci 0000:00:15.0: [8086:a0e8] type 00 class 0x0c8000
[    0.517938] pci 0000:00:15.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.518983] pci 0000:00:15.1: [8086:a0e9] type 00 class 0x0c8000
[    0.519013] pci 0000:00:15.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.520051] pci 0000:00:16.0: [8086:a0e0] type 00 class 0x078000
[    0.520073] pci 0000:00:16.0: reg 0x10: [mem 0x603d1e4000-0x603d1e4fff 64bit]
[    0.520158] pci 0000:00:16.0: PME# supported from D3hot
[    0.521134] pci 0000:00:19.0: [8086:a0c5] type 00 class 0x0c8000
[    0.521164] pci 0000:00:19.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.522189] pci 0000:00:19.1: [8086:a0c6] type 00 class 0x0c8000
[    0.522219] pci 0000:00:19.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.523246] pci 0000:00:1c.0: [8086:a0b8] type 01 class 0x060400
[    0.523344] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.523371] pci 0000:00:1c.0: PTM enabled (root), 4ns granularity
[    0.524304] pci 0000:00:1d.0: [8086:a0b3] type 01 class 0x060400
[    0.524403] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[    0.524433] pci 0000:00:1d.0: PTM enabled (root), 4ns granularity
[    0.525404] pci 0000:00:1e.0: [8086:a0a8] type 00 class 0x078000
[    0.525433] pci 0000:00:1e.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.526472] pci 0000:00:1f.0: [8086:a082] type 00 class 0x060100
[    0.527455] pci 0000:00:1f.3: [8086:a0c8] type 00 class 0x040100
[    0.527497] pci 0000:00:1f.3: reg 0x10: [mem 0x603d1d8000-0x603d1dbfff 64bit]
[    0.527551] pci 0000:00:1f.3: reg 0x20: [mem 0x603d000000-0x603d0fffff 64bit]
[    0.527660] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[    0.528571] pci 0000:00:1f.4: [8086:a0a3] type 00 class 0x0c0500
[    0.528593] pci 0000:00:1f.4: reg 0x10: [mem 0x603d1e0000-0x603d1e00ff 64bit]
[    0.528615] pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
[    0.529501] pci 0000:00:1f.5: [8086:a0a4] type 00 class 0x0c8000
[    0.529519] pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
[    0.530759] pci 0000:01:00.0: [144d:a808] type 00 class 0x010802
[    0.530774] pci 0000:01:00.0: reg 0x10: [mem 0x8c400000-0x8c403fff 64bit]
[    0.530951] pci 0000:00:06.0: PCI bridge to [bus 01]
[    0.530953] pci 0000:00:06.0:   bridge window [mem 0x8c400000-0x8c4fffff]
[    0.530985] pci 0000:00:07.0: PCI bridge to [bus 02-2b]
[    0.530988] pci 0000:00:07.0:   bridge window [mem 0x80000000-0x8c1fffff]
[    0.530992] pci 0000:00:07.0:   bridge window [mem 0x6000000000-0x601bffffff 64bit pref]
[    0.531021] pci 0000:00:07.2: PCI bridge to [bus 2c-55]
[    0.531025] pci 0000:00:07.2:   bridge window [mem 0x72000000-0x7e1fffff]
[    0.531028] pci 0000:00:07.2:   bridge window [mem 0x6020000000-0x603bffffff 64bit pref]
[    0.531101] pci 0000:56:00.0: [17cb:1101] type 00 class 0x028000
[    0.531124] pci 0000:56:00.0: reg 0x10: [mem 0x8c300000-0x8c3fffff 64bit]
[    0.531262] pci 0000:56:00.0: PME# supported from D0 D3hot D3cold
[    0.531334] pci 0000:56:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:1c.0 (capable of 7.876 Gb/s with 8.0 GT/s PCIe x1 link)
[    0.531418] pci 0000:00:1c.0: PCI bridge to [bus 56]
[    0.531422] pci 0000:00:1c.0:   bridge window [mem 0x8c300000-0x8c3fffff]
[    0.531487] pci 0000:57:00.0: [10ec:5260] type 00 class 0xff0000
[    0.531503] pci 0000:57:00.0: reg 0x10: [mem 0x8c200000-0x8c200fff]
[    0.531637] pci 0000:57:00.0: supports D1 D2
[    0.531638] pci 0000:57:00.0: PME# supported from D1 D2 D3hot D3cold
[    0.531773] pci 0000:00:1d.0: PCI bridge to [bus 57]
[    0.531778] pci 0000:00:1d.0:   bridge window [mem 0x8c200000-0x8c2fffff]
[    0.551101] ACPI: EC: interrupt unblocked
[    0.551102] ACPI: EC: event unblocked
[    0.551109] ACPI: EC: EC_CMD/EC_SC=0x934, EC_DATA=0x930
[    0.551109] ACPI: EC: GPE=0x6e
[    0.551110] ACPI: \_SB_.PC00.LPCB.ECDV: Boot DSDT EC initialization complete
[    0.551111] ACPI: \_SB_.PC00.LPCB.ECDV: EC: Used to handle transactions and events
[    0.551191] iommu: Default domain type: Translated 
[    0.551191] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    0.551191] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.551191] pci 0000:00:02.0: vgaarb: bridge control possible
[    0.551191] vgaarb: loaded
[    0.551191] SCSI subsystem initialized
[    0.551191] libata version 3.00 loaded.
[    0.551191] ACPI: bus type USB registered
[    0.551191] usbcore: registered new interface driver usbfs
[    0.551191] usbcore: registered new interface driver hub
[    0.551191] usbcore: registered new device driver usb
[    0.551191] pps_core: LinuxPPS API ver. 1 registered
[    0.551191] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.551191] PTP clock support registered
[    0.551191] EDAC MC: Ver: 3.0.0
[    0.552083] Registered efivars operations
[    0.552083] NetLabel: Initializing
[    0.552083] NetLabel:  domain hash size = 128
[    0.552083] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.552083] NetLabel:  unlabeled traffic allowed by default
[    0.552083] PCI: Using ACPI for IRQ routing
[    0.569343] PCI: pci_cache_line_size set to 64 bytes
[    0.569832] pci 0000:00:1f.5: can't claim BAR 0 [mem 0xfe010000-0xfe010fff]: no compatible bridge window
[    0.570262] e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
[    0.570263] e820: reserve RAM buffer [mem 0x5ad50000-0x5bffffff]
[    0.570264] e820: reserve RAM buffer [mem 0x5f72b000-0x5fffffff]
[    0.570264] e820: reserve RAM buffer [mem 0x88f800000-0x88fffffff]
[    0.570268] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.570268] hpet0: 8 comparators, 64-bit 19.200000 MHz counter
[    0.573693] clocksource: Switched to clocksource tsc-early
[    0.577600] VFS: Disk quotas dquot_6.6.0
[    0.577600] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.577600] AppArmor: AppArmor Filesystem Enabled
[    0.577600] pnp: PnP ACPI init
[    0.577600] system 00:00: [io  0x0680-0x069f] has been reserved
[    0.577600] system 00:00: [io  0x164e-0x164f] has been reserved
[    0.577600] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.577600] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.577600] system 00:02: [io  0x1854-0x1857] has been reserved
[    0.577600] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.577600] pnp 00:03: Plug and Play ACPI device, IDs PNP0303 (active)
[    0.577600] pnp 00:04: Plug and Play ACPI device, IDs DLL0991 PNP0f13 (active)
[    0.580221] pnp 00:05: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]
[    0.580237] system 00:05: [mem 0xfedc0000-0xfedc7fff] has been reserved
[    0.580237] system 00:05: [mem 0xfeda0000-0xfeda0fff] has been reserved
[    0.580238] system 00:05: [mem 0xfeda1000-0xfeda1fff] has been reserved
[    0.580239] system 00:05: [mem 0xfed20000-0xfed7ffff] could not be reserved
[    0.580239] system 00:05: [mem 0xfed90000-0xfed93fff] could not be reserved
[    0.580240] system 00:05: [mem 0xfed45000-0xfed8ffff] could not be reserved
[    0.580241] system 00:05: [mem 0xfee00000-0xfeefffff] has been reserved
[    0.580242] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.580998] system 00:06: [io  0x1800-0x18fe] could not be reserved
[    0.580998] system 00:06: [mem 0xfe000000-0xfe01ffff] has been reserved
[    0.580999] system 00:06: [mem 0xfe04c000-0xfe04ffff] has been reserved
[    0.580999] system 00:06: [mem 0xfe050000-0xfe0affff] has been reserved
[    0.581000] system 00:06: [mem 0xfe0d0000-0xfe0fffff] has been reserved
[    0.581001] system 00:06: [mem 0xfe200000-0xfe7fffff] has been reserved
[    0.581001] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
[    0.581002] system 00:06: [mem 0xfd000000-0xfd68ffff] has been reserved
[    0.581003] system 00:06: [mem 0xfd6b0000-0xfd6cffff] has been reserved
[    0.581003] system 00:06: [mem 0xfd6f0000-0xfdffffff] has been reserved
[    0.581005] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.581242] system 00:07: [io  0x2000-0x20fe] has been reserved
[    0.581244] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.581409] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.584240] pnp: PnP ACPI: found 9 devices
[    0.589442] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.589474] NET: Registered protocol family 2
[    0.589601] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.589772] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.589991] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.590033] TCP: Hash tables configured (established 262144 bind 65536)
[    0.590140] MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)
[    0.590229] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.590292] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.590344] NET: Registered protocol family 1
[    0.590348] NET: Registered protocol family 44
[    0.590351] pci_bus 0000:00: max bus depth: 1 pci_try_num: 2
[    0.590359] pci 0000:00:02.0: BAR 9: assigned [mem 0x4020000000-0x40ffffffff 64bit pref]
[    0.590361] pci 0000:00:02.0: BAR 7: assigned [mem 0x4010000000-0x4016ffffff 64bit]
[    0.590363] pci 0000:00:07.0: BAR 13: assigned [io  0x4000-0x4fff]
[    0.590363] pci 0000:00:07.2: BAR 13: assigned [io  0x5000-0x5fff]
[    0.590364] pci 0000:00:15.0: BAR 0: assigned [mem 0x4017000000-0x4017000fff 64bit]
[    0.590426] pci 0000:00:15.1: BAR 0: assigned [mem 0x4017001000-0x4017001fff 64bit]
[    0.590441] pci 0000:00:19.0: BAR 0: assigned [mem 0x4017002000-0x4017002fff 64bit]
[    0.590456] pci 0000:00:19.1: BAR 0: assigned [mem 0x4017003000-0x4017003fff 64bit]
[    0.590516] pci 0000:00:1e.0: BAR 0: assigned [mem 0x4017004000-0x4017004fff 64bit]
[    0.590530] pci 0000:00:1f.5: BAR 0: assigned [mem 0x70800000-0x70800fff]
[    0.590541] pci 0000:00:06.0: PCI bridge to [bus 01]
[    0.590549] pci 0000:00:06.0:   bridge window [mem 0x8c400000-0x8c4fffff]
[    0.590558] pci 0000:00:07.0: PCI bridge to [bus 02-2b]
[    0.590559] pci 0000:00:07.0:   bridge window [io  0x4000-0x4fff]
[    0.590561] pci 0000:00:07.0:   bridge window [mem 0x80000000-0x8c1fffff]
[    0.590563] pci 0000:00:07.0:   bridge window [mem 0x6000000000-0x601bffffff 64bit pref]
[    0.590567] pci 0000:00:07.2: PCI bridge to [bus 2c-55]
[    0.590568] pci 0000:00:07.2:   bridge window [io  0x5000-0x5fff]
[    0.590571] pci 0000:00:07.2:   bridge window [mem 0x72000000-0x7e1fffff]
[    0.590573] pci 0000:00:07.2:   bridge window [mem 0x6020000000-0x603bffffff 64bit pref]
[    0.590576] pci 0000:00:1c.0: PCI bridge to [bus 56]
[    0.590581] pci 0000:00:1c.0:   bridge window [mem 0x8c300000-0x8c3fffff]
[    0.590587] pci 0000:00:1d.0: PCI bridge to [bus 57]
[    0.590590] pci 0000:00:1d.0:   bridge window [mem 0x8c200000-0x8c2fffff]
[    0.590597] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.590598] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.590598] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.590599] pci_bus 0000:00: resource 7 [mem 0x70800000-0xbfffffff window]
[    0.590599] pci_bus 0000:00: resource 8 [mem 0x4000000000-0x7fffffffff window]
[    0.590600] pci_bus 0000:01: resource 1 [mem 0x8c400000-0x8c4fffff]
[    0.590600] pci_bus 0000:02: resource 0 [io  0x4000-0x4fff]
[    0.590601] pci_bus 0000:02: resource 1 [mem 0x80000000-0x8c1fffff]
[    0.590601] pci_bus 0000:02: resource 2 [mem 0x6000000000-0x601bffffff 64bit pref]
[    0.590602] pci_bus 0000:2c: resource 0 [io  0x5000-0x5fff]
[    0.590602] pci_bus 0000:2c: resource 1 [mem 0x72000000-0x7e1fffff]
[    0.590603] pci_bus 0000:2c: resource 2 [mem 0x6020000000-0x603bffffff 64bit pref]
[    0.590604] pci_bus 0000:56: resource 1 [mem 0x8c300000-0x8c3fffff]
[    0.590604] pci_bus 0000:57: resource 1 [mem 0x8c200000-0x8c2fffff]
[    0.590729] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.591483] PCI: CLS 0 bytes, default 64
[    0.591508] Trying to unpack rootfs image as initramfs...
[    0.703713] Freeing initrd memory: 87124K
[    0.703747] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.703748] software IO TLB: mapped [mem 0x0000000051a9c000-0x0000000055a9c000] (64MB)
[    0.703828] resource sanity check: requesting [mem 0xfedc0000-0xfedcdfff], which spans more than pnp 00:05 [mem 0xfedc0000-0xfedc7fff]
[    0.703834] caller tgl_uncore_imc_freerunning_init_box+0xb9/0x100 mapping multiple BARs
[    0.703950] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x28680fa287f, max_idle_ns: 440795281151 ns
[    0.703968] clocksource: Switched to clocksource tsc
[    0.704132] check: Scanning for low memory corruption every 60 seconds
[    0.704472] Initialise system trusted keyrings
[    0.704482] Key type blacklist registered
[    0.704526] workingset: timestamp_bits=36 max_order=23 bucket_order=0
[    0.705035] zbud: loaded
[    0.705162] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.705279] fuse: init (API version 7.32)
[    0.705380] integrity: Platform Keyring initialized
[    0.712145] Key type asymmetric registered
[    0.712146] Asymmetric key parser 'x509' registered
[    0.712151] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.712208] io scheduler mq-deadline registered
[    0.712686] pcieport 0000:00:06.0: PME: Signaling with IRQ 120
[    0.712866] pcieport 0000:00:07.0: PME: Signaling with IRQ 121
[    0.712880] pcieport 0000:00:07.0: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.713081] pcieport 0000:00:07.2: PME: Signaling with IRQ 122
[    0.713094] pcieport 0000:00:07.2: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.713293] pcieport 0000:00:1c.0: PME: Signaling with IRQ 123
[    0.713472] pcieport 0000:00:1d.0: PME: Signaling with IRQ 124
[    0.713548] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    0.713591] efifb: probing for efifb
[    0.713606] efifb: Ignoring BGRT: unexpected or invalid BMP data
[    0.713606] efifb: framebuffer at 0x4000000000, using 9000k, total 9000k
[    0.713607] efifb: mode is 1920x1200x32, linelength=7680, pages=1
[    0.713607] efifb: scrolling: redraw
[    0.713608] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.713661] Console: switching to colour frame buffer device 240x75
[    0.718244] fb0: EFI VGA frame buffer device
[    0.718248] intel_idle: MWAIT substates: 0x11121020
[    0.718434] Monitor-Mwait will be used to enter C-1 state
[    0.718438] Monitor-Mwait will be used to enter C-2 state
[    0.718442] Monitor-Mwait will be used to enter C-3 state
[    0.718446] ACPI: \_SB_.PR00: Found 3 idle states
[    0.718447] intel_idle: v0.5.1 model 0x8C
[    0.718604] intel_idle: Local APIC timer is reliable in all C-states
[    0.719431] ACPI: AC Adapter [AC] (on-line)
[    0.719472] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[    0.719491] ACPI: Lid Switch [LID0]
[    0.719502] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[    0.719511] ACPI: Power Button [PBTN]
[    0.719521] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[    0.719527] ACPI: Sleep Button [SBTN]
[    0.721227] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    0.723887] serial 0000:00:12.0: enabling device (0000 -> 0002)
[    0.725134] Linux agpgart interface v0.103
[    0.727158] tpm_tis STM0125:00: 2.0 TPM (device-id 0x0, rev-id 78)
[    0.743119] loop: module loaded
[    0.743419] libphy: Fixed MDIO Bus: probed
[    0.743419] tun: Universal TUN/TAP device driver, 1.6
[    0.743573] PPP generic driver version 2.4.2
[    0.743602] VFIO - User Level meta-driver version: 0.3
[    0.743757] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.743758] ehci-pci: EHCI PCI platform driver
[    0.743763] ehci-platform: EHCI generic platform driver
[    0.743769] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.743771] ohci-pci: OHCI PCI platform driver
[    0.743774] ohci-platform: OHCI generic platform driver
[    0.743777] uhci_hcd: USB Universal Host Controller Interface driver
[    0.743802] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    0.744554] i8042: Warning: Keylock active
[    0.747730] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.747731] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.748036] mousedev: PS/2 mouse device common for all mice
[    0.748081] battery: ACPI: Battery Slot [BAT0] (battery present)
[    0.748273] rtc_cmos 00:01: RTC can wake from S4
[    0.748918] rtc_cmos 00:01: registered as rtc0
[    0.749095] rtc_cmos 00:01: setting system clock to 2020-11-04T12:34:09 UTC (1604493249)
[    0.749138] rtc_cmos 00:01: alarms up to one month, y3k, 242 bytes nvram
[    0.749140] i2c /dev entries driver
[    0.749162] device-mapper: uevent: version 1.0.3
[    0.749205] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
[    0.749213] platform eisa.0: Probing EISA bus 0
[    0.749214] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.749214] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.749215] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.749215] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.749216] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.749216] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.749217] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.749217] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.749218] platform eisa.0: Cannot allocate resource for EISA slot 8
[    0.749218] platform eisa.0: EISA: Detected 0 cards
[    0.749220] intel_pstate: Intel P-state driver initializing
[    0.749796] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    0.749947] intel_pstate: HWP enabled
[    0.749976] ledtrig-cpu: registered to indicate activity on CPUs
[    0.749979] EFI Variables Facility v0.08 2004-May-17
[    0.751929] intel_pmc_core INT33A1:00:  initialized
[    0.751999] drop_monitor: Initializing network drop monitor service
[    0.752119] NET: Registered protocol family 10
[    0.755856] Segment Routing with IPv6
[    0.755876] NET: Registered protocol family 17
[    0.755967] Key type dns_resolver registered
[    0.756563] microcode: sig=0x806c1, pf=0x80, revision=0x60
[    0.756637] microcode: Microcode Update Driver: v2.2.
[    0.756773] resctrl: L2 allocation detected
[    0.756773] resctrl: L2DATA allocation detected
[    0.756773] resctrl: L2CODE allocation detected
[    0.756776] IPI shorthand broadcast: enabled
[    0.756781] sched_clock: Marking stable (756324155, 441923)->(763657306, -6891228)
[    0.756833] registered taskstats version 1
[    0.756839] Loading compiled-in X.509 certificates
[    0.757313] Loaded X.509 cert 'Build time autogenerated kernel key: e7023dac6afd3a5685011f478d7c4ec5045876be'
[    0.757336] zswap: loaded using pool lzo/zbud
[    0.757430] Key type ._fscrypt registered
[    0.757430] Key type .fscrypt registered
[    0.757431] Key type fscrypt-provisioning registered
[    0.757459] Key type trusted registered
[    0.758920] Key type encrypted registered
[    0.758922] AppArmor: AppArmor sha1 policy hashing enabled
[    0.759013] integrity: Loading X.509 certificate: UEFI:db
[    0.759028] integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios DB Key: 637fa7a9f74471b406de0511557071fd41dd5487'
[    0.759028] integrity: Loading X.509 certificate: UEFI:db
[    0.759036] integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios FW Aux Authority 2018: dd4df7c3f5ce7e5a77847915abc37b031f6b10bd'
[    0.759037] integrity: Loading X.509 certificate: UEFI:db
[    0.759047] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    0.759048] integrity: Loading X.509 certificate: UEFI:db
[    0.759061] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    0.759739] integrity: Loading X.509 certificate: UEFI:MokListRT
[    0.759748] integrity: Loaded X.509 cert 'SomeOrg: shim: a01ee84e9b37ace407961cc468c5909447878469'
[    0.759748] integrity: Loading X.509 certificate: UEFI:MokListRT
[    0.759980] integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
[    0.759986] ima: Allocated hash algorithm: sha1
[    0.775791] ima: No architecture policies found
[    0.775797] evm: Initialising EVM extended attributes:
[    0.775798] evm: security.selinux
[    0.775798] evm: security.SMACK64
[    0.775798] evm: security.SMACK64EXEC
[    0.775799] evm: security.SMACK64TRANSMUTE
[    0.775799] evm: security.SMACK64MMAP
[    0.775799] evm: security.apparmor
[    0.775799] evm: security.ima
[    0.775800] evm: security.capability
[    0.775800] evm: HMAC attrs: 0x1
[    0.777852] PM:   Magic number: 12:631:581
[    0.777883] pci_bus 0000:02: hash matches
[    0.778146] RAS: Correctable Errors collector initialized.
[    0.784040] Freeing unused decrypted memory: 2036K
[    0.784362] Freeing unused kernel image (initmem) memory: 2636K
[    0.819802] Write protecting the kernel read-only data: 22528k
[    0.820621] Freeing unused kernel image (text/rodata gap) memory: 2036K
[    0.820894] Freeing unused kernel image (rodata/data gap) memory: 932K
[    0.837568] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    0.837575] Run /init as init process
[    0.837577]   with arguments:
[    0.837578]     /init
[    0.837578]     splash
[    0.837579]   with environment:
[    0.837580]     HOME=/
[    0.837580]     TERM=linux
[    0.837581]     BOOT_IMAGE=/vmlinuz-5.10.0-rc1-wt-ath+
[    0.898169] hid: raw HID events driver (C) Jiri Kosina
[    0.900997] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.901029] wmi_bus wmi_bus-PNP0C14:02: WQBC data block query control method not found
[    0.901030] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.903428] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.904733] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.904738] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 1
[    0.905179] acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.905226] acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.905271] acpi PNP0C14:06: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.905836] xhci_hcd 0000:00:0d.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000200009810
[    0.905840] xhci_hcd 0000:00:0d.0: cache line size of 64 is not supported
[    0.905963] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    0.905964] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.905965] usb usb1: Product: xHCI Host Controller
[    0.905966] usb usb1: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.905966] usb usb1: SerialNumber: 0000:00:0d.0
[    0.906028] hub 1-0:1.0: USB hub found
[    0.906032] hub 1-0:1.0: 1 port detected
[    0.906149] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.906151] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 2
[    0.906152] xhci_hcd 0000:00:0d.0: Host supports USB 3.1 Enhanced SuperSpeed
[    0.906195] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    0.906196] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.906197] usb usb2: Product: xHCI Host Controller
[    0.906197] usb usb2: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.906197] usb usb2: SerialNumber: 0000:00:0d.0
[    0.906236] hub 2-0:1.0: USB hub found
[    0.906244] hub 2-0:1.0: 4 ports detected
[    0.906669] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.906674] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    0.907698] nvme nvme0: pci function 0000:01:00.0
[    0.907764] xhci_hcd 0000:00:14.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000000009810
[    0.908014] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    0.908166] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    0.908167] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.908168] usb usb3: Product: xHCI Host Controller
[    0.908168] usb usb3: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.908169] usb usb3: SerialNumber: 0000:00:14.0
[    0.908217] hub 3-0:1.0: USB hub found
[    0.908234] hub 3-0:1.0: 12 ports detected
[    0.908985] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.908987] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[    0.908989] xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
[    0.909015] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    0.909015] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.909017] usb usb4: Product: xHCI Host Controller
[    0.909018] usb usb4: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.909018] usb usb4: SerialNumber: 0000:00:14.0
[    0.909086] hub 4-0:1.0: USB hub found
[    0.909099] hub 4-0:1.0: 4 ports detected
[    0.909207] usb: port power management may be unreliable
[    0.910841] rtsx_pci 0000:57:00.0: enabling device (0000 -> 0002)
[    0.911267] i801_smbus 0000:00:1f.4: enabling device (0000 -> 0003)
[    0.911391] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[    0.911447] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[    0.913858] nvme nvme0: missing or invalid SUBNQN field.
[    0.913880] nvme nvme0: Shutdown timeout set to 8 seconds
[    0.916691] cryptd: max_cpu_qlen set to 1000
[    0.920917] AVX2 version of gcm_enc/dec engaged.
[    0.920918] AES CTR mode by8 optimization enabled
[    0.926033] nvme nvme0: 8/0/0 default/read/poll queues
[    0.926669] i2c i2c-0: 8/8 memory slots populated (from DMI)
[    0.926671] i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD
[    0.929250]  nvme0n1: p1 p2 p3 p4 p5
[    0.931675] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[    0.931907] idma64 idma64.0: Found Intel integrated DMA 64-bit
[    0.966773] checking generic (4000000000 8ca000) vs hw (603c000000 1000000)
[    0.966774] checking generic (4000000000 8ca000) vs hw (4000000000 10000000)
[    0.966775] fb0: switching to inteldrmfb from EFI VGA
[    0.966831] Console: switching to colour dummy device 80x25
[    0.966857] i915 0000:00:02.0: vgaarb: deactivate vga console
[    0.967670] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[    0.968105] idma64 idma64.1: Found Intel integrated DMA 64-bit
[    0.968223] i915 0000:00:02.0: [drm] Couldn't get system memory bandwidth
[    0.968815] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    0.969306] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_08.bin (v2.8)
[    0.978728] i2c_hid i2c-DLL0945:00: supply vdd not found, using dummy regulator
[    0.978745] i2c_hid i2c-DLL0945:00: supply vddl not found, using dummy regulator
[    1.003659] intel-lpss 0000:00:19.0: enabling device (0000 -> 0002)
[    1.003864] idma64 idma64.2: Found Intel integrated DMA 64-bit
[    1.012376] [drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on minor 0
[    1.014910] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.016829] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[    1.018613] fbcon: i915drmfb (fb0) is primary device
[    1.035670] intel-lpss 0000:00:19.1: enabling device (0000 -> 0002)
[    1.035966] idma64 idma64.3: Found Intel integrated DMA 64-bit
[    1.067739] intel-lpss 0000:00:1e.0: enabling device (0000 -> 0002)
[    1.068569] idma64 idma64.4: Found Intel integrated DMA 64-bit
[    1.156096] input: DLL0945:00 06CB:CDE6 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input7
[    1.156174] input: DLL0945:00 06CB:CDE6 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input8
[    1.156235] hid-generic 0018:06CB:CDE6.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL0945:00 06CB:CDE6] on i2c-DLL0945:00
[    1.319669] usb 3-4: new high-speed USB device number 2 using xhci_hcd
[    1.540621] usb 3-4: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00
[    1.540624] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.540625] usb 3-4: Product: 802.11ac NIC
[    1.540627] usb 3-4: Manufacturer: Realtek
[    1.540628] usb 3-4: SerialNumber: 123456
[    1.577639] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
[    1.579308] hid-generic 001F:8087:0AC2.0002: hidraw1: <UNKNOWN> HID v2.00 Device [hid-ishtp 8087:0AC2] on 
[    1.675685] usb 3-6: new high-speed USB device number 3 using xhci_hcd
[    1.826107] usb 3-6: New USB device found, idVendor=0bda, idProduct=5517, bcdDevice= 4.21
[    1.826111] usb 3-6: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    1.826113] usb 3-6: Product: Integrated_Webcam_HD
[    1.826114] usb 3-6: Manufacturer: Integrated_Webcam_HD
[    1.826115] usb 3-6: SerialNumber: 200901010001
[    2.143937] Console: switching to colour frame buffer device 240x75
[    2.167063] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[    7.027376] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[    7.151724] systemd[1]: Inserted module 'autofs4'
[    7.164490] systemd[1]: systemd 246.6-1ubuntu1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    7.187995] systemd[1]: Detected architecture x86-64.
[    7.247914] systemd[1]: Set hostname to <tk-9310>.
[    7.308624] systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    7.325537] systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    7.347103] systemd[1]: Queued start job for default target Graphical Interface.
[    7.347885] systemd[1]: Created slice system-modprobe.slice.
[    7.347993] systemd[1]: Created slice system-postgresql.slice.
[    7.348075] systemd[1]: Created slice Cryptsetup Units Slice.
[    7.348182] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    7.348259] systemd[1]: Created slice User and Session Slice.
[    7.348284] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    7.348369] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    7.348400] systemd[1]: Reached target Remote File Systems.
[    7.348405] systemd[1]: Reached target Slices.
[    7.348442] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[    7.348475] systemd[1]: Listening on LVM2 poll daemon socket.
[    7.348512] systemd[1]: Listening on Syslog Socket.
[    7.348550] systemd[1]: Listening on fsck to fsckd communication Socket.
[    7.348564] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    7.348925] systemd[1]: Listening on Journal Audit Socket.
[    7.348975] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.349014] systemd[1]: Listening on Journal Socket.
[    7.349064] systemd[1]: Listening on udev Control Socket.
[    7.349093] systemd[1]: Listening on udev Kernel Socket.
[    7.349438] systemd[1]: Mounting Huge Pages File System...
[    7.349824] systemd[1]: Mounting POSIX Message Queue File System...
[    7.350306] systemd[1]: Mounting Kernel Debug File System...
[    7.350701] systemd[1]: Mounting Kernel Trace File System...
[    7.351386] systemd[1]: Starting Journal Service...
[    7.351803] systemd[1]: Starting Availability of block devices...
[    7.352357] systemd[1]: Starting Set the console keyboard layout...
[    7.352795] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    7.353151] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[    7.353168] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[    7.353503] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    7.353539] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[    7.354338] systemd[1]: Starting Load Kernel Modules...
[    7.354887] systemd[1]: Starting Remount Root and Kernel File Systems...
[    7.355433] systemd[1]: Starting Coldplug All udev Devices...
[    7.356014] systemd[1]: Starting Uncomplicated firewall...
[    7.357078] systemd[1]: Mounted Huge Pages File System.
[    7.357170] systemd[1]: Mounted POSIX Message Queue File System.
[    7.357248] systemd[1]: Mounted Kernel Debug File System.
[    7.357328] systemd[1]: Mounted Kernel Trace File System.
[    7.357623] systemd[1]: Finished Availability of block devices.
[    7.357965] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    7.358251] systemd[1]: Finished Uncomplicated firewall.
[    7.361666] EXT4-fs (dm-2): re-mounted. Opts: errors=remount-ro
[    7.362351] lp: driver loaded but no devices found
[    7.362395] systemd[1]: Finished Remount Root and Kernel File Systems.
[    7.363091] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[    7.363123] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[    7.363697] systemd[1]: Starting Load/Save Random Seed...
[    7.364136] ppdev: user-space parallel port driver
[    7.364284] systemd[1]: Starting Create System Users...
[    7.366769] systemd[1]: Finished Load Kernel Modules.
[    7.367528] systemd[1]: Mounting FUSE Control File System...
[    7.368206] systemd[1]: Mounting Kernel Configuration File System...
[    7.368794] systemd[1]: Starting Apply Kernel Variables...
[    7.369621] systemd[1]: Mounted FUSE Control File System.
[    7.369705] systemd[1]: Mounted Kernel Configuration File System.
[    7.372915] systemd[1]: Finished Create System Users.
[    7.373549] systemd[1]: Starting Create Static Device Nodes in /dev...
[    7.375964] systemd[1]: Finished Load/Save Random Seed.
[    7.378178] systemd[1]: Finished Apply Kernel Variables.
[    7.380695] systemd[1]: Finished Create Static Device Nodes in /dev.
[    7.381628] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    7.386758] systemd[1]: Finished Set the console keyboard layout.
[    7.398485] systemd[1]: Started Journal Service.
[    7.479923] input: Intel HID events as /devices/platform/INTC1051:00/input/input10
[    7.480078] intel-hid INTC1051:00: platform supports 5 button array
[    7.480128] input: Intel HID 5 button array as /devices/platform/INTC1051:00/input/input11
[    7.501054] ACPI BIOS Error (bug): Could not resolve symbol [\S1CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.501063] No Local Variables are initialized for Method [_CRT]
[    7.501065] No Arguments are initialized for method [_CRT]

[    7.501067] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.501088] ACPI BIOS Error (bug): Could not resolve symbol [\S1HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.501091] No Local Variables are initialized for Method [_HOT]
[    7.501093] No Arguments are initialized for method [_HOT]

[    7.501094] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.501113] ACPI BIOS Error (bug): Could not resolve symbol [\S1PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.501117] No Local Variables are initialized for Method [_PSV]
[    7.501118] No Arguments are initialized for method [_PSV]

[    7.501120] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.501137] ACPI BIOS Error (bug): Could not resolve symbol [\S1AC], AE_NOT_FOUND (20200925/psargs-330)
[    7.501140] No Local Variables are initialized for Method [_AC0]
[    7.501141] No Arguments are initialized for method [_AC0]

[    7.501143] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._AC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.505599] ACPI BIOS Error (bug): Could not resolve symbol [\S2CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.505608] No Local Variables are initialized for Method [_CRT]
[    7.505610] No Arguments are initialized for method [_CRT]

[    7.505612] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TSKN._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.505632] ACPI BIOS Error (bug): Could not resolve symbol [\S2HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.505636] No Local Variables are initialized for Method [_HOT]
[    7.505637] No Arguments are initialized for method [_HOT]

[    7.505639] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TSKN._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.505657] ACPI BIOS Error (bug): Could not resolve symbol [\S2PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.505661] No Local Variables are initialized for Method [_PSV]
[    7.505662] No Arguments are initialized for method [_PSV]

[    7.505664] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TSKN._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.508786] ACPI BIOS Error (bug): Could not resolve symbol [\S3CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.508793] No Local Variables are initialized for Method [_CRT]
[    7.508794] No Arguments are initialized for method [_CRT]

[    7.508796] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TVR._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.508814] ACPI BIOS Error (bug): Could not resolve symbol [\S3HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.508818] No Local Variables are initialized for Method [_HOT]
[    7.508819] No Arguments are initialized for method [_HOT]

[    7.508821] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TVR._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.508838] ACPI BIOS Error (bug): Could not resolve symbol [\S3PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.508842] No Local Variables are initialized for Method [_PSV]
[    7.508843] No Arguments are initialized for method [_PSV]

[    7.508845] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TVR._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.511930] ACPI BIOS Error (bug): Could not resolve symbol [\S4CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.511936] No Local Variables are initialized for Method [_CRT]
[    7.511938] No Arguments are initialized for method [_CRT]

[    7.511940] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.511959] ACPI BIOS Error (bug): Could not resolve symbol [\S4HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.511963] No Local Variables are initialized for Method [_HOT]
[    7.511964] No Arguments are initialized for method [_HOT]

[    7.511966] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.511984] ACPI BIOS Error (bug): Could not resolve symbol [\S4PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.511987] No Local Variables are initialized for Method [_PSV]
[    7.511989] No Arguments are initialized for method [_PSV]

[    7.511991] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.512008] ACPI BIOS Error (bug): Could not resolve symbol [\S4AC], AE_NOT_FOUND (20200925/psargs-330)
[    7.512012] No Local Variables are initialized for Method [_AC0]
[    7.512013] No Arguments are initialized for method [_AC0]

[    7.512015] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._AC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.518544] ACPI BIOS Error (bug): Could not resolve symbol [\S5CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.518552] No Local Variables are initialized for Method [_CRT]
[    7.518554] No Arguments are initialized for method [_CRT]

[    7.518556] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.THP._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.518575] ACPI BIOS Error (bug): Could not resolve symbol [\S5HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.518579] No Local Variables are initialized for Method [_HOT]
[    7.518580] No Arguments are initialized for method [_HOT]

[    7.518582] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.THP._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.518601] ACPI BIOS Error (bug): Could not resolve symbol [\S5PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.518604] No Local Variables are initialized for Method [_PSV]
[    7.518605] No Arguments are initialized for method [_PSV]

[    7.518607] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.THP._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.540608] Bluetooth: Core ver 2.22
[    7.540620] NET: Registered protocol family 31
[    7.540621] Bluetooth: HCI device and connection manager initialized
[    7.540624] Bluetooth: HCI socket layer initialized
[    7.540625] Bluetooth: L2CAP socket layer initialized
[    7.540628] Bluetooth: SCO socket layer initialized
[    7.545705] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
[    7.551854] intel_rapl_common: Found RAPL domain package
[    7.552645] proc_thermal 0000:00:04.0: Creating sysfs group for PROC_THERMAL_PCI
[    7.580866] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[    7.582762] Bluetooth: HCI UART driver ver 2.3
[    7.582764] Bluetooth: HCI UART protocol H4 registered
[    7.582765] Bluetooth: HCI UART protocol BCSP registered
[    7.582770] Bluetooth: HCI UART protocol LL registered
[    7.582771] Bluetooth: HCI UART protocol ATH3K registered
[    7.582775] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    7.582812] Bluetooth: HCI UART protocol Intel registered
[    7.582841] Bluetooth: HCI UART protocol Broadcom registered
[    7.582847] Bluetooth: HCI UART protocol QCA registered
[    7.582847] Bluetooth: HCI UART protocol AG6XX registered
[    7.582852] Bluetooth: HCI UART protocol Marvell registered
[    7.588409] pstore: Using crash dump compression: deflate
[    7.588419] pstore: Registered efi as persistent store backend
[    7.595679] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.595830] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.604193] dw-apb-uart.4: ttyS4 at MMIO 0x4017004000 (irq = 16, base_baud = 6250000) is a 16550A
[    7.604441] input: Dell WMI hotkeys as /devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input12
[    7.605755] hci_uart_qca serial0-0: failed to acquire enable gpio
[    7.609742] serial serial0: tty port ttyS4 registered
[    7.610656] Bluetooth: hci0: setting up ROME/QCA6390
[    7.617755] Bluetooth: hci0: Frame reassembly failed (-84)
[    7.698575] EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null)
[    7.712164] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support is experimental!
[    7.720933] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem 0x8c300000-0x8c3fffff 64bit]
[    7.720952] ath11k_pci 0000:56:00.0: enabling device (0000 -> 0002)
[    7.721000] ath11k_pci 0000:56:00.0: failed to get 32 MSI vectors, only -28 available
[    7.721003] ath11k_pci 0000:56:00.0: failed to enable msi: -28
[    7.721021] ath11k_pci: probe of 0000:56:00.0 failed with error -28
[    7.729699] input: DLL0945:00 06CB:CDE6 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input13
[    7.729776] input: DLL0945:00 06CB:CDE6 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input14
[    7.729850] hid-multitouch 0018:06CB:CDE6.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL0945:00 06CB:CDE6] on i2c-DLL0945:00
[    7.761465] intel_rapl_msr: PL4 support detected.
[    7.761491] intel_rapl_common: Found RAPL domain package
[    7.761493] intel_rapl_common: Found RAPL domain core
[    7.761494] intel_rapl_common: Found RAPL domain uncore
[    7.761496] intel_rapl_common: Found RAPL domain psys
[    7.764115] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    7.764119] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[    7.800477] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[    7.811669] Adding 33554428k swap on /dev/mapper/ubuntu--vg-swap_1.  Priority:-2 extents:1 across:33554428k SSFS
[    7.817952] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    7.817955] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[    7.817967] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002)
[    7.818679] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[    7.818789] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    7.825738] sof-audio-pci 0000:00:1f.3: use msi interrupt mode
[    7.886390] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5
[    7.886393] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[    7.886399] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2
[    7.940218] Bluetooth: hci0: QCA Product ID   :0x00000010
[    7.940220] Bluetooth: hci0: QCA SOC Version  :0x400a0200
[    7.940220] Bluetooth: hci0: QCA ROM Version  :0x00000200
[    7.940221] Bluetooth: hci0: QCA Patch Version:0x00000d2b
[    7.940221] Bluetooth: hci0: QCA controller version 0x02000200
[    7.940222] Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
[    7.977205] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:5:0-58b36
[    7.977208] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:16:0 Kernel ABI 3:17:0
[    7.977364] sof-audio-pci 0000:00:1f.3: warning: unknown ext header type 3 size 0x1c
[    7.977373] sof-audio-pci 0000:00:1f.3: warning: unknown ext header type 4 size 0x10
[    7.983357] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:11:0 Kernel ABI 3:17:0
[    7.997455] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred
[    8.017550] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC289: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[    8.017551] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    8.017552] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    8.017553] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[    8.017553] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[    8.017554] snd_hda_codec_realtek ehdaudio0D0:      Headset Mic=0x19
[    8.017554] snd_hda_codec_realtek ehdaudio0D0:      Headphone Mic=0x1b
[    8.068759] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten
[    8.068764] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten
[    8.068868] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten
[    8.068871] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten
[    8.068873] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten
[    8.068876] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten
[    8.068878] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten
[    8.068881] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten
[    8.068885] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten
[    8.068888] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten
[    8.068891] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten
[    8.068894] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten
[    8.068898] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten
[    8.068905] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3

[    8.068906] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4

[    8.068907] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 5

[    8.068908] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 6

[    8.068909] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 7

[    8.068909] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8

[    8.083734] input: sof-hda-dsp Headphone Mic as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input16
[    8.083760] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input17
[    8.083788] input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input18
[    8.083823] input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input19
[    8.608647] audit: type=1400 audit(1604493257.356:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=1223 comm="apparmor_parser"
[    8.609264] audit: type=1400 audit(1604493257.356:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=1221 comm="apparmor_parser"
[    8.609540] audit: type=1400 audit(1604493257.356:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=1218 comm="apparmor_parser"
[    8.609543] audit: type=1400 audit(1604493257.356:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=1218 comm="apparmor_parser"
[    8.610965] audit: type=1400 audit(1604493257.356:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=1222 comm="apparmor_parser"
[    8.613725] audit: type=1400 audit(1604493257.360:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=1226 comm="apparmor_parser"
[    8.613729] audit: type=1400 audit(1604493257.360:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1226 comm="apparmor_parser"
[    8.615041] audit: type=1400 audit(1604493257.360:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=1229 comm="apparmor_parser"
[    8.616310] audit: type=1400 audit(1604493257.364:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1219 comm="apparmor_parser"
[    8.616314] audit: type=1400 audit(1604493257.364:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1219 comm="apparmor_parser"
[    8.663760] mc: Linux media interface: v0.10
[    8.665307] usbcore: registered new interface driver btusb
[    8.668662] Bluetooth: hci1: RTL: examining hci_ver=08 hci_rev=826c lmp_ver=08 lmp_subver=a99e
[    8.668665] Bluetooth: hci1: RTL: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008
[    8.668667] Bluetooth: hci1: RTL: assuming no firmware upload needed
[    8.669945] videodev: Linux video capture interface: v2.00
[    8.771761] Bluetooth: hci0: QCA Downloading qca/htnv20.bin
[    8.816047] uvcvideo: Found UVC 1.10 device Integrated_Webcam_HD (0bda:5517)
[    8.818187] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/input/input20
[    8.818687] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:5517)
[    8.819297] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/input/input21
[    8.819531] usbcore: registered new interface driver uvcvideo
[    8.819533] USB Video Class driver (1.1.1)
[    8.974133] Bluetooth: hci0: QCA setup on UART is completed
[   10.039258] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.039259] Bluetooth: BNEP filters: protocol multicast
[   10.039263] Bluetooth: BNEP socket layer initialized
[   10.054450] NET: Registered protocol family 38
[   13.805606] rfkill: input handler disabled
[   14.075673] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
[   14.563726] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   18.839784] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input5
[   19.043772] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   20.916310] Bluetooth: RFCOMM TTY layer initialized
[   20.916315] Bluetooth: RFCOMM socket layer initialized
[   20.916319] Bluetooth: RFCOMM ver 1.11
[   21.112484] rfkill: input handler enabled
[   22.946707] rfkill: input handler disabled
[   23.174208] kauditd_printk_skb: 93 callbacks suppressed
[   23.174210] audit: type=1400 audit(1604493271.920:105): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=2831 comm="snap-confine" capability=4  capname="fsetid"
[   24.616261] audit: type=1326 audit(1604493273.364:106): auid=1000 uid=1000 gid=1000 ses=3 subj==snap.snap-store.ubuntu-software (enforce) pid=2831 comm="snap-store" exe="/snap/snap-store/481/usr/bin/snap-store" sig=0 arch=c000003e syscall=314 compat=0 ip=0x7f84aca0a959 code=0x50000

[-- Attachment #3: lspci.txt --]
[-- Type: text/plain, Size: 53465 bytes --]

00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
	Subsystem: Dell 11th Gen Core Processor Host Bridge/DRAM Registers
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=14 <?>

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 01) (prog-if 00 [VGA controller])
	DeviceName: To Be Filled by O.E.M.
	Subsystem: Dell UHD Graphics
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 153
	Region 0: Memory at 603c000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at 4000000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 3000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+ FLReset+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
		Address: fee80004  Data: 4025
		Masking: 00000000  Pending: 00000000
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Process Address Space ID (PASID)
		PASIDCap: Exec- Priv-, Max PASID Width: 14
		PASIDCtl: Enable- Exec- Priv-
	Capabilities: [200 v1] Address Translation Service (ATS)
		ATSCap:	Invalidate Queue Depth: 00
		ATSCtl:	Enable-, Smallest Translation Unit: 00
	Capabilities: [300 v1] Page Request Interface (PRI)
		PRICtl: Enable- Reset-
		PRISta: RF- UPRGI- Stopped+
		Page Request Capacity: 00008000, Page Request Allocation: 00000000
	Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV)
		IOVCap:	Migration-, Interrupt Message Number: 000
		IOVCtl:	Enable- Migration- Interrupt- MSE- ARIHierarchy-
		IOVSta:	Migration-
		Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function Dependency Link: 00
		VF offset: 1, stride: 1, Device ID: 9a49
		Supported Page Size: 00000553, System Page Size: 00000001
		Region 0: Memory at 0000004010000000 (64-bit, non-prefetchable)
		Region 2: Memory at 0000004020000000 (64-bit, prefetchable)
		VF Migration: offset: 00000000, BIR: 0
	Kernel driver in use: i915
	Kernel modules: i915

00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
	Subsystem: Dell Device 0991
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d180000 (64-bit, non-prefetchable) [size=128K]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [d0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device

00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin D routed to IRQ 120
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c400000-8c4fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (downgraded), Width x4 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #0, PowerLimit 75.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet+ LinkState+
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp+ 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing+ 32bit+ 64bit+ 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn+ EgressBlck+
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee04004  Data: 4021
	Capabilities: [90] Subsystem: Dell 11th Gen Core Processor PCIe Controller
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=45us PortTPowerOnTime=50us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=45us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=50us
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [280 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Capabilities: [a30 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [a90 v1] Data Link Feature <?>
	Capabilities: [a9c v1] Physical Layer 16.0 GT/s <?>
	Capabilities: [edc v1] Lane Margining at the Receiver <?>
	Kernel driver in use: pcieport

00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #0 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 121
	Bus: primary=00, secondary=02, subordinate=2b, sec-latency=0
	I/O behind bridge: 00004000-00004fff [size=4K]
	Memory behind bridge: 80000000-8c1fffff [size=194M]
	Prefetchable memory behind bridge: 0000006000000000-000000601bffffff [size=448M]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #2, Speed 2.5GT/s, Width x4, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x0 (downgraded)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee08004  Data: 4021
	Capabilities: [90] Subsystem: Dell Tiger Lake-LP Thunderbolt PCI Express Root Port
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v0] Null
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP- SwTrigger- RP PIO Log 0, DL_ActiveErr-
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #2 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 122
	Bus: primary=00, secondary=2c, subordinate=55, sec-latency=0
	I/O behind bridge: 00005000-00005fff [size=4K]
	Memory behind bridge: 72000000-7e1fffff [size=194M]
	Prefetchable memory behind bridge: 0000006020000000-000000603bffffff [size=448M]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #4, Speed 2.5GT/s, Width x4, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x0 (downgraded)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee10004  Data: 4021
	Capabilities: [90] Subsystem: Dell Tiger Lake-LP Thunderbolt PCI Express Root Port
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v0] Null
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP- SwTrigger- RP PIO Log 0, DL_ActiveErr-
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
	Subsystem: Dell Device 0991
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 603d1d0000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag+ RBE- FLReset-
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
	Capabilities: [d0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Designated Vendor-Specific: Vendor=8086 ID=0002 Rev=1 Len=16 <?>
	Capabilities: [110 v1] Designated Vendor-Specific: Vendor=8086 ID=0003 Rev=1 Len=16 <?>
	Capabilities: [120 v1] Designated Vendor-Specific: Vendor=8086 ID=0004 Rev=1 Len=16 <?>

00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt USB Controller (rev 01) (prog-if 30 [XHCI])
	Subsystem: Dell Tiger Lake-LP Thunderbolt USB Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin ? routed to IRQ 125
	Region 0: Memory at 603d1c0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
		Address: 00000000fee08004  Data: 4022
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Capabilities: [b0] Vendor Specific Information: Len=00 <?>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt NHI #0 (rev 01) (prog-if 40 [USB4 Host Interface])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d140000 (64-bit, non-prefetchable) [size=256K]
	Region 2: Memory at 603d1e9000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [88] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [a0] MSI-X: Enable+ Count=16 Masked-
		Vector table: BAR=2 offset=00000000
		PBA: BAR=2 offset=00000fa0
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt

00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt NHI #1 (rev 01) (prog-if 40 [USB4 Host Interface])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d100000 (64-bit, non-prefetchable) [size=256K]
	Region 2: Memory at 603d1e8000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [88] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [a0] MSI-X: Enable+ Count=16 Masked-
		Vector table: BAR=2 offset=00000000
		PBA: BAR=2 offset=00000fa0
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt

00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated Sensor Hub (rev 20) (prog-if 00 [8250])
	Subsystem: Dell Tiger Lake-LP Integrated Sensor Hub
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d1b0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel_ish_ipc
	Kernel modules: intel_ish_ipc

00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20) (prog-if 30 [XHCI])
	Subsystem: Dell Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 142
	Region 0: Memory at 603d1a0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
		Address: 00000000fee10004  Data: 4022
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Capabilities: [b0] Vendor Specific Information: Len=00 <?>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
	Subsystem: Dell Tiger Lake-LP Shared SRAM
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 603d1dc000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Region 2: Memory at 603d1e7000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-

00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 27
	Region 0: Memory at 4017000000 (64-bit, non-prefetchable) [virtual] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 40
	Region 0: Memory at 4017001000 (64-bit, non-prefetchable) [virtual] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
	Subsystem: Dell Tiger Lake-LP Management Engine Interface
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 171
	Region 0: Memory at 603d1e4000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee02004  Data: 4025
	Capabilities: [a4] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:19.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #4 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 31
	Region 0: Memory at 4017002000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:19.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #5 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 32
	Region 0: Memory at 4017003000 (64-bit, non-prefetchable) [virtual] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 123
	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c300000-8c3fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee20004  Data: 4021
	Capabilities: [90] Subsystem: Dell Device 0991
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D3 NoSoftRst- PME-Enable+ DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=70us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=44us
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1d.0 PCI bridge: Intel Corporation Device a0b3 (rev 20) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin D routed to IRQ 124
	Bus: primary=00, secondary=57, subordinate=57, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c200000-8c2fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #12, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #11, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee40004  Data: 4021
	Capabilities: [90] Subsystem: Dell Device 0991
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=60us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=60us
	Capabilities: [a30 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1e.0 Communication controller: Intel Corporation Tiger Lake-LP Serial IO UART Controller #0 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO UART Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 4017004000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP LPC Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP Smart Sound Technology Audio Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 174
	Region 0: Memory at 603d1d8000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at 603d000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Vendor Specific Information: Len=14 <?>
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee04004  Data: 4025
	Kernel driver in use: sof-audio-pci
	Kernel modules: snd_hda_intel, snd_sof_pci

00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP SMBus Controller
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d1e0000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP SPI Controller
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 70800000 (32-bit, non-prefetchable) [size=4K]

01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
	Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	NUMA node: 0
	Region 0: Memory at 8c400000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 75.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x4 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
		Vector table: BAR=0 offset=00003000
		PBA: BAR=0 offset=00002000
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap+ MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [158 v1] Power Budgeting <?>
	Capabilities: [168 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [188 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [190 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=10us PortTPowerOnTime=10us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=50us
	Kernel driver in use: nvme
	Kernel modules: nvme

56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
	Subsystem: Bigfoot Networks, Inc. Device a501
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit-
		Address: 00000000  Data: 0000
		Masking: 00000000  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (downgraded), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp+ ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [158 v1] Transaction Processing Hints
		No steering table available
	Capabilities: [1e4 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [1ec v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=70us PortTPowerOnTime=0us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=44us
	Kernel modules: ath11k_pci

57:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)
	Subsystem: Dell RTS5260 PCI Express Card Reader
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 144
	Region 0: Memory at 8c200000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee20004  Data: 4022
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 unlimited
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via message/WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Device Serial Number 00-00-00-01-00-4c-e0-00
	Capabilities: [158 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [168 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [170 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=60us PortTPowerOnTime=60us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=60us
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]


> Can I have a full dmesg please?
>
> Please enable CONFIG_IRQ_REMAP and CONFIG_INTEL_IOMMU (not strictly
> required, but it's a Dell BIOS after all). Also set
> CONFIG_INTEL_IOMMU_DEFAULT_ON.

I attached a full dmesg with the latest ath11k master and the 
configuration enabled. VT-d was enabled in BIOS. Most options have been 
already been present in the previous attempts (copied from the distro 
config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
hope this helps, if there is more I can do to debug it on my side I'm 
happy to do so.


[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 83128 bytes --]

[    0.000000] Linux version 5.10.0-rc1-wt-ath+ (thomas@tk-9310) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #1 SMP Wed Nov 4 12:19:14 CET 2020
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-rc1-wt-ath+ root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000]   zhaoxin   Shanghai  
[    0.000000] x86/split lock detection: warning about user-space split_locks
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: xstate_offset[5]:  832, xstate_sizes[5]:   64
[    0.000000] x86/fpu: xstate_offset[6]:  896, xstate_sizes[6]:  512
[    0.000000] x86/fpu: xstate_offset[7]: 1408, xstate_sizes[7]: 1024
[    0.000000] x86/fpu: xstate_offset[9]: 2432, xstate_sizes[9]:    8
[    0.000000] x86/fpu: Enabled xstate features 0x2e7, context size is 2440 bytes, using 'compacted' format.
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005f72afff] usable
[    0.000000] BIOS-e820: [mem 0x000000005f72b000-0x0000000063510fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000063511000-0x0000000063d71fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000063d72000-0x0000000063ffefff] ACPI data
[    0.000000] BIOS-e820: [mem 0x0000000063fff000-0x0000000063ffffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000064000000-0x0000000067ffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000068600000-0x00000000687fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000069000000-0x00000000707fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000088f7fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.70 by Dell
[    0.000000] efi: ACPI=0x63ffe000 ACPI 2.0=0x63ffe014 SMBIOS=0x5fdd7000 TPMFinalLog=0x63cd8000 ESRT=0x5fcecd18 MEMATTR=0x588b3018 RNG=0x5fcf0f98 TPMEventLog=0x5ad43018 
[    0.000000] efi: seeding entropy pool
[    0.000000] random: fast init done
[    0.000000] SMBIOS 3.2 present.
[    0.000000] DMI: Dell Inc. XPS 13 9310/0F7M4C, BIOS 1.1.1 10/05/2020
[    0.000000] tsc: Detected 2800.000 MHz processor
[    0.000000] tsc: Detected 2803.200 MHz TSC
[    0.000004] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000005] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000009] last_pfn = 0x88f800 max_arch_pfn = 0x400000000
[    0.000011] MTRR default type: write-back
[    0.000011] MTRR fixed ranges enabled:
[    0.000012]   00000-9FFFF write-back
[    0.000012]   A0000-BFFFF uncachable
[    0.000013]   C0000-FFFFF write-protect
[    0.000013] MTRR variable ranges enabled:
[    0.000014]   0 base 0080000000 mask 7F80000000 uncachable
[    0.000015]   1 base 0070000000 mask 7FF0000000 uncachable
[    0.000015]   2 base 006C000000 mask 7FFC000000 uncachable
[    0.000016]   3 base 2000000000 mask 6000000000 uncachable
[    0.000016]   4 base 1000000000 mask 7000000000 uncachable
[    0.000016]   5 base 4000000000 mask 4000000000 uncachable
[    0.000017]   6 disabled
[    0.000017]   7 disabled
[    0.000017]   8 disabled
[    0.000018]   9 disabled
[    0.000450] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[    0.000802] last_pfn = 0x64000 max_arch_pfn = 0x400000000
[    0.007947] esrt: Reserving ESRT space from 0x000000005fcecd18 to 0x000000005fcecda0.
[    0.007956] check: Scanning 1 areas for low memory corruption
[    0.007960] Using GB pages for direct mapping
[    0.008076] Secure boot disabled
[    0.008076] RAMDISK: [mem 0x22f82000-0x28496fff]
[    0.008091] ACPI: Early table checksum verification disabled
[    0.008094] ACPI: RSDP 0x0000000063FFE014 000024 (v02 DELL  )
[    0.008097] ACPI: XSDT 0x0000000063F79188 00010C (v01 DELL   Dell Inc 00000002      01000013)
[    0.008102] ACPI: FACP 0x0000000063FF5000 000114 (v06 DELL   Dell Inc 00000002      01000013)
[    0.008106] ACPI: DSDT 0x0000000063F98000 05903E (v02 DELL   Dell Inc 00000002      01000013)
[    0.008108] ACPI: FACS 0x0000000063D1B000 000040
[    0.008110] ACPI: SSDT 0x0000000063FFA000 00255D (v02 CpuRef CpuSsdt  00003000 INTL 20191018)
[    0.008112] ACPI: SSDT 0x0000000063FF6000 0038E4 (v02 DptfTb DptfTabl 00001000 INTL 20191018)
[    0.008114] ACPI: HPET 0x0000000063FF4000 000038 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008116] ACPI: APIC 0x0000000063FF3000 00012C (v04 DELL   Dell Inc 00000002      01000013)
[    0.008118] ACPI: MCFG 0x0000000063FF2000 00003C (v01 DELL   Dell Inc 00000002      01000013)
[    0.008120] ACPI: SSDT 0x0000000063F97000 000D01 (v02 DELL   DellRtd3 00001000 INTL 20191018)
[    0.008121] ACPI: NHLT 0x0000000063F95000 001B54 (v00 DELL   Dell Inc 00000002      01000013)
[    0.008123] ACPI: SSDT 0x0000000063F92000 002BB5 (v02 SaSsdt SaSsdt   00003000 INTL 20191018)
[    0.008125] ACPI: SSDT 0x0000000063F90000 0012AA (v02 INTEL  IgfxSsdt 00003000 INTL 20191018)
[    0.008127] ACPI: SSDT 0x0000000063F84000 00B192 (v02 INTEL  TcssSsdt 00001000 INTL 20191018)
[    0.008129] ACPI: SSDT 0x0000000063F83000 000CD2 (v02 DELL   UsbCTabl 00001000 INTL 20191018)
[    0.008131] ACPI: LPIT 0x0000000063F82000 0000CC (v01 DELL   Dell Inc 00000002      01000013)
[    0.008133] ACPI: WSMT 0x0000000063F81000 000028 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008135] ACPI: SSDT 0x0000000063F80000 000B75 (v02 DELL   PtidDevc 00001000 INTL 20191018)
[    0.008137] ACPI: SSDT 0x0000000063F7F000 00012A (v02 DELL   TbtTypeC 00000000 INTL 20191018)
[    0.008139] ACPI: DBGP 0x0000000063F7E000 000034 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008141] ACPI: DBG2 0x0000000063F7D000 000054 (v00 DELL   Dell Inc 00000002      01000013)
[    0.008143] ACPI: SLIC 0x0000000063F7C000 000176 (v03 DELL   CBX3     06222004 MSFT 00010013)
[    0.008144] ACPI: BOOT 0x0000000063F7B000 000028 (v01 DELL   CBX3     00000002      01000013)
[    0.008146] ACPI: SSDT 0x0000000063F7A000 00060E (v02 DELL   Tpm2Tabl 00001000 INTL 20191018)
[    0.008148] ACPI: TPM2 0x0000000063FFD000 00004C (v04 DELL   Dell Inc 00000002      01000013)
[    0.008150] ACPI: MSDM 0x0000000063F78000 000055 (v03 DELL   CBX3     06222004 AMI  00010013)
[    0.008152] ACPI: DMAR 0x0000000063F77000 0000A8 (v02 INTEL  Dell Inc 00000002      01000013)
[    0.008154] ACPI: SSDT 0x0000000063F76000 000841 (v02 DELL   xh_Dell_ 00000000 INTL 20191018)
[    0.008156] ACPI: SSDT 0x0000000063F75000 000144 (v02 Intel  ADebTabl 00001000 INTL 20191018)
[    0.008158] ACPI: PTDT 0x0000000063F74000 000D44 (v00 DELL   Dell Inc 00000005 MSFT 0100000D)
[    0.008160] ACPI: BGRT 0x0000000063F73000 000038 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008162] ACPI: FPDT 0x0000000063F72000 000034 (v01 DELL   Dell Inc 00000002      01000013)
[    0.008168] ACPI: Local APIC address 0xfee00000
[    0.008441] No NUMA configuration found
[    0.008441] Faking a node at [mem 0x0000000000000000-0x000000088f7fffff]
[    0.008447] NODE_DATA(0) allocated [mem 0x88f7d6000-0x88f7fffff]
[    0.008637] Zone ranges:
[    0.008638]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.008638]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.008639]   Normal   [mem 0x0000000100000000-0x000000088f7fffff]
[    0.008640]   Device   empty
[    0.008641] Movable zone start for each node
[    0.008643] Early memory node ranges
[    0.008643]   node   0: [mem 0x0000000000001000-0x000000000009efff]
[    0.008644]   node   0: [mem 0x0000000000100000-0x000000005f72afff]
[    0.008644]   node   0: [mem 0x0000000063fff000-0x0000000063ffffff]
[    0.008645]   node   0: [mem 0x0000000100000000-0x000000088f7fffff]
[    0.008929] Zeroed struct page in unavailable ranges: 37174 pages
[    0.008931] Initmem setup node 0 [mem 0x0000000000001000-0x000000088f7fffff]
[    0.008932] On node 0 totalpages: 8318666
[    0.008933]   DMA zone: 64 pages used for memmap
[    0.008933]   DMA zone: 22 pages reserved
[    0.008934]   DMA zone: 3998 pages, LIFO batch:0
[    0.008957]   DMA32 zone: 6045 pages used for memmap
[    0.008958]   DMA32 zone: 386860 pages, LIFO batch:63
[    0.010805]   Normal zone: 123872 pages used for memmap
[    0.010805]   Normal zone: 7927808 pages, LIFO batch:63
[    0.046187] Reserving Intel graphics memory at [mem 0x6c800000-0x707fffff]
[    0.046975] ACPI: PM-Timer IO Port: 0x1808
[    0.046976] ACPI: Local APIC address 0xfee00000
[    0.046981] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.046982] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.046982] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.046982] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.046983] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.046983] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.046983] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.046984] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.046984] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
[    0.046984] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
[    0.046985] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
[    0.046985] ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
[    0.046985] ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
[    0.046986] ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
[    0.046986] ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
[    0.046986] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
[    0.047022] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119
[    0.047023] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.047024] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.047025] ACPI: IRQ0 used by override.
[    0.047026] ACPI: IRQ9 used by override.
[    0.047027] Using ACPI (MADT) for SMP configuration information
[    0.047028] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.047033] e820: update [mem 0x5ad50000-0x5ad6dfff] usable ==> reserved
[    0.047038] TSC deadline timer available
[    0.047038] smpboot: Allowing 8 CPUs, 0 hotplug CPUs
[    0.047046] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.047047] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x000fffff]
[    0.047047] PM: hibernation: Registered nosave memory: [mem 0x5ad50000-0x5ad6dfff]
[    0.047048] PM: hibernation: Registered nosave memory: [mem 0x5f72b000-0x63510fff]
[    0.047049] PM: hibernation: Registered nosave memory: [mem 0x63511000-0x63d71fff]
[    0.047049] PM: hibernation: Registered nosave memory: [mem 0x63d72000-0x63ffefff]
[    0.047050] PM: hibernation: Registered nosave memory: [mem 0x64000000-0x67ffffff]
[    0.047050] PM: hibernation: Registered nosave memory: [mem 0x68000000-0x685fffff]
[    0.047050] PM: hibernation: Registered nosave memory: [mem 0x68600000-0x687fffff]
[    0.047051] PM: hibernation: Registered nosave memory: [mem 0x68800000-0x68ffffff]
[    0.047051] PM: hibernation: Registered nosave memory: [mem 0x69000000-0x707fffff]
[    0.047051] PM: hibernation: Registered nosave memory: [mem 0x70800000-0xbfffffff]
[    0.047052] PM: hibernation: Registered nosave memory: [mem 0xc0000000-0xcfffffff]
[    0.047052] PM: hibernation: Registered nosave memory: [mem 0xd0000000-0xfed1ffff]
[    0.047052] PM: hibernation: Registered nosave memory: [mem 0xfed20000-0xfed7ffff]
[    0.047053] PM: hibernation: Registered nosave memory: [mem 0xfed80000-0xfeffffff]
[    0.047053] PM: hibernation: Registered nosave memory: [mem 0xff000000-0xffffffff]
[    0.047054] [mem 0x70800000-0xbfffffff] available for PCI devices
[    0.047055] Booting paravirtualized kernel on bare hardware
[    0.047056] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645519600211568 ns
[    0.047060] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:8 nr_cpu_ids:8 nr_node_ids:1
[    0.047164] percpu: Embedded 56 pages/cpu s192512 r8192 d28672 u262144
[    0.047167] pcpu-alloc: s192512 r8192 d28672 u262144 alloc=1*2097152
[    0.047168] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
[    0.047182] Built 1 zonelists, mobility grouping on.  Total pages: 8188663
[    0.047183] Policy zone: Normal
[    0.047183] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-rc1-wt-ath+ root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
[    0.048019] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes, linear)
[    0.048423] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes, linear)
[    0.048474] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!
               BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version: 
[    0.091268] Memory: 32407176K/33274664K available (14345K kernel code, 3506K rwdata, 5212K rodata, 2636K init, 6000K bss, 867228K reserved, 0K cma-reserved)
[    0.091273] random: get_random_u64 called from __kmem_cache_create+0x2d/0x540 with crng_init=1
[    0.091351] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.091358] ftrace: allocating 46263 entries in 181 pages
[    0.100864] ftrace: allocated 181 pages with 5 groups
[    0.100940] rcu: Hierarchical RCU implementation.
[    0.100941] rcu: 	RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=8.
[    0.100942] 	Rude variant of Tasks RCU enabled.
[    0.100942] 	Tracing variant of Tasks RCU enabled.
[    0.100943] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.100943] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=8
[    0.102847] NR_IRQS: 524544, nr_irqs: 2048, preallocated irqs: 16
[    0.103281] random: crng done (trusting CPU's manufacturer)
[    0.103295] Console: colour dummy device 80x25
[    0.103303] printk: console [tty0] enabled
[    0.103314] ACPI: Core revision 20200925
[    0.103583] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 99544814920 ns
[    0.103691] APIC: Switch to symmetric I/O mode setup
[    0.103693] DMAR: Host address width 39
[    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
[    0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 69e2ff0505e
[    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
[    0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
[    0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap d2008c40660462 ecap f050da
[    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
[    0.103707] DMAR: Parse DMAR table failure.
[    0.104980] x2apic: IRQ remapping doesn't support X2APIC mode
[    0.109990] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.127643] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x28680fa287f, max_idle_ns: 440795281151 ns
[    0.127646] Calibrating delay loop (skipped), value calculated using timer frequency.. 5606.40 BogoMIPS (lpj=11212800)
[    0.127648] pid_max: default: 32768 minimum: 301
[    0.129518] LSM: Security Framework initializing
[    0.129527] Yama: becoming mindful.
[    0.129556] AppArmor: AppArmor initialized
[    0.129625] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.129682] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.129857] x86/cpu: User Mode Instruction Prevention (UMIP) activated
[    0.129885] mce: CPU0: Thermal monitoring enabled (TM1)
[    0.129950] process: using mwait in idle threads
[    0.129951] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[    0.129952] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[    0.129954] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.129955] Spectre V2 : Mitigation: Enhanced IBRS
[    0.129955] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.129957] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier
[    0.129957] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp
[    0.130177] Freeing SMP alternatives memory: 40K
[    0.131733] smpboot: CPU0: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (family: 0x6, model: 0x8c, stepping: 0x1)
[    0.131801] Performance Events: PEBS fmt4+-baseline, Icelake events, 32-deep LBR, full-width counters, Intel PMU driver.
[    0.131808] ... version:                5
[    0.131808] ... bit width:              48
[    0.131808] ... generic registers:      8
[    0.131809] ... value mask:             0000ffffffffffff
[    0.131809] ... max period:             00007fffffffffff
[    0.131809] ... fixed-purpose events:   4
[    0.131810] ... event mask:             0001000f000000ff
[    0.131857] rcu: Hierarchical SRCU implementation.
[    0.132296] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
[    0.132345] smp: Bringing up secondary CPUs ...
[    0.132390] x86: Booting SMP configuration:
[    0.132391] .... node  #0, CPUs:      #1 #2 #3 #4 #5 #6 #7
[    0.141093] smp: Brought up 1 node, 8 CPUs
[    0.141093] smpboot: Max logical packages: 1
[    0.141093] smpboot: Total of 8 processors activated (44851.20 BogoMIPS)
[    0.144518] devtmpfs: initialized
[    0.144518] x86/mm: Memory block size: 128MB
[    0.144701] PM: Registering ACPI NVS region [mem 0x63511000-0x63d71fff] (8785920 bytes)
[    0.144701] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.144701] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[    0.144701] pinctrl core: initialized pinctrl subsystem
[    0.144701] PM: RTC time: 12:34:09, date: 2020-11-04
[    0.144701] NET: Registered protocol family 16
[    0.144701] DMA: preallocated 4096 KiB GFP_KERNEL pool for atomic allocations
[    0.144701] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.144723] DMA: preallocated 4096 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.144728] audit: initializing netlink subsys (disabled)
[    0.144733] audit: type=2000 audit(1604493249.040:1): state=initialized audit_enabled=0 res=1
[    0.144733] thermal_sys: Registered thermal governor 'fair_share'
[    0.144733] thermal_sys: Registered thermal governor 'bang_bang'
[    0.144733] thermal_sys: Registered thermal governor 'step_wise'
[    0.144733] thermal_sys: Registered thermal governor 'user_space'
[    0.144733] thermal_sys: Registered thermal governor 'power_allocator'
[    0.144733] EISA bus registered
[    0.144733] cpuidle: using governor ladder
[    0.144733] cpuidle: using governor menu
[    0.144733] Simple Boot Flag at 0x47 set to 0x80
[    0.144733] ACPI: bus type PCI registered
[    0.144733] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.144733] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xc0000000-0xcfffffff] (base 0xc0000000)
[    0.144733] PCI: MMCONFIG at [mem 0xc0000000-0xcfffffff] reserved in E820
[    0.144733] PCI: Using configuration type 1 for base access
[    0.147650] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.148275] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.148275] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.148275] ACPI: Added _OSI(Module Device)
[    0.148275] ACPI: Added _OSI(Processor Device)
[    0.148275] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.148275] ACPI: Added _OSI(Processor Aggregator Device)
[    0.148275] ACPI: Added _OSI(Linux-Dell-Video)
[    0.148275] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.148275] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.202420] ACPI: 13 ACPI AML tables successfully acquired and loaded
[    0.215261] ACPI: Dynamic OEM Table Load:
[    0.215268] ACPI: SSDT 0xFFFF934700DF7E00 0001CB (v02 PmRef  Cpu0Psd  00003000 INTL 20191018)
[    0.216201] ACPI: \_SB_.PR00: _OSC native thermal LVT Acked
[    0.218127] ACPI: Dynamic OEM Table Load:
[    0.218131] ACPI: SSDT 0xFFFF934700DB5400 000394 (v02 PmRef  Cpu0Cst  00003001 INTL 20191018)
[    0.219215] ACPI: Dynamic OEM Table Load:
[    0.219219] ACPI: SSDT 0xFFFF9347015C6800 000647 (v02 PmRef  Cpu0Ist  00003000 INTL 20191018)
[    0.220376] ACPI: Dynamic OEM Table Load:
[    0.220380] ACPI: SSDT 0xFFFF934700DB6C00 000266 (v02 PmRef  Cpu0Hwp  00003000 INTL 20191018)
[    0.221595] ACPI: Dynamic OEM Table Load:
[    0.221599] ACPI: SSDT 0xFFFF93470013A000 0008E7 (v02 PmRef  ApIst    00003000 INTL 20191018)
[    0.222798] ACPI: Dynamic OEM Table Load:
[    0.222801] ACPI: SSDT 0xFFFF9347015C3000 00048A (v02 PmRef  ApHwp    00003000 INTL 20191018)
[    0.223913] ACPI: Dynamic OEM Table Load:
[    0.223916] ACPI: SSDT 0xFFFF9347015C4000 0004D2 (v02 PmRef  ApPsd    00003000 INTL 20191018)
[    0.225037] ACPI: Dynamic OEM Table Load:
[    0.225040] ACPI: SSDT 0xFFFF9347015C7000 00048A (v02 PmRef  ApCst    00003000 INTL 20191018)
[    0.229625] ACPI: EC: EC started
[    0.229625] ACPI: EC: interrupt blocked
[    0.232144] ACPI: EC: EC_CMD/EC_SC=0x934, EC_DATA=0x930
[    0.232145] ACPI: \_SB_.PC00.LPCB.ECDV: Boot DSDT EC used to handle transactions
[    0.232145] ACPI: Interpreter enabled
[    0.232186] ACPI: (supports S0 S4 S5)
[    0.232187] ACPI: Using IOAPIC for interrupt routing
[    0.232222] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.233868] ACPI: Enabled 8 GPEs in block 00 to 7F
[    0.239996] ACPI: Power Resource [WRST] (on)
[    0.240014] ACPI: Power Resource [DRST] (on)
[    0.245952] ACPI: Power Resource [V0PR] (on)
[    0.246062] ACPI: Power Resource [V1PR] (on)
[    0.246166] ACPI: Power Resource [V2PR] (on)
[    0.249717] ACPI: Power Resource [WRST] (on)
[    0.257257] ACPI: Power Resource [TBT0] (on)
[    0.257292] ACPI: Power Resource [TBT1] (on)
[    0.257319] ACPI: Power Resource [D3C] (on)
[    0.497199] ACPI: Power Resource [PIN] (off)
[    0.497496] ACPI: PCI Root Bridge [PC00] (domain 0000 [bus 00-fe])
[    0.497500] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.499133] acpi PNP0A08:00: _OSC: platform does not support [AER]
[    0.502179] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME PCIeCapability LTR]
[    0.505031] PCI host bridge to bus 0000:00
[    0.505032] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.505033] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff window]
[    0.505033] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window]
[    0.505034] pci_bus 0000:00: root bus resource [mem 0x70800000-0xbfffffff window]
[    0.505034] pci_bus 0000:00: root bus resource [mem 0x4000000000-0x7fffffffff window]
[    0.505035] pci_bus 0000:00: root bus resource [bus 00-fe]
[    0.505059] pci 0000:00:00.0: [8086:9a14] type 00 class 0x060000
[    0.506292] pci 0000:00:02.0: [8086:9a49] type 00 class 0x030000
[    0.506300] pci 0000:00:02.0: reg 0x10: [mem 0x603c000000-0x603cffffff 64bit]
[    0.506304] pci 0000:00:02.0: reg 0x18: [mem 0x4000000000-0x400fffffff 64bit pref]
[    0.506307] pci 0000:00:02.0: reg 0x20: [io  0x3000-0x303f]
[    0.506320] pci 0000:00:02.0: BAR 2: assigned to efifb
[    0.506321] pci 0000:00:02.0: DMAR: Skip IOMMU disabling for graphics
[    0.506344] pci 0000:00:02.0: reg 0x344: [mem 0x00000000-0x00ffffff 64bit]
[    0.506345] pci 0000:00:02.0: VF(n) BAR0 space: [mem 0x00000000-0x06ffffff 64bit] (contains BAR0 for 7 VFs)
[    0.506349] pci 0000:00:02.0: reg 0x34c: [mem 0x00000000-0x1fffffff 64bit pref]
[    0.506349] pci 0000:00:02.0: VF(n) BAR2 space: [mem 0x00000000-0xdfffffff 64bit pref] (contains BAR2 for 7 VFs)
[    0.507214] pci 0000:00:04.0: [8086:9a03] type 00 class 0x118000
[    0.507229] pci 0000:00:04.0: reg 0x10: [mem 0x603d180000-0x603d19ffff 64bit]
[    0.508179] pci 0000:00:06.0: [8086:9a09] type 01 class 0x060400
[    0.508267] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
[    0.508302] pci 0000:00:06.0: PTM enabled (root), 4ns granularity
[    0.509228] pci 0000:00:07.0: [8086:9a23] type 01 class 0x060400
[    0.510098] pci 0000:00:07.0: PME# supported from D0 D3hot D3cold
[    0.510119] pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid
[    0.510126] fbcon: Taking over console
[    0.510230] pci 0000:00:07.2: [8086:9a27] type 01 class 0x060400
[    0.511100] pci 0000:00:07.2: PME# supported from D0 D3hot D3cold
[    0.511121] pci 0000:00:07.2: DPC: RP PIO log size 0 is invalid
[    0.511234] pci 0000:00:0a.0: [8086:9a0d] type 00 class 0x118000
[    0.511240] pci 0000:00:0a.0: reg 0x10: [mem 0x603d1d0000-0x603d1d7fff 64bit]
[    0.511259] pci 0000:00:0a.0: enabling Extended Tags
[    0.512127] pci 0000:00:0d.0: [8086:9a13] type 00 class 0x0c0330
[    0.512139] pci 0000:00:0d.0: reg 0x10: [mem 0x603d1c0000-0x603d1cffff 64bit]
[    0.512192] pci 0000:00:0d.0: PME# supported from D3hot D3cold
[    0.513071] pci 0000:00:0d.2: [8086:9a1b] type 00 class 0x0c0340
[    0.513081] pci 0000:00:0d.2: reg 0x10: [mem 0x603d140000-0x603d17ffff 64bit]
[    0.513088] pci 0000:00:0d.2: reg 0x18: [mem 0x603d1e9000-0x603d1e9fff 64bit]
[    0.513123] pci 0000:00:0d.2: supports D1 D2
[    0.513123] pci 0000:00:0d.2: PME# supported from D0 D1 D2 D3hot D3cold
[    0.513966] pci 0000:00:0d.3: [8086:9a1d] type 00 class 0x0c0340
[    0.513976] pci 0000:00:0d.3: reg 0x10: [mem 0x603d100000-0x603d13ffff 64bit]
[    0.513983] pci 0000:00:0d.3: reg 0x18: [mem 0x603d1e8000-0x603d1e8fff 64bit]
[    0.514016] pci 0000:00:0d.3: supports D1 D2
[    0.514017] pci 0000:00:0d.3: PME# supported from D0 D1 D2 D3hot D3cold
[    0.514894] pci 0000:00:12.0: [8086:a0fc] type 00 class 0x070000
[    0.514915] pci 0000:00:12.0: reg 0x10: [mem 0x603d1b0000-0x603d1bffff 64bit]
[    0.514986] pci 0000:00:12.0: PME# supported from D0 D3hot
[    0.515927] pci 0000:00:14.0: [8086:a0ed] type 00 class 0x0c0330
[    0.515948] pci 0000:00:14.0: reg 0x10: [mem 0x603d1a0000-0x603d1affff 64bit]
[    0.516033] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.516924] pci 0000:00:14.2: [8086:a0ef] type 00 class 0x050000
[    0.516943] pci 0000:00:14.2: reg 0x10: [mem 0x603d1dc000-0x603d1dffff 64bit]
[    0.516956] pci 0000:00:14.2: reg 0x18: [mem 0x603d1e7000-0x603d1e7fff 64bit]
[    0.517907] pci 0000:00:15.0: [8086:a0e8] type 00 class 0x0c8000
[    0.517938] pci 0000:00:15.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.518983] pci 0000:00:15.1: [8086:a0e9] type 00 class 0x0c8000
[    0.519013] pci 0000:00:15.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.520051] pci 0000:00:16.0: [8086:a0e0] type 00 class 0x078000
[    0.520073] pci 0000:00:16.0: reg 0x10: [mem 0x603d1e4000-0x603d1e4fff 64bit]
[    0.520158] pci 0000:00:16.0: PME# supported from D3hot
[    0.521134] pci 0000:00:19.0: [8086:a0c5] type 00 class 0x0c8000
[    0.521164] pci 0000:00:19.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.522189] pci 0000:00:19.1: [8086:a0c6] type 00 class 0x0c8000
[    0.522219] pci 0000:00:19.1: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.523246] pci 0000:00:1c.0: [8086:a0b8] type 01 class 0x060400
[    0.523344] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.523371] pci 0000:00:1c.0: PTM enabled (root), 4ns granularity
[    0.524304] pci 0000:00:1d.0: [8086:a0b3] type 01 class 0x060400
[    0.524403] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[    0.524433] pci 0000:00:1d.0: PTM enabled (root), 4ns granularity
[    0.525404] pci 0000:00:1e.0: [8086:a0a8] type 00 class 0x078000
[    0.525433] pci 0000:00:1e.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[    0.526472] pci 0000:00:1f.0: [8086:a082] type 00 class 0x060100
[    0.527455] pci 0000:00:1f.3: [8086:a0c8] type 00 class 0x040100
[    0.527497] pci 0000:00:1f.3: reg 0x10: [mem 0x603d1d8000-0x603d1dbfff 64bit]
[    0.527551] pci 0000:00:1f.3: reg 0x20: [mem 0x603d000000-0x603d0fffff 64bit]
[    0.527660] pci 0000:00:1f.3: PME# supported from D3hot D3cold
[    0.528571] pci 0000:00:1f.4: [8086:a0a3] type 00 class 0x0c0500
[    0.528593] pci 0000:00:1f.4: reg 0x10: [mem 0x603d1e0000-0x603d1e00ff 64bit]
[    0.528615] pci 0000:00:1f.4: reg 0x20: [io  0xefa0-0xefbf]
[    0.529501] pci 0000:00:1f.5: [8086:a0a4] type 00 class 0x0c8000
[    0.529519] pci 0000:00:1f.5: reg 0x10: [mem 0xfe010000-0xfe010fff]
[    0.530759] pci 0000:01:00.0: [144d:a808] type 00 class 0x010802
[    0.530774] pci 0000:01:00.0: reg 0x10: [mem 0x8c400000-0x8c403fff 64bit]
[    0.530951] pci 0000:00:06.0: PCI bridge to [bus 01]
[    0.530953] pci 0000:00:06.0:   bridge window [mem 0x8c400000-0x8c4fffff]
[    0.530985] pci 0000:00:07.0: PCI bridge to [bus 02-2b]
[    0.530988] pci 0000:00:07.0:   bridge window [mem 0x80000000-0x8c1fffff]
[    0.530992] pci 0000:00:07.0:   bridge window [mem 0x6000000000-0x601bffffff 64bit pref]
[    0.531021] pci 0000:00:07.2: PCI bridge to [bus 2c-55]
[    0.531025] pci 0000:00:07.2:   bridge window [mem 0x72000000-0x7e1fffff]
[    0.531028] pci 0000:00:07.2:   bridge window [mem 0x6020000000-0x603bffffff 64bit pref]
[    0.531101] pci 0000:56:00.0: [17cb:1101] type 00 class 0x028000
[    0.531124] pci 0000:56:00.0: reg 0x10: [mem 0x8c300000-0x8c3fffff 64bit]
[    0.531262] pci 0000:56:00.0: PME# supported from D0 D3hot D3cold
[    0.531334] pci 0000:56:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0000:00:1c.0 (capable of 7.876 Gb/s with 8.0 GT/s PCIe x1 link)
[    0.531418] pci 0000:00:1c.0: PCI bridge to [bus 56]
[    0.531422] pci 0000:00:1c.0:   bridge window [mem 0x8c300000-0x8c3fffff]
[    0.531487] pci 0000:57:00.0: [10ec:5260] type 00 class 0xff0000
[    0.531503] pci 0000:57:00.0: reg 0x10: [mem 0x8c200000-0x8c200fff]
[    0.531637] pci 0000:57:00.0: supports D1 D2
[    0.531638] pci 0000:57:00.0: PME# supported from D1 D2 D3hot D3cold
[    0.531773] pci 0000:00:1d.0: PCI bridge to [bus 57]
[    0.531778] pci 0000:00:1d.0:   bridge window [mem 0x8c200000-0x8c2fffff]
[    0.551101] ACPI: EC: interrupt unblocked
[    0.551102] ACPI: EC: event unblocked
[    0.551109] ACPI: EC: EC_CMD/EC_SC=0x934, EC_DATA=0x930
[    0.551109] ACPI: EC: GPE=0x6e
[    0.551110] ACPI: \_SB_.PC00.LPCB.ECDV: Boot DSDT EC initialization complete
[    0.551111] ACPI: \_SB_.PC00.LPCB.ECDV: EC: Used to handle transactions and events
[    0.551191] iommu: Default domain type: Translated 
[    0.551191] pci 0000:00:02.0: vgaarb: setting as boot VGA device
[    0.551191] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
[    0.551191] pci 0000:00:02.0: vgaarb: bridge control possible
[    0.551191] vgaarb: loaded
[    0.551191] SCSI subsystem initialized
[    0.551191] libata version 3.00 loaded.
[    0.551191] ACPI: bus type USB registered
[    0.551191] usbcore: registered new interface driver usbfs
[    0.551191] usbcore: registered new interface driver hub
[    0.551191] usbcore: registered new device driver usb
[    0.551191] pps_core: LinuxPPS API ver. 1 registered
[    0.551191] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.551191] PTP clock support registered
[    0.551191] EDAC MC: Ver: 3.0.0
[    0.552083] Registered efivars operations
[    0.552083] NetLabel: Initializing
[    0.552083] NetLabel:  domain hash size = 128
[    0.552083] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.552083] NetLabel:  unlabeled traffic allowed by default
[    0.552083] PCI: Using ACPI for IRQ routing
[    0.569343] PCI: pci_cache_line_size set to 64 bytes
[    0.569832] pci 0000:00:1f.5: can't claim BAR 0 [mem 0xfe010000-0xfe010fff]: no compatible bridge window
[    0.570262] e820: reserve RAM buffer [mem 0x0009f000-0x0009ffff]
[    0.570263] e820: reserve RAM buffer [mem 0x5ad50000-0x5bffffff]
[    0.570264] e820: reserve RAM buffer [mem 0x5f72b000-0x5fffffff]
[    0.570264] e820: reserve RAM buffer [mem 0x88f800000-0x88fffffff]
[    0.570268] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.570268] hpet0: 8 comparators, 64-bit 19.200000 MHz counter
[    0.573693] clocksource: Switched to clocksource tsc-early
[    0.577600] VFS: Disk quotas dquot_6.6.0
[    0.577600] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.577600] AppArmor: AppArmor Filesystem Enabled
[    0.577600] pnp: PnP ACPI init
[    0.577600] system 00:00: [io  0x0680-0x069f] has been reserved
[    0.577600] system 00:00: [io  0x164e-0x164f] has been reserved
[    0.577600] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.577600] pnp 00:01: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.577600] system 00:02: [io  0x1854-0x1857] has been reserved
[    0.577600] system 00:02: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.577600] pnp 00:03: Plug and Play ACPI device, IDs PNP0303 (active)
[    0.577600] pnp 00:04: Plug and Play ACPI device, IDs DLL0991 PNP0f13 (active)
[    0.580221] pnp 00:05: disabling [mem 0xc0000000-0xcfffffff] because it overlaps 0000:00:02.0 BAR 9 [mem 0x00000000-0xdfffffff 64bit pref]
[    0.580237] system 00:05: [mem 0xfedc0000-0xfedc7fff] has been reserved
[    0.580237] system 00:05: [mem 0xfeda0000-0xfeda0fff] has been reserved
[    0.580238] system 00:05: [mem 0xfeda1000-0xfeda1fff] has been reserved
[    0.580239] system 00:05: [mem 0xfed20000-0xfed7ffff] could not be reserved
[    0.580239] system 00:05: [mem 0xfed90000-0xfed93fff] could not be reserved
[    0.580240] system 00:05: [mem 0xfed45000-0xfed8ffff] could not be reserved
[    0.580241] system 00:05: [mem 0xfee00000-0xfeefffff] has been reserved
[    0.580242] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.580998] system 00:06: [io  0x1800-0x18fe] could not be reserved
[    0.580998] system 00:06: [mem 0xfe000000-0xfe01ffff] has been reserved
[    0.580999] system 00:06: [mem 0xfe04c000-0xfe04ffff] has been reserved
[    0.580999] system 00:06: [mem 0xfe050000-0xfe0affff] has been reserved
[    0.581000] system 00:06: [mem 0xfe0d0000-0xfe0fffff] has been reserved
[    0.581001] system 00:06: [mem 0xfe200000-0xfe7fffff] has been reserved
[    0.581001] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
[    0.581002] system 00:06: [mem 0xfd000000-0xfd68ffff] has been reserved
[    0.581003] system 00:06: [mem 0xfd6b0000-0xfd6cffff] has been reserved
[    0.581003] system 00:06: [mem 0xfd6f0000-0xfdffffff] has been reserved
[    0.581005] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.581242] system 00:07: [io  0x2000-0x20fe] has been reserved
[    0.581244] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.581409] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.584240] pnp: PnP ACPI: found 9 devices
[    0.589442] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.589474] NET: Registered protocol family 2
[    0.589601] tcp_listen_portaddr_hash hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.589772] TCP established hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.589991] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes, linear)
[    0.590033] TCP: Hash tables configured (established 262144 bind 65536)
[    0.590140] MPTCP token hash table entries: 32768 (order: 7, 786432 bytes, linear)
[    0.590229] UDP hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.590292] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes, linear)
[    0.590344] NET: Registered protocol family 1
[    0.590348] NET: Registered protocol family 44
[    0.590351] pci_bus 0000:00: max bus depth: 1 pci_try_num: 2
[    0.590359] pci 0000:00:02.0: BAR 9: assigned [mem 0x4020000000-0x40ffffffff 64bit pref]
[    0.590361] pci 0000:00:02.0: BAR 7: assigned [mem 0x4010000000-0x4016ffffff 64bit]
[    0.590363] pci 0000:00:07.0: BAR 13: assigned [io  0x4000-0x4fff]
[    0.590363] pci 0000:00:07.2: BAR 13: assigned [io  0x5000-0x5fff]
[    0.590364] pci 0000:00:15.0: BAR 0: assigned [mem 0x4017000000-0x4017000fff 64bit]
[    0.590426] pci 0000:00:15.1: BAR 0: assigned [mem 0x4017001000-0x4017001fff 64bit]
[    0.590441] pci 0000:00:19.0: BAR 0: assigned [mem 0x4017002000-0x4017002fff 64bit]
[    0.590456] pci 0000:00:19.1: BAR 0: assigned [mem 0x4017003000-0x4017003fff 64bit]
[    0.590516] pci 0000:00:1e.0: BAR 0: assigned [mem 0x4017004000-0x4017004fff 64bit]
[    0.590530] pci 0000:00:1f.5: BAR 0: assigned [mem 0x70800000-0x70800fff]
[    0.590541] pci 0000:00:06.0: PCI bridge to [bus 01]
[    0.590549] pci 0000:00:06.0:   bridge window [mem 0x8c400000-0x8c4fffff]
[    0.590558] pci 0000:00:07.0: PCI bridge to [bus 02-2b]
[    0.590559] pci 0000:00:07.0:   bridge window [io  0x4000-0x4fff]
[    0.590561] pci 0000:00:07.0:   bridge window [mem 0x80000000-0x8c1fffff]
[    0.590563] pci 0000:00:07.0:   bridge window [mem 0x6000000000-0x601bffffff 64bit pref]
[    0.590567] pci 0000:00:07.2: PCI bridge to [bus 2c-55]
[    0.590568] pci 0000:00:07.2:   bridge window [io  0x5000-0x5fff]
[    0.590571] pci 0000:00:07.2:   bridge window [mem 0x72000000-0x7e1fffff]
[    0.590573] pci 0000:00:07.2:   bridge window [mem 0x6020000000-0x603bffffff 64bit pref]
[    0.590576] pci 0000:00:1c.0: PCI bridge to [bus 56]
[    0.590581] pci 0000:00:1c.0:   bridge window [mem 0x8c300000-0x8c3fffff]
[    0.590587] pci 0000:00:1d.0: PCI bridge to [bus 57]
[    0.590590] pci 0000:00:1d.0:   bridge window [mem 0x8c200000-0x8c2fffff]
[    0.590597] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.590598] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff window]
[    0.590598] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff window]
[    0.590599] pci_bus 0000:00: resource 7 [mem 0x70800000-0xbfffffff window]
[    0.590599] pci_bus 0000:00: resource 8 [mem 0x4000000000-0x7fffffffff window]
[    0.590600] pci_bus 0000:01: resource 1 [mem 0x8c400000-0x8c4fffff]
[    0.590600] pci_bus 0000:02: resource 0 [io  0x4000-0x4fff]
[    0.590601] pci_bus 0000:02: resource 1 [mem 0x80000000-0x8c1fffff]
[    0.590601] pci_bus 0000:02: resource 2 [mem 0x6000000000-0x601bffffff 64bit pref]
[    0.590602] pci_bus 0000:2c: resource 0 [io  0x5000-0x5fff]
[    0.590602] pci_bus 0000:2c: resource 1 [mem 0x72000000-0x7e1fffff]
[    0.590603] pci_bus 0000:2c: resource 2 [mem 0x6020000000-0x603bffffff 64bit pref]
[    0.590604] pci_bus 0000:56: resource 1 [mem 0x8c300000-0x8c3fffff]
[    0.590604] pci_bus 0000:57: resource 1 [mem 0x8c200000-0x8c2fffff]
[    0.590729] pci 0000:00:02.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
[    0.591483] PCI: CLS 0 bytes, default 64
[    0.591508] Trying to unpack rootfs image as initramfs...
[    0.703713] Freeing initrd memory: 87124K
[    0.703747] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.703748] software IO TLB: mapped [mem 0x0000000051a9c000-0x0000000055a9c000] (64MB)
[    0.703828] resource sanity check: requesting [mem 0xfedc0000-0xfedcdfff], which spans more than pnp 00:05 [mem 0xfedc0000-0xfedc7fff]
[    0.703834] caller tgl_uncore_imc_freerunning_init_box+0xb9/0x100 mapping multiple BARs
[    0.703950] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x28680fa287f, max_idle_ns: 440795281151 ns
[    0.703968] clocksource: Switched to clocksource tsc
[    0.704132] check: Scanning for low memory corruption every 60 seconds
[    0.704472] Initialise system trusted keyrings
[    0.704482] Key type blacklist registered
[    0.704526] workingset: timestamp_bits=36 max_order=23 bucket_order=0
[    0.705035] zbud: loaded
[    0.705162] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.705279] fuse: init (API version 7.32)
[    0.705380] integrity: Platform Keyring initialized
[    0.712145] Key type asymmetric registered
[    0.712146] Asymmetric key parser 'x509' registered
[    0.712151] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[    0.712208] io scheduler mq-deadline registered
[    0.712686] pcieport 0000:00:06.0: PME: Signaling with IRQ 120
[    0.712866] pcieport 0000:00:07.0: PME: Signaling with IRQ 121
[    0.712880] pcieport 0000:00:07.0: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.713081] pcieport 0000:00:07.2: PME: Signaling with IRQ 122
[    0.713094] pcieport 0000:00:07.2: pciehp: Slot #0 AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Interlock- NoCompl+ IbPresDis- LLActRep+
[    0.713293] pcieport 0000:00:1c.0: PME: Signaling with IRQ 123
[    0.713472] pcieport 0000:00:1d.0: PME: Signaling with IRQ 124
[    0.713548] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[    0.713591] efifb: probing for efifb
[    0.713606] efifb: Ignoring BGRT: unexpected or invalid BMP data
[    0.713606] efifb: framebuffer at 0x4000000000, using 9000k, total 9000k
[    0.713607] efifb: mode is 1920x1200x32, linelength=7680, pages=1
[    0.713607] efifb: scrolling: redraw
[    0.713608] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[    0.713661] Console: switching to colour frame buffer device 240x75
[    0.718244] fb0: EFI VGA frame buffer device
[    0.718248] intel_idle: MWAIT substates: 0x11121020
[    0.718434] Monitor-Mwait will be used to enter C-1 state
[    0.718438] Monitor-Mwait will be used to enter C-2 state
[    0.718442] Monitor-Mwait will be used to enter C-3 state
[    0.718446] ACPI: \_SB_.PR00: Found 3 idle states
[    0.718447] intel_idle: v0.5.1 model 0x8C
[    0.718604] intel_idle: Local APIC timer is reliable in all C-states
[    0.719431] ACPI: AC Adapter [AC] (on-line)
[    0.719472] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
[    0.719491] ACPI: Lid Switch [LID0]
[    0.719502] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[    0.719511] ACPI: Power Button [PBTN]
[    0.719521] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2
[    0.719527] ACPI: Sleep Button [SBTN]
[    0.721227] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    0.723887] serial 0000:00:12.0: enabling device (0000 -> 0002)
[    0.725134] Linux agpgart interface v0.103
[    0.727158] tpm_tis STM0125:00: 2.0 TPM (device-id 0x0, rev-id 78)
[    0.743119] loop: module loaded
[    0.743419] libphy: Fixed MDIO Bus: probed
[    0.743419] tun: Universal TUN/TAP device driver, 1.6
[    0.743573] PPP generic driver version 2.4.2
[    0.743602] VFIO - User Level meta-driver version: 0.3
[    0.743757] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.743758] ehci-pci: EHCI PCI platform driver
[    0.743763] ehci-platform: EHCI generic platform driver
[    0.743769] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.743771] ohci-pci: OHCI PCI platform driver
[    0.743774] ohci-platform: OHCI generic platform driver
[    0.743777] uhci_hcd: USB Universal Host Controller Interface driver
[    0.743802] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[    0.744554] i8042: Warning: Keylock active
[    0.747730] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.747731] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.748036] mousedev: PS/2 mouse device common for all mice
[    0.748081] battery: ACPI: Battery Slot [BAT0] (battery present)
[    0.748273] rtc_cmos 00:01: RTC can wake from S4
[    0.748918] rtc_cmos 00:01: registered as rtc0
[    0.749095] rtc_cmos 00:01: setting system clock to 2020-11-04T12:34:09 UTC (1604493249)
[    0.749138] rtc_cmos 00:01: alarms up to one month, y3k, 242 bytes nvram
[    0.749140] i2c /dev entries driver
[    0.749162] device-mapper: uevent: version 1.0.3
[    0.749205] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: dm-devel@redhat.com
[    0.749213] platform eisa.0: Probing EISA bus 0
[    0.749214] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    0.749214] platform eisa.0: Cannot allocate resource for EISA slot 1
[    0.749215] platform eisa.0: Cannot allocate resource for EISA slot 2
[    0.749215] platform eisa.0: Cannot allocate resource for EISA slot 3
[    0.749216] platform eisa.0: Cannot allocate resource for EISA slot 4
[    0.749216] platform eisa.0: Cannot allocate resource for EISA slot 5
[    0.749217] platform eisa.0: Cannot allocate resource for EISA slot 6
[    0.749217] platform eisa.0: Cannot allocate resource for EISA slot 7
[    0.749218] platform eisa.0: Cannot allocate resource for EISA slot 8
[    0.749218] platform eisa.0: EISA: Detected 0 cards
[    0.749220] intel_pstate: Intel P-state driver initializing
[    0.749796] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3
[    0.749947] intel_pstate: HWP enabled
[    0.749976] ledtrig-cpu: registered to indicate activity on CPUs
[    0.749979] EFI Variables Facility v0.08 2004-May-17
[    0.751929] intel_pmc_core INT33A1:00:  initialized
[    0.751999] drop_monitor: Initializing network drop monitor service
[    0.752119] NET: Registered protocol family 10
[    0.755856] Segment Routing with IPv6
[    0.755876] NET: Registered protocol family 17
[    0.755967] Key type dns_resolver registered
[    0.756563] microcode: sig=0x806c1, pf=0x80, revision=0x60
[    0.756637] microcode: Microcode Update Driver: v2.2.
[    0.756773] resctrl: L2 allocation detected
[    0.756773] resctrl: L2DATA allocation detected
[    0.756773] resctrl: L2CODE allocation detected
[    0.756776] IPI shorthand broadcast: enabled
[    0.756781] sched_clock: Marking stable (756324155, 441923)->(763657306, -6891228)
[    0.756833] registered taskstats version 1
[    0.756839] Loading compiled-in X.509 certificates
[    0.757313] Loaded X.509 cert 'Build time autogenerated kernel key: e7023dac6afd3a5685011f478d7c4ec5045876be'
[    0.757336] zswap: loaded using pool lzo/zbud
[    0.757430] Key type ._fscrypt registered
[    0.757430] Key type .fscrypt registered
[    0.757431] Key type fscrypt-provisioning registered
[    0.757459] Key type trusted registered
[    0.758920] Key type encrypted registered
[    0.758922] AppArmor: AppArmor sha1 policy hashing enabled
[    0.759013] integrity: Loading X.509 certificate: UEFI:db
[    0.759028] integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios DB Key: 637fa7a9f74471b406de0511557071fd41dd5487'
[    0.759028] integrity: Loading X.509 certificate: UEFI:db
[    0.759036] integrity: Loaded X.509 cert 'Dell Inc.: Dell Bios FW Aux Authority 2018: dd4df7c3f5ce7e5a77847915abc37b031f6b10bd'
[    0.759037] integrity: Loading X.509 certificate: UEFI:db
[    0.759047] integrity: Loaded X.509 cert 'Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[    0.759048] integrity: Loading X.509 certificate: UEFI:db
[    0.759061] integrity: Loaded X.509 cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[    0.759739] integrity: Loading X.509 certificate: UEFI:MokListRT
[    0.759748] integrity: Loaded X.509 cert 'SomeOrg: shim: a01ee84e9b37ace407961cc468c5909447878469'
[    0.759748] integrity: Loading X.509 certificate: UEFI:MokListRT
[    0.759980] integrity: Loaded X.509 cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63'
[    0.759986] ima: Allocated hash algorithm: sha1
[    0.775791] ima: No architecture policies found
[    0.775797] evm: Initialising EVM extended attributes:
[    0.775798] evm: security.selinux
[    0.775798] evm: security.SMACK64
[    0.775798] evm: security.SMACK64EXEC
[    0.775799] evm: security.SMACK64TRANSMUTE
[    0.775799] evm: security.SMACK64MMAP
[    0.775799] evm: security.apparmor
[    0.775799] evm: security.ima
[    0.775800] evm: security.capability
[    0.775800] evm: HMAC attrs: 0x1
[    0.777852] PM:   Magic number: 12:631:581
[    0.777883] pci_bus 0000:02: hash matches
[    0.778146] RAS: Correctable Errors collector initialized.
[    0.784040] Freeing unused decrypted memory: 2036K
[    0.784362] Freeing unused kernel image (initmem) memory: 2636K
[    0.819802] Write protecting the kernel read-only data: 22528k
[    0.820621] Freeing unused kernel image (text/rodata gap) memory: 2036K
[    0.820894] Freeing unused kernel image (rodata/data gap) memory: 932K
[    0.837568] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    0.837575] Run /init as init process
[    0.837577]   with arguments:
[    0.837578]     /init
[    0.837578]     splash
[    0.837579]   with environment:
[    0.837580]     HOME=/
[    0.837580]     TERM=linux
[    0.837581]     BOOT_IMAGE=/vmlinuz-5.10.0-rc1-wt-ath+
[    0.898169] hid: raw HID events driver (C) Jiri Kosina
[    0.900997] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.901029] wmi_bus wmi_bus-PNP0C14:02: WQBC data block query control method not found
[    0.901030] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.903428] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.904733] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.904738] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 1
[    0.905179] acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.905226] acpi PNP0C14:05: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.905271] acpi PNP0C14:06: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    0.905836] xhci_hcd 0000:00:0d.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000200009810
[    0.905840] xhci_hcd 0000:00:0d.0: cache line size of 64 is not supported
[    0.905963] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    0.905964] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.905965] usb usb1: Product: xHCI Host Controller
[    0.905966] usb usb1: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.905966] usb usb1: SerialNumber: 0000:00:0d.0
[    0.906028] hub 1-0:1.0: USB hub found
[    0.906032] hub 1-0:1.0: 1 port detected
[    0.906149] xhci_hcd 0000:00:0d.0: xHCI Host Controller
[    0.906151] xhci_hcd 0000:00:0d.0: new USB bus registered, assigned bus number 2
[    0.906152] xhci_hcd 0000:00:0d.0: Host supports USB 3.1 Enhanced SuperSpeed
[    0.906195] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    0.906196] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.906197] usb usb2: Product: xHCI Host Controller
[    0.906197] usb usb2: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.906197] usb usb2: SerialNumber: 0000:00:0d.0
[    0.906236] hub 2-0:1.0: USB hub found
[    0.906244] hub 2-0:1.0: 4 ports detected
[    0.906669] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.906674] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    0.907698] nvme nvme0: pci function 0000:01:00.0
[    0.907764] xhci_hcd 0000:00:14.0: hcc params 0x20007fc1 hci version 0x120 quirks 0x0000000000009810
[    0.908014] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    0.908166] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    0.908167] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.908168] usb usb3: Product: xHCI Host Controller
[    0.908168] usb usb3: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.908169] usb usb3: SerialNumber: 0000:00:14.0
[    0.908217] hub 3-0:1.0: USB hub found
[    0.908234] hub 3-0:1.0: 12 ports detected
[    0.908985] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.908987] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[    0.908989] xhci_hcd 0000:00:14.0: Host supports USB 3.1 Enhanced SuperSpeed
[    0.909015] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.10
[    0.909015] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.909017] usb usb4: Product: xHCI Host Controller
[    0.909018] usb usb4: Manufacturer: Linux 5.10.0-rc1-wt-ath+ xhci-hcd
[    0.909018] usb usb4: SerialNumber: 0000:00:14.0
[    0.909086] hub 4-0:1.0: USB hub found
[    0.909099] hub 4-0:1.0: 4 ports detected
[    0.909207] usb: port power management may be unreliable
[    0.910841] rtsx_pci 0000:57:00.0: enabling device (0000 -> 0002)
[    0.911267] i801_smbus 0000:00:1f.4: enabling device (0000 -> 0003)
[    0.911391] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[    0.911447] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[    0.913858] nvme nvme0: missing or invalid SUBNQN field.
[    0.913880] nvme nvme0: Shutdown timeout set to 8 seconds
[    0.916691] cryptd: max_cpu_qlen set to 1000
[    0.920917] AVX2 version of gcm_enc/dec engaged.
[    0.920918] AES CTR mode by8 optimization enabled
[    0.926033] nvme nvme0: 8/0/0 default/read/poll queues
[    0.926669] i2c i2c-0: 8/8 memory slots populated (from DMI)
[    0.926671] i2c i2c-0: Systems with more than 4 memory slots not supported yet, not instantiating SPD
[    0.929250]  nvme0n1: p1 p2 p3 p4 p5
[    0.931675] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[    0.931907] idma64 idma64.0: Found Intel integrated DMA 64-bit
[    0.966773] checking generic (4000000000 8ca000) vs hw (603c000000 1000000)
[    0.966774] checking generic (4000000000 8ca000) vs hw (4000000000 10000000)
[    0.966775] fb0: switching to inteldrmfb from EFI VGA
[    0.966831] Console: switching to colour dummy device 80x25
[    0.966857] i915 0000:00:02.0: vgaarb: deactivate vga console
[    0.967670] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[    0.968105] idma64 idma64.1: Found Intel integrated DMA 64-bit
[    0.968223] i915 0000:00:02.0: [drm] Couldn't get system memory bandwidth
[    0.968815] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    0.969306] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/tgl_dmc_ver2_08.bin (v2.8)
[    0.978728] i2c_hid i2c-DLL0945:00: supply vdd not found, using dummy regulator
[    0.978745] i2c_hid i2c-DLL0945:00: supply vddl not found, using dummy regulator
[    1.003659] intel-lpss 0000:00:19.0: enabling device (0000 -> 0002)
[    1.003864] idma64 idma64.2: Found Intel integrated DMA 64-bit
[    1.012376] [drm] Initialized i915 1.6.0 20200917 for 0000:00:02.0 on minor 0
[    1.014910] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[    1.016829] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
[    1.018613] fbcon: i915drmfb (fb0) is primary device
[    1.035670] intel-lpss 0000:00:19.1: enabling device (0000 -> 0002)
[    1.035966] idma64 idma64.3: Found Intel integrated DMA 64-bit
[    1.067739] intel-lpss 0000:00:1e.0: enabling device (0000 -> 0002)
[    1.068569] idma64 idma64.4: Found Intel integrated DMA 64-bit
[    1.156096] input: DLL0945:00 06CB:CDE6 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input7
[    1.156174] input: DLL0945:00 06CB:CDE6 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input8
[    1.156235] hid-generic 0018:06CB:CDE6.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL0945:00 06CB:CDE6] on i2c-DLL0945:00
[    1.319669] usb 3-4: new high-speed USB device number 2 using xhci_hcd
[    1.540621] usb 3-4: New USB device found, idVendor=0bda, idProduct=c820, bcdDevice= 2.00
[    1.540624] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    1.540625] usb 3-4: Product: 802.11ac NIC
[    1.540627] usb 3-4: Manufacturer: Realtek
[    1.540628] usb 3-4: SerialNumber: 123456
[    1.577639] ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done OK, num_hid_devices=1
[    1.579308] hid-generic 001F:8087:0AC2.0002: hidraw1: <UNKNOWN> HID v2.00 Device [hid-ishtp 8087:0AC2] on 
[    1.675685] usb 3-6: new high-speed USB device number 3 using xhci_hcd
[    1.826107] usb 3-6: New USB device found, idVendor=0bda, idProduct=5517, bcdDevice= 4.21
[    1.826111] usb 3-6: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    1.826113] usb 3-6: Product: Integrated_Webcam_HD
[    1.826114] usb 3-6: Manufacturer: Integrated_Webcam_HD
[    1.826115] usb 3-6: SerialNumber: 200901010001
[    2.143937] Console: switching to colour frame buffer device 240x75
[    2.167063] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[    7.027376] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[    7.151724] systemd[1]: Inserted module 'autofs4'
[    7.164490] systemd[1]: systemd 246.6-1ubuntu1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[    7.187995] systemd[1]: Detected architecture x86-64.
[    7.247914] systemd[1]: Set hostname to <tk-9310>.
[    7.308624] systemd[1]: /lib/systemd/system/dbus.service:12: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    7.325537] systemd[1]: /lib/systemd/system/plymouth-start.service:17: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[    7.347103] systemd[1]: Queued start job for default target Graphical Interface.
[    7.347885] systemd[1]: Created slice system-modprobe.slice.
[    7.347993] systemd[1]: Created slice system-postgresql.slice.
[    7.348075] systemd[1]: Created slice Cryptsetup Units Slice.
[    7.348182] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[    7.348259] systemd[1]: Created slice User and Session Slice.
[    7.348284] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    7.348369] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    7.348400] systemd[1]: Reached target Remote File Systems.
[    7.348405] systemd[1]: Reached target Slices.
[    7.348442] systemd[1]: Listening on Device-mapper event daemon FIFOs.
[    7.348475] systemd[1]: Listening on LVM2 poll daemon socket.
[    7.348512] systemd[1]: Listening on Syslog Socket.
[    7.348550] systemd[1]: Listening on fsck to fsckd communication Socket.
[    7.348564] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    7.348925] systemd[1]: Listening on Journal Audit Socket.
[    7.348975] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.349014] systemd[1]: Listening on Journal Socket.
[    7.349064] systemd[1]: Listening on udev Control Socket.
[    7.349093] systemd[1]: Listening on udev Kernel Socket.
[    7.349438] systemd[1]: Mounting Huge Pages File System...
[    7.349824] systemd[1]: Mounting POSIX Message Queue File System...
[    7.350306] systemd[1]: Mounting Kernel Debug File System...
[    7.350701] systemd[1]: Mounting Kernel Trace File System...
[    7.351386] systemd[1]: Starting Journal Service...
[    7.351803] systemd[1]: Starting Availability of block devices...
[    7.352357] systemd[1]: Starting Set the console keyboard layout...
[    7.352795] systemd[1]: Starting Create list of static device nodes for the current kernel...
[    7.353151] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
[    7.353168] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
[    7.353503] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[    7.353539] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[    7.354338] systemd[1]: Starting Load Kernel Modules...
[    7.354887] systemd[1]: Starting Remount Root and Kernel File Systems...
[    7.355433] systemd[1]: Starting Coldplug All udev Devices...
[    7.356014] systemd[1]: Starting Uncomplicated firewall...
[    7.357078] systemd[1]: Mounted Huge Pages File System.
[    7.357170] systemd[1]: Mounted POSIX Message Queue File System.
[    7.357248] systemd[1]: Mounted Kernel Debug File System.
[    7.357328] systemd[1]: Mounted Kernel Trace File System.
[    7.357623] systemd[1]: Finished Availability of block devices.
[    7.357965] systemd[1]: Finished Create list of static device nodes for the current kernel.
[    7.358251] systemd[1]: Finished Uncomplicated firewall.
[    7.361666] EXT4-fs (dm-2): re-mounted. Opts: errors=remount-ro
[    7.362351] lp: driver loaded but no devices found
[    7.362395] systemd[1]: Finished Remount Root and Kernel File Systems.
[    7.363091] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[    7.363123] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[    7.363697] systemd[1]: Starting Load/Save Random Seed...
[    7.364136] ppdev: user-space parallel port driver
[    7.364284] systemd[1]: Starting Create System Users...
[    7.366769] systemd[1]: Finished Load Kernel Modules.
[    7.367528] systemd[1]: Mounting FUSE Control File System...
[    7.368206] systemd[1]: Mounting Kernel Configuration File System...
[    7.368794] systemd[1]: Starting Apply Kernel Variables...
[    7.369621] systemd[1]: Mounted FUSE Control File System.
[    7.369705] systemd[1]: Mounted Kernel Configuration File System.
[    7.372915] systemd[1]: Finished Create System Users.
[    7.373549] systemd[1]: Starting Create Static Device Nodes in /dev...
[    7.375964] systemd[1]: Finished Load/Save Random Seed.
[    7.378178] systemd[1]: Finished Apply Kernel Variables.
[    7.380695] systemd[1]: Finished Create Static Device Nodes in /dev.
[    7.381628] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    7.386758] systemd[1]: Finished Set the console keyboard layout.
[    7.398485] systemd[1]: Started Journal Service.
[    7.479923] input: Intel HID events as /devices/platform/INTC1051:00/input/input10
[    7.480078] intel-hid INTC1051:00: platform supports 5 button array
[    7.480128] input: Intel HID 5 button array as /devices/platform/INTC1051:00/input/input11
[    7.501054] ACPI BIOS Error (bug): Could not resolve symbol [\S1CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.501063] No Local Variables are initialized for Method [_CRT]
[    7.501065] No Arguments are initialized for method [_CRT]

[    7.501067] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.501088] ACPI BIOS Error (bug): Could not resolve symbol [\S1HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.501091] No Local Variables are initialized for Method [_HOT]
[    7.501093] No Arguments are initialized for method [_HOT]

[    7.501094] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.501113] ACPI BIOS Error (bug): Could not resolve symbol [\S1PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.501117] No Local Variables are initialized for Method [_PSV]
[    7.501118] No Arguments are initialized for method [_PSV]

[    7.501120] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.501137] ACPI BIOS Error (bug): Could not resolve symbol [\S1AC], AE_NOT_FOUND (20200925/psargs-330)
[    7.501140] No Local Variables are initialized for Method [_AC0]
[    7.501141] No Arguments are initialized for method [_AC0]

[    7.501143] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TMEM._AC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.505599] ACPI BIOS Error (bug): Could not resolve symbol [\S2CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.505608] No Local Variables are initialized for Method [_CRT]
[    7.505610] No Arguments are initialized for method [_CRT]

[    7.505612] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TSKN._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.505632] ACPI BIOS Error (bug): Could not resolve symbol [\S2HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.505636] No Local Variables are initialized for Method [_HOT]
[    7.505637] No Arguments are initialized for method [_HOT]

[    7.505639] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TSKN._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.505657] ACPI BIOS Error (bug): Could not resolve symbol [\S2PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.505661] No Local Variables are initialized for Method [_PSV]
[    7.505662] No Arguments are initialized for method [_PSV]

[    7.505664] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TSKN._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.508786] ACPI BIOS Error (bug): Could not resolve symbol [\S3CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.508793] No Local Variables are initialized for Method [_CRT]
[    7.508794] No Arguments are initialized for method [_CRT]

[    7.508796] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TVR._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.508814] ACPI BIOS Error (bug): Could not resolve symbol [\S3HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.508818] No Local Variables are initialized for Method [_HOT]
[    7.508819] No Arguments are initialized for method [_HOT]

[    7.508821] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TVR._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.508838] ACPI BIOS Error (bug): Could not resolve symbol [\S3PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.508842] No Local Variables are initialized for Method [_PSV]
[    7.508843] No Arguments are initialized for method [_PSV]

[    7.508845] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TVR._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.511930] ACPI BIOS Error (bug): Could not resolve symbol [\S4CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.511936] No Local Variables are initialized for Method [_CRT]
[    7.511938] No Arguments are initialized for method [_CRT]

[    7.511940] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.511959] ACPI BIOS Error (bug): Could not resolve symbol [\S4HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.511963] No Local Variables are initialized for Method [_HOT]
[    7.511964] No Arguments are initialized for method [_HOT]

[    7.511966] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.511984] ACPI BIOS Error (bug): Could not resolve symbol [\S4PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.511987] No Local Variables are initialized for Method [_PSV]
[    7.511989] No Arguments are initialized for method [_PSV]

[    7.511991] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.512008] ACPI BIOS Error (bug): Could not resolve symbol [\S4AC], AE_NOT_FOUND (20200925/psargs-330)
[    7.512012] No Local Variables are initialized for Method [_AC0]
[    7.512013] No Arguments are initialized for method [_AC0]

[    7.512015] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.TAMB._AC0 due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.518544] ACPI BIOS Error (bug): Could not resolve symbol [\S5CC], AE_NOT_FOUND (20200925/psargs-330)
[    7.518552] No Local Variables are initialized for Method [_CRT]
[    7.518554] No Arguments are initialized for method [_CRT]

[    7.518556] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.THP._CRT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.518575] ACPI BIOS Error (bug): Could not resolve symbol [\S5HP], AE_NOT_FOUND (20200925/psargs-330)
[    7.518579] No Local Variables are initialized for Method [_HOT]
[    7.518580] No Arguments are initialized for method [_HOT]

[    7.518582] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.THP._HOT due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.518601] ACPI BIOS Error (bug): Could not resolve symbol [\S5PV], AE_NOT_FOUND (20200925/psargs-330)
[    7.518604] No Local Variables are initialized for Method [_PSV]
[    7.518605] No Arguments are initialized for method [_PSV]

[    7.518607] ACPI Error: Aborting method \_SB.PC00.LPCB.ECDV.THP._PSV due to previous error (AE_NOT_FOUND) (20200925/psparse-529)
[    7.540608] Bluetooth: Core ver 2.22
[    7.540620] NET: Registered protocol family 31
[    7.540621] Bluetooth: HCI device and connection manager initialized
[    7.540624] Bluetooth: HCI socket layer initialized
[    7.540625] Bluetooth: L2CAP socket layer initialized
[    7.540628] Bluetooth: SCO socket layer initialized
[    7.545705] proc_thermal 0000:00:04.0: enabling device (0000 -> 0002)
[    7.551854] intel_rapl_common: Found RAPL domain package
[    7.552645] proc_thermal 0000:00:04.0: Creating sysfs group for PROC_THERMAL_PCI
[    7.580866] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[    7.582762] Bluetooth: HCI UART driver ver 2.3
[    7.582764] Bluetooth: HCI UART protocol H4 registered
[    7.582765] Bluetooth: HCI UART protocol BCSP registered
[    7.582770] Bluetooth: HCI UART protocol LL registered
[    7.582771] Bluetooth: HCI UART protocol ATH3K registered
[    7.582775] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    7.582812] Bluetooth: HCI UART protocol Intel registered
[    7.582841] Bluetooth: HCI UART protocol Broadcom registered
[    7.582847] Bluetooth: HCI UART protocol QCA registered
[    7.582847] Bluetooth: HCI UART protocol AG6XX registered
[    7.582852] Bluetooth: HCI UART protocol Marvell registered
[    7.588409] pstore: Using crash dump compression: deflate
[    7.588419] pstore: Registered efi as persistent store backend
[    7.595679] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.595830] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.604193] dw-apb-uart.4: ttyS4 at MMIO 0x4017004000 (irq = 16, base_baud = 6250000) is a 16550A
[    7.604441] input: Dell WMI hotkeys as /devices/platform/PNP0C14:02/wmi_bus/wmi_bus-PNP0C14:02/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input12
[    7.605755] hci_uart_qca serial0-0: failed to acquire enable gpio
[    7.609742] serial serial0: tty port ttyS4 registered
[    7.610656] Bluetooth: hci0: setting up ROME/QCA6390
[    7.617755] Bluetooth: hci0: Frame reassembly failed (-84)
[    7.698575] EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Opts: (null)
[    7.712164] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support is experimental!
[    7.720933] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem 0x8c300000-0x8c3fffff 64bit]
[    7.720952] ath11k_pci 0000:56:00.0: enabling device (0000 -> 0002)
[    7.721000] ath11k_pci 0000:56:00.0: failed to get 32 MSI vectors, only -28 available
[    7.721003] ath11k_pci 0000:56:00.0: failed to enable msi: -28
[    7.721021] ath11k_pci: probe of 0000:56:00.0 failed with error -28
[    7.729699] input: DLL0945:00 06CB:CDE6 Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input13
[    7.729776] input: DLL0945:00 06CB:CDE6 Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-11/i2c-DLL0945:00/0018:06CB:CDE6.0001/input/input14
[    7.729850] hid-multitouch 0018:06CB:CDE6.0001: input,hidraw0: I2C HID v1.00 Mouse [DLL0945:00 06CB:CDE6] on i2c-DLL0945:00
[    7.761465] intel_rapl_msr: PL4 support detected.
[    7.761491] intel_rapl_common: Found RAPL domain package
[    7.761493] intel_rapl_common: Found RAPL domain core
[    7.761494] intel_rapl_common: Found RAPL domain uncore
[    7.761496] intel_rapl_common: Found RAPL domain psys
[    7.764115] snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    7.764119] snd_hda_intel 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[    7.800477] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
[    7.811669] Adding 33554428k swap on /dev/mapper/ubuntu--vg-swap_1.  Priority:-2 extents:1 across:33554428k SSFS
[    7.817952] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100
[    7.817955] sof-audio-pci 0000:00:1f.3: Digital mics found on Skylake+ platform, using SOF driver
[    7.817967] sof-audio-pci 0000:00:1f.3: enabling device (0000 -> 0002)
[    7.818679] sof-audio-pci 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100
[    7.818789] sof-audio-pci 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[    7.825738] sof-audio-pci 0000:00:1f.3: use msi interrupt mode
[    7.886390] sof-audio-pci 0000:00:1f.3: hda codecs found, mask 5
[    7.886393] sof-audio-pci 0000:00:1f.3: using HDA machine driver skl_hda_dsp_generic now
[    7.886399] sof-audio-pci 0000:00:1f.3: DMICs detected in NHLT tables: 2
[    7.940218] Bluetooth: hci0: QCA Product ID   :0x00000010
[    7.940220] Bluetooth: hci0: QCA SOC Version  :0x400a0200
[    7.940220] Bluetooth: hci0: QCA ROM Version  :0x00000200
[    7.940221] Bluetooth: hci0: QCA Patch Version:0x00000d2b
[    7.940221] Bluetooth: hci0: QCA controller version 0x02000200
[    7.940222] Bluetooth: hci0: QCA Downloading qca/htbtfw20.tlv
[    7.977205] sof-audio-pci 0000:00:1f.3: Firmware info: version 1:5:0-58b36
[    7.977208] sof-audio-pci 0000:00:1f.3: Firmware: ABI 3:16:0 Kernel ABI 3:17:0
[    7.977364] sof-audio-pci 0000:00:1f.3: warning: unknown ext header type 3 size 0x1c
[    7.977373] sof-audio-pci 0000:00:1f.3: warning: unknown ext header type 4 size 0x10
[    7.983357] sof-audio-pci 0000:00:1f.3: Topology: ABI 3:11:0 Kernel ABI 3:17:0
[    7.997455] sof-audio-pci 0000:00:1f.3: ASoC: Parent card not yet available, widget card binding deferred
[    8.017550] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC289: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[    8.017551] snd_hda_codec_realtek ehdaudio0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    8.017552] snd_hda_codec_realtek ehdaudio0D0:    hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[    8.017553] snd_hda_codec_realtek ehdaudio0D0:    mono: mono_out=0x0
[    8.017553] snd_hda_codec_realtek ehdaudio0D0:    inputs:
[    8.017554] snd_hda_codec_realtek ehdaudio0D0:      Headset Mic=0x19
[    8.017554] snd_hda_codec_realtek ehdaudio0D0:      Headphone Mic=0x1b
[    8.068759] snd_hda_codec_realtek ehdaudio0D0: ASoC: sink widget AIF1TX overwritten
[    8.068764] snd_hda_codec_realtek ehdaudio0D0: ASoC: source widget AIF1RX overwritten
[    8.068868] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi3 overwritten
[    8.068871] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi2 overwritten
[    8.068873] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget hifi1 overwritten
[    8.068876] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Codec Output Pin1 overwritten
[    8.068878] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Codec Input Pin1 overwritten
[    8.068881] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Analog Codec Playback overwritten
[    8.068885] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Digital Codec Playback overwritten
[    8.068888] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: sink widget Alt Analog Codec Playback overwritten
[    8.068891] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Analog Codec Capture overwritten
[    8.068894] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Digital Codec Capture overwritten
[    8.068898] skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: source widget Alt Analog Codec Capture overwritten
[    8.068905] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 3

[    8.068906] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 4

[    8.068907] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 5

[    8.068908] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 6

[    8.068909] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 7

[    8.068909] skl_hda_dsp_generic skl_hda_dsp_generic: hda_dsp_hdmi_build_controls: no PCM in topology for HDMI converter 8

[    8.083734] input: sof-hda-dsp Headphone Mic as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input16
[    8.083760] input: sof-hda-dsp HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input17
[    8.083788] input: sof-hda-dsp HDMI/DP,pcm=4 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input18
[    8.083823] input: sof-hda-dsp HDMI/DP,pcm=5 as /devices/pci0000:00/0000:00:1f.3/skl_hda_dsp_generic/sound/card0/input19
[    8.608647] audit: type=1400 audit(1604493257.356:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=1223 comm="apparmor_parser"
[    8.609264] audit: type=1400 audit(1604493257.356:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=1221 comm="apparmor_parser"
[    8.609540] audit: type=1400 audit(1604493257.356:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=1218 comm="apparmor_parser"
[    8.609543] audit: type=1400 audit(1604493257.356:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=1218 comm="apparmor_parser"
[    8.610965] audit: type=1400 audit(1604493257.356:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=1222 comm="apparmor_parser"
[    8.613725] audit: type=1400 audit(1604493257.360:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine" pid=1226 comm="apparmor_parser"
[    8.613729] audit: type=1400 audit(1604493257.360:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=1226 comm="apparmor_parser"
[    8.615041] audit: type=1400 audit(1604493257.360:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=1229 comm="apparmor_parser"
[    8.616310] audit: type=1400 audit(1604493257.364:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1219 comm="apparmor_parser"
[    8.616314] audit: type=1400 audit(1604493257.364:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cupsd" pid=1219 comm="apparmor_parser"
[    8.663760] mc: Linux media interface: v0.10
[    8.665307] usbcore: registered new interface driver btusb
[    8.668662] Bluetooth: hci1: RTL: examining hci_ver=08 hci_rev=826c lmp_ver=08 lmp_subver=a99e
[    8.668665] Bluetooth: hci1: RTL: unknown IC info, lmp subver a99e, hci rev 826c, hci ver 0008
[    8.668667] Bluetooth: hci1: RTL: assuming no firmware upload needed
[    8.669945] videodev: Linux video capture interface: v2.00
[    8.771761] Bluetooth: hci0: QCA Downloading qca/htnv20.bin
[    8.816047] uvcvideo: Found UVC 1.10 device Integrated_Webcam_HD (0bda:5517)
[    8.818187] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.0/input/input20
[    8.818687] uvcvideo: Found UVC 1.50 device Integrated_Webcam_HD (0bda:5517)
[    8.819297] input: Integrated_Webcam_HD: Integrate as /devices/pci0000:00/0000:00:14.0/usb3/3-6/3-6:1.2/input/input21
[    8.819531] usbcore: registered new interface driver uvcvideo
[    8.819533] USB Video Class driver (1.1.1)
[    8.974133] Bluetooth: hci0: QCA setup on UART is completed
[   10.039258] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.039259] Bluetooth: BNEP filters: protocol multicast
[   10.039263] Bluetooth: BNEP socket layer initialized
[   10.054450] NET: Registered protocol family 38
[   13.805606] rfkill: input handler disabled
[   14.075673] psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
[   14.563726] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   18.839784] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/input/input5
[   19.043772] psmouse serio1: Failed to enable mouse on isa0060/serio1
[   20.916310] Bluetooth: RFCOMM TTY layer initialized
[   20.916315] Bluetooth: RFCOMM socket layer initialized
[   20.916319] Bluetooth: RFCOMM ver 1.11
[   21.112484] rfkill: input handler enabled
[   22.946707] rfkill: input handler disabled
[   23.174208] kauditd_printk_skb: 93 callbacks suppressed
[   23.174210] audit: type=1400 audit(1604493271.920:105): apparmor="DENIED" operation="capable" profile="/usr/lib/snapd/snap-confine" pid=2831 comm="snap-confine" capability=4  capname="fsetid"
[   24.616261] audit: type=1326 audit(1604493273.364:106): auid=1000 uid=1000 gid=1000 ses=3 subj==snap.snap-store.ubuntu-software (enforce) pid=2831 comm="snap-store" exe="/snap/snap-store/481/usr/bin/snap-store" sig=0 arch=c000003e syscall=314 compat=0 ip=0x7f84aca0a959 code=0x50000

[-- Attachment #3: lspci.txt --]
[-- Type: text/plain, Size: 53465 bytes --]

00:00.0 Host bridge: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers (rev 01)
	Subsystem: Dell 11th Gen Core Processor Host Bridge/DRAM Registers
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: [e0] Vendor Specific Information: Len=14 <?>

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 01) (prog-if 00 [VGA controller])
	DeviceName: To Be Filled by O.E.M.
	Subsystem: Dell UHD Graphics
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 153
	Region 0: Memory at 603c000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at 4000000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 3000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: [40] Vendor Specific Information: Len=0c <?>
	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+ FLReset+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
	Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit-
		Address: fee80004  Data: 4025
		Masking: 00000000  Pending: 00000000
	Capabilities: [d0] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Process Address Space ID (PASID)
		PASIDCap: Exec- Priv-, Max PASID Width: 14
		PASIDCtl: Enable- Exec- Priv-
	Capabilities: [200 v1] Address Translation Service (ATS)
		ATSCap:	Invalidate Queue Depth: 00
		ATSCtl:	Enable-, Smallest Translation Unit: 00
	Capabilities: [300 v1] Page Request Interface (PRI)
		PRICtl: Enable- Reset-
		PRISta: RF- UPRGI- Stopped+
		Page Request Capacity: 00008000, Page Request Allocation: 00000000
	Capabilities: [320 v1] Single Root I/O Virtualization (SR-IOV)
		IOVCap:	Migration-, Interrupt Message Number: 000
		IOVCtl:	Enable- Migration- Interrupt- MSE- ARIHierarchy-
		IOVSta:	Migration-
		Initial VFs: 7, Total VFs: 7, Number of VFs: 0, Function Dependency Link: 00
		VF offset: 1, stride: 1, Device ID: 9a49
		Supported Page Size: 00000553, System Page Size: 00000001
		Region 0: Memory at 0000004010000000 (64-bit, non-prefetchable)
		Region 2: Memory at 0000004020000000 (64-bit, prefetchable)
		VF Migration: offset: 00000000, BIR: 0
	Kernel driver in use: i915
	Kernel modules: i915

00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01)
	Subsystem: Dell Device 0991
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d180000 (64-bit, non-prefetchable) [size=128K]
	Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit-
		Address: 00000000  Data: 0000
	Capabilities: [d0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [e0] Vendor Specific Information: Len=0c <?>
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device

00:06.0 PCI bridge: Intel Corporation 11th Gen Core Processor PCIe Controller (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin D routed to IRQ 120
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c400000-8c4fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 16GT/s, Width x4, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (downgraded), Width x4 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #0, PowerLimit 75.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet+ LinkState+
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp+ 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing+ 32bit+ 64bit+ 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn+ EgressBlck+
		LnkCap2: Supported Link Speeds: 2.5-16GT/s, Crosslink- Retimer+ 2Retimers+ DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee04004  Data: 4021
	Capabilities: [90] Subsystem: Dell 11th Gen Core Processor PCIe Controller
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt+ RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=45us PortTPowerOnTime=50us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=45us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=50us
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [280 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Capabilities: [a30 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [a90 v1] Data Link Feature <?>
	Capabilities: [a9c v1] Physical Layer 16.0 GT/s <?>
	Capabilities: [edc v1] Lane Margining at the Receiver <?>
	Kernel driver in use: pcieport

00:07.0 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #0 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 121
	Bus: primary=00, secondary=02, subordinate=2b, sec-latency=0
	I/O behind bridge: 00004000-00004fff [size=4K]
	Memory behind bridge: 80000000-8c1fffff [size=194M]
	Prefetchable memory behind bridge: 0000006000000000-000000601bffffff [size=448M]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #2, Speed 2.5GT/s, Width x4, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x0 (downgraded)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee08004  Data: 4021
	Capabilities: [90] Subsystem: Dell Tiger Lake-LP Thunderbolt PCI Express Root Port
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v0] Null
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP- SwTrigger- RP PIO Log 0, DL_ActiveErr-
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:07.2 PCI bridge: Intel Corporation Tiger Lake-LP Thunderbolt PCI Express Root Port #2 (rev 01) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin C routed to IRQ 122
	Bus: primary=00, secondary=2c, subordinate=55, sec-latency=0
	I/O behind bridge: 00005000-00005fff [size=4K]
	Memory behind bridge: 72000000-7e1fffff [size=194M]
	Prefetchable memory behind bridge: 0000006020000000-000000603bffffff [size=448M]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #4, Speed 2.5GT/s, Width x4, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s (ok), Width x0 (downgraded)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
			Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
			Changed: MRL- PresDet- LinkState-
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee10004  Data: 4021
	Capabilities: [90] Subsystem: Dell Tiger Lake-LP Thunderbolt PCI Express Root Port
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v0] Null
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP- SwTrigger- RP PIO Log 0, DL_ActiveErr-
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:0a.0 Signal processing controller: Intel Corporation Device 9a0d (rev 01)
	Subsystem: Dell Device 0991
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 603d1d0000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0
			ExtTag+ RBE- FLReset-
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR-
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
	Capabilities: [d0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Designated Vendor-Specific: Vendor=8086 ID=0002 Rev=1 Len=16 <?>
	Capabilities: [110 v1] Designated Vendor-Specific: Vendor=8086 ID=0003 Rev=1 Len=16 <?>
	Capabilities: [120 v1] Designated Vendor-Specific: Vendor=8086 ID=0004 Rev=1 Len=16 <?>

00:0d.0 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt USB Controller (rev 01) (prog-if 30 [XHCI])
	Subsystem: Dell Tiger Lake-LP Thunderbolt USB Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin ? routed to IRQ 125
	Region 0: Memory at 603d1c0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
		Address: 00000000fee08004  Data: 4022
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Capabilities: [b0] Vendor Specific Information: Len=00 <?>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:0d.2 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt NHI #0 (rev 01) (prog-if 40 [USB4 Host Interface])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d140000 (64-bit, non-prefetchable) [size=256K]
	Region 2: Memory at 603d1e9000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [88] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [a0] MSI-X: Enable+ Count=16 Masked-
		Vector table: BAR=2 offset=00000000
		PBA: BAR=2 offset=00000fa0
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt

00:0d.3 USB controller: Intel Corporation Tiger Lake-LP Thunderbolt NHI #1 (rev 01) (prog-if 40 [USB4 Host Interface])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d100000 (64-bit, non-prefetchable) [size=256K]
	Region 2: Memory at 603d1e8000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [88] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [a0] MSI-X: Enable+ Count=16 Masked-
		Vector table: BAR=2 offset=00000000
		PBA: BAR=2 offset=00000fa0
	Kernel driver in use: thunderbolt
	Kernel modules: thunderbolt

00:12.0 Serial controller: Intel Corporation Tiger Lake-LP Integrated Sensor Hub (rev 20) (prog-if 00 [8250])
	Subsystem: Dell Tiger Lake-LP Integrated Sensor Hub
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d1b0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel_ish_ipc
	Kernel modules: intel_ish_ipc

00:14.0 USB controller: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller (rev 20) (prog-if 30 [XHCI])
	Subsystem: Dell Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 142
	Region 0: Memory at 603d1a0000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [70] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D3 NoSoftRst+ PME-Enable+ DSel=0 DScale=0 PME-
	Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+
		Address: 00000000fee10004  Data: 4022
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Capabilities: [b0] Vendor Specific Information: Len=00 <?>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:14.2 RAM memory: Intel Corporation Tiger Lake-LP Shared SRAM (rev 20)
	Subsystem: Dell Tiger Lake-LP Shared SRAM
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 603d1dc000 (64-bit, non-prefetchable) [disabled] [size=16K]
	Region 2: Memory at 603d1e7000 (64-bit, non-prefetchable) [disabled] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-

00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 27
	Region 0: Memory at 4017000000 (64-bit, non-prefetchable) [virtual] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 40
	Region 0: Memory at 4017001000 (64-bit, non-prefetchable) [virtual] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:16.0 Communication controller: Intel Corporation Tiger Lake-LP Management Engine Interface (rev 20)
	Subsystem: Dell Tiger Lake-LP Management Engine Interface
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 171
	Region 0: Memory at 603d1e4000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee02004  Data: 4025
	Capabilities: [a4] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:19.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #4 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 31
	Region 0: Memory at 4017002000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:19.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #5 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 32
	Region 0: Memory at 4017003000 (64-bit, non-prefetchable) [virtual] [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D3 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:1c.0 PCI bridge: Intel Corporation Device a0b8 (rev 20) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 123
	Bus: primary=00, secondary=56, subordinate=56, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c300000-8c3fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 128 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #1, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee20004  Data: 4021
	Capabilities: [90] Subsystem: Dell Device 0991
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D3 NoSoftRst- PME-Enable+ DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=70us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=44us
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1d.0 PCI bridge: Intel Corporation Device a0b3 (rev 20) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin D routed to IRQ 124
	Bus: primary=00, secondary=57, subordinate=57, sec-latency=0
	I/O behind bridge: [disabled]
	Memory behind bridge: 8c200000-8c2fffff [size=1M]
	Prefetchable memory behind bridge: [disabled]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0
			ExtTag- RBE+
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 128 bytes
		DevSta:	CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
		LnkCap:	Port #12, Speed 8GT/s, Width x1, ASPM L1, Exit Latency L1 <16us
			ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive+ BWMgmt+ ABWMgmt-
		SltCap:	AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise-
			Slot #11, PowerLimit 10.000W; Interlock- NoCompl+
		SltCtl:	Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg-
			Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
		SltSta:	Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
			Changed: MRL- PresDet- LinkState+
		RootCap: CRSVisible-
		RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
		RootSta: PME ReqID 0000, PMEStatus- PMEPending-
		DevCap2: Completion Timeout: Range ABC, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- ARIFwd+
			 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled, ARIFwd-
			 AtomicOpsCtl: ReqEn- EgressBlck-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
		Address: fee40004  Data: 4021
	Capabilities: [90] Subsystem: Dell Device 0991
	Capabilities: [a0] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [100 v1] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
		RootCmd: CERptEn- NFERptEn- FERptEn-
		RootSta: CERcvd- MultCERcvd- UERcvd- MultUERcvd-
			 FirstFatal- NonFatalMsg- FatalMsg- IntMsg 0
		ErrorSrc: ERR_COR: 0000 ERR_FATAL/NONFATAL: 0000
	Capabilities: [220 v1] Access Control Services
		ACSCap:	SrcValid+ TransBlk+ ReqRedir+ CmpltRedir+ UpstreamFwd+ EgressCtrl- DirectTrans-
		ACSCtl:	SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-
	Capabilities: [150 v1] Precision Time Measurement
		PTMCap: Requester:- Responder:+ Root:+
		PTMClockGranularity: 4ns
		PTMControl: Enabled:+ RootSelected:+
		PTMEffectiveGranularity: Unknown
	Capabilities: [200 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=40us PortTPowerOnTime=44us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=60us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=60us
	Capabilities: [a30 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [a00 v1] Downstream Port Containment
		DpcCap:	INT Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
		DpcCtl:	Trigger:0 Cmpl- INT- ErrCor- PoisonedTLP- SwTrigger- DL_ActiveErr-
		DpcSta:	Trigger- Reason:00 INT- RPBusy- TriggerExt:00 RP PIO ErrPtr:1f
		Source:	0000
	Kernel driver in use: pcieport

00:1e.0 Communication controller: Intel Corporation Tiger Lake-LP Serial IO UART Controller #0 (rev 20)
	Subsystem: Dell Tiger Lake-LP Serial IO UART Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 4017004000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: [80] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [90] Vendor Specific Information: Len=14 <?>
	Kernel driver in use: intel-lpss
	Kernel modules: intel_lpss_pci

00:1f.0 ISA bridge: Intel Corporation Tiger Lake-LP LPC Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP LPC Controller
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP Smart Sound Technology Audio Controller
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 64
	Interrupt: pin A routed to IRQ 174
	Region 0: Memory at 603d1d8000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at 603d000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [50] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [80] Vendor Specific Information: Len=14 <?>
	Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee04004  Data: 4025
	Kernel driver in use: sof-audio-pci
	Kernel modules: snd_hda_intel, snd_sof_pci

00:1f.4 SMBus: Intel Corporation Tiger Lake-LP SMBus Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP SMBus Controller
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at 603d1e0000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at efa0 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller (rev 20)
	Subsystem: Dell Tiger Lake-LP SPI Controller
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 70800000 (32-bit, non-prefetchable) [size=4K]

01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
	Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	NUMA node: 0
	Region 0: Memory at 8c400000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 75.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x4, ASPM L1, Exit Latency L1 <64us
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x4 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
		Vector table: BAR=0 offset=00003000
		PBA: BAR=0 offset=00002000
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap+ MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Device Serial Number 00-00-00-00-00-00-00-00
	Capabilities: [158 v1] Power Budgeting <?>
	Capabilities: [168 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [188 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [190 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=10us PortTPowerOnTime=10us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=50us
	Kernel driver in use: nvme
	Kernel modules: nvme

56:00.0 Network controller: Qualcomm Device 1101 (rev 01)
	Subsystem: Bigfoot Networks, Inc. Device a501
	Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Region 0: Memory at 8c300000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable- Count=1/32 Maskable+ 64bit-
		Address: 00000000  Data: 0000
		Masking: 00000000  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (downgraded), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp+ ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [158 v1] Transaction Processing Hints
		No steering table available
	Capabilities: [1e4 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [1ec v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=70us PortTPowerOnTime=0us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=44us
	Kernel modules: ath11k_pci

57:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5260 PCI Express Card Reader (rev 01)
	Subsystem: Dell RTS5260 PCI Express Card Reader
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 144
	Region 0: Memory at 8c200000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee20004  Data: 4022
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 512 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 unlimited
			ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM L1 Enabled; RCB 64 bytes, Disabled- CommClk-
			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 8GT/s (ok), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Not Supported, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Via message/WAKE#, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp- ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 2Retimers- DRS-
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+ EqualizationPhase1+
			 EqualizationPhase2+ EqualizationPhase3+ LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Device Serial Number 00-00-00-01-00-4c-e0-00
	Capabilities: [158 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [168 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [170 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=60us PortTPowerOnTime=60us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=60us
	Kernel driver in use: rtsx_pci
	Kernel modules: rtsx_pci


[-- Attachment #4: Type: text/plain, Size: 102 bytes --]

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
> hope this helps, if there is more I can do to debug it on my side I'm 
> happy to do so.

> [    0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!
>                BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:

> [    0.103693] DMAR: Host address width 39
> [    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
> [    0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 69e2ff0505e
> [    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
> [    0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap d2008c40660462 ecap f050da
> [    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
> [    0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap d2008c40660462 ecap f050da
> [    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
> [    0.103707] DMAR: Parse DMAR table failure.

which disables interrupt remapping and therefore the driver gets only
one MSI which makes it unhappy.

Not that I'm surprised, it's Dell.... Can you check whether they have a
BIOS update for that box?

Thanks,

        tglx

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
> hope this helps, if there is more I can do to debug it on my side I'm 
> happy to do so.

> [    0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!
>                BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:

> [    0.103693] DMAR: Host address width 39
> [    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
> [    0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 69e2ff0505e
> [    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
> [    0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap d2008c40660462 ecap f050da
> [    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
> [    0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap d2008c40660462 ecap f050da
> [    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
> [    0.103707] DMAR: Parse DMAR table failure.

which disables interrupt remapping and therefore the driver gets only
one MSI which makes it unhappy.

Not that I'm surprised, it's Dell.... Can you check whether they have a
BIOS update for that box?

Thanks,

        tglx

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Gleixner <tglx@linutronix.de> writes:

> On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
>> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
>> hope this helps, if there is more I can do to debug it on my side I'm 
>> happy to do so.
>
>> [    0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!
>>                BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:
>
>> [    0.103693] DMAR: Host address width 39
>> [    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
>> [    0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 69e2ff0505e
>> [    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
>> [    0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap d2008c40660462 ecap f050da
>> [    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
>> [    0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap d2008c40660462 ecap f050da
>> [    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
>> [    0.103707] DMAR: Parse DMAR table failure.
>
> which disables interrupt remapping and therefore the driver gets only
> one MSI which makes it unhappy.
>
> Not that I'm surprised, it's Dell.... Can you check whether they have a
> BIOS update for that box?

I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
separate "Virtualisation" setting in BIOS. See if you have that and try
enabling it.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Gleixner <tglx@linutronix.de> writes:

> On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
>> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
>> hope this helps, if there is more I can do to debug it on my side I'm 
>> happy to do so.
>
>> [    0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!
>>                BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:
>
>> [    0.103693] DMAR: Host address width 39
>> [    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
>> [    0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap 1c0000c40660462 ecap 69e2ff0505e
>> [    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
>> [    0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap d2008c40660462 ecap f050da
>> [    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
>> [    0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap d2008c40660462 ecap f050da
>> [    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
>> [    0.103707] DMAR: Parse DMAR table failure.
>
> which disables interrupt remapping and therefore the driver gets only
> one MSI which makes it unhappy.
>
> Not that I'm surprised, it's Dell.... Can you check whether they have a
> BIOS update for that box?

I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
separate "Virtualisation" setting in BIOS. See if you have that and try
enabling it.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Devin Bayer]

On 03/11/2020 22.08, Thomas Gleixner wrote:
> On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
> 
> Check the BIOS for a switch which is named 'VT-d' or such. It might
> depend on 'Intel Virtualization Technology' or such.
> 

Thanks for this info. The platform I have, J1900, indeed does not support VT-d.

So I guess I'm not able to use this card. That's unfortunate.

It doesn't seem like the Windows driver works either. It doesn't give any errors
but it fails to find any wireless networks.

~ dev

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Devin Bayer]

On 03/11/2020 22.08, Thomas Gleixner wrote:
> On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
> 
> Check the BIOS for a switch which is named 'VT-d' or such. It might
> depend on 'Intel Virtualization Technology' or such.
> 

Thanks for this info. The platform I have, J1900, indeed does not support VT-d.

So I guess I'm not able to use this card. That's unfortunate.

It doesn't seem like the Windows driver works either. It doesn't give any errors
but it fails to find any wireless networks.

~ dev

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

>> i tried the latest ath11k driver using linux 5.10 rc2 on a new dell
>> 9310 XPS 13.
>>
>> The driver will always complain "failed to get 32 MSI vectors, only
-28
>> available".
>>
>> I think the -28 is the error code for ENOSPC return by the
>> pci_alloc_irq_vectors() function.
>>

>Please try enabling Virtualisation and VT-d in BIOS. And also enable
>CONFIG_IRQ_REMAP in kernel config.

Thanks for the advise. I already configured the BIOS and kernel in this
way. I also update the BIOS XPS 13 9310 Bios to 1.1.1, but the 

 "DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!"

still remains and therefor the 

 "failed to get 32 MSI vectors, only -28 available"

message.

The really bad thing is that the Killer Wi-Fi 6 AX500-DBS QCA6390 is
solder on the mainboard :-(

- Stefani



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Gleixner <tglx@linutronix.de> writes:

> On Tue, Nov 03 2020 at 22:08, Thomas Gleixner wrote:
>> On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
>>>> > But it seems a little greedy if the device can't operate at all unless
>>>> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
>>>> > devices can work with fewer vectors, even if it reduces performance.
>>
>> Right, even most high end network cards work with one interrupt.
>>
>>>> This was my first reaction as well when I saw the code for the first
>>>> time. And the reply I got is that the firmware needs all 32 vectors, it
>>>> won't work with less.
>>
>> Great design.
>
> Just to put more information to this:
>
> Enforcing 32 vectors with MSI is beyond silly. Due to the limitations of
> MSI all of these vectors will be affine to a single CPU unless irq
> remapping is available and enabled.
>
> So if irq remapping is not enabled, then what are the 32 vectors buying?
> Exactly nothing because they just compete to be handled on the very same
> CPU. If the design requires more than one vector, then this should be
> done with MSI-X (which allows individual affinities and individual
> masking).
>
> That's known for 20 years and MSI-X exists for exactly that reason. But
> hardware people still insist on implementing MSI (probably because it
> saves 0.002$ per chip).
>
> But there is also the firmware side. Enforcing the availability of 32
> vectors on MSI is silly to begin with as explained above, but it's also
> silly given the constraints of the x86 vector space. It takes just 6
> devices having the same 32 vector requirement to exhaust it. Oh well...

Thanks Thomas, this is great info. I'm pushing this internally and we
try to get ath11k working with just one MSI vector.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Gleixner <tglx@linutronix.de> writes:

> On Tue, Nov 03 2020 at 22:08, Thomas Gleixner wrote:
>> On Tue, Nov 03 2020 at 10:08, Bjorn Helgaas wrote:
>>>> > But it seems a little greedy if the device can't operate at all unless
>>>> > it gets 32 vectors.  Are you sure that's a hard requirement?  Most
>>>> > devices can work with fewer vectors, even if it reduces performance.
>>
>> Right, even most high end network cards work with one interrupt.
>>
>>>> This was my first reaction as well when I saw the code for the first
>>>> time. And the reply I got is that the firmware needs all 32 vectors, it
>>>> won't work with less.
>>
>> Great design.
>
> Just to put more information to this:
>
> Enforcing 32 vectors with MSI is beyond silly. Due to the limitations of
> MSI all of these vectors will be affine to a single CPU unless irq
> remapping is available and enabled.
>
> So if irq remapping is not enabled, then what are the 32 vectors buying?
> Exactly nothing because they just compete to be handled on the very same
> CPU. If the design requires more than one vector, then this should be
> done with MSI-X (which allows individual affinities and individual
> masking).
>
> That's known for 20 years and MSI-X exists for exactly that reason. But
> hardware people still insist on implementing MSI (probably because it
> saves 0.002$ per chip).
>
> But there is also the firmware side. Enforcing the availability of 32
> vectors on MSI is silly to begin with as explained above, but it's also
> silly given the constraints of the x86 vector space. It takes just 6
> devices having the same 32 vector requirement to exhaust it. Oh well...

Thanks Thomas, this is great info. I'm pushing this internally and we
try to get ath11k working with just one MSI vector.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Bjorn Helgaas <helgaas@kernel.org> writes:

>> > Tangent: have you considered getting this list archived on
>> > https://lore.kernel.org/lists.html?
>> 
>> Good point, actually I have not. I'll add both ath10k and ath11k lists
>> to lore. It's even more important now that lists.infradead.org had a
>> hard drive crash and lost years of archives.
>
> Or you could just add linux-wireless, e.g.,
>
>   L:      ath11k@lists.infradead.org
>   L:      linux-wireless@vger.kernel.org
>
> or even consider moving from ath10k and ath11k to
> linux-wireless@vger.kernel.org.  I think there's some value in
> consolidating low-volume lists.  It looks like ath11k had < 90
> messages for all of October.

The background here is that linux-wireless is quite high volume list and
not everyone have time to follow that, so having specific ath10k and
ath11k lists make it easier for those people. So I'm hesitant to
shutdown driver lists for that reason.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Bjorn Helgaas <helgaas@kernel.org> writes:

>> > Tangent: have you considered getting this list archived on
>> > https://lore.kernel.org/lists.html?
>> 
>> Good point, actually I have not. I'll add both ath10k and ath11k lists
>> to lore. It's even more important now that lists.infradead.org had a
>> hard drive crash and lost years of archives.
>
> Or you could just add linux-wireless, e.g.,
>
>   L:      ath11k@lists.infradead.org
>   L:      linux-wireless@vger.kernel.org
>
> or even consider moving from ath10k and ath11k to
> linux-wireless@vger.kernel.org.  I think there's some value in
> consolidating low-volume lists.  It looks like ath11k had < 90
> messages for all of October.

The background here is that linux-wireless is quite high volume list and
not everyone have time to follow that, so having specific ath10k and
ath11k lists make it easier for those people. So I'm hesitant to
shutdown driver lists for that reason.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Thomas Gleixner <tglx@linutronix.de> writes:
>
>> On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
>>> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
>>> hope this helps, if there is more I can do to debug it on my side I'm 
>>> happy to do so.
>>
>>> [ 0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR
>>> reported at address 0!
>>>                BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:
>>
>>> [    0.103693] DMAR: Host address width 39
>>> [    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
>>> [ 0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap
>>> 1c0000c40660462 ecap 69e2ff0505e
>>> [    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
>>> [ 0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
>>> [ 0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
>>> [    0.103707] DMAR: Parse DMAR table failure.
>>
>> which disables interrupt remapping and therefore the driver gets only
>> one MSI which makes it unhappy.
>>
>> Not that I'm surprised, it's Dell.... Can you check whether they have a
>> BIOS update for that box?
>
> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
> separate "Virtualisation" setting in BIOS. See if you have that and try
> enabling it.

I was informed about another setting to test: try disabling "Enable
Secure Boot" in the BIOS. I don't know yet why it would help, but that's
what few people have recommended.

Please let me know how it goes.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Thomas Gleixner <tglx@linutronix.de> writes:
>
>> On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
>>> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I 
>>> hope this helps, if there is more I can do to debug it on my side I'm 
>>> happy to do so.
>>
>>> [ 0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR
>>> reported at address 0!
>>>                BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:
>>
>>> [    0.103693] DMAR: Host address width 39
>>> [    0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
>>> [ 0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap
>>> 1c0000c40660462 ecap 69e2ff0505e
>>> [    0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
>>> [ 0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [    0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
>>> [ 0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [    0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
>>> [    0.103707] DMAR: Parse DMAR table failure.
>>
>> which disables interrupt remapping and therefore the driver gets only
>> one MSI which makes it unhappy.
>>
>> Not that I'm surprised, it's Dell.... Can you check whether they have a
>> BIOS update for that box?
>
> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
> separate "Virtualisation" setting in BIOS. See if you have that and try
> enabling it.

I was informed about another setting to test: try disabling "Enable
Secure Boot" in the BIOS. I don't know yet why it would help, but that's
what few people have recommended.

Please let me know how it goes.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

Am 10.11.20 um 09:33 schrieb Kalle Valo:
>
>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>> separate "Virtualisation" setting in BIOS. See if you have that and try
>> enabling it.
> I was informed about another setting to test: try disabling "Enable
> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
> what few people have recommended.
>
> Please let me know how it goes.
>
I have two options under "Virtualization" in the BIOS: "Enable Intel 
Virtualization Technology (VT)" and "VT for Direct I/O". Both were 
enabled. Secure boot was also turned off. BIOS version is also at the 
most current version 1.1.1. Because of the dmesg errors Thomas Gleixner 
mentioned, I assume it would be best to contact Dell directly (even if 
I'm not sure if and how fast they will respond). If the driver would 
manage to work with only 1 vector, I assume this would also make it work 
on my configuration, even with possible performance hits.

Best,

Thomas

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

Am 10.11.20 um 09:33 schrieb Kalle Valo:
>
>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>> separate "Virtualisation" setting in BIOS. See if you have that and try
>> enabling it.
> I was informed about another setting to test: try disabling "Enable
> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
> what few people have recommended.
>
> Please let me know how it goes.
>
I have two options under "Virtualization" in the BIOS: "Enable Intel 
Virtualization Technology (VT)" and "VT for Direct I/O". Both were 
enabled. Secure boot was also turned off. BIOS version is also at the 
most current version 1.1.1. Because of the dmesg errors Thomas Gleixner 
mentioned, I assume it would be best to contact Dell directly (even if 
I'm not sure if and how fast they will respond). If the driver would 
manage to work with only 1 vector, I assume this would also make it work 
on my configuration, even with possible performance hits.

Best,

Thomas



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Krause <thomaskrause@posteo.de> writes:

> Am 10.11.20 um 09:33 schrieb Kalle Valo:
>>
>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>>> separate "Virtualisation" setting in BIOS. See if you have that and try
>>> enabling it.
>> I was informed about another setting to test: try disabling "Enable
>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
>> what few people have recommended.
>>
>> Please let me know how it goes.
>>
> I have two options under "Virtualization" in the BIOS: "Enable Intel
> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
> enabled. Secure boot was also turned off. BIOS version is also at the
> most current version 1.1.1.

This is good to know, thanks for testing. Now we have explored all
possible BIOS options as I know of.

> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
> would be best to contact Dell directly (even if I'm not sure if and
> how fast they will respond).

I have asked our people to report this to Dell, but no response yet.

> If the driver would manage to work with only 1 vector, I assume this
> would also make it work on my configuration, even with possible
> performance hits.

This is the workaround we are working on at the moment. There's now a
proof of concept patch but I'm not certain if it will work. I'll post it
as soon as I can and will provide the link in this thread.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Thomas Krause <thomaskrause@posteo.de> writes:

> Am 10.11.20 um 09:33 schrieb Kalle Valo:
>>
>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>>> separate "Virtualisation" setting in BIOS. See if you have that and try
>>> enabling it.
>> I was informed about another setting to test: try disabling "Enable
>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
>> what few people have recommended.
>>
>> Please let me know how it goes.
>>
> I have two options under "Virtualization" in the BIOS: "Enable Intel
> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
> enabled. Secure boot was also turned off. BIOS version is also at the
> most current version 1.1.1.

This is good to know, thanks for testing. Now we have explored all
possible BIOS options as I know of.

> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
> would be best to contact Dell directly (even if I'm not sure if and
> how fast they will respond).

I have asked our people to report this to Dell, but no response yet.

> If the driver would manage to work with only 1 vector, I assume this
> would also make it work on my configuration, even with possible
> performance hits.

This is the workaround we are working on at the moment. There's now a
proof of concept patch but I'm not certain if it will work. I'll post it
as soon as I can and will provide the link in this thread.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Wed, Nov 11 2020 at 09:53, Thomas Krause wrote:
> Am 10.11.20 um 09:33 schrieb Kalle Valo:
>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>>> separate "Virtualisation" setting in BIOS. See if you have that and try
>>> enabling it.
>> I was informed about another setting to test: try disabling "Enable
>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
>> what few people have recommended.
>>
>> Please let me know how it goes.
>>
> I have two options under "Virtualization" in the BIOS: "Enable Intel 
> Virtualization Technology (VT)" and "VT for Direct I/O". Both were

VT for Direct I/O enables the IOMMU and the interrupt remapping unit,
but the kernel can't use it because the ACPI tables are busted.

> enabled. Secure boot was also turned off. BIOS version is also at the 
> most current version 1.1.1. Because of the dmesg errors Thomas Gleixner 
> mentioned, I assume it would be best to contact Dell directly (even if 
> I'm not sure if and how fast they will respond). If the driver would

Good luck.

Thanks,

        tglx

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Wed, Nov 11 2020 at 09:53, Thomas Krause wrote:
> Am 10.11.20 um 09:33 schrieb Kalle Valo:
>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>>> separate "Virtualisation" setting in BIOS. See if you have that and try
>>> enabling it.
>> I was informed about another setting to test: try disabling "Enable
>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
>> what few people have recommended.
>>
>> Please let me know how it goes.
>>
> I have two options under "Virtualization" in the BIOS: "Enable Intel 
> Virtualization Technology (VT)" and "VT for Direct I/O". Both were

VT for Direct I/O enables the IOMMU and the interrupt remapping unit,
but the kernel can't use it because the ACPI tables are busted.

> enabled. Secure boot was also turned off. BIOS version is also at the 
> most current version 1.1.1. Because of the dmesg errors Thomas Gleixner 
> mentioned, I assume it would be best to contact Dell directly (even if 
> I'm not sure if and how fast they will respond). If the driver would

Good luck.

Thanks,

        tglx

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Thomas Krause <thomaskrause@posteo.de> writes:
>
>> Am 10.11.20 um 09:33 schrieb Kalle Valo:
>>>
>>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>>>> separate "Virtualisation" setting in BIOS. See if you have that and try
>>>> enabling it.
>>> I was informed about another setting to test: try disabling "Enable
>>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
>>> what few people have recommended.
>>>
>>> Please let me know how it goes.
>>>
>> I have two options under "Virtualization" in the BIOS: "Enable Intel
>> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
>> enabled. Secure boot was also turned off. BIOS version is also at the
>> most current version 1.1.1.
>
> This is good to know, thanks for testing. Now we have explored all
> possible BIOS options as I know of.
>
>> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
>> would be best to contact Dell directly (even if I'm not sure if and
>> how fast they will respond).
>
> I have asked our people to report this to Dell, but no response yet.
>
>> If the driver would manage to work with only 1 vector, I assume this
>> would also make it work on my configuration, even with possible
>> performance hits.
>
> This is the workaround we are working on at the moment. There's now a
> proof of concept patch but I'm not certain if it will work. I'll post it
> as soon as I can and will provide the link in this thread.

The proof of concept patch for v5.10-rc2 is here:

https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/

Hopefully it makes it possible to boot the firmware now. But this is a
quick hack and most likely buggy, so keep your expectations low :)

In case there are these warnings during firmware initialisation:

ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110

Try reverting this commit:

7fef431be9c9 mm/page_alloc: place pages to tail in __free_pages_core()

That's another issue which is debugged here:

http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Thomas Krause <thomaskrause@posteo.de> writes:
>
>> Am 10.11.20 um 09:33 schrieb Kalle Valo:
>>>
>>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
>>>> separate "Virtualisation" setting in BIOS. See if you have that and try
>>>> enabling it.
>>> I was informed about another setting to test: try disabling "Enable
>>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
>>> what few people have recommended.
>>>
>>> Please let me know how it goes.
>>>
>> I have two options under "Virtualization" in the BIOS: "Enable Intel
>> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
>> enabled. Secure boot was also turned off. BIOS version is also at the
>> most current version 1.1.1.
>
> This is good to know, thanks for testing. Now we have explored all
> possible BIOS options as I know of.
>
>> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
>> would be best to contact Dell directly (even if I'm not sure if and
>> how fast they will respond).
>
> I have asked our people to report this to Dell, but no response yet.
>
>> If the driver would manage to work with only 1 vector, I assume this
>> would also make it work on my configuration, even with possible
>> performance hits.
>
> This is the workaround we are working on at the moment. There's now a
> proof of concept patch but I'm not certain if it will work. I'll post it
> as soon as I can and will provide the link in this thread.

The proof of concept patch for v5.10-rc2 is here:

https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/

Hopefully it makes it possible to boot the firmware now. But this is a
quick hack and most likely buggy, so keep your expectations low :)

In case there are these warnings during firmware initialisation:

ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110

Try reverting this commit:

7fef431be9c9 mm/page_alloc: place pages to tail in __free_pages_core()

That's another issue which is debugged here:

http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

Kalle,

  Thanks so much for your and your teams efforts.  I've applied the
patch, and I'm receiving some errors similar to what you thought might
occur:

[    7.802756] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[    7.802797] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[    7.802815] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[    7.803291] ath11k_pci 0000:55:00.0: MSI vectors: 1
[    8.172623] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 48
[    8.172624] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22

I've reverted the commit you mentioned and am rebuilding now.  I'll
test in a few minutes.

Thanks!

On Wed, Nov 11, 2020 at 8:10 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Kalle Valo <kvalo@codeaurora.org> writes:
>
> > Thomas Krause <thomaskrause@posteo.de> writes:
> >
> >> Am 10.11.20 um 09:33 schrieb Kalle Valo:
> >>>
> >>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
> >>>> separate "Virtualisation" setting in BIOS. See if you have that and try
> >>>> enabling it.
> >>> I was informed about another setting to test: try disabling "Enable
> >>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
> >>> what few people have recommended.
> >>>
> >>> Please let me know how it goes.
> >>>
> >> I have two options under "Virtualization" in the BIOS: "Enable Intel
> >> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
> >> enabled. Secure boot was also turned off. BIOS version is also at the
> >> most current version 1.1.1.
> >
> > This is good to know, thanks for testing. Now we have explored all
> > possible BIOS options as I know of.
> >
> >> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
> >> would be best to contact Dell directly (even if I'm not sure if and
> >> how fast they will respond).
> >
> > I have asked our people to report this to Dell, but no response yet.
> >
> >> If the driver would manage to work with only 1 vector, I assume this
> >> would also make it work on my configuration, even with possible
> >> performance hits.
> >
> > This is the workaround we are working on at the moment. There's now a
> > proof of concept patch but I'm not certain if it will work. I'll post it
> > as soon as I can and will provide the link in this thread.
>
> The proof of concept patch for v5.10-rc2 is here:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
>
> Hopefully it makes it possible to boot the firmware now. But this is a
> quick hack and most likely buggy, so keep your expectations low :)
>
> In case there are these warnings during firmware initialisation:
>
> ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
>
> Try reverting this commit:
>
> 7fef431be9c9 mm/page_alloc: place pages to tail in __free_pages_core()
>
> That's another issue which is debugged here:
>
> http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

Kalle,

  Thanks so much for your and your teams efforts.  I've applied the
patch, and I'm receiving some errors similar to what you thought might
occur:

[    7.802756] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[    7.802797] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[    7.802815] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[    7.803291] ath11k_pci 0000:55:00.0: MSI vectors: 1
[    8.172623] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 48
[    8.172624] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22

I've reverted the commit you mentioned and am rebuilding now.  I'll
test in a few minutes.

Thanks!

On Wed, Nov 11, 2020 at 8:10 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Kalle Valo <kvalo@codeaurora.org> writes:
>
> > Thomas Krause <thomaskrause@posteo.de> writes:
> >
> >> Am 10.11.20 um 09:33 schrieb Kalle Valo:
> >>>
> >>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
> >>>> separate "Virtualisation" setting in BIOS. See if you have that and try
> >>>> enabling it.
> >>> I was informed about another setting to test: try disabling "Enable
> >>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
> >>> what few people have recommended.
> >>>
> >>> Please let me know how it goes.
> >>>
> >> I have two options under "Virtualization" in the BIOS: "Enable Intel
> >> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
> >> enabled. Secure boot was also turned off. BIOS version is also at the
> >> most current version 1.1.1.
> >
> > This is good to know, thanks for testing. Now we have explored all
> > possible BIOS options as I know of.
> >
> >> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
> >> would be best to contact Dell directly (even if I'm not sure if and
> >> how fast they will respond).
> >
> > I have asked our people to report this to Dell, but no response yet.
> >
> >> If the driver would manage to work with only 1 vector, I assume this
> >> would also make it work on my configuration, even with possible
> >> performance hits.
> >
> > This is the workaround we are working on at the moment. There's now a
> > proof of concept patch but I'm not certain if it will work. I'll post it
> > as soon as I can and will provide the link in this thread.
>
> The proof of concept patch for v5.10-rc2 is here:
>
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
>
> Hopefully it makes it possible to boot the firmware now. But this is a
> quick hack and most likely buggy, so keep your expectations low :)
>
> In case there are these warnings during firmware initialisation:
>
> ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
>
> Try reverting this commit:
>
> 7fef431be9c9 mm/page_alloc: place pages to tail in __free_pages_core()
>
> That's another issue which is debugged here:
>
> http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

Ok with 7fef431be9c9 reverted, it doesn't seem to change the initialization any:

[    7.961867] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[    7.961913] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[    7.961930] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[    7.962009] ath11k_pci 0000:55:00.0: MSI vectors: 1
[    8.461553] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 48
[    8.461556] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22

and just for thoroughness, here are my firmware file checksums (sha256):

9cc48d1dce819ead4112c6a8051c51e4d75e2b11f99ba9d8738cf8108967b70e  amss.bin
5081930c3b207f8ed82ff250f9b90fb77e87b2a92c3cf80ad020a58dea0bc5b7  board.bin
596482f780d21645f72a48acd9aed6c6fc8cf2d039ac31552a19800674d253cc  m3.bin


Thanks!


On Wed, Nov 11, 2020 at 8:24 PM wi nk <wink@technolu.st> wrote:
>
> Kalle,
>
>   Thanks so much for your and your teams efforts.  I've applied the
> patch, and I'm receiving some errors similar to what you thought might
> occur:
>
> [    7.802756] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
> experimental!
> [    7.802797] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
> 0x8e300000-0x8e3fffff 64bit]
> [    7.802815] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
> [    7.803291] ath11k_pci 0000:55:00.0: MSI vectors: 1
> [    8.172623] ath11k_pci 0000:55:00.0: Respond mem req failed,
> result: 1, err: 48
> [    8.172624] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
>
> I've reverted the commit you mentioned and am rebuilding now.  I'll
> test in a few minutes.
>
> Thanks!
>
> On Wed, Nov 11, 2020 at 8:10 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > Kalle Valo <kvalo@codeaurora.org> writes:
> >
> > > Thomas Krause <thomaskrause@posteo.de> writes:
> > >
> > >> Am 10.11.20 um 09:33 schrieb Kalle Valo:
> > >>>
> > >>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
> > >>>> separate "Virtualisation" setting in BIOS. See if you have that and try
> > >>>> enabling it.
> > >>> I was informed about another setting to test: try disabling "Enable
> > >>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
> > >>> what few people have recommended.
> > >>>
> > >>> Please let me know how it goes.
> > >>>
> > >> I have two options under "Virtualization" in the BIOS: "Enable Intel
> > >> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
> > >> enabled. Secure boot was also turned off. BIOS version is also at the
> > >> most current version 1.1.1.
> > >
> > > This is good to know, thanks for testing. Now we have explored all
> > > possible BIOS options as I know of.
> > >
> > >> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
> > >> would be best to contact Dell directly (even if I'm not sure if and
> > >> how fast they will respond).
> > >
> > > I have asked our people to report this to Dell, but no response yet.
> > >
> > >> If the driver would manage to work with only 1 vector, I assume this
> > >> would also make it work on my configuration, even with possible
> > >> performance hits.
> > >
> > > This is the workaround we are working on at the moment. There's now a
> > > proof of concept patch but I'm not certain if it will work. I'll post it
> > > as soon as I can and will provide the link in this thread.
> >
> > The proof of concept patch for v5.10-rc2 is here:
> >
> > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> >
> > Hopefully it makes it possible to boot the firmware now. But this is a
> > quick hack and most likely buggy, so keep your expectations low :)
> >
> > In case there are these warnings during firmware initialisation:
> >
> > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> >
> > Try reverting this commit:
> >
> > 7fef431be9c9 mm/page_alloc: place pages to tail in __free_pages_core()
> >
> > That's another issue which is debugged here:
> >
> > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> >
> > --
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

Ok with 7fef431be9c9 reverted, it doesn't seem to change the initialization any:

[    7.961867] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[    7.961913] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[    7.961930] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[    7.962009] ath11k_pci 0000:55:00.0: MSI vectors: 1
[    8.461553] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 48
[    8.461556] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22

and just for thoroughness, here are my firmware file checksums (sha256):

9cc48d1dce819ead4112c6a8051c51e4d75e2b11f99ba9d8738cf8108967b70e  amss.bin
5081930c3b207f8ed82ff250f9b90fb77e87b2a92c3cf80ad020a58dea0bc5b7  board.bin
596482f780d21645f72a48acd9aed6c6fc8cf2d039ac31552a19800674d253cc  m3.bin


Thanks!


On Wed, Nov 11, 2020 at 8:24 PM wi nk <wink@technolu.st> wrote:
>
> Kalle,
>
>   Thanks so much for your and your teams efforts.  I've applied the
> patch, and I'm receiving some errors similar to what you thought might
> occur:
>
> [    7.802756] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
> experimental!
> [    7.802797] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
> 0x8e300000-0x8e3fffff 64bit]
> [    7.802815] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
> [    7.803291] ath11k_pci 0000:55:00.0: MSI vectors: 1
> [    8.172623] ath11k_pci 0000:55:00.0: Respond mem req failed,
> result: 1, err: 48
> [    8.172624] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
>
> I've reverted the commit you mentioned and am rebuilding now.  I'll
> test in a few minutes.
>
> Thanks!
>
> On Wed, Nov 11, 2020 at 8:10 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > Kalle Valo <kvalo@codeaurora.org> writes:
> >
> > > Thomas Krause <thomaskrause@posteo.de> writes:
> > >
> > >> Am 10.11.20 um 09:33 schrieb Kalle Valo:
> > >>>
> > >>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a
> > >>>> separate "Virtualisation" setting in BIOS. See if you have that and try
> > >>>> enabling it.
> > >>> I was informed about another setting to test: try disabling "Enable
> > >>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's
> > >>> what few people have recommended.
> > >>>
> > >>> Please let me know how it goes.
> > >>>
> > >> I have two options under "Virtualization" in the BIOS: "Enable Intel
> > >> Virtualization Technology (VT)" and "VT for Direct I/O". Both were
> > >> enabled. Secure boot was also turned off. BIOS version is also at the
> > >> most current version 1.1.1.
> > >
> > > This is good to know, thanks for testing. Now we have explored all
> > > possible BIOS options as I know of.
> > >
> > >> Because of the dmesg errors Thomas Gleixner mentioned, I assume it
> > >> would be best to contact Dell directly (even if I'm not sure if and
> > >> how fast they will respond).
> > >
> > > I have asked our people to report this to Dell, but no response yet.
> > >
> > >> If the driver would manage to work with only 1 vector, I assume this
> > >> would also make it work on my configuration, even with possible
> > >> performance hits.
> > >
> > > This is the workaround we are working on at the moment. There's now a
> > > proof of concept patch but I'm not certain if it will work. I'll post it
> > > as soon as I can and will provide the link in this thread.
> >
> > The proof of concept patch for v5.10-rc2 is here:
> >
> > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> >
> > Hopefully it makes it possible to boot the firmware now. But this is a
> > quick hack and most likely buggy, so keep your expectations low :)
> >
> > In case there are these warnings during firmware initialisation:
> >
> > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> >
> > Try reverting this commit:
> >
> > 7fef431be9c9 mm/page_alloc: place pages to tail in __free_pages_core()
> >
> > That's another issue which is debugged here:
> >
> > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> >
> > --
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

(please don't top post, makes it harder to read emails)

wi nk <wink@technolu.st> writes:

> Ok with 7fef431be9c9 reverted, it doesn't seem to change the initialization any:
>
> [    7.961867] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
> experimental!
> [    7.961913] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
> 0x8e300000-0x8e3fffff 64bit]
> [    7.961930] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
> [    7.962009] ath11k_pci 0000:55:00.0: MSI vectors: 1
> [    8.461553] ath11k_pci 0000:55:00.0: Respond mem req failed,
> result: 1, err: 48
> [    8.461556] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22

I also see this -22 error (see my logs in [1]), even when the firmware
reboots normally. Do you see anything after these messages?

The problem which reverting 7fef431be9c9 helps has these errors:

ath11k_pci 0000:06:00.0: qmi failed memory request, err = -110
ath11k_pci 0000:06:00.0: qmi failed to respond fw mem req:-110

[1] http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html

> and just for thoroughness, here are my firmware file checksums (sha256):
>
> 9cc48d1dce819ead4112c6a8051c51e4d75e2b11f99ba9d8738cf8108967b70e  amss.bin
> 5081930c3b207f8ed82ff250f9b90fb77e87b2a92c3cf80ad020a58dea0bc5b7  board.bin
> 596482f780d21645f72a48acd9aed6c6fc8cf2d039ac31552a19800674d253cc  m3.bin

But these do not look same. I have:

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

Download them like this:

wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/amss.bin

wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/m3.bin

wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/board-2.bin

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

(please don't top post, makes it harder to read emails)

wi nk <wink@technolu.st> writes:

> Ok with 7fef431be9c9 reverted, it doesn't seem to change the initialization any:
>
> [    7.961867] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
> experimental!
> [    7.961913] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
> 0x8e300000-0x8e3fffff 64bit]
> [    7.961930] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
> [    7.962009] ath11k_pci 0000:55:00.0: MSI vectors: 1
> [    8.461553] ath11k_pci 0000:55:00.0: Respond mem req failed,
> result: 1, err: 48
> [    8.461556] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22

I also see this -22 error (see my logs in [1]), even when the firmware
reboots normally. Do you see anything after these messages?

The problem which reverting 7fef431be9c9 helps has these errors:

ath11k_pci 0000:06:00.0: qmi failed memory request, err = -110
ath11k_pci 0000:06:00.0: qmi failed to respond fw mem req:-110

[1] http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html

> and just for thoroughness, here are my firmware file checksums (sha256):
>
> 9cc48d1dce819ead4112c6a8051c51e4d75e2b11f99ba9d8738cf8108967b70e  amss.bin
> 5081930c3b207f8ed82ff250f9b90fb77e87b2a92c3cf80ad020a58dea0bc5b7  board.bin
> 596482f780d21645f72a48acd9aed6c6fc8cf2d039ac31552a19800674d253cc  m3.bin

But these do not look same. I have:

a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin

Download them like this:

wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/amss.bin

wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/m3.bin

wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/board-2.bin

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Wed, Nov 11, 2020 at 8:45 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> (please don't top post, makes it harder to read emails)
>
> wi nk <wink@technolu.st> writes:
>
> > Ok with 7fef431be9c9 reverted, it doesn't seem to change the initialization any:
> >
> > [    7.961867] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
> > experimental!
> > [    7.961913] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
> > 0x8e300000-0x8e3fffff 64bit]
> > [    7.961930] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
> > [    7.962009] ath11k_pci 0000:55:00.0: MSI vectors: 1
> > [    8.461553] ath11k_pci 0000:55:00.0: Respond mem req failed,
> > result: 1, err: 48
> > [    8.461556] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
>
> I also see this -22 error (see my logs in [1]), even when the firmware
> reboots normally. Do you see anything after these messages?
>
> The problem which reverting 7fef431be9c9 helps has these errors:
>
> ath11k_pci 0000:06:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:06:00.0: qmi failed to respond fw mem req:-110
>
> [1] http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
>
> > and just for thoroughness, here are my firmware file checksums (sha256):
> >
> > 9cc48d1dce819ead4112c6a8051c51e4d75e2b11f99ba9d8738cf8108967b70e  amss.bin
> > 5081930c3b207f8ed82ff250f9b90fb77e87b2a92c3cf80ad020a58dea0bc5b7  board.bin
> > 596482f780d21645f72a48acd9aed6c6fc8cf2d039ac31552a19800674d253cc  m3.bin
>
> But these do not look same. I have:
>
> a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
> 4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
> d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin
>
> Download them like this:
>
> wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/amss.bin
>
> wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/m3.bin
>
> wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/board-2.bin
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Sorry for the top posting, web email has ruined my mailing list
etiquette.  It seems having the correct firmware in place has caused
some forward movement.  I now see this:

[    8.513210] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[    8.513251] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[    8.513269] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[    8.513348] ath11k_pci 0000:55:00.0: MSI vectors: 1
[    8.789499] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 0
[    8.789500] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
[    8.794236] ath11k_pci 0000:55:00.0: req mem_seg[0] 0x28100000 524288 1
[    8.794237] ath11k_pci 0000:55:00.0: req mem_seg[1] 0x28180000 524288 1
[    8.794238] ath11k_pci 0000:55:00.0: req mem_seg[2] 0x28200000 524288 1
[    8.794238] ath11k_pci 0000:55:00.0: req mem_seg[3] 0x28280000 294912 1
[    8.794239] ath11k_pci 0000:55:00.0: req mem_seg[4] 0x28300000 524288 1
[    8.794239] ath11k_pci 0000:55:00.0: req mem_seg[5] 0x28380000 524288 1
[    8.794240] ath11k_pci 0000:55:00.0: req mem_seg[6] 0x27c00000 458752 1
[    8.794240] ath11k_pci 0000:55:00.0: req mem_seg[7] 0x27c80000 131072 1
[    8.794240] ath11k_pci 0000:55:00.0: req mem_seg[8] 0x27d00000 524288 4
[    8.794241] ath11k_pci 0000:55:00.0: req mem_seg[9] 0x27d80000 360448 4
[    8.794241] ath11k_pci 0000:55:00.0: req mem_seg[10] 0x28578000 16384 1
[    8.807053] ath11k_pci 0000:55:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    8.807054] ath11k_pci 0000:55:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[    8.910984] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
[    9.446566] ath11k_pci 0000:55:00.0 wlp85s0: renamed from wlan0
[   11.296620] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
[   22.088028] ath11k_pci 0000:55:00.0: wmi command 12290 timeout
[   22.088030] ath11k_pci 0000:55:00.0: failed to send WMI_STOP_SCAN_CMDID
[   22.088031] ath11k_pci 0000:55:00.0: failed to stop wmi scan: -11
[   22.088032] ath11k_pci 0000:55:00.0: failed to stop scan: -11
[   22.088033] ath11k_pci 0000:55:00.0: failed to start hw scan: -110
[   28.232066] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   28.232069] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   28.232073] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[   38.216054] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   38.216057] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   38.216061] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[   51.783961] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   51.783965] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   51.783970] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[   71.695627] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   71.695629] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   71.695630] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[  100.864905] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[  100.864909] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[  100.864913] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[  107.306896] mhi 0000:55:00.0: Device failed to exit MHI Reset state
[  143.868561] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[  143.868564] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[  143.868566] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[  199.464250] mhi 0000:55:00.0: Device failed to exit MHI Reset state
<snip>

Occasionally my kernel is panic'ing at random spots (this is probably
related to the other patch I guess), but I do have a bit of an adapter
now ,ifconfig shows it.  I don't seem to be able to find any networks
with it however.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Wed, Nov 11, 2020 at 8:45 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> (please don't top post, makes it harder to read emails)
>
> wi nk <wink@technolu.st> writes:
>
> > Ok with 7fef431be9c9 reverted, it doesn't seem to change the initialization any:
> >
> > [    7.961867] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
> > experimental!
> > [    7.961913] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
> > 0x8e300000-0x8e3fffff 64bit]
> > [    7.961930] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
> > [    7.962009] ath11k_pci 0000:55:00.0: MSI vectors: 1
> > [    8.461553] ath11k_pci 0000:55:00.0: Respond mem req failed,
> > result: 1, err: 48
> > [    8.461556] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
>
> I also see this -22 error (see my logs in [1]), even when the firmware
> reboots normally. Do you see anything after these messages?
>
> The problem which reverting 7fef431be9c9 helps has these errors:
>
> ath11k_pci 0000:06:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:06:00.0: qmi failed to respond fw mem req:-110
>
> [1] http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
>
> > and just for thoroughness, here are my firmware file checksums (sha256):
> >
> > 9cc48d1dce819ead4112c6a8051c51e4d75e2b11f99ba9d8738cf8108967b70e  amss.bin
> > 5081930c3b207f8ed82ff250f9b90fb77e87b2a92c3cf80ad020a58dea0bc5b7  board.bin
> > 596482f780d21645f72a48acd9aed6c6fc8cf2d039ac31552a19800674d253cc  m3.bin
>
> But these do not look same. I have:
>
> a101dc90f8e876f39383b60c9da64ec4  /lib/firmware/ath11k/QCA6390/hw2.0/amss.bin
> 4c0781f659d2b7d6bef10a2e3d457728  /lib/firmware/ath11k/QCA6390/hw2.0/board-2.bin
> d4c912a3501a3694a3f460d13de06d28  /lib/firmware/ath11k/QCA6390/hw2.0/m3.bin
>
> Download them like this:
>
> wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/amss.bin
>
> wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/1.0.1/WLAN.HST.1.0.1-01740-QCAHSTSWPLZ_V2_TO_X86-1/m3.bin
>
> wget https://github.com/kvalo/ath11k-firmware/raw/master/QCA6390/hw2.0/board-2.bin
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Sorry for the top posting, web email has ruined my mailing list
etiquette.  It seems having the correct firmware in place has caused
some forward movement.  I now see this:

[    8.513210] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[    8.513251] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[    8.513269] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[    8.513348] ath11k_pci 0000:55:00.0: MSI vectors: 1
[    8.789499] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 0
[    8.789500] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
[    8.794236] ath11k_pci 0000:55:00.0: req mem_seg[0] 0x28100000 524288 1
[    8.794237] ath11k_pci 0000:55:00.0: req mem_seg[1] 0x28180000 524288 1
[    8.794238] ath11k_pci 0000:55:00.0: req mem_seg[2] 0x28200000 524288 1
[    8.794238] ath11k_pci 0000:55:00.0: req mem_seg[3] 0x28280000 294912 1
[    8.794239] ath11k_pci 0000:55:00.0: req mem_seg[4] 0x28300000 524288 1
[    8.794239] ath11k_pci 0000:55:00.0: req mem_seg[5] 0x28380000 524288 1
[    8.794240] ath11k_pci 0000:55:00.0: req mem_seg[6] 0x27c00000 458752 1
[    8.794240] ath11k_pci 0000:55:00.0: req mem_seg[7] 0x27c80000 131072 1
[    8.794240] ath11k_pci 0000:55:00.0: req mem_seg[8] 0x27d00000 524288 4
[    8.794241] ath11k_pci 0000:55:00.0: req mem_seg[9] 0x27d80000 360448 4
[    8.794241] ath11k_pci 0000:55:00.0: req mem_seg[10] 0x28578000 16384 1
[    8.807053] ath11k_pci 0000:55:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    8.807054] ath11k_pci 0000:55:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[    8.910984] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
[    9.446566] ath11k_pci 0000:55:00.0 wlp85s0: renamed from wlan0
[   11.296620] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
[   22.088028] ath11k_pci 0000:55:00.0: wmi command 12290 timeout
[   22.088030] ath11k_pci 0000:55:00.0: failed to send WMI_STOP_SCAN_CMDID
[   22.088031] ath11k_pci 0000:55:00.0: failed to stop wmi scan: -11
[   22.088032] ath11k_pci 0000:55:00.0: failed to stop scan: -11
[   22.088033] ath11k_pci 0000:55:00.0: failed to start hw scan: -110
[   28.232066] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   28.232069] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   28.232073] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[   38.216054] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   38.216057] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   38.216061] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[   51.783961] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   51.783965] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   51.783970] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[   71.695627] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[   71.695629] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[   71.695630] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[  100.864905] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[  100.864909] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[  100.864913] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[  107.306896] mhi 0000:55:00.0: Device failed to exit MHI Reset state
[  143.868561] ath11k_pci 0000:55:00.0: wmi command 12289 timeout
[  143.868564] ath11k_pci 0000:55:00.0: failed to send WMI_START_SCAN_CMDID
[  143.868566] ath11k_pci 0000:55:00.0: failed to start hw scan: -11
[  199.464250] mhi 0000:55:00.0: Device failed to exit MHI Reset state
<snip>

Occasionally my kernel is panic'ing at random spots (this is probably
related to the other patch I guess), but I do have a bit of an adapter
now ,ifconfig shows it.  I don't seem to be able to find any networks
with it however.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> 
> 
> The proof of concept patch for v5.10-rc2 is here:
> 
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> 
> Hopefully it makes it possible to boot the firmware now. But this is
> a
> quick hack and most likely buggy, so keep your expectations low :)
> 
> In case there are these warnings during firmware initialisation:
> 
> ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> 
> Try reverting this commit:
> 
> 7fef431be9c9 mm/page_alloc: place pages to tail in
> __free_pages_core()
> 
> That's another issue which is debugged here:
> 
> http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> 

Success on DELL XPS13 910. Applying the patch and revert patch
7fef431be9c9 worked for me.

Thanks!

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> 
> 
> The proof of concept patch for v5.10-rc2 is here:
> 
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> 
> Hopefully it makes it possible to boot the firmware now. But this is
> a
> quick hack and most likely buggy, so keep your expectations low :)
> 
> In case there are these warnings during firmware initialisation:
> 
> ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> 
> Try reverting this commit:
> 
> 7fef431be9c9 mm/page_alloc: place pages to tail in
> __free_pages_core()
> 
> That's another issue which is debugged here:
> 
> http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> 

Success on DELL XPS13 910. Applying the patch and revert patch
7fef431be9c9 worked for me.

Thanks!



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> 
> The proof of concept patch for v5.10-rc2 is here:
> 
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> 
> Hopefully it makes it possible to boot the firmware now. But this is
> a
> quick hack and most likely buggy, so keep your expectations low :)
> 
> In case there are these warnings during firmware initialisation:
> 
> ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> 
> Try reverting this commit:
> 
> 7fef431be9c9 mm/page_alloc: place pages to tail in
> __free_pages_core()
> 
> That's another issue which is debugged here:
> 
> http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> 

Applying the patch and revert patch 7fef431be9c9 worked on the first
glance.

After a couple of minutes the connection get broken. The kernel log
shows the following error:

ath11k_pci 0000:55:00.0: wmi command 16387 timeout
ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
ath11k_pc
i 0000:55:00.0: failed to enable PMF QOS: (-11

It is also not possible to unload the ath11k_pci, rmmod will hang.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> 
> The proof of concept patch for v5.10-rc2 is here:
> 
> https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> 
> Hopefully it makes it possible to boot the firmware now. But this is
> a
> quick hack and most likely buggy, so keep your expectations low :)
> 
> In case there are these warnings during firmware initialisation:
> 
> ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> 
> Try reverting this commit:
> 
> 7fef431be9c9 mm/page_alloc: place pages to tail in
> __free_pages_core()
> 
> That's another issue which is debugged here:
> 
> http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> 

Applying the patch and revert patch 7fef431be9c9 worked on the first
glance.

After a couple of minutes the connection get broken. The kernel log
shows the following error:

ath11k_pci 0000:55:00.0: wmi command 16387 timeout
ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
ath11k_pc
i 0000:55:00.0: failed to enable PMF QOS: (-11

It is also not possible to unload the ath11k_pci, rmmod will hang.



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
>
> On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> >
> > The proof of concept patch for v5.10-rc2 is here:
> >
> > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> >
> > Hopefully it makes it possible to boot the firmware now. But this is
> > a
> > quick hack and most likely buggy, so keep your expectations low :)
> >
> > In case there are these warnings during firmware initialisation:
> >
> > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> >
> > Try reverting this commit:
> >
> > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > __free_pages_core()
> >
> > That's another issue which is debugged here:
> >
> > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> >
>
> Applying the patch and revert patch 7fef431be9c9 worked on the first
> glance.
>
> After a couple of minutes the connection get broken. The kernel log
> shows the following error:
>
> ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> ath11k_pc
> i 0000:55:00.0: failed to enable PMF QOS: (-11
>
> It is also not possible to unload the ath11k_pci, rmmod will hang.
>
>

I can confirm the same behavior as Stefani so far.  After applying the
patch, and reverting commit 7fef431be9c9, I am able to connect to a
network.  It hasn't disconnected yet (I'm sending this email via that
connection).  I'll report what I find next.

Thanks again for the help!

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
>
> On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> >
> > The proof of concept patch for v5.10-rc2 is here:
> >
> > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> >
> > Hopefully it makes it possible to boot the firmware now. But this is
> > a
> > quick hack and most likely buggy, so keep your expectations low :)
> >
> > In case there are these warnings during firmware initialisation:
> >
> > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> >
> > Try reverting this commit:
> >
> > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > __free_pages_core()
> >
> > That's another issue which is debugged here:
> >
> > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> >
>
> Applying the patch and revert patch 7fef431be9c9 worked on the first
> glance.
>
> After a couple of minutes the connection get broken. The kernel log
> shows the following error:
>
> ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> ath11k_pc
> i 0000:55:00.0: failed to enable PMF QOS: (-11
>
> It is also not possible to unload the ath11k_pci, rmmod will hang.
>
>

I can confirm the same behavior as Stefani so far.  After applying the
patch, and reverting commit 7fef431be9c9, I am able to connect to a
network.  It hasn't disconnected yet (I'm sending this email via that
connection).  I'll report what I find next.

Thanks again for the help!

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

I've yet to see any instability after 45 minutes of exercising it, I
do see a couple of messages that came out of the driver:

[    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
[   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a

then when it associates:

[   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
[   16.722636] wlp85s0: authenticated
[   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
[   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
(capab=0x411 status=0 aid=8)
[   16.738443] wlp85s0: associated
[   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready

The adapter is achieving around 500 mbps on my gigabit connection, my
2018 mbp sees around 650, so it's doing pretty well so far.

Stefani - when you applied the patch that Kalle shared, which branch
did you apply it to?  I applied it to ath11k-qca6390-bringup and when
I revert 7fef431be9c9 there is a small merge conflict I needed to
resolve.  I wonder if either the starting branch, or your chosen
resolution are related to the instability you see (or I'm just lucky
so far! :)).

On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
>
> On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> >
> > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > >
> > > The proof of concept patch for v5.10-rc2 is here:
> > >
> > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> > >
> > > Hopefully it makes it possible to boot the firmware now. But this is
> > > a
> > > quick hack and most likely buggy, so keep your expectations low :)
> > >
> > > In case there are these warnings during firmware initialisation:
> > >
> > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> > >
> > > Try reverting this commit:
> > >
> > > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > > __free_pages_core()
> > >
> > > That's another issue which is debugged here:
> > >
> > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> > >
> >
> > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > glance.
> >
> > After a couple of minutes the connection get broken. The kernel log
> > shows the following error:
> >
> > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > ath11k_pc
> > i 0000:55:00.0: failed to enable PMF QOS: (-11
> >
> > It is also not possible to unload the ath11k_pci, rmmod will hang.
> >
> >
>
> I can confirm the same behavior as Stefani so far.  After applying the
> patch, and reverting commit 7fef431be9c9, I am able to connect to a
> network.  It hasn't disconnected yet (I'm sending this email via that
> connection).  I'll report what I find next.
>
> Thanks again for the help!

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

I've yet to see any instability after 45 minutes of exercising it, I
do see a couple of messages that came out of the driver:

[    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
[   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a

then when it associates:

[   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
[   16.722636] wlp85s0: authenticated
[   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
[   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
(capab=0x411 status=0 aid=8)
[   16.738443] wlp85s0: associated
[   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready

The adapter is achieving around 500 mbps on my gigabit connection, my
2018 mbp sees around 650, so it's doing pretty well so far.

Stefani - when you applied the patch that Kalle shared, which branch
did you apply it to?  I applied it to ath11k-qca6390-bringup and when
I revert 7fef431be9c9 there is a small merge conflict I needed to
resolve.  I wonder if either the starting branch, or your chosen
resolution are related to the instability you see (or I'm just lucky
so far! :)).

On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
>
> On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> >
> > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > >
> > > The proof of concept patch for v5.10-rc2 is here:
> > >
> > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> > >
> > > Hopefully it makes it possible to boot the firmware now. But this is
> > > a
> > > quick hack and most likely buggy, so keep your expectations low :)
> > >
> > > In case there are these warnings during firmware initialisation:
> > >
> > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> > >
> > > Try reverting this commit:
> > >
> > > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > > __free_pages_core()
> > >
> > > That's another issue which is debugged here:
> > >
> > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> > >
> >
> > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > glance.
> >
> > After a couple of minutes the connection get broken. The kernel log
> > shows the following error:
> >
> > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > ath11k_pc
> > i 0000:55:00.0: failed to enable PMF QOS: (-11
> >
> > It is also not possible to unload the ath11k_pci, rmmod will hang.
> >
> >
>
> I can confirm the same behavior as Stefani so far.  After applying the
> patch, and reverting commit 7fef431be9c9, I am able to connect to a
> network.  It hasn't disconnected yet (I'm sending this email via that
> connection).  I'll report what I find next.
>
> Thanks again for the help!

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
>
> I've yet to see any instability after 45 minutes of exercising it, I
> do see a couple of messages that came out of the driver:
>
> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>
> then when it associates:
>
> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> [   16.722636] wlp85s0: authenticated
> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> (capab=0x411 status=0 aid=8)
> [   16.738443] wlp85s0: associated
> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
>
> The adapter is achieving around 500 mbps on my gigabit connection, my
> 2018 mbp sees around 650, so it's doing pretty well so far.
>
> Stefani - when you applied the patch that Kalle shared, which branch
> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> I revert 7fef431be9c9 there is a small merge conflict I needed to
> resolve.  I wonder if either the starting branch, or your chosen
> resolution are related to the instability you see (or I'm just lucky
> so far! :)).
>
> On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
> >
> > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> > >
> > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > > >
> > > > The proof of concept patch for v5.10-rc2 is here:
> > > >
> > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> > > >
> > > > Hopefully it makes it possible to boot the firmware now. But this is
> > > > a
> > > > quick hack and most likely buggy, so keep your expectations low :)
> > > >
> > > > In case there are these warnings during firmware initialisation:
> > > >
> > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> > > >
> > > > Try reverting this commit:
> > > >
> > > > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > > > __free_pages_core()
> > > >
> > > > That's another issue which is debugged here:
> > > >
> > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> > > >
> > >
> > > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > > glance.
> > >
> > > After a couple of minutes the connection get broken. The kernel log
> > > shows the following error:
> > >
> > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > > ath11k_pc
> > > i 0000:55:00.0: failed to enable PMF QOS: (-11
> > >
> > > It is also not possible to unload the ath11k_pci, rmmod will hang.
> > >
> > >
> >
> > I can confirm the same behavior as Stefani so far.  After applying the
> > patch, and reverting commit 7fef431be9c9, I am able to connect to a
> > network.  It hasn't disconnected yet (I'm sending this email via that
> > connection).  I'll report what I find next.
> >
> > Thanks again for the help!

Sigh.... sorry for the top post again.  I'll now get a real email client.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
>
> I've yet to see any instability after 45 minutes of exercising it, I
> do see a couple of messages that came out of the driver:
>
> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>
> then when it associates:
>
> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> [   16.722636] wlp85s0: authenticated
> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> (capab=0x411 status=0 aid=8)
> [   16.738443] wlp85s0: associated
> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
>
> The adapter is achieving around 500 mbps on my gigabit connection, my
> 2018 mbp sees around 650, so it's doing pretty well so far.
>
> Stefani - when you applied the patch that Kalle shared, which branch
> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> I revert 7fef431be9c9 there is a small merge conflict I needed to
> resolve.  I wonder if either the starting branch, or your chosen
> resolution are related to the instability you see (or I'm just lucky
> so far! :)).
>
> On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
> >
> > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> > >
> > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > > >
> > > > The proof of concept patch for v5.10-rc2 is here:
> > > >
> > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> > > >
> > > > Hopefully it makes it possible to boot the firmware now. But this is
> > > > a
> > > > quick hack and most likely buggy, so keep your expectations low :)
> > > >
> > > > In case there are these warnings during firmware initialisation:
> > > >
> > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> > > >
> > > > Try reverting this commit:
> > > >
> > > > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > > > __free_pages_core()
> > > >
> > > > That's another issue which is debugged here:
> > > >
> > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> > > >
> > >
> > > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > > glance.
> > >
> > > After a couple of minutes the connection get broken. The kernel log
> > > shows the following error:
> > >
> > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > > ath11k_pc
> > > i 0000:55:00.0: failed to enable PMF QOS: (-11
> > >
> > > It is also not possible to unload the ath11k_pci, rmmod will hang.
> > >
> > >
> >
> > I can confirm the same behavior as Stefani so far.  After applying the
> > patch, and reverting commit 7fef431be9c9, I am able to connect to a
> > network.  It hasn't disconnected yet (I'm sending this email via that
> > connection).  I'll report what I find next.
> >
> > Thanks again for the help!

Sigh.... sorry for the top post again.  I'll now get a real email client.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 2:11 AM wi nk <wink@technolu.st> wrote:
>
> On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
> >
> > I've yet to see any instability after 45 minutes of exercising it, I
> > do see a couple of messages that came out of the driver:
> >
> > [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >
> > then when it associates:
> >
> > [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > [   16.722636] wlp85s0: authenticated
> > [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > (capab=0x411 status=0 aid=8)
> > [   16.738443] wlp85s0: associated
> > [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
> >
> > The adapter is achieving around 500 mbps on my gigabit connection, my
> > 2018 mbp sees around 650, so it's doing pretty well so far.
> >
> > Stefani - when you applied the patch that Kalle shared, which branch
> > did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> > I revert 7fef431be9c9 there is a small merge conflict I needed to
> > resolve.  I wonder if either the starting branch, or your chosen
> > resolution are related to the instability you see (or I'm just lucky
> > so far! :)).
> >
> > On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
> > >
> > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> > > >
> > > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > > > >
> > > > > The proof of concept patch for v5.10-rc2 is here:
> > > > >
> > > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> > > > >
> > > > > Hopefully it makes it possible to boot the firmware now. But this is
> > > > > a
> > > > > quick hack and most likely buggy, so keep your expectations low :)
> > > > >
> > > > > In case there are these warnings during firmware initialisation:
> > > > >
> > > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> > > > >
> > > > > Try reverting this commit:
> > > > >
> > > > > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > > > > __free_pages_core()
> > > > >
> > > > > That's another issue which is debugged here:
> > > > >
> > > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> > > > >
> > > >
> > > > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > > > glance.
> > > >
> > > > After a couple of minutes the connection get broken. The kernel log
> > > > shows the following error:
> > > >
> > > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > > > ath11k_pc
> > > > i 0000:55:00.0: failed to enable PMF QOS: (-11
> > > >
> > > > It is also not possible to unload the ath11k_pci, rmmod will hang.
> > > >
> > > >
> > >
> > > I can confirm the same behavior as Stefani so far.  After applying the
> > > patch, and reverting commit 7fef431be9c9, I am able to connect to a
> > > network.  It hasn't disconnected yet (I'm sending this email via that
> > > connection).  I'll report what I find next.
> > >
> > > Thanks again for the help!
>
> Sigh.... sorry for the top post again.  I'll now get a real email client.

So the connection remained super stable for a while, so I decided to
tempt fate and suspend the laptop to see what would happen :).

[ 5994.143715] PM: suspend exit
[ 5997.260351] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 5997.260353] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 5997.260356] ath11k_pci 0000:55:00.0: failed to enable dynamic bw: -11
[ 6000.332299] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6000.332303] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6000.332308] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6003.404365] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6003.404368] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6003.404373] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6016.204347] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6016.204351] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6016.204357] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6019.276319] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6019.276323] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6019.276329] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6031.052272] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6031.052275] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6031.052279] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6034.128257] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6034.128261] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6034.128265] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6039.500241] ath11k_pci 0000:55:00.0: qmi failed set mode request,
mode: 4, err = -110
[ 6039.500244] ath11k_pci 0000:55:00.0: qmi failed to send wlan mode off

I was able to remove the ath11k module using rmmod -f , and then
modprobe ath11k + atk11k_pci and the device was able to reassociate
and bring the connection back up.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 2:11 AM wi nk <wink@technolu.st> wrote:
>
> On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
> >
> > I've yet to see any instability after 45 minutes of exercising it, I
> > do see a couple of messages that came out of the driver:
> >
> > [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >
> > then when it associates:
> >
> > [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > [   16.722636] wlp85s0: authenticated
> > [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > (capab=0x411 status=0 aid=8)
> > [   16.738443] wlp85s0: associated
> > [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
> >
> > The adapter is achieving around 500 mbps on my gigabit connection, my
> > 2018 mbp sees around 650, so it's doing pretty well so far.
> >
> > Stefani - when you applied the patch that Kalle shared, which branch
> > did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> > I revert 7fef431be9c9 there is a small merge conflict I needed to
> > resolve.  I wonder if either the starting branch, or your chosen
> > resolution are related to the instability you see (or I'm just lucky
> > so far! :)).
> >
> > On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
> > >
> > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> > > >
> > > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > > > >
> > > > > The proof of concept patch for v5.10-rc2 is here:
> > > > >
> > > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
> > > > >
> > > > > Hopefully it makes it possible to boot the firmware now. But this is
> > > > > a
> > > > > quick hack and most likely buggy, so keep your expectations low :)
> > > > >
> > > > > In case there are these warnings during firmware initialisation:
> > > > >
> > > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
> > > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
> > > > >
> > > > > Try reverting this commit:
> > > > >
> > > > > 7fef431be9c9 mm/page_alloc: place pages to tail in
> > > > > __free_pages_core()
> > > > >
> > > > > That's another issue which is debugged here:
> > > > >
> > > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
> > > > >
> > > >
> > > > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > > > glance.
> > > >
> > > > After a couple of minutes the connection get broken. The kernel log
> > > > shows the following error:
> > > >
> > > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > > > ath11k_pc
> > > > i 0000:55:00.0: failed to enable PMF QOS: (-11
> > > >
> > > > It is also not possible to unload the ath11k_pci, rmmod will hang.
> > > >
> > > >
> > >
> > > I can confirm the same behavior as Stefani so far.  After applying the
> > > patch, and reverting commit 7fef431be9c9, I am able to connect to a
> > > network.  It hasn't disconnected yet (I'm sending this email via that
> > > connection).  I'll report what I find next.
> > >
> > > Thanks again for the help!
>
> Sigh.... sorry for the top post again.  I'll now get a real email client.

So the connection remained super stable for a while, so I decided to
tempt fate and suspend the laptop to see what would happen :).

[ 5994.143715] PM: suspend exit
[ 5997.260351] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 5997.260353] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 5997.260356] ath11k_pci 0000:55:00.0: failed to enable dynamic bw: -11
[ 6000.332299] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6000.332303] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6000.332308] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6003.404365] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6003.404368] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6003.404373] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6016.204347] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6016.204351] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6016.204357] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6019.276319] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6019.276323] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6019.276329] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6031.052272] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6031.052275] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6031.052279] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6034.128257] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6034.128261] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6034.128265] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6039.500241] ath11k_pci 0000:55:00.0: qmi failed set mode request,
mode: 4, err = -110
[ 6039.500244] ath11k_pci 0000:55:00.0: qmi failed to send wlan mode off

I was able to remove the ath11k module using rmmod -f , and then
modprobe ath11k + atk11k_pci and the device was able to reassociate
and bring the connection back up.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Carl Huang]

On 2020-11-12 10:31, wi nk wrote:
> On Thu, Nov 12, 2020 at 2:11 AM wi nk <wink@technolu.st> wrote:
>> 
>> On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
>> >
>> > I've yet to see any instability after 45 minutes of exercising it, I
>> > do see a couple of messages that came out of the driver:
>> >
>> > [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>> > [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>> >
>> > then when it associates:
>> >
>> > [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>> > [   16.722636] wlp85s0: authenticated
>> > [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>> > [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>> > (capab=0x411 status=0 aid=8)
>> > [   16.738443] wlp85s0: associated
>> > [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
>> >
>> > The adapter is achieving around 500 mbps on my gigabit connection, my
>> > 2018 mbp sees around 650, so it's doing pretty well so far.
>> >
>> > Stefani - when you applied the patch that Kalle shared, which branch
>> > did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>> > I revert 7fef431be9c9 there is a small merge conflict I needed to
>> > resolve.  I wonder if either the starting branch, or your chosen
>> > resolution are related to the instability you see (or I'm just lucky
>> > so far! :)).
>> >
>> > On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
>> > >
>> > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
>> > > >
>> > > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
>> > > > >
>> > > > > The proof of concept patch for v5.10-rc2 is here:
>> > > > >
>> > > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
>> > > > >
>> > > > > Hopefully it makes it possible to boot the firmware now. But this is
>> > > > > a
>> > > > > quick hack and most likely buggy, so keep your expectations low :)
>> > > > >
>> > > > > In case there are these warnings during firmware initialisation:
>> > > > >
>> > > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
>> > > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
>> > > > >
>> > > > > Try reverting this commit:
>> > > > >
>> > > > > 7fef431be9c9 mm/page_alloc: place pages to tail in
>> > > > > __free_pages_core()
>> > > > >
>> > > > > That's another issue which is debugged here:
>> > > > >
>> > > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
>> > > > >
>> > > >
>> > > > Applying the patch and revert patch 7fef431be9c9 worked on the first
>> > > > glance.
>> > > >
>> > > > After a couple of minutes the connection get broken. The kernel log
>> > > > shows the following error:
>> > > >
>> > > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
>> > > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
>> > > > ath11k_pc
>> > > > i 0000:55:00.0: failed to enable PMF QOS: (-11
>> > > >
>> > > > It is also not possible to unload the ath11k_pci, rmmod will hang.
>> > > >
>> > > >
>> > >
>> > > I can confirm the same behavior as Stefani so far.  After applying the
>> > > patch, and reverting commit 7fef431be9c9, I am able to connect to a
>> > > network.  It hasn't disconnected yet (I'm sending this email via that
>> > > connection).  I'll report what I find next.
>> > >
>> > > Thanks again for the help!
>> 
>> Sigh.... sorry for the top post again.  I'll now get a real email 
>> client.
> 
> So the connection remained super stable for a while, so I decided to
> tempt fate and suspend the laptop to see what would happen :).
> 
> [ 5994.143715] PM: suspend exit
> [ 5997.260351] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 5997.260353] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 5997.260356] ath11k_pci 0000:55:00.0: failed to enable dynamic bw: 
> -11
> [ 6000.332299] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6000.332303] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6000.332308] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6003.404365] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6003.404368] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6003.404373] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6016.204347] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6016.204351] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6016.204357] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6019.276319] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6019.276323] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6019.276329] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6031.052272] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6031.052275] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6031.052279] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6034.128257] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6034.128261] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6034.128265] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6039.500241] ath11k_pci 0000:55:00.0: qmi failed set mode request,
> mode: 4, err = -110
> [ 6039.500244] ath11k_pci 0000:55:00.0: qmi failed to send wlan mode 
> off
> 
> I was able to remove the ath11k module using rmmod -f , and then
> modprobe ath11k + atk11k_pci and the device was able to reassociate
> and bring the connection back up.

Please apply below to have a try:
https://patchwork.kernel.org/project/linux-wireless/patch/20201112062555.3335-1-cjhuang@codeaurora.org/

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Carl Huang]

On 2020-11-12 10:31, wi nk wrote:
> On Thu, Nov 12, 2020 at 2:11 AM wi nk <wink@technolu.st> wrote:
>> 
>> On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
>> >
>> > I've yet to see any instability after 45 minutes of exercising it, I
>> > do see a couple of messages that came out of the driver:
>> >
>> > [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>> > [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>> >
>> > then when it associates:
>> >
>> > [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>> > [   16.722636] wlp85s0: authenticated
>> > [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>> > [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>> > (capab=0x411 status=0 aid=8)
>> > [   16.738443] wlp85s0: associated
>> > [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
>> >
>> > The adapter is achieving around 500 mbps on my gigabit connection, my
>> > 2018 mbp sees around 650, so it's doing pretty well so far.
>> >
>> > Stefani - when you applied the patch that Kalle shared, which branch
>> > did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>> > I revert 7fef431be9c9 there is a small merge conflict I needed to
>> > resolve.  I wonder if either the starting branch, or your chosen
>> > resolution are related to the instability you see (or I'm just lucky
>> > so far! :)).
>> >
>> > On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
>> > >
>> > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
>> > > >
>> > > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
>> > > > >
>> > > > > The proof of concept patch for v5.10-rc2 is here:
>> > > > >
>> > > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@codeaurora.org/
>> > > > >
>> > > > > Hopefully it makes it possible to boot the firmware now. But this is
>> > > > > a
>> > > > > quick hack and most likely buggy, so keep your expectations low :)
>> > > > >
>> > > > > In case there are these warnings during firmware initialisation:
>> > > > >
>> > > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110
>> > > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110
>> > > > >
>> > > > > Try reverting this commit:
>> > > > >
>> > > > > 7fef431be9c9 mm/page_alloc: place pages to tail in
>> > > > > __free_pages_core()
>> > > > >
>> > > > > That's another issue which is debugged here:
>> > > > >
>> > > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html
>> > > > >
>> > > >
>> > > > Applying the patch and revert patch 7fef431be9c9 worked on the first
>> > > > glance.
>> > > >
>> > > > After a couple of minutes the connection get broken. The kernel log
>> > > > shows the following error:
>> > > >
>> > > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
>> > > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
>> > > > ath11k_pc
>> > > > i 0000:55:00.0: failed to enable PMF QOS: (-11
>> > > >
>> > > > It is also not possible to unload the ath11k_pci, rmmod will hang.
>> > > >
>> > > >
>> > >
>> > > I can confirm the same behavior as Stefani so far.  After applying the
>> > > patch, and reverting commit 7fef431be9c9, I am able to connect to a
>> > > network.  It hasn't disconnected yet (I'm sending this email via that
>> > > connection).  I'll report what I find next.
>> > >
>> > > Thanks again for the help!
>> 
>> Sigh.... sorry for the top post again.  I'll now get a real email 
>> client.
> 
> So the connection remained super stable for a while, so I decided to
> tempt fate and suspend the laptop to see what would happen :).
> 
> [ 5994.143715] PM: suspend exit
> [ 5997.260351] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 5997.260353] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 5997.260356] ath11k_pci 0000:55:00.0: failed to enable dynamic bw: 
> -11
> [ 6000.332299] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6000.332303] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6000.332308] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6003.404365] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6003.404368] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6003.404373] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6016.204347] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6016.204351] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6016.204357] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6019.276319] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6019.276323] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6019.276329] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6031.052272] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6031.052275] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6031.052279] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6034.128257] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> [ 6034.128261] ath11k_pci 0000:55:00.0: failed to send 
> WMI_PDEV_SET_PARAM cmd
> [ 6034.128265] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
> [ 6039.500241] ath11k_pci 0000:55:00.0: qmi failed set mode request,
> mode: 4, err = -110
> [ 6039.500244] ath11k_pci 0000:55:00.0: qmi failed to send wlan mode 
> off
> 
> I was able to remove the ath11k module using rmmod -f , and then
> modprobe ath11k + atk11k_pci and the device was able to reassociate
> and bring the connection back up.

Please apply below to have a try:
https://patchwork.kernel.org/project/linux-wireless/patch/20201112062555.3335-1-cjhuang@codeaurora.org/


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> I've yet to see any instability after 45 minutes of exercising it, I
> do see a couple of messages that came out of the driver:
> 
> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> 
> then when it associates:
> 
> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> [   16.722636] wlp85s0: authenticated
> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> (capab=0x411 status=0 aid=8)
> [   16.738443] wlp85s0: associated
> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> ready
> 
> The adapter is achieving around 500 mbps on my gigabit connection, my
> 2018 mbp sees around 650, so it's doing pretty well so far.
> 
> Stefani - when you applied the patch that Kalle shared, which branch
> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> I revert 7fef431be9c9 there is a small merge conflict I needed to
> resolve.  I wonder if either the starting branch, or your chosen
> resolution are related to the instability you see (or I'm just lucky
> so far! :)).
> 

I used the vanilla kernel tree 
https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
i applied the 

RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch

and reverted the patch 7fef431be9c9

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Stefani Seibold]

Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> I've yet to see any instability after 45 minutes of exercising it, I
> do see a couple of messages that came out of the driver:
> 
> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> 
> then when it associates:
> 
> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> [   16.722636] wlp85s0: authenticated
> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> (capab=0x411 status=0 aid=8)
> [   16.738443] wlp85s0: associated
> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> ready
> 
> The adapter is achieving around 500 mbps on my gigabit connection, my
> 2018 mbp sees around 650, so it's doing pretty well so far.
> 
> Stefani - when you applied the patch that Kalle shared, which branch
> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> I revert 7fef431be9c9 there is a small merge conflict I needed to
> resolve.  I wonder if either the starting branch, or your chosen
> resolution are related to the instability you see (or I'm just lucky
> so far! :)).
> 

I used the vanilla kernel tree 
https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
i applied the 

RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch

and reverted the patch 7fef431be9c9



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Stefani Seibold <stefani@seibold.net> writes:

> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
>> I've yet to see any instability after 45 minutes of exercising it, I
>> do see a couple of messages that came out of the driver:
>> 
>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>> 
>> then when it associates:
>> 
>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>> [   16.722636] wlp85s0: authenticated
>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>> (capab=0x411 status=0 aid=8)
>> [   16.738443] wlp85s0: associated
>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
>> ready
>> 
>> The adapter is achieving around 500 mbps on my gigabit connection, my
>> 2018 mbp sees around 650, so it's doing pretty well so far.
>> 
>> Stefani - when you applied the patch that Kalle shared, which branch
>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>> I revert 7fef431be9c9 there is a small merge conflict I needed to
>> resolve.  I wonder if either the starting branch, or your chosen
>> resolution are related to the instability you see (or I'm just lucky
>> so far! :)).
>> 
>
> I used the vanilla kernel tree 
> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> i applied the 
>
> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
>
> and reverted the patch 7fef431be9c9

I did also my testing on v5.10-rc2 and I recommend to use that as the
baseline when debuggin these ath11k problems. It helps to compare the
results if everyone have the same baseline.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

Stefani Seibold <stefani@seibold.net> writes:

> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
>> I've yet to see any instability after 45 minutes of exercising it, I
>> do see a couple of messages that came out of the driver:
>> 
>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>> 
>> then when it associates:
>> 
>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>> [   16.722636] wlp85s0: authenticated
>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>> (capab=0x411 status=0 aid=8)
>> [   16.738443] wlp85s0: associated
>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
>> ready
>> 
>> The adapter is achieving around 500 mbps on my gigabit connection, my
>> 2018 mbp sees around 650, so it's doing pretty well so far.
>> 
>> Stefani - when you applied the patch that Kalle shared, which branch
>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>> I revert 7fef431be9c9 there is a small merge conflict I needed to
>> resolve.  I wonder if either the starting branch, or your chosen
>> resolution are related to the instability you see (or I'm just lucky
>> so far! :)).
>> 
>
> I used the vanilla kernel tree 
> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> i applied the 
>
> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
>
> and reverted the patch 7fef431be9c9

I did also my testing on v5.10-rc2 and I recommend to use that as the
baseline when debuggin these ath11k problems. It helps to compare the
results if everyone have the same baseline.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Stefani Seibold <stefani@seibold.net> writes:
>
> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> >> I've yet to see any instability after 45 minutes of exercising it, I
> >> do see a couple of messages that came out of the driver:
> >>
> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >>
> >> then when it associates:
> >>
> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> >> [   16.722636] wlp85s0: authenticated
> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> >> (capab=0x411 status=0 aid=8)
> >> [   16.738443] wlp85s0: associated
> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> >> ready
> >>
> >> The adapter is achieving around 500 mbps on my gigabit connection, my
> >> 2018 mbp sees around 650, so it's doing pretty well so far.
> >>
> >> Stefani - when you applied the patch that Kalle shared, which branch
> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
> >> resolve.  I wonder if either the starting branch, or your chosen
> >> resolution are related to the instability you see (or I'm just lucky
> >> so far! :)).
> >>
> >
> > I used the vanilla kernel tree
> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> > i applied the
> >
> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> >
> > and reverted the patch 7fef431be9c9
>
> I did also my testing on v5.10-rc2 and I recommend to use that as the
> baseline when debuggin these ath11k problems. It helps to compare the
> results if everyone have the same baseline.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Absolutely, I'll rebuild to 5.10 later today and apply the same series
of patches and report back.  I'll also test out the patch on both
versions from Carl to fix resuming.  It stands to reason that we may
be seeing another regression between Stefani (5.10) and myself (5.9
bringup branch) as I don't see any disconnections or instability once
the interface is online.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Stefani Seibold <stefani@seibold.net> writes:
>
> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> >> I've yet to see any instability after 45 minutes of exercising it, I
> >> do see a couple of messages that came out of the driver:
> >>
> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >>
> >> then when it associates:
> >>
> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> >> [   16.722636] wlp85s0: authenticated
> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> >> (capab=0x411 status=0 aid=8)
> >> [   16.738443] wlp85s0: associated
> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> >> ready
> >>
> >> The adapter is achieving around 500 mbps on my gigabit connection, my
> >> 2018 mbp sees around 650, so it's doing pretty well so far.
> >>
> >> Stefani - when you applied the patch that Kalle shared, which branch
> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
> >> resolve.  I wonder if either the starting branch, or your chosen
> >> resolution are related to the instability you see (or I'm just lucky
> >> so far! :)).
> >>
> >
> > I used the vanilla kernel tree
> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> > i applied the
> >
> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> >
> > and reverted the patch 7fef431be9c9
>
> I did also my testing on v5.10-rc2 and I recommend to use that as the
> baseline when debuggin these ath11k problems. It helps to compare the
> results if everyone have the same baseline.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Absolutely, I'll rebuild to 5.10 later today and apply the same series
of patches and report back.  I'll also test out the patch on both
versions from Carl to fix resuming.  It stands to reason that we may
be seeing another regression between Stefani (5.10) and myself (5.9
bringup branch) as I don't see any disconnections or instability once
the interface is online.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

wi nk <wink@technolu.st> writes:

> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> Stefani Seibold <stefani@seibold.net> writes:
>>
>> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
>> >> I've yet to see any instability after 45 minutes of exercising it, I
>> >> do see a couple of messages that came out of the driver:
>> >>
>> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>> >>
>> >> then when it associates:
>> >>
>> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>> >> [   16.722636] wlp85s0: authenticated
>> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>> >> (capab=0x411 status=0 aid=8)
>> >> [   16.738443] wlp85s0: associated
>> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
>> >> ready
>> >>
>> >> The adapter is achieving around 500 mbps on my gigabit connection, my
>> >> 2018 mbp sees around 650, so it's doing pretty well so far.
>> >>
>> >> Stefani - when you applied the patch that Kalle shared, which branch
>> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
>> >> resolve.  I wonder if either the starting branch, or your chosen
>> >> resolution are related to the instability you see (or I'm just lucky
>> >> so far! :)).
>> >>
>> >
>> > I used the vanilla kernel tree
>> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
>> > i applied the
>> >
>> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
>> >
>> > and reverted the patch 7fef431be9c9
>>
>> I did also my testing on v5.10-rc2 and I recommend to use that as the
>> baseline when debuggin these ath11k problems. It helps to compare the
>> results if everyone have the same baseline.
>>
>> --
>> https://patchwork.kernel.org/project/linux-wireless/list/
>>
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>
> Absolutely, I'll rebuild to 5.10 later today and apply the same series
> of patches and report back.

Great, thanks.

> I'll also test out the patch on both versions from Carl to fix
> resuming. It stands to reason that we may be seeing another regression
> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> any disconnections or instability once the interface is online.

Yeah, there is something strange happening between v5.9 and v5.10 we
have not yet figured out. Most likely it has something to do with memory
allocations and DMA transfers failing, but no clear understanding yet.

But to keep things simple let's only discuss the MSI problem on this
thread, and discuss the timeouts in the another thread:

http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html

I'll include you and other reporters to that thread.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Kalle Valo]

wi nk <wink@technolu.st> writes:

> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>>
>> Stefani Seibold <stefani@seibold.net> writes:
>>
>> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
>> >> I've yet to see any instability after 45 minutes of exercising it, I
>> >> do see a couple of messages that came out of the driver:
>> >>
>> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>> >>
>> >> then when it associates:
>> >>
>> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>> >> [   16.722636] wlp85s0: authenticated
>> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>> >> (capab=0x411 status=0 aid=8)
>> >> [   16.738443] wlp85s0: associated
>> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
>> >> ready
>> >>
>> >> The adapter is achieving around 500 mbps on my gigabit connection, my
>> >> 2018 mbp sees around 650, so it's doing pretty well so far.
>> >>
>> >> Stefani - when you applied the patch that Kalle shared, which branch
>> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
>> >> resolve.  I wonder if either the starting branch, or your chosen
>> >> resolution are related to the instability you see (or I'm just lucky
>> >> so far! :)).
>> >>
>> >
>> > I used the vanilla kernel tree
>> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
>> > i applied the
>> >
>> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
>> >
>> > and reverted the patch 7fef431be9c9
>>
>> I did also my testing on v5.10-rc2 and I recommend to use that as the
>> baseline when debuggin these ath11k problems. It helps to compare the
>> results if everyone have the same baseline.
>>
>> --
>> https://patchwork.kernel.org/project/linux-wireless/list/
>>
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>
> Absolutely, I'll rebuild to 5.10 later today and apply the same series
> of patches and report back.

Great, thanks.

> I'll also test out the patch on both versions from Carl to fix
> resuming. It stands to reason that we may be seeing another regression
> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> any disconnections or instability once the interface is online.

Yeah, there is something strange happening between v5.9 and v5.10 we
have not yet figured out. Most likely it has something to do with memory
allocations and DMA transfers failing, but no clear understanding yet.

But to keep things simple let's only discuss the MSI problem on this
thread, and discuss the timeouts in the another thread:

http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html

I'll include you and other reporters to that thread.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> wi nk <wink@technolu.st> writes:
>
> > On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >>
> >> Stefani Seibold <stefani@seibold.net> writes:
> >>
> >> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> >> >> I've yet to see any instability after 45 minutes of exercising it, I
> >> >> do see a couple of messages that came out of the driver:
> >> >>
> >> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> >> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >> >>
> >> >> then when it associates:
> >> >>
> >> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> >> >> [   16.722636] wlp85s0: authenticated
> >> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> >> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> >> >> (capab=0x411 status=0 aid=8)
> >> >> [   16.738443] wlp85s0: associated
> >> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> >> >> ready
> >> >>
> >> >> The adapter is achieving around 500 mbps on my gigabit connection, my
> >> >> 2018 mbp sees around 650, so it's doing pretty well so far.
> >> >>
> >> >> Stefani - when you applied the patch that Kalle shared, which branch
> >> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> >> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
> >> >> resolve.  I wonder if either the starting branch, or your chosen
> >> >> resolution are related to the instability you see (or I'm just lucky
> >> >> so far! :)).
> >> >>
> >> >
> >> > I used the vanilla kernel tree
> >> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> >> > i applied the
> >> >
> >> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> >> >
> >> > and reverted the patch 7fef431be9c9
> >>
> >> I did also my testing on v5.10-rc2 and I recommend to use that as the
> >> baseline when debuggin these ath11k problems. It helps to compare the
> >> results if everyone have the same baseline.
> >>
> >> --
> >> https://patchwork.kernel.org/project/linux-wireless/list/
> >>
> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> >
> > Absolutely, I'll rebuild to 5.10 later today and apply the same series
> > of patches and report back.
>
> Great, thanks.
>
> > I'll also test out the patch on both versions from Carl to fix
> > resuming. It stands to reason that we may be seeing another regression
> > between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> > any disconnections or instability once the interface is online.
>
> Yeah, there is something strange happening between v5.9 and v5.10 we
> have not yet figured out. Most likely it has something to do with memory
> allocations and DMA transfers failing, but no clear understanding yet.
>
> But to keep things simple let's only discuss the MSI problem on this
> thread, and discuss the timeouts in the another thread:
>
> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
>
> I'll include you and other reporters to that thread.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
into anything usable with that configuration.  I'm running ubuntu so
its starting right into X and sometime between showing the available
users and me clicking the icon to login the machine freezes.  I can
see in the system tray that the wifi adapter is being activated and
appears to have associated with an AP, I just can't do much beyond
that as the keyboard backlight wakes up, but the caps lock key doesn't
work.  I see similar behavior with the 5.9 configuration, but after a
reboot or two I win whatever race is occuring.  With 5.10, I tried
maybe 10-15 times with 0 success.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> wi nk <wink@technolu.st> writes:
>
> > On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >>
> >> Stefani Seibold <stefani@seibold.net> writes:
> >>
> >> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> >> >> I've yet to see any instability after 45 minutes of exercising it, I
> >> >> do see a couple of messages that came out of the driver:
> >> >>
> >> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> >> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >> >>
> >> >> then when it associates:
> >> >>
> >> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> >> >> [   16.722636] wlp85s0: authenticated
> >> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> >> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> >> >> (capab=0x411 status=0 aid=8)
> >> >> [   16.738443] wlp85s0: associated
> >> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> >> >> ready
> >> >>
> >> >> The adapter is achieving around 500 mbps on my gigabit connection, my
> >> >> 2018 mbp sees around 650, so it's doing pretty well so far.
> >> >>
> >> >> Stefani - when you applied the patch that Kalle shared, which branch
> >> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> >> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
> >> >> resolve.  I wonder if either the starting branch, or your chosen
> >> >> resolution are related to the instability you see (or I'm just lucky
> >> >> so far! :)).
> >> >>
> >> >
> >> > I used the vanilla kernel tree
> >> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> >> > i applied the
> >> >
> >> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> >> >
> >> > and reverted the patch 7fef431be9c9
> >>
> >> I did also my testing on v5.10-rc2 and I recommend to use that as the
> >> baseline when debuggin these ath11k problems. It helps to compare the
> >> results if everyone have the same baseline.
> >>
> >> --
> >> https://patchwork.kernel.org/project/linux-wireless/list/
> >>
> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> >
> > Absolutely, I'll rebuild to 5.10 later today and apply the same series
> > of patches and report back.
>
> Great, thanks.
>
> > I'll also test out the patch on both versions from Carl to fix
> > resuming. It stands to reason that we may be seeing another regression
> > between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> > any disconnections or instability once the interface is online.
>
> Yeah, there is something strange happening between v5.9 and v5.10 we
> have not yet figured out. Most likely it has something to do with memory
> allocations and DMA transfers failing, but no clear understanding yet.
>
> But to keep things simple let's only discuss the MSI problem on this
> thread, and discuss the timeouts in the another thread:
>
> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
>
> I'll include you and other reporters to that thread.
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
into anything usable with that configuration.  I'm running ubuntu so
its starting right into X and sometime between showing the available
users and me clicking the icon to login the machine freezes.  I can
see in the system tray that the wifi adapter is being activated and
appears to have associated with an AP, I just can't do much beyond
that as the keyboard backlight wakes up, but the caps lock key doesn't
work.  I see similar behavior with the 5.9 configuration, but after a
reboot or two I win whatever race is occuring.  With 5.10, I tried
maybe 10-15 times with 0 success.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 4:44 PM wi nk <wink@technolu.st> wrote:
>
> On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > wi nk <wink@technolu.st> writes:
> >
> > > On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> > >>
> > >> Stefani Seibold <stefani@seibold.net> writes:
> > >>
> > >> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> > >> >> I've yet to see any instability after 45 minutes of exercising it, I
> > >> >> do see a couple of messages that came out of the driver:
> > >> >>
> > >> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > >> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> > >> >>
> > >> >> then when it associates:
> > >> >>
> > >> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > >> >> [   16.722636] wlp85s0: authenticated
> > >> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > >> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > >> >> (capab=0x411 status=0 aid=8)
> > >> >> [   16.738443] wlp85s0: associated
> > >> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> > >> >> ready
> > >> >>
> > >> >> The adapter is achieving around 500 mbps on my gigabit connection, my
> > >> >> 2018 mbp sees around 650, so it's doing pretty well so far.
> > >> >>
> > >> >> Stefani - when you applied the patch that Kalle shared, which branch
> > >> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> > >> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
> > >> >> resolve.  I wonder if either the starting branch, or your chosen
> > >> >> resolution are related to the instability you see (or I'm just lucky
> > >> >> so far! :)).
> > >> >>
> > >> >
> > >> > I used the vanilla kernel tree
> > >> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> > >> > i applied the
> > >> >
> > >> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> > >> >
> > >> > and reverted the patch 7fef431be9c9
> > >>
> > >> I did also my testing on v5.10-rc2 and I recommend to use that as the
> > >> baseline when debuggin these ath11k problems. It helps to compare the
> > >> results if everyone have the same baseline.
> > >>
> > >> --
> > >> https://patchwork.kernel.org/project/linux-wireless/list/
> > >>
> > >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > >
> > > Absolutely, I'll rebuild to 5.10 later today and apply the same series
> > > of patches and report back.
> >
> > Great, thanks.
> >
> > > I'll also test out the patch on both versions from Carl to fix
> > > resuming. It stands to reason that we may be seeing another regression
> > > between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> > > any disconnections or instability once the interface is online.
> >
> > Yeah, there is something strange happening between v5.9 and v5.10 we
> > have not yet figured out. Most likely it has something to do with memory
> > allocations and DMA transfers failing, but no clear understanding yet.
> >
> > But to keep things simple let's only discuss the MSI problem on this
> > thread, and discuss the timeouts in the another thread:
> >
> > http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
> >
> > I'll include you and other reporters to that thread.
> >
> > --
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>
> Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> into anything usable with that configuration.  I'm running ubuntu so
> its starting right into X and sometime between showing the available
> users and me clicking the icon to login the machine freezes.  I can
> see in the system tray that the wifi adapter is being activated and
> appears to have associated with an AP, I just can't do much beyond
> that as the keyboard backlight wakes up, but the caps lock key doesn't
> work.  I see similar behavior with the 5.9 configuration, but after a
> reboot or two I win whatever race is occuring.  With 5.10, I tried
> maybe 10-15 times with 0 success.

Kalle, what would be a useful next move for trying to hunt this?  It
seems I can't really test the single MSI patch on 5.10 since with the
patch (+ the reverted commit) the driver isn't stable enough for my
machine to stay running.  It seems your hunch is that this is related
to the issues in the other thread
(http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html)?
 I see the SOTA for debugging these things would be to use the kdump
tools and let the secondary kernel dump diagnostics for me.  Would
such logs be useful for you/this?

Thanks!

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Thu, Nov 12, 2020 at 4:44 PM wi nk <wink@technolu.st> wrote:
>
> On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >
> > wi nk <wink@technolu.st> writes:
> >
> > > On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> > >>
> > >> Stefani Seibold <stefani@seibold.net> writes:
> > >>
> > >> > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> > >> >> I've yet to see any instability after 45 minutes of exercising it, I
> > >> >> do see a couple of messages that came out of the driver:
> > >> >>
> > >> >> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > >> >> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> > >> >>
> > >> >> then when it associates:
> > >> >>
> > >> >> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > >> >> [   16.722636] wlp85s0: authenticated
> > >> >> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > >> >> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > >> >> (capab=0x411 status=0 aid=8)
> > >> >> [   16.738443] wlp85s0: associated
> > >> >> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> > >> >> ready
> > >> >>
> > >> >> The adapter is achieving around 500 mbps on my gigabit connection, my
> > >> >> 2018 mbp sees around 650, so it's doing pretty well so far.
> > >> >>
> > >> >> Stefani - when you applied the patch that Kalle shared, which branch
> > >> >> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> > >> >> I revert 7fef431be9c9 there is a small merge conflict I needed to
> > >> >> resolve.  I wonder if either the starting branch, or your chosen
> > >> >> resolution are related to the instability you see (or I'm just lucky
> > >> >> so far! :)).
> > >> >>
> > >> >
> > >> > I used the vanilla kernel tree
> > >> > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> > >> > i applied the
> > >> >
> > >> > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> > >> >
> > >> > and reverted the patch 7fef431be9c9
> > >>
> > >> I did also my testing on v5.10-rc2 and I recommend to use that as the
> > >> baseline when debuggin these ath11k problems. It helps to compare the
> > >> results if everyone have the same baseline.
> > >>
> > >> --
> > >> https://patchwork.kernel.org/project/linux-wireless/list/
> > >>
> > >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > >
> > > Absolutely, I'll rebuild to 5.10 later today and apply the same series
> > > of patches and report back.
> >
> > Great, thanks.
> >
> > > I'll also test out the patch on both versions from Carl to fix
> > > resuming. It stands to reason that we may be seeing another regression
> > > between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> > > any disconnections or instability once the interface is online.
> >
> > Yeah, there is something strange happening between v5.9 and v5.10 we
> > have not yet figured out. Most likely it has something to do with memory
> > allocations and DMA transfers failing, but no clear understanding yet.
> >
> > But to keep things simple let's only discuss the MSI problem on this
> > thread, and discuss the timeouts in the another thread:
> >
> > http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
> >
> > I'll include you and other reporters to that thread.
> >
> > --
> > https://patchwork.kernel.org/project/linux-wireless/list/
> >
> > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>
> Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> into anything usable with that configuration.  I'm running ubuntu so
> its starting right into X and sometime between showing the available
> users and me clicking the icon to login the machine freezes.  I can
> see in the system tray that the wifi adapter is being activated and
> appears to have associated with an AP, I just can't do much beyond
> that as the keyboard backlight wakes up, but the caps lock key doesn't
> work.  I see similar behavior with the 5.9 configuration, but after a
> reboot or two I win whatever race is occuring.  With 5.10, I tried
> maybe 10-15 times with 0 success.

Kalle, what would be a useful next move for trying to hunt this?  It
seems I can't really test the single MSI patch on 5.10 since with the
patch (+ the reverted commit) the driver isn't stable enough for my
machine to stay running.  It seems your hunch is that this is related
to the issues in the other thread
(http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html)?
 I see the SOTA for debugging these things would be to use the kdump
tools and let the secondary kernel dump diagnostics for me.  Would
such logs be useful for you/this?

Thanks!

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

Am 12.11.20 um 16:44 schrieb wi nk:
> On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>> wi nk <wink@technolu.st> writes:
>>
>>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>>>> Stefani Seibold <stefani@seibold.net> writes:
>>>>
>>>>> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
>>>>>> I've yet to see any instability after 45 minutes of exercising it, I
>>>>>> do see a couple of messages that came out of the driver:
>>>>>>
>>>>>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>>>>>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>>>>>>
>>>>>> then when it associates:
>>>>>>
>>>>>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>>>>>> [   16.722636] wlp85s0: authenticated
>>>>>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>>>>>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>>>>>> (capab=0x411 status=0 aid=8)
>>>>>> [   16.738443] wlp85s0: associated
>>>>>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
>>>>>> ready
>>>>>>
>>>>>> The adapter is achieving around 500 mbps on my gigabit connection, my
>>>>>> 2018 mbp sees around 650, so it's doing pretty well so far.
>>>>>>
>>>>>> Stefani - when you applied the patch that Kalle shared, which branch
>>>>>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>>>>>> I revert 7fef431be9c9 there is a small merge conflict I needed to
>>>>>> resolve.  I wonder if either the starting branch, or your chosen
>>>>>> resolution are related to the instability you see (or I'm just lucky
>>>>>> so far! :)).
>>>>>>
>>>>> I used the vanilla kernel tree
>>>>> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
>>>>> i applied the
>>>>>
>>>>> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
>>>>>
>>>>> and reverted the patch 7fef431be9c9
>>>> I did also my testing on v5.10-rc2 and I recommend to use that as the
>>>> baseline when debuggin these ath11k problems. It helps to compare the
>>>> results if everyone have the same baseline.
>>>>
>>>> --
>>>> https://patchwork.kernel.org/project/linux-wireless/list/
>>>>
>>>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>>> Absolutely, I'll rebuild to 5.10 later today and apply the same series
>>> of patches and report back.
>> Great, thanks.
>>
>>> I'll also test out the patch on both versions from Carl to fix
>>> resuming. It stands to reason that we may be seeing another regression
>>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
>>> any disconnections or instability once the interface is online.
>> Yeah, there is something strange happening between v5.9 and v5.10 we
>> have not yet figured out. Most likely it has something to do with memory
>> allocations and DMA transfers failing, but no clear understanding yet.
>>
>> But to keep things simple let's only discuss the MSI problem on this
>> thread, and discuss the timeouts in the another thread:
>>
>> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
>>
>> I'll include you and other reporters to that thread.
>>
>> --
>> https://patchwork.kernel.org/project/linux-wireless/list/
>>
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> into anything usable with that configuration.  I'm running ubuntu so
> its starting right into X and sometime between showing the available
> users and me clicking the icon to login the machine freezes.  I can
> see in the system tray that the wifi adapter is being activated and
> appears to have associated with an AP, I just can't do much beyond
> that as the keyboard backlight wakes up, but the caps lock key doesn't
> work.  I see similar behavior with the 5.9 configuration, but after a
> reboot or two I win whatever race is occuring.  With 5.10, I tried
> maybe 10-15 times with 0 success.

I can confirm this behavior on my configuration. I managed to login once 
and select the Wifi and connect to it. It seemed curiously enough be 
stable long enough to enter the Wifi passphrase. After the connection 
was established, the system hang and on each attempt to reboot into the 
graphical system it would freeze at some point (sometimes even before 
showing the login screen).

Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same 
behavior) with the patch applied, 7fef431be9c9 reverted and firmware 
downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Krause]

Am 12.11.20 um 16:44 schrieb wi nk:
> On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>> wi nk <wink@technolu.st> writes:
>>
>>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>>>> Stefani Seibold <stefani@seibold.net> writes:
>>>>
>>>>> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
>>>>>> I've yet to see any instability after 45 minutes of exercising it, I
>>>>>> do see a couple of messages that came out of the driver:
>>>>>>
>>>>>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
>>>>>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
>>>>>>
>>>>>> then when it associates:
>>>>>>
>>>>>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
>>>>>> [   16.722636] wlp85s0: authenticated
>>>>>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
>>>>>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
>>>>>> (capab=0x411 status=0 aid=8)
>>>>>> [   16.738443] wlp85s0: associated
>>>>>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
>>>>>> ready
>>>>>>
>>>>>> The adapter is achieving around 500 mbps on my gigabit connection, my
>>>>>> 2018 mbp sees around 650, so it's doing pretty well so far.
>>>>>>
>>>>>> Stefani - when you applied the patch that Kalle shared, which branch
>>>>>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
>>>>>> I revert 7fef431be9c9 there is a small merge conflict I needed to
>>>>>> resolve.  I wonder if either the starting branch, or your chosen
>>>>>> resolution are related to the instability you see (or I'm just lucky
>>>>>> so far! :)).
>>>>>>
>>>>> I used the vanilla kernel tree
>>>>> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
>>>>> i applied the
>>>>>
>>>>> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
>>>>>
>>>>> and reverted the patch 7fef431be9c9
>>>> I did also my testing on v5.10-rc2 and I recommend to use that as the
>>>> baseline when debuggin these ath11k problems. It helps to compare the
>>>> results if everyone have the same baseline.
>>>>
>>>> --
>>>> https://patchwork.kernel.org/project/linux-wireless/list/
>>>>
>>>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
>>> Absolutely, I'll rebuild to 5.10 later today and apply the same series
>>> of patches and report back.
>> Great, thanks.
>>
>>> I'll also test out the patch on both versions from Carl to fix
>>> resuming. It stands to reason that we may be seeing another regression
>>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
>>> any disconnections or instability once the interface is online.
>> Yeah, there is something strange happening between v5.9 and v5.10 we
>> have not yet figured out. Most likely it has something to do with memory
>> allocations and DMA transfers failing, but no clear understanding yet.
>>
>> But to keep things simple let's only discuss the MSI problem on this
>> thread, and discuss the timeouts in the another thread:
>>
>> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
>>
>> I'll include you and other reporters to that thread.
>>
>> --
>> https://patchwork.kernel.org/project/linux-wireless/list/
>>
>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> into anything usable with that configuration.  I'm running ubuntu so
> its starting right into X and sometime between showing the available
> users and me clicking the icon to login the machine freezes.  I can
> see in the system tray that the wifi adapter is being activated and
> appears to have associated with an AP, I just can't do much beyond
> that as the keyboard backlight wakes up, but the caps lock key doesn't
> work.  I see similar behavior with the 5.9 configuration, but after a
> reboot or two I win whatever race is occuring.  With 5.10, I tried
> maybe 10-15 times with 0 success.

I can confirm this behavior on my configuration. I managed to login once 
and select the Wifi and connect to it. It seemed curiously enough be 
stable long enough to enter the Wifi passphrase. After the connection 
was established, the system hang and on each attempt to reboot into the 
graphical system it would freeze at some point (sometimes even before 
showing the login screen).

Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same 
behavior) with the patch applied, 7fef431be9c9 reverted and firmware 
downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/.



-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Sun, Nov 15, 2020 at 2:30 PM Thomas Krause <thomaskrause@posteo.de> wrote:
>
>
> Am 12.11.20 um 16:44 schrieb wi nk:
> > On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >> wi nk <wink@technolu.st> writes:
> >>
> >>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >>>> Stefani Seibold <stefani@seibold.net> writes:
> >>>>
> >>>>> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> >>>>>> I've yet to see any instability after 45 minutes of exercising it, I
> >>>>>> do see a couple of messages that came out of the driver:
> >>>>>>
> >>>>>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> >>>>>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >>>>>>
> >>>>>> then when it associates:
> >>>>>>
> >>>>>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> >>>>>> [   16.722636] wlp85s0: authenticated
> >>>>>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> >>>>>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> >>>>>> (capab=0x411 status=0 aid=8)
> >>>>>> [   16.738443] wlp85s0: associated
> >>>>>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> >>>>>> ready
> >>>>>>
> >>>>>> The adapter is achieving around 500 mbps on my gigabit connection, my
> >>>>>> 2018 mbp sees around 650, so it's doing pretty well so far.
> >>>>>>
> >>>>>> Stefani - when you applied the patch that Kalle shared, which branch
> >>>>>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> >>>>>> I revert 7fef431be9c9 there is a small merge conflict I needed to
> >>>>>> resolve.  I wonder if either the starting branch, or your chosen
> >>>>>> resolution are related to the instability you see (or I'm just lucky
> >>>>>> so far! :)).
> >>>>>>
> >>>>> I used the vanilla kernel tree
> >>>>> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> >>>>> i applied the
> >>>>>
> >>>>> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> >>>>>
> >>>>> and reverted the patch 7fef431be9c9
> >>>> I did also my testing on v5.10-rc2 and I recommend to use that as the
> >>>> baseline when debuggin these ath11k problems. It helps to compare the
> >>>> results if everyone have the same baseline.
> >>>>
> >>>> --
> >>>> https://patchwork.kernel.org/project/linux-wireless/list/
> >>>>
> >>>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> >>> Absolutely, I'll rebuild to 5.10 later today and apply the same series
> >>> of patches and report back.
> >> Great, thanks.
> >>
> >>> I'll also test out the patch on both versions from Carl to fix
> >>> resuming. It stands to reason that we may be seeing another regression
> >>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> >>> any disconnections or instability once the interface is online.
> >> Yeah, there is something strange happening between v5.9 and v5.10 we
> >> have not yet figured out. Most likely it has something to do with memory
> >> allocations and DMA transfers failing, but no clear understanding yet.
> >>
> >> But to keep things simple let's only discuss the MSI problem on this
> >> thread, and discuss the timeouts in the another thread:
> >>
> >> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
> >>
> >> I'll include you and other reporters to that thread.
> >>
> >> --
> >> https://patchwork.kernel.org/project/linux-wireless/list/
> >>
> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> > applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> > into anything usable with that configuration.  I'm running ubuntu so
> > its starting right into X and sometime between showing the available
> > users and me clicking the icon to login the machine freezes.  I can
> > see in the system tray that the wifi adapter is being activated and
> > appears to have associated with an AP, I just can't do much beyond
> > that as the keyboard backlight wakes up, but the caps lock key doesn't
> > work.  I see similar behavior with the 5.9 configuration, but after a
> > reboot or two I win whatever race is occuring.  With 5.10, I tried
> > maybe 10-15 times with 0 success.
>
> I can confirm this behavior on my configuration. I managed to login once
> and select the Wifi and connect to it. It seemed curiously enough be
> stable long enough to enter the Wifi passphrase. After the connection
> was established, the system hang and on each attempt to reboot into the
> graphical system it would freeze at some point (sometimes even before
> showing the login screen).
>
> Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same
> behavior) with the patch applied, 7fef431be9c9 reverted and firmware
> downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/.
>
>

I did a bit more digging to see if I could find any new information,
I'm not sure I did but here's what I did / found.  I spent the time to
get a kdump kernel running and enabled, I was able to SysRq-C (both
via keyboard and echo c > /proc/sysrq-trigger) and generate a crash
dump.  Actually viewing them at the moment will require reverting a
couple of patches to printk to fix the file for the crash utility
(https://github.com/crash-utility/crash/issues/67), but right now
that's not super important since the mechanism isn't being triggered.
As reported here and by Mitchell, the adapter will work occasionally,
but more often it will hang the machine (I too tried 5.10-rc3 with no
noticable differences).  Whatever is causing the system to hang isn't
triggering the kdump kernel to take over and dump the vmcore.  I've
set watchdog=1 , nmi_watchdog=1, hung_task_panic=1, softlockup_panic=1
trying to convince the kernel to dump it's state during this.  I've
not been able to make it write a crash, it just sits 'hung'.  One
interesting observation that may be related, is that if the lockup
occurs during my login, I can actually see the system grind to a halt
over the course of a number of frames (the rendering of the login
animations starts to stutter/get really slow, then after a few frames
everything is frozen).  If something were spin locking/ed, I'd expect
the soft lockup panic to find it, but I don't know these mechanisms
well.

The only consistent behavior that I managed to create is that if the
wifi adapter / machine are in a 'working' state (ie: I can browse the
internet, etc) and I issue sysrq-c to crash the kernel and then let
the crash dump write and reboot the machine, once booted the adapter
is no longer seen by the kernel, and there are zero messages in dmesg
that match "ath11k".  The driver shows up in lsmod , but it reports
zero messages and it's like the adapter is completely invisible.  A
power off and back on of the machine will re-enter it into the
freezing/wifi working lottery.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Sun, Nov 15, 2020 at 2:30 PM Thomas Krause <thomaskrause@posteo.de> wrote:
>
>
> Am 12.11.20 um 16:44 schrieb wi nk:
> > On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >> wi nk <wink@technolu.st> writes:
> >>
> >>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> >>>> Stefani Seibold <stefani@seibold.net> writes:
> >>>>
> >>>>> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> >>>>>> I've yet to see any instability after 45 minutes of exercising it, I
> >>>>>> do see a couple of messages that came out of the driver:
> >>>>>>
> >>>>>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> >>>>>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >>>>>>
> >>>>>> then when it associates:
> >>>>>>
> >>>>>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> >>>>>> [   16.722636] wlp85s0: authenticated
> >>>>>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> >>>>>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> >>>>>> (capab=0x411 status=0 aid=8)
> >>>>>> [   16.738443] wlp85s0: associated
> >>>>>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> >>>>>> ready
> >>>>>>
> >>>>>> The adapter is achieving around 500 mbps on my gigabit connection, my
> >>>>>> 2018 mbp sees around 650, so it's doing pretty well so far.
> >>>>>>
> >>>>>> Stefani - when you applied the patch that Kalle shared, which branch
> >>>>>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> >>>>>> I revert 7fef431be9c9 there is a small merge conflict I needed to
> >>>>>> resolve.  I wonder if either the starting branch, or your chosen
> >>>>>> resolution are related to the instability you see (or I'm just lucky
> >>>>>> so far! :)).
> >>>>>>
> >>>>> I used the vanilla kernel tree
> >>>>> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> >>>>> i applied the
> >>>>>
> >>>>> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> >>>>>
> >>>>> and reverted the patch 7fef431be9c9
> >>>> I did also my testing on v5.10-rc2 and I recommend to use that as the
> >>>> baseline when debuggin these ath11k problems. It helps to compare the
> >>>> results if everyone have the same baseline.
> >>>>
> >>>> --
> >>>> https://patchwork.kernel.org/project/linux-wireless/list/
> >>>>
> >>>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> >>> Absolutely, I'll rebuild to 5.10 later today and apply the same series
> >>> of patches and report back.
> >> Great, thanks.
> >>
> >>> I'll also test out the patch on both versions from Carl to fix
> >>> resuming. It stands to reason that we may be seeing another regression
> >>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> >>> any disconnections or instability once the interface is online.
> >> Yeah, there is something strange happening between v5.9 and v5.10 we
> >> have not yet figured out. Most likely it has something to do with memory
> >> allocations and DMA transfers failing, but no clear understanding yet.
> >>
> >> But to keep things simple let's only discuss the MSI problem on this
> >> thread, and discuss the timeouts in the another thread:
> >>
> >> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
> >>
> >> I'll include you and other reporters to that thread.
> >>
> >> --
> >> https://patchwork.kernel.org/project/linux-wireless/list/
> >>
> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> > applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> > into anything usable with that configuration.  I'm running ubuntu so
> > its starting right into X and sometime between showing the available
> > users and me clicking the icon to login the machine freezes.  I can
> > see in the system tray that the wifi adapter is being activated and
> > appears to have associated with an AP, I just can't do much beyond
> > that as the keyboard backlight wakes up, but the caps lock key doesn't
> > work.  I see similar behavior with the 5.9 configuration, but after a
> > reboot or two I win whatever race is occuring.  With 5.10, I tried
> > maybe 10-15 times with 0 success.
>
> I can confirm this behavior on my configuration. I managed to login once
> and select the Wifi and connect to it. It seemed curiously enough be
> stable long enough to enter the Wifi passphrase. After the connection
> was established, the system hang and on each attempt to reboot into the
> graphical system it would freeze at some point (sometimes even before
> showing the login screen).
>
> Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same
> behavior) with the patch applied, 7fef431be9c9 reverted and firmware
> downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/.
>
>

I did a bit more digging to see if I could find any new information,
I'm not sure I did but here's what I did / found.  I spent the time to
get a kdump kernel running and enabled, I was able to SysRq-C (both
via keyboard and echo c > /proc/sysrq-trigger) and generate a crash
dump.  Actually viewing them at the moment will require reverting a
couple of patches to printk to fix the file for the crash utility
(https://github.com/crash-utility/crash/issues/67), but right now
that's not super important since the mechanism isn't being triggered.
As reported here and by Mitchell, the adapter will work occasionally,
but more often it will hang the machine (I too tried 5.10-rc3 with no
noticable differences).  Whatever is causing the system to hang isn't
triggering the kdump kernel to take over and dump the vmcore.  I've
set watchdog=1 , nmi_watchdog=1, hung_task_panic=1, softlockup_panic=1
trying to convince the kernel to dump it's state during this.  I've
not been able to make it write a crash, it just sits 'hung'.  One
interesting observation that may be related, is that if the lockup
occurs during my login, I can actually see the system grind to a halt
over the course of a number of frames (the rendering of the login
animations starts to stutter/get really slow, then after a few frames
everything is frozen).  If something were spin locking/ed, I'd expect
the soft lockup panic to find it, but I don't know these mechanisms
well.

The only consistent behavior that I managed to create is that if the
wifi adapter / machine are in a 'working' state (ie: I can browse the
internet, etc) and I issue sysrq-c to crash the kernel and then let
the crash dump write and reboot the machine, once booted the adapter
is no longer seen by the kernel, and there are zero messages in dmesg
that match "ath11k".  The driver shows up in lsmod , but it reports
zero messages and it's like the adapter is completely invisible.  A
power off and back on of the machine will re-enter it into the
freezing/wifi working lottery.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Sun, Nov 15, 2020 at 8:55 PM wi nk <wink@technolu.st> wrote:
>
> On Sun, Nov 15, 2020 at 2:30 PM Thomas Krause <thomaskrause@posteo.de> wrote:
> >
> >
> > Am 12.11.20 um 16:44 schrieb wi nk:
> > > On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> > >> wi nk <wink@technolu.st> writes:
> > >>
> > >>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> > >>>> Stefani Seibold <stefani@seibold.net> writes:
> > >>>>
> > >>>>> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> > >>>>>> I've yet to see any instability after 45 minutes of exercising it, I
> > >>>>>> do see a couple of messages that came out of the driver:
> > >>>>>>
> > >>>>>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > >>>>>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> > >>>>>>
> > >>>>>> then when it associates:
> > >>>>>>
> > >>>>>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > >>>>>> [   16.722636] wlp85s0: authenticated
> > >>>>>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > >>>>>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > >>>>>> (capab=0x411 status=0 aid=8)
> > >>>>>> [   16.738443] wlp85s0: associated
> > >>>>>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> > >>>>>> ready
> > >>>>>>
> > >>>>>> The adapter is achieving around 500 mbps on my gigabit connection, my
> > >>>>>> 2018 mbp sees around 650, so it's doing pretty well so far.
> > >>>>>>
> > >>>>>> Stefani - when you applied the patch that Kalle shared, which branch
> > >>>>>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> > >>>>>> I revert 7fef431be9c9 there is a small merge conflict I needed to
> > >>>>>> resolve.  I wonder if either the starting branch, or your chosen
> > >>>>>> resolution are related to the instability you see (or I'm just lucky
> > >>>>>> so far! :)).
> > >>>>>>
> > >>>>> I used the vanilla kernel tree
> > >>>>> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> > >>>>> i applied the
> > >>>>>
> > >>>>> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> > >>>>>
> > >>>>> and reverted the patch 7fef431be9c9
> > >>>> I did also my testing on v5.10-rc2 and I recommend to use that as the
> > >>>> baseline when debuggin these ath11k problems. It helps to compare the
> > >>>> results if everyone have the same baseline.
> > >>>>
> > >>>> --
> > >>>> https://patchwork.kernel.org/project/linux-wireless/list/
> > >>>>
> > >>>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > >>> Absolutely, I'll rebuild to 5.10 later today and apply the same series
> > >>> of patches and report back.
> > >> Great, thanks.
> > >>
> > >>> I'll also test out the patch on both versions from Carl to fix
> > >>> resuming. It stands to reason that we may be seeing another regression
> > >>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> > >>> any disconnections or instability once the interface is online.
> > >> Yeah, there is something strange happening between v5.9 and v5.10 we
> > >> have not yet figured out. Most likely it has something to do with memory
> > >> allocations and DMA transfers failing, but no clear understanding yet.
> > >>
> > >> But to keep things simple let's only discuss the MSI problem on this
> > >> thread, and discuss the timeouts in the another thread:
> > >>
> > >> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
> > >>
> > >> I'll include you and other reporters to that thread.
> > >>
> > >> --
> > >> https://patchwork.kernel.org/project/linux-wireless/list/
> > >>
> > >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > > Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> > > applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> > > into anything usable with that configuration.  I'm running ubuntu so
> > > its starting right into X and sometime between showing the available
> > > users and me clicking the icon to login the machine freezes.  I can
> > > see in the system tray that the wifi adapter is being activated and
> > > appears to have associated with an AP, I just can't do much beyond
> > > that as the keyboard backlight wakes up, but the caps lock key doesn't
> > > work.  I see similar behavior with the 5.9 configuration, but after a
> > > reboot or two I win whatever race is occuring.  With 5.10, I tried
> > > maybe 10-15 times with 0 success.
> >
> > I can confirm this behavior on my configuration. I managed to login once
> > and select the Wifi and connect to it. It seemed curiously enough be
> > stable long enough to enter the Wifi passphrase. After the connection
> > was established, the system hang and on each attempt to reboot into the
> > graphical system it would freeze at some point (sometimes even before
> > showing the login screen).
> >
> > Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same
> > behavior) with the patch applied, 7fef431be9c9 reverted and firmware
> > downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/.
> >
> >
>
> I did a bit more digging to see if I could find any new information,
> I'm not sure I did but here's what I did / found.  I spent the time to
> get a kdump kernel running and enabled, I was able to SysRq-C (both
> via keyboard and echo c > /proc/sysrq-trigger) and generate a crash
> dump.  Actually viewing them at the moment will require reverting a
> couple of patches to printk to fix the file for the crash utility
> (https://github.com/crash-utility/crash/issues/67), but right now
> that's not super important since the mechanism isn't being triggered.
> As reported here and by Mitchell, the adapter will work occasionally,
> but more often it will hang the machine (I too tried 5.10-rc3 with no
> noticable differences).  Whatever is causing the system to hang isn't
> triggering the kdump kernel to take over and dump the vmcore.  I've
> set watchdog=1 , nmi_watchdog=1, hung_task_panic=1, softlockup_panic=1
> trying to convince the kernel to dump it's state during this.  I've
> not been able to make it write a crash, it just sits 'hung'.  One
> interesting observation that may be related, is that if the lockup
> occurs during my login, I can actually see the system grind to a halt
> over the course of a number of frames (the rendering of the login
> animations starts to stutter/get really slow, then after a few frames
> everything is frozen).  If something were spin locking/ed, I'd expect
> the soft lockup panic to find it, but I don't know these mechanisms
> well.
>
> The only consistent behavior that I managed to create is that if the
> wifi adapter / machine are in a 'working' state (ie: I can browse the
> internet, etc) and I issue sysrq-c to crash the kernel and then let
> the crash dump write and reboot the machine, once booted the adapter
> is no longer seen by the kernel, and there are zero messages in dmesg
> that match "ath11k".  The driver shows up in lsmod , but it reports
> zero messages and it's like the adapter is completely invisible.  A
> power off and back on of the machine will re-enter it into the
> freezing/wifi working lottery.

Good evening all!  Just wanted to follow up as I think I've started to
uncover some of what's happening with the XPS and this driver.  So
since I can't get the kdump kernel to dump anything for me, I took a
bit more of a naive approach.  I blacklisted the modules (ath11k /
ath11k_pci) from modprobe so I could at least control when it was
loaded.  I managed to capture a series of crashes (in phone pics, but
I'll transcribe the relevant bits here) that seem to indicate some
kind of runaway / spin locked behavior.  In all but one case[*], both
the crash and the eventual working state, the driver completely
initialized successfully with messaging like this:

[   23.209335] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[   23.209404] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[   23.209421] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[   23.209502] ath11k_pci 0000:55:00.0: MSI vectors: 1
[   23.454227] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 0
[   23.454233] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
[   23.455810] ath11k_pci 0000:55:00.0: req mem_seg[0] 0x27d00000 524288 1
[   23.455814] ath11k_pci 0000:55:00.0: req mem_seg[1] 0x27d80000 524288 1
[   23.455816] ath11k_pci 0000:55:00.0: req mem_seg[2] 0x27e00000 524288 1
[   23.455817] ath11k_pci 0000:55:00.0: req mem_seg[3] 0x27e80000 294912 1
[   23.455819] ath11k_pci 0000:55:00.0: req mem_seg[4] 0x27f00000 524288 1
[   23.455820] ath11k_pci 0000:55:00.0: req mem_seg[5] 0x27f80000 524288 1
[   23.455822] ath11k_pci 0000:55:00.0: req mem_seg[6] 0x27800000 458752 1
[   23.455824] ath11k_pci 0000:55:00.0: req mem_seg[7] 0x27cc0000 131072 1
[   23.455825] ath11k_pci 0000:55:00.0: req mem_seg[8] 0x27880000 524288 4
[   23.455827] ath11k_pci 0000:55:00.0: req mem_seg[9] 0x27900000 360448 4
[   23.455829] ath11k_pci 0000:55:00.0: req mem_seg[10] 0x27ca4000 16384 1
[   23.466226] ath11k_pci 0000:55:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[   23.466230] ath11k_pci 0000:55:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[   23.677675] ath11k_pci 0000:55:00.0 wlp85s0: renamed from wlan0

So up until this point, everything is working without issues.
Everything seems to spiral out of control a couple of seconds later
when my system attempts to actually bring up the adapter.  In most of
the crash states I will see this:

[   31.286725] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
[   31.390187] wlp85s0: send auth to ec:08:6b:27:01:ea (try 2/3)
[   31.391928] wlp85s0: authenticated
[   31.394196] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
[   31.396513] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
(capab=0x411 status=0 aid=6)
[   31.407730] wlp85s0: associated
[   31.434354] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready

And then either somewhere in that pile of messages, or a second or two
after this my machine will start to stutter as I mentioned before, and
then it either hangs, or I see this message (I'm truncating the
timestamp):

[   35.xxxx ] sched: RT throttling activated

After that moment, the machine is unresponsive.  Sorry I can't seem to
extract this data other than screenshots from my phone at the moment,
you can see the dmesg output from 6 different hangs here:
https://github.com/w1nk/ath11k-debug

* - In the case where the driver didn't fully initialize successfully
and hung; during the initialization right after the "MSI vectors: %d"
printk, I started seeing these:

[ 77.xxx ] alloc_contig_range: [88d8e0, 88d8e9) PFNs busy

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Sun, Nov 15, 2020 at 8:55 PM wi nk <wink@technolu.st> wrote:
>
> On Sun, Nov 15, 2020 at 2:30 PM Thomas Krause <thomaskrause@posteo.de> wrote:
> >
> >
> > Am 12.11.20 um 16:44 schrieb wi nk:
> > > On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> > >> wi nk <wink@technolu.st> writes:
> > >>
> > >>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo <kvalo@codeaurora.org> wrote:
> > >>>> Stefani Seibold <stefani@seibold.net> writes:
> > >>>>
> > >>>>> Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk:
> > >>>>>> I've yet to see any instability after 45 minutes of exercising it, I
> > >>>>>> do see a couple of messages that came out of the driver:
> > >>>>>>
> > >>>>>> [    8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > >>>>>> [   11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> > >>>>>>
> > >>>>>> then when it associates:
> > >>>>>>
> > >>>>>> [   16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > >>>>>> [   16.722636] wlp85s0: authenticated
> > >>>>>> [   16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > >>>>>> [   16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > >>>>>> (capab=0x411 status=0 aid=8)
> > >>>>>> [   16.738443] wlp85s0: associated
> > >>>>>> [   16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes
> > >>>>>> ready
> > >>>>>>
> > >>>>>> The adapter is achieving around 500 mbps on my gigabit connection, my
> > >>>>>> 2018 mbp sees around 650, so it's doing pretty well so far.
> > >>>>>>
> > >>>>>> Stefani - when you applied the patch that Kalle shared, which branch
> > >>>>>> did you apply it to?  I applied it to ath11k-qca6390-bringup and when
> > >>>>>> I revert 7fef431be9c9 there is a small merge conflict I needed to
> > >>>>>> resolve.  I wonder if either the starting branch, or your chosen
> > >>>>>> resolution are related to the instability you see (or I'm just lucky
> > >>>>>> so far! :)).
> > >>>>>>
> > >>>>> I used the vanilla kernel tree
> > >>>>> https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this
> > >>>>> i applied the
> > >>>>>
> > >>>>> RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch
> > >>>>>
> > >>>>> and reverted the patch 7fef431be9c9
> > >>>> I did also my testing on v5.10-rc2 and I recommend to use that as the
> > >>>> baseline when debuggin these ath11k problems. It helps to compare the
> > >>>> results if everyone have the same baseline.
> > >>>>
> > >>>> --
> > >>>> https://patchwork.kernel.org/project/linux-wireless/list/
> > >>>>
> > >>>> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > >>> Absolutely, I'll rebuild to 5.10 later today and apply the same series
> > >>> of patches and report back.
> > >> Great, thanks.
> > >>
> > >>> I'll also test out the patch on both versions from Carl to fix
> > >>> resuming. It stands to reason that we may be seeing another regression
> > >>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see
> > >>> any disconnections or instability once the interface is online.
> > >> Yeah, there is something strange happening between v5.9 and v5.10 we
> > >> have not yet figured out. Most likely it has something to do with memory
> > >> allocations and DMA transfers failing, but no clear understanding yet.
> > >>
> > >> But to keep things simple let's only discuss the MSI problem on this
> > >> thread, and discuss the timeouts in the another thread:
> > >>
> > >> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html
> > >>
> > >> I'll include you and other reporters to that thread.
> > >>
> > >> --
> > >> https://patchwork.kernel.org/project/linux-wireless/list/
> > >>
> > >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
> > > Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch
> > > applied and 7fef431be9c9 reverted.  I can't get my machine to  boot
> > > into anything usable with that configuration.  I'm running ubuntu so
> > > its starting right into X and sometime between showing the available
> > > users and me clicking the icon to login the machine freezes.  I can
> > > see in the system tray that the wifi adapter is being activated and
> > > appears to have associated with an AP, I just can't do much beyond
> > > that as the keyboard backlight wakes up, but the caps lock key doesn't
> > > work.  I see similar behavior with the 5.9 configuration, but after a
> > > reboot or two I win whatever race is occuring.  With 5.10, I tried
> > > maybe 10-15 times with 0 success.
> >
> > I can confirm this behavior on my configuration. I managed to login once
> > and select the Wifi and connect to it. It seemed curiously enough be
> > stable long enough to enter the Wifi passphrase. After the connection
> > was established, the system hang and on each attempt to reboot into the
> > graphical system it would freeze at some point (sometimes even before
> > showing the login screen).
> >
> > Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same
> > behavior) with the patch applied, 7fef431be9c9 reverted and firmware
> > downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/.
> >
> >
>
> I did a bit more digging to see if I could find any new information,
> I'm not sure I did but here's what I did / found.  I spent the time to
> get a kdump kernel running and enabled, I was able to SysRq-C (both
> via keyboard and echo c > /proc/sysrq-trigger) and generate a crash
> dump.  Actually viewing them at the moment will require reverting a
> couple of patches to printk to fix the file for the crash utility
> (https://github.com/crash-utility/crash/issues/67), but right now
> that's not super important since the mechanism isn't being triggered.
> As reported here and by Mitchell, the adapter will work occasionally,
> but more often it will hang the machine (I too tried 5.10-rc3 with no
> noticable differences).  Whatever is causing the system to hang isn't
> triggering the kdump kernel to take over and dump the vmcore.  I've
> set watchdog=1 , nmi_watchdog=1, hung_task_panic=1, softlockup_panic=1
> trying to convince the kernel to dump it's state during this.  I've
> not been able to make it write a crash, it just sits 'hung'.  One
> interesting observation that may be related, is that if the lockup
> occurs during my login, I can actually see the system grind to a halt
> over the course of a number of frames (the rendering of the login
> animations starts to stutter/get really slow, then after a few frames
> everything is frozen).  If something were spin locking/ed, I'd expect
> the soft lockup panic to find it, but I don't know these mechanisms
> well.
>
> The only consistent behavior that I managed to create is that if the
> wifi adapter / machine are in a 'working' state (ie: I can browse the
> internet, etc) and I issue sysrq-c to crash the kernel and then let
> the crash dump write and reboot the machine, once booted the adapter
> is no longer seen by the kernel, and there are zero messages in dmesg
> that match "ath11k".  The driver shows up in lsmod , but it reports
> zero messages and it's like the adapter is completely invisible.  A
> power off and back on of the machine will re-enter it into the
> freezing/wifi working lottery.

Good evening all!  Just wanted to follow up as I think I've started to
uncover some of what's happening with the XPS and this driver.  So
since I can't get the kdump kernel to dump anything for me, I took a
bit more of a naive approach.  I blacklisted the modules (ath11k /
ath11k_pci) from modprobe so I could at least control when it was
loaded.  I managed to capture a series of crashes (in phone pics, but
I'll transcribe the relevant bits here) that seem to indicate some
kind of runaway / spin locked behavior.  In all but one case[*], both
the crash and the eventual working state, the driver completely
initialized successfully with messaging like this:

[   23.209335] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is
experimental!
[   23.209404] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem
0x8e300000-0x8e3fffff 64bit]
[   23.209421] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002)
[   23.209502] ath11k_pci 0000:55:00.0: MSI vectors: 1
[   23.454227] ath11k_pci 0000:55:00.0: Respond mem req failed,
result: 1, err: 0
[   23.454233] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22
[   23.455810] ath11k_pci 0000:55:00.0: req mem_seg[0] 0x27d00000 524288 1
[   23.455814] ath11k_pci 0000:55:00.0: req mem_seg[1] 0x27d80000 524288 1
[   23.455816] ath11k_pci 0000:55:00.0: req mem_seg[2] 0x27e00000 524288 1
[   23.455817] ath11k_pci 0000:55:00.0: req mem_seg[3] 0x27e80000 294912 1
[   23.455819] ath11k_pci 0000:55:00.0: req mem_seg[4] 0x27f00000 524288 1
[   23.455820] ath11k_pci 0000:55:00.0: req mem_seg[5] 0x27f80000 524288 1
[   23.455822] ath11k_pci 0000:55:00.0: req mem_seg[6] 0x27800000 458752 1
[   23.455824] ath11k_pci 0000:55:00.0: req mem_seg[7] 0x27cc0000 131072 1
[   23.455825] ath11k_pci 0000:55:00.0: req mem_seg[8] 0x27880000 524288 4
[   23.455827] ath11k_pci 0000:55:00.0: req mem_seg[9] 0x27900000 360448 4
[   23.455829] ath11k_pci 0000:55:00.0: req mem_seg[10] 0x27ca4000 16384 1
[   23.466226] ath11k_pci 0000:55:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[   23.466230] ath11k_pci 0000:55:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id
[   23.677675] ath11k_pci 0000:55:00.0 wlp85s0: renamed from wlan0

So up until this point, everything is working without issues.
Everything seems to spiral out of control a couple of seconds later
when my system attempts to actually bring up the adapter.  In most of
the crash states I will see this:

[   31.286725] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
[   31.390187] wlp85s0: send auth to ec:08:6b:27:01:ea (try 2/3)
[   31.391928] wlp85s0: authenticated
[   31.394196] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
[   31.396513] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
(capab=0x411 status=0 aid=6)
[   31.407730] wlp85s0: associated
[   31.434354] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready

And then either somewhere in that pile of messages, or a second or two
after this my machine will start to stutter as I mentioned before, and
then it either hangs, or I see this message (I'm truncating the
timestamp):

[   35.xxxx ] sched: RT throttling activated

After that moment, the machine is unresponsive.  Sorry I can't seem to
extract this data other than screenshots from my phone at the moment,
you can see the dmesg output from 6 different hangs here:
https://github.com/w1nk/ath11k-debug

* - In the case where the driver didn't fully initialize successfully
and hung; during the initialization right after the "MSI vectors: %d"
printk, I started seeing these:

[ 77.xxx ] alloc_contig_range: [88d8e0, 88d8e9) PFNs busy

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Tue, Nov 17 2020 at 16:49, wi nk wrote:
> On Sun, Nov 15, 2020 at 8:55 PM wi nk <wink@technolu.st> wrote:
> So up until this point, everything is working without issues.
> Everything seems to spiral out of control a couple of seconds later
> when my system attempts to actually bring up the adapter.  In most of
> the crash states I will see this:
>
> [   31.286725] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> [   31.390187] wlp85s0: send auth to ec:08:6b:27:01:ea (try 2/3)
> [   31.391928] wlp85s0: authenticated
> [   31.394196] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> [   31.396513] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> (capab=0x411 status=0 aid=6)
> [   31.407730] wlp85s0: associated
> [   31.434354] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
>
> And then either somewhere in that pile of messages, or a second or two
> after this my machine will start to stutter as I mentioned before, and
> then it either hangs, or I see this message (I'm truncating the
> timestamp):
>
> [   35.xxxx ] sched: RT throttling activated

As this driver uses threaded interrupts, this looks like an interrupt
storm and the interrupt thread consumes the CPU fully. The RT throttler
limits the RT runtime of it which allows other tasks make some
progress. That's what you observe as stutter.

You can apply the hack below so the irq thread(s) run in the SCHED_OTHER
class which prevents them from monopolizing the CPU. That might make the
problem simpler to debug.

Thanks,

        tglx
---
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index c460e0496006..8473ecacac7a 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1320,7 +1320,7 @@ setup_irq_thread(struct irqaction *new, unsigned int irq, bool secondary)
 	if (IS_ERR(t))
 		return PTR_ERR(t);
 
-	sched_set_fifo(t);
+	//sched_set_fifo(t);
 
 	/*
 	 * We keep the reference to the task struct even if

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[Thomas Gleixner]

On Tue, Nov 17 2020 at 16:49, wi nk wrote:
> On Sun, Nov 15, 2020 at 8:55 PM wi nk <wink@technolu.st> wrote:
> So up until this point, everything is working without issues.
> Everything seems to spiral out of control a couple of seconds later
> when my system attempts to actually bring up the adapter.  In most of
> the crash states I will see this:
>
> [   31.286725] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> [   31.390187] wlp85s0: send auth to ec:08:6b:27:01:ea (try 2/3)
> [   31.391928] wlp85s0: authenticated
> [   31.394196] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> [   31.396513] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> (capab=0x411 status=0 aid=6)
> [   31.407730] wlp85s0: associated
> [   31.434354] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
>
> And then either somewhere in that pile of messages, or a second or two
> after this my machine will start to stutter as I mentioned before, and
> then it either hangs, or I see this message (I'm truncating the
> timestamp):
>
> [   35.xxxx ] sched: RT throttling activated

As this driver uses threaded interrupts, this looks like an interrupt
storm and the interrupt thread consumes the CPU fully. The RT throttler
limits the RT runtime of it which allows other tasks make some
progress. That's what you observe as stutter.

You can apply the hack below so the irq thread(s) run in the SCHED_OTHER
class which prevents them from monopolizing the CPU. That might make the
problem simpler to debug.

Thanks,

        tglx
---
diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index c460e0496006..8473ecacac7a 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -1320,7 +1320,7 @@ setup_irq_thread(struct irqaction *new, unsigned int irq, bool secondary)
 	if (IS_ERR(t))
 		return PTR_ERR(t);
 
-	sched_set_fifo(t);
+	//sched_set_fifo(t);
 
 	/*
 	 * We keep the reference to the task struct even if

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Tue, Nov 17, 2020 at 9:59 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Tue, Nov 17 2020 at 16:49, wi nk wrote:
> > On Sun, Nov 15, 2020 at 8:55 PM wi nk <wink@technolu.st> wrote:
> > So up until this point, everything is working without issues.
> > Everything seems to spiral out of control a couple of seconds later
> > when my system attempts to actually bring up the adapter.  In most of
> > the crash states I will see this:
> >
> > [   31.286725] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > [   31.390187] wlp85s0: send auth to ec:08:6b:27:01:ea (try 2/3)
> > [   31.391928] wlp85s0: authenticated
> > [   31.394196] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > [   31.396513] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > (capab=0x411 status=0 aid=6)
> > [   31.407730] wlp85s0: associated
> > [   31.434354] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
> >
> > And then either somewhere in that pile of messages, or a second or two
> > after this my machine will start to stutter as I mentioned before, and
> > then it either hangs, or I see this message (I'm truncating the
> > timestamp):
> >
> > [   35.xxxx ] sched: RT throttling activated
>
> As this driver uses threaded interrupts, this looks like an interrupt
> storm and the interrupt thread consumes the CPU fully. The RT throttler
> limits the RT runtime of it which allows other tasks make some
> progress. That's what you observe as stutter.
>
> You can apply the hack below so the irq thread(s) run in the SCHED_OTHER
> class which prevents them from monopolizing the CPU. That might make the
> problem simpler to debug.
>
> Thanks,
>
>         tglx
> ---
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index c460e0496006..8473ecacac7a 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -1320,7 +1320,7 @@ setup_irq_thread(struct irqaction *new, unsigned int irq, bool secondary)
>         if (IS_ERR(t))
>                 return PTR_ERR(t);
>
> -       sched_set_fifo(t);
> +       //sched_set_fifo(t);
>
>         /*
>          * We keep the reference to the task struct even if

I was able to apply this patch and play a little bit.  Unfortunately,
whatever is still going on is mostly the same.  It seems this patch
extends the 'stuttering' I see a little bit, but the end result is
still an unresponsive machine.  I didn't get tons of time to play yet,
so the extra time may make it possible to finally get sysrq-c issued
and get a vmcore dump.  I also tried to replicate a google android
patch I found to basically BUG() on the rt throttling activating
(https://groups.google.com/a/chromium.org/g/chromium-os-reviews/c/NDyPucYrvRY)
but that path hasn't activated for me since I booted it.  I'll
hopefully have a chance again this evening.

Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310

[wi nk]

On Tue, Nov 17, 2020 at 9:59 PM Thomas Gleixner <tglx@linutronix.de> wrote:
>
> On Tue, Nov 17 2020 at 16:49, wi nk wrote:
> > On Sun, Nov 15, 2020 at 8:55 PM wi nk <wink@technolu.st> wrote:
> > So up until this point, everything is working without issues.
> > Everything seems to spiral out of control a couple of seconds later
> > when my system attempts to actually bring up the adapter.  In most of
> > the crash states I will see this:
> >
> > [   31.286725] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > [   31.390187] wlp85s0: send auth to ec:08:6b:27:01:ea (try 2/3)
> > [   31.391928] wlp85s0: authenticated
> > [   31.394196] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > [   31.396513] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > (capab=0x411 status=0 aid=6)
> > [   31.407730] wlp85s0: associated
> > [   31.434354] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
> >
> > And then either somewhere in that pile of messages, or a second or two
> > after this my machine will start to stutter as I mentioned before, and
> > then it either hangs, or I see this message (I'm truncating the
> > timestamp):
> >
> > [   35.xxxx ] sched: RT throttling activated
>
> As this driver uses threaded interrupts, this looks like an interrupt
> storm and the interrupt thread consumes the CPU fully. The RT throttler
> limits the RT runtime of it which allows other tasks make some
> progress. That's what you observe as stutter.
>
> You can apply the hack below so the irq thread(s) run in the SCHED_OTHER
> class which prevents them from monopolizing the CPU. That might make the
> problem simpler to debug.
>
> Thanks,
>
>         tglx
> ---
> diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
> index c460e0496006..8473ecacac7a 100644
> --- a/kernel/irq/manage.c
> +++ b/kernel/irq/manage.c
> @@ -1320,7 +1320,7 @@ setup_irq_thread(struct irqaction *new, unsigned int irq, bool secondary)
>         if (IS_ERR(t))
>                 return PTR_ERR(t);
>
> -       sched_set_fifo(t);
> +       //sched_set_fifo(t);
>
>         /*
>          * We keep the reference to the task struct even if

I was able to apply this patch and play a little bit.  Unfortunately,
whatever is still going on is mostly the same.  It seems this patch
extends the 'stuttering' I see a little bit, but the end result is
still an unresponsive machine.  I didn't get tons of time to play yet,
so the extra time may make it possible to finally get sysrq-c issued
and get a vmcore dump.  I also tried to replicate a google android
patch I found to basically BUG() on the rt throttling activating
(https://groups.google.com/a/chromium.org/g/chromium-os-reviews/c/NDyPucYrvRY)
but that path hasn't activated for me since I booted it.  I'll
hopefully have a chance again this evening.

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k