public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan De Luyck <ml_linuxkernel_20060528@kcore.org>
To: linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>, Andrew Morton <akpm@osdl.org>,
	David Brownell <david-b@pacbell.net>,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	Greg KH <greg@kroah.com>, Alan Stern <stern@rowland.harvard.edu>
Subject: Re: 2.6.18-rc6-mm2 (-mm1): ohci_hcd does not recognize new devices
Date: Mon, 18 Sep 2006 08:50:43 +0200	[thread overview]
Message-ID: <200609180850.43815.ml_linuxkernel_20060528@kcore.org> (raw)
In-Reply-To: <200609180827.53626.rjw@sisk.pl>

On Monday 18 September 2006 08:27, Rafael J. Wysocki wrote:
> On Saturday, 16 September 2006 10:13, Rafael J. Wysocki wrote:
> > On Saturday, 16 September 2006 00:13, Rafael J. Wysocki wrote:
> > > It looks like the ohci_hcd driver sometimes has problems with the
> > > initialization (eg. USB mouse doesn't work after a fresh boot and
> > > reloading of the driver helps).
> > >
> > > I have observed this on two different x86_64 boxes (HPC 6325, Asus
> > > L5D), but it is not readily reproducible.  Anyway I've got a dmesg
> > > output from a failing case which is attached.
> >
> > 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 can confirm this behaviour. I've also seen that sometimes my USB 
keyboard/mouse doesn't work after booting up. Reloading the module solves the 
problem.

This is on an amd64 box, ABIT kn9-sli, nForce 550.

This is with 2.6.17.13.

> I have carried out a binary search and found that the problem is caused by
>
> gregkh-usb-usbcore-remove-usb_suspend_root_hub.patch

Will this work against 2.6.17.13 vanilla?

Thanks,

Jan
-- 
QOTD:
	"If I could walk that way, I wouldn't need the cologne, now would I?"

  reply	other threads:[~2006-09-18  6:51 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 [this message]
2006-09-18 11:20       ` Rafael J. Wysocki
2006-09-18 15:07     ` Alan Stern
2006-09-18 20:51       ` Rafael J. Wysocki
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=200609180850.43815.ml_linuxkernel_20060528@kcore.org \
    --to=ml_linuxkernel_20060528@kcore.org \
    --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=rjw@sisk.pl \
    --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