Re: How to interpret PM_TRACE output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

> > > I tried PM_TRACE to find the driver that breaks resume from suspend.
> > > I got working resume until I switched to the sk98lin driver
> > > (because sky2 doesn't support wake on LAN). That's why I was quite sure that
> > > sk98lin is the culprit, but I tried PM_TRACE anymay.
> > 
> > See Doc*/power/*.
> 
> There is a nice mixture of documentation about swusp, video stuff,
> developer documentation, and one short paragraph about PM_TRACE that
> tells me nothing new. Could you point me to the documentation part that
> you are referring to, and that tells me what to do if PM_TRACE shows
> the usb device but the failure only occurs when I load the sk98lin
> driver?

Hmmm, so it fails somewhere in usb only if sk98lin is loaded? If you
unload it again, resume works? Are usb interrupts shared? Where
exactly in the usb does it fail?
-- 
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux