Hi, > For your next test, get the system into this resume-stuck state and press > Alt-SysRq-T to get a stack trace in the system log. The entry for the > khubd process should be very enlightening.
23:14:16 khubd S C0356548 0 1866 1 1977 899 (L-TLB) 23:14:16 dcb7ff8c 00000046 dbf10ae0 c0356548 0000000a 00000001 00000006 0000ffc0 23:14:16 93b7ab2a 0000000a dbf10ae0 0000390a 93b7b08d 0000000a dcb0f17c dcb7ffc0 23:14:16 ffffe000 dcb7e000 dcb7ffcc e0064a9d 00004000 00000000 dcb7e000 00000000 23:14:16 Call Trace: 23:14:16 [<e0064a9d>] hub_thread+0x9d/0x130 [usbcore] 23:14:16 [<c0128e10>] autoremove_wake_function+0x0/0x60 23:14:16 [<c0102f72>] ret_from_fork+0x6/0x14 23:14:16 [<c0128e10>] autoremove_wake_function+0x0/0x60 23:14:16 [<e0064a00>] hub_thread+0x0/0x130 [usbcore] 23:14:16 [<c01012ad>] kernel_thread_helper+0x5/0x18 This didn't look very special to me. I should have made more clear that the suspend_hc()/resume_hc() messages appear only once per interrupt. Anyway I've added a dump_stack() to suspend_hc() and to resume_hc(), may be this reveals more information. "hi11 uhci_hcd" is printed after the uhci interrupt handler returns with IRQ_HANDLED: 23:26:27 [<c0330380>] unknown_bootoption+0x0/0x1e0 23:26:28 uhci_hcd 0000:00:1d.0: suspend_hc 23:26:28 [<e03b201a>] suspend_hc+0x4a/0x80 [uhci_hcd] 23:26:28 [<e03b22c7>] hc_state_transitions+0xa7/0xb0 [uhci_hcd] 23:26:28 [<e03b1af8>] stall_callback+0xf8/0x140 [uhci_hcd] 23:26:28 [<c01efbfb>] acpi_processor_idle+0xdd/0x1de 23:26:28 [<e03b1a00>] stall_callback+0x0/0x140 [uhci_hcd] 23:26:28 [<c011e25a>] run_timer_softirq+0xaa/0x170 23:26:28 [<c011a382>] __do_softirq+0x42/0x90 23:26:28 [<c011a3f7>] do_softirq+0x27/0x30 23:26:28 [<c0104cfe>] do_IRQ+0x1e/0x30 23:26:28 [<c01031ce>] common_interrupt+0x1a/0x20 23:26:28 [<c01efbfb>] acpi_processor_idle+0xdd/0x1de 23:26:28 [<c01010dd>] cpu_idle+0x2d/0x40 23:26:28 [<c03307ef>] start_kernel+0x14f/0x170 23:26:28 [<c0330380>] unknown_bootoption+0x0/0x1e0 23:26:28 hi11 uhci_hcd 23:26:28 uhci_hcd 0000:00:1d.0: wakeup_hc 23:26:28 [<e03b22a3>] hc_state_transitions+0x83/0xb0 [uhci_hcd] 23:26:28 [<e03b1af8>] stall_callback+0xf8/0x140 [uhci_hcd] 23:26:28 [<c01efc4d>] acpi_processor_idle+0x12f/0x1de 23:26:28 [<e03b1a00>] stall_callback+0x0/0x140 [uhci_hcd] 23:26:28 [<c011e25a>] run_timer_softirq+0xaa/0x170 23:26:28 [<c011a382>] __do_softirq+0x42/0x90 23:26:28 [<c011a3f7>] do_softirq+0x27/0x30 23:26:28 [<c0104cfe>] do_IRQ+0x1e/0x30 23:26:28 [<c01031ce>] common_interrupt+0x1a/0x20 23:26:28 [<c01efc4d>] acpi_processor_idle+0x12f/0x1de 23:26:28 [<c01010dd>] cpu_idle+0x2d/0x40 23:26:28 [<c03307ef>] start_kernel+0x14f/0x170 23:26:28 [<c0330380>] unknown_bootoption+0x0/0x1e0 23:26:28 [<e03b22a3>] hc_state_transitions+0x83/0xb0 [uhci_hcd] 23:26:28 [<e03b1af8>] stall_callback+0xf8/0x140 [uhci_hcd] 23:26:28 [<c01efc4d>] acpi_processor_idle+0x12f/0x1de 23:26:28 [<e03b1a00>] stall_callback+0x0/0x140 [uhci_hcd] 23:26:28 [<c011e25a>] run_timer_softirq+0xaa/0x170 23:26:28 [<c011a382>] __do_softirq+0x42/0x90 23:26:28 [<c011a3f7>] do_softirq+0x27/0x30 23:26:28 [<c0104cfe>] do_IRQ+0x1e/0x30 23:26:28 [<c01031ce>] common_interrupt+0x1a/0x20 23:26:28 [<c01efc4d>] acpi_processor_idle+0x12f/0x1de [snip] > Let's see what your next test shows. For the moment, bear in mind that > USB support for suspend/resume is still fairly primitive. No problem. However I think the feature is very useful for linux, so I bother driver maintainer by driver maintainer, with patches if I can ;-) Stefan ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
