Re: [linux-usb-devel] OHCI problems with suspend/resume

[Pavel Machek <pavel@suse.cz>]

Hi!

> >Can you try echo 4 > /proc/acpi/sleep? echo 3 breaks it, too, but that
> >is little harder to set up.
> 
> I usually test with "apm -s" ... since I've yet to come up with
> an ACPI configuration that works properly.  IRQ misconfiguration
> for USB is still a blocking issue for many people (not just me).

Actually, you do not need acpi to test swsusp (echo 4 >
/proc/acpi/sleep is the easiest way, but there's syscall to do the
same).

> Going through ACPI would certainly explain some breakage; it's
> been sufficiently troublesome with USB that it's not gotten much
> testing at all.  I happened to notice this morning that ACPI's
> USB IRQ problems are one of the longest-standing open 2.6 bugs:
> http://bugme.osdl.org/show_bug.cgi?id=10 ... and it's now been
> migrated into the 2.4.22-pre series (sigh).

That's okay, ACPI in 2.4.22-pre just replaced older ACPI and
even-more-buggy ACPI in 2.4.21.

> Could you try reproducing this failure using just APM?  I could
> believe there's a generic PM issue (I've been expecting 2.6-test
> to eventually start shaking PM out); but given the amount of
> trouble ACPI has caused, we should first rule that factor out.

ACPI is not much involved. If you want, I can (attempt to) make swsusp
work on your machine....

> >Actually, as PCI interrupts are shared, I do not find that too
> >surprising. 
> 
> I do.  Sharing is irrelevant.  If it's been cleaned up, then
> the IRQ should no longer be bound to that device.

ohci_stop() does not seem to unregister IRQ...

> >That would be good. I definitely had another failure path, where it
> >did not tell me that hcd is no K.O...
> 
> I'll likely submit that to Greg in the next few days, cc you.

Okay, thanx.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]