lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Thu, 28 Dec 2006 08:36:21 +0000
From:	Pavel Machek <pavel@....cz>
To:	linux-kernel@...r.kernel.org
Subject: Re: How to interpret PM_TRACE output

Hi!

> > > 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
> 
> Yes, it works with sky2. Yes, the USB device that is reported to fail
> by PM_TRACE shares the interrupt with eth0, which is sk98lin (see my
> original posting in this thread).
> 
> > exactly in the usb does it fail?
> 
> I don't know, all I have is the PM_TRACE output.
> 
> Meanwhile, tried to remove uhci_hcd before suspend, and wakeup works
> then.

Send a nice bug report to usb people, then...
							Pavel
-- 
Thanks for all the (sleeping) penguins.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ