linux-kernel - Re: [linux-usb-devel] 2.6.18-rc6-mm1 (-mm2): ohci resume problem

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 Sep 2006 17:55:06 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Andrew Morton <akpm@...l.org>, Mattia Dongili <malattia@...ux.it>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	USB development list <linux-usb-devel@...ts.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.18-rc6-mm1 (-mm2): ohci resume problem

On Wed, 13 Sep 2006, Rafael J. Wysocki wrote:

> > Try this patch instead.  It looks for problems occurring a little earlier 
> > in the call chain.
> 
> I've applied both patches at a time (I hope they don't conflict).
> 
> The dmesg output is attached.

The dmesg output shows the root-hub device state is set wrong.

I have to leave now, so I can't give you another patch to try.  You can 
experiment as follows...

Look in drivers/usb/host/ehci-pci.c, at ehci_pci_resume().  The part of 
interest is everything following the "restart:" statement label.

Try adding some ehci_dbg() lines in there (copy the form of the line just
after restart:).  We want to follow the value of
hcd->self.root_hub->state.  Initially it should be equal to
USB_STATE_SUSPENDED (= 8), and it shouldn't change.  But somewhere it is
getting set to USB_STATE_CONFIGURED (= 7).  I don't know where, but almost 
certainly somewhere in this routine.  If you can find out where that 
happens, I'd appreciate it.

Alan Stern

-
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/