Re: Swsusp hanging the second time

From: Oliver Neukum
Date: Wed Jan 05 2005 - 16:08:18 EST


Am Dienstag, 4. Januar 2005 12:08 schrieb Pavel Machek:
> Hi!
>
> > there's a second, more serious problem with this laptop. It hangs the
> > in the second swsusp cycle on suspension.
> > As before 2.6.10, i386/UP/no highmem.
> > On the screen I get the two messages "radeonfb resumed!" and
> > "setting latency" superimposed and it hangs forever. This is a regression
> > the previous user commented: "It worked under 2.6.6"
>
> Unless it was on the same hardware/config, I'd not call it regression.
>
> Anyway two suspends in the row seem to work here on 2.6.10+my
> patches. I suspect you have problems with some more obscure driver.
>
> Can you try going with minimal driver config to see if it is
> reproducible? If it is broken even with minimal drivers, I'll try
> harder to reproduce it here (but I believe it will just go away).

The culprit seems to be EHCI, possibly together with UHCI only.

0000:00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 03) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems: Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1200 [size=32]

0000:00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 03) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems: Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1220 [size=32]

0000:00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 03) (prog-if 00 [UHCI])
Subsystem: Toshiba America Info Systems: Unknown device ff10
Flags: bus master, medium devsel, latency 0, IRQ 11
I/O ports at 1240 [size=32]

0000:00:1d.7 USB Controller: Intel Corp. 82801DB USB2 (rev 03) (prog-if 20 [EHCI])
Subsystem: Toshiba America Info Systems: Unknown device ff10
Flags: bus master, medium devsel, latency 0
Memory at f4000000 (32-bit, non-prefetchable)
Capabilities: <available only to root>

Regards
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/