Bjørn Mork <bj...@mork.no> writes:
>
> Jul 26 12:20:43 nemi kernel: [ 493.812266] iwlwifi 0000:03:00.0: Refused to
> change power state, currently in D3
> Jul 26 12:20:43 nemi kernel: [ 493.812331] iwlwifi 0000:03:00.0:
> pci_resource_len = 0x00002000
> Jul 26 12:20:43 nemi kernel: [ 493.812335] iwlwifi 0000:03:00.0:
> pci_resource_base = ffffc900055a4000
> Jul 26 12:20:43 nemi kernel: [ 493.812339] iwlwifi 0000:03:00.0: HW Revision
> ID = 0x0
> Jul 26 12:20:43 nemi kernel: [ 493.812350] iwlwifi 0000:03:00.0:
> pci_enable_msi failed(0Xffffffea)
[..]
> Jul 26 12:20:43 nemi kernel: [ 493.832013] ---[ end trace fcaaf916dd43b7ca
> ]---
> Jul 26 12:20:43 nemi kernel: [ 493.864785] iwlwifi 0000:03:00.0: bad
> EEPROM/OTP signature, type=OTP, EEPROM_GP=0x00000007
> Jul 26 12:20:43 nemi kernel: [ 493.864791] iwlwifi 0000:03:00.0: EEPROM not
> found, EEPROM_GP=0xffffffff
> Jul 26 12:20:43 nemi kernel: [ 493.864795] iwlwifi 0000:03:00.0: Unable to
> init EEPROM
Doing
echo on >/sys/bus/pci/devices/0000:00:1c.1/power/control
to force the brigde on and then unload/reload driver "fixes" this issue.
But I believe it is safe to say that this does not work as it should. I
assume the bridge should have been automatically woken up first here?
And why the odd autosuspend output? The Wifi device and bridge PM caps
look compatible to my untrained eye, and should make both D3hot and
D3cold supported ?:
Capabilities: [c8] 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: [a0] 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-
Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
