Alto consumo de energia do driver de rede Atheros Communications

4

Estou executando o Ubuntu 16.04 em um Dell XPS 15 9560.

Kernel:

Linux XPS 4.9.10-040910-genérico # 201702141931 SMP Qua 15 de fevereiro 00:33:24 UTC 2017 x86_64 x86_64 x86_64 GNU / Linux

No powertop, mostra que dois dispositivos têm um consumo de energia muito alto. Tudo está definido como "bom" no powertop.

11,9 W 100,0% Dispositivo USB: usb-device-0cf3-e300

7,02 W 100,0% Dispositivo de rádio: ath10k_pci

Às vezes, o aparelho de rádio cai, mas o outro é muito alto. 23,4 W 100,0% dispositivo USB: usb-device-0cf3-e300

O dispositivo USB no lsusb mostra que é do dispositivo 002 do barramento 001: ID 0cf3: e300 Atheros Communications, Inc.

A Atheros Communications, Inc parece fabricar drivers sem fio. O dispositivo de rádio ath10k é o driver upstream link e link

Poderia ser um problema de driver ou algo assim? Porque eu não acho que sejam números razoáveis de consumo de energia.

Acredito que esta é a placa Wireless do sudo lspci -vvnn:

02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535]
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 136
Region 0: Memory at ed200000 (64-bit, non-prefetchable) [size=2M]
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/8 Maskable+ 64bit-
    Address: fee00418  Data: 0000
    Masking: 000000fe  Pending: 00000000
Capabilities: [70] Express (v2) Endpoint, MSI 00
    DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
        ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
        MaxPayload 256 bytes, MaxReadReq 512 bytes
    DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <64us
        ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
    LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
        ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
    DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR+, OBFF Via message
    DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
    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: -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- NonFatalErr-
    CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
    AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
Capabilities: [148 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: [168 v1] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178 v1] Latency Tolerance Reporting
    Max snoop latency: 3145728ns
    Max no snoop latency: 3145728ns
Capabilities: [180 v1] L1 PM Substates
    L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
          PortCommonModeRestoreTime=50us PortTPowerOnTime=10us
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci
    
por Jakkra 16.02.2017 / 12:30

1 resposta

1

É impossível medir o consumo de energia dos componentes do laptop. O que o powertop lhe diz são apenas estimativas aproximadas. Muitas vezes eles estão longe, como no seu caso. Por favor, ignore-os.

    
por linrunner 23.02.2017 / 18:50