Am Donnerstag, 6. Januar 2005 18:19 schrieb David Brownell:
> On Thursday 06 January 2005 6:54 am, Alan Stern wrote:
> > On Wed, 5 Jan 2005, David Brownell wrote:
> >
> > > > > Is EHCI being resumed before UHCI -- or afterwards?
> > > >
> > > > EHCI was resumed after UHCI.
> > >
> > > I suspect it'd work better the other way around.
> >
> > Maybe it would, maybe not.
>
> I'd like to see Oliver try the experiment (implies a
> modular kernel). And besides, you asked for ideas,
> on the assumption that it was the port routing (to
> EHCI or UHCI) that was going wrong ...
#!/bin/bash
/etc/rc.d/smpppd stop
/etc/rc.d/network stop
rmmod ipw2100
rmmod ehci_hcd
sync
echo -n "4" >/proc/acpi/sleep
modprobe ehci_hcd
modprobe ipw2100
/etc/rc.d/network start
/etc/rc.d/smpppd start
Ehci is modular, uhci is not.
> We saw the /proc/debug/uhci/0000:00:1d:0 output; what
> does the corresponding /sys/class/usb_host/.../registers
> information (for EHCI) show, before and after suspend?
Before:
[EMAIL PROTECTED]:~> cat /sys/class/usb_host/usb4/registers
bus pci, device 0000:00:1d.7 (driver 26 Oct 2004)
EHCI 1.00, hcd state 1
structural params 0x00103206
capability params 0x00006871
status 0008 FLR
command 010001 (park)=0 ithresh=1 period=1024 RUN
intrenable 37 IAA FATAL PCD ERR INT
uframe 2fc2
port 1 status 003002 POWER OWNER sig=se0 CSC
port 2 status 001000 POWER sig=se0
port 3 status 001000 POWER sig=se0
port 4 status 001000 POWER sig=se0
port 5 status 001000 POWER sig=se0
port 6 status 001000 POWER sig=se0
irq normal 0 err 0 reclaim 0 (lost 0)
complete 0 unlink 0
> > In any case this isn't under our control.
> > Devices are resumed in the same order they were detected initially. I
> > think the only way to solve this problem is to find a workaround for EHCI
> > controllers that act weird when they resume.
>
> The problem could well be in UHCI instead, or BIOS.
> There are at least several dozen different configurations
> to test here, after all ... ;)
>
> Oliver, you're using some kind of BIOS suspend right?
Plain old swsusp.
> That is, /sys/power/disk says "platform" not "shutdown".
> Does swsusp behave correctly in the "shutdown" case?
> That's roughly the difference between an ACPI S4bios
> and an ACPI S4 suspend sequence. Both need testing.
I'll test platform, too.
Regards
Oliver
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
