Hmm.
As I mentioned in a previous message, I had spoken too
soon when I sent the message reporting that the membase
was different than the value shown in the "bogus controller
address" errors. In fact, when I collected values for a
complete cycle (boot, suspend, resume), the membase and
error messages showed the same values.
I think I have already sent the debugging info you
requested. Please let me know if you need more/different
info.
Thanks,
Miles
On Fri, 16 Jun 2000, David Brownell wrote:
> > Looks like we have forgotten to switch off the timer-driven
> > interrupt callback of the virtual root hub in suspend mode.
> > I will look at this on the weekend.
> >
> > Roman
>
>
> Actually, since Miles provided separate information about the
> controller's real address (0xc5882000) which isn't the one
> provided through the URB (0xc5880000), it's clear that some
> pointer in the "urb->bus->dev->hcpriv" sequence used to get
> that pointer (hcpriv) became bogus ...
>
> Miles, can you recompile with full OHCI debugging and send
> us the kernel logs for a "modprobe usb-ohci; apm -s ;
> rmmod usb-ohci" sequence? Does this reproduce with no
> devices, or is it something that happens when lots of them
> are connected at the same time?
>
> I can imagine some code paths that could have those failure
> modes, but getting more information about the actual ones in
> use would save a lot of time!
>
> - Dave
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
