Skip to contentSkip to conversation

usb fails to suspend [was: mmotm 2009-06-05-16-19]

DISCUSSION Jiri Slaby 3 participants 7 messages Jun 6, 2009 – Jun 7, 2009

lore
Share & tools
lore

Jiri Slaby

author
#0 lore raw

Hi,

there is a suspend regression somewhere between mmotm 2009-05-17-12-15 and 2009-06-05-16-19:
hcd_pci_suspend_noirq(): pci_prepare_to_sleep+0x0/0x80 returns -19 pci_pm_suspend_noirq(): hcd_pci_suspend_noirq+0x0/0xb0 returns -19 pm_noirq_op(): pci_pm_suspend_noirq+0x0/0x180 returns -19
PM: Device 0000:00:1d.2 failed to suspend late: error -19

$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3
        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 D routed to IRQ 16
        Region 4: I/O ports at d000 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
00: 86 80 36 29 05 00 90 02 02 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d0 00 00 00 00 00 00 00 00 00 00 86 80 36 29
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 04 00 00

Any ideas?

#1 lore raw
Quoted 28 lines · Jiri Slaby

Hi,

there is a suspend regression somewhere between mmotm 2009-05-17-12-15 and 2009-06-05-16-19:
hcd_pci_suspend_noirq(): pci_prepare_to_sleep+0x0/0x80 returns -19 pci_pm_suspend_noirq(): hcd_pci_suspend_noirq+0x0/0xb0 returns -19 pm_noirq_op(): pci_pm_suspend_noirq+0x0/0x180 returns -19
PM: Device 0000:00:1d.2 failed to suspend late: error -19

$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3
        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 D routed to IRQ 16
        Region 4: I/O ports at d000 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
00: 86 80 36 29 05 00 90 02 02 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d0 00 00 00 00 00 00 00 00 00 00 86 80 36 29
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 04 00 00
Quoted 1 line

Any ideas?

Not really. Is it -mm-only or is the mainline affected too?

author
#2 lore raw
Quoted 29 lines · Rafael J. Wysocki
Quoted 28 lines · Jiri Slaby

Hi,

there is a suspend regression somewhere between mmotm 2009-05-17-12-15 and 2009-06-05-16-19:
hcd_pci_suspend_noirq(): pci_prepare_to_sleep+0x0/0x80 returns -19 pci_pm_suspend_noirq(): hcd_pci_suspend_noirq+0x0/0xb0 returns -19 pm_noirq_op(): pci_pm_suspend_noirq+0x0/0x180 returns -19
PM: Device 0000:00:1d.2 failed to suspend late: error -19

$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3
        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 D routed to IRQ 16
        Region 4: I/O ports at d000 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
00: 86 80 36 29 05 00 90 02 02 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d0 00 00 00 00 00 00 00 00 00 00 86 80 36 29
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 04 00 00
Quoted 3 lines
Quoted 1 line

Any ideas?

Not really. Is it -mm-only or is the mainline affected too?

Yup, only an -mm thing. I reverted these two:
pci-pm-read-device-power-state-from-register-after-updating-it.patch pci-pm-read-device-power-state-from-register-after-updating-it-update.patch and it works now :).

#3 lore raw
Quoted 30 lines · Jiri Slaby
Quoted 29 lines · Rafael J. Wysocki
Quoted 28 lines · Jiri Slaby

Hi,

there is a suspend regression somewhere between mmotm 2009-05-17-12-15 and 2009-06-05-16-19:
hcd_pci_suspend_noirq(): pci_prepare_to_sleep+0x0/0x80 returns -19 pci_pm_suspend_noirq(): hcd_pci_suspend_noirq+0x0/0xb0 returns -19 pm_noirq_op(): pci_pm_suspend_noirq+0x0/0x180 returns -19
PM: Device 0000:00:1d.2 failed to suspend late: error -19

$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3
        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 D routed to IRQ 16
        Region 4: I/O ports at d000 [size=32]
        Capabilities: [50] Vendor Specific Information <?>
        Kernel driver in use: uhci_hcd
00: 86 80 36 29 05 00 90 02 02 00 03 0c 00 00 00 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 01 d0 00 00 00 00 00 00 00 00 00 00 86 80 36 29
30: 00 00 00 00 50 00 00 00 00 00 00 00 05 04 00 00
Quoted 8 lines
Quoted 3 lines
Quoted 1 line

Any ideas?

Not really. Is it -mm-only or is the mainline affected too?

Yup, only an -mm thing. I reverted these two:
pci-pm-read-device-power-state-from-register-after-updating-it.patch pci-pm-read-device-power-state-from-register-after-updating-it-update.patch and it works now :).

OK, thanks.

Andrew, can you drop these two patches from -mm please?

Best,
Rafael

#4 lore raw
In reply to Jiri Slaby

Hi Jiri,

Quoted 7 lines

there is a suspend regression somewhere between mmotm 2009-05-17-12-15 and 2009-06-05-16-19:
hcd_pci_suspend_noirq(): pci_prepare_to_sleep+0x0/0x80 returns -19 pci_pm_suspend_noirq(): hcd_pci_suspend_noirq+0x0/0xb0 returns -19 pm_noirq_op(): pci_pm_suspend_noirq+0x0/0x180 returns -19
PM: Device 0000:00:1d.2 failed to suspend late: error -19

Quoted 5 lines
$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3

what is the likelihood that you have an Intel WiMAX card in this system? There is a suspend issue when i2400m_usb is loaded. Took me a while to figure that one out. It suspends/resumes fine for the first time after reboot, but on resume it deadlocks the whole USB subsystem.

Regards

Marcel

author
#5 lore raw
Quoted 1 line · Marcel Holtmann

Hi Jiri,

Hi.

Quoted 7 lines
Quoted 5 lines
$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3

what is the likelihood that you have an Intel WiMAX card in this system?

None :) -- I have no such card in the system.

Quoted 3 lines

There is a suspend issue when i2400m_usb is loaded. Took me a while to figure that one out. It suspends/resumes fine for the first time after reboot, but on resume it deadlocks the whole USB subsystem.

This was the first time I tried to suspend.

#6 lore raw

Hi Jiri,

Quoted 8 lines
Quoted 7 lines
Quoted 5 lines
$ lspci -xxvvs 0000:00:1d.2
00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: Intel Corporation 82801I (ICH9 Family) USB UHCI
Controller #3

what is the likelihood that you have an Intel WiMAX card in this system?

Quoted 7 lines

None :) -- I have no such card in the system.

Quoted 3 lines

There is a suspend issue when i2400m_usb is loaded. Took me a while to figure that one out. It suspends/resumes fine for the first time after reboot, but on resume it deadlocks the whole USB subsystem.

This was the first time I tried to suspend.

then it is not that issue and I have no idea what happens.

Regards

Marcel