From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@osdl.org>,
David Brownell <david-b@pacbell.net>,
LKML <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>,
Greg KH <greg@kroah.com>
Subject: Re: 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices
Date: Mon, 18 Sep 2006 22:51:08 +0200 [thread overview]
Message-ID: <200609182251.09318.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0609181102450.7192-100000@iolanthe.rowland.org>
On Monday, 18 September 2006 17:07, Alan Stern wrote:
> On Mon, 18 Sep 2006, Rafael J. Wysocki wrote:
>
> > > Actually, the problem is ohci_hcd doesn't seem to recognize devices plugged
> > > into the USB ports.
> > >
> > > For example, if I unplug and replug a mouse (that worked before unplugging),
> > > it doesn't work any more. I have to reload ohci_hcd to make it work again.
> > >
> > > This is 100% reproducible and occurs on the two boxes above.
> >
> > I have carried out a binary search and found that the problem is caused by
> >
> > gregkh-usb-usbcore-remove-usb_suspend_root_hub.patch
>
> Tell me, what happens if you leave that patch installed, and you use
> the patch I sent last week (the one that removes a chunk of code from
> ohci-hub.c), and you also set CONFIG_USB_SUSPEND?
The problem continues to happen.
Moreover, if I revert the above patch and apply the patch removing code
from ohci-hub.c, the problem reappears.
> I think the real underlying problem here is that David's implementation of
> root-hub suspend in ohci-hcd is incompatible with the overall scheme I've
> been working on. In the end I'll probably have to rewrite the ohci-hcd
> code.
Well, at this point I can only help you by testing some code. ;-)
Seriously, if you have any new patches to test, please let me know.
Greetings,
Rafael
--
You never change things by fighting the existing reality.
R. Buckminster Fuller
next prev parent reply other threads:[~2006-09-18 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 22:13 2.6.18-rc6-mm2 (-mm1): ohci_hcd sometimes does not initialize properly on x86_64 Rafael J. Wysocki
2006-09-16 8:13 ` 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices Rafael J. Wysocki
2006-09-18 6:27 ` Rafael J. Wysocki
2006-09-18 6:50 ` Jan De Luyck
2006-09-18 11:20 ` Rafael J. Wysocki
2006-09-18 15:07 ` Alan Stern
2006-09-18 20:51 ` Rafael J. Wysocki [this message]
2006-09-18 21:16 ` Alan Stern
2006-09-19 0:04 ` 2.6.18-rc6-mm2 (-mm1): ohci_hcd sometimes does not initialize properly on x86_64 David Brownell
2006-09-19 20:53 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200609182251.09318.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®