public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zilvinas Valinskas <zilvinas@gemtek.lt>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.5-rc2, hotplug and ohci-hcd issue
Date: Mon, 22 Mar 2004 10:32:51 +0200	[thread overview]
Message-ID: <1079944371.2064.1.camel@swoop.gemtek.lt> (raw)
In-Reply-To: <405CC7EC.9030205@gmx.de>

If you boot without any plugged USB devices and later on plug in USB
devices things are working as expected. Something fishy about hotplug
and perhaps in particular when OHCI and EHCI are initialized with USB
devices connected.

BR 

On Sun, 2004-03-21 at 00:38, Prakash K. Cheemplavam wrote:
> Prakash K. Cheemplavam wrote:
> 
> > I maybe found something: I compiled "force module unloading" into 
> > kernel, and now it doesn't seem to hang, though I don't understand why 
> > it should make a difference, as nothing is forced. I have to test a bit 
> > more.
> 
> I was wrong, above doesn't work. It still hangs. I don't know how to 
> circumvent it. Something seems to be broken.
> 
> Prakash
> 


  reply	other threads:[~2004-03-22  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-20  3:39 Linux 2.6.5-rc2 Linus Torvalds
2004-03-20 10:21 ` Linux 2.6.5-rc2, hotplug and ohci-hcd issue Prakash K. Cheemplavam
2004-03-20 10:32   ` Prakash K. Cheemplavam
2004-03-20 13:23   ` Zilvinas Valinskas
2004-03-20 19:12     ` Prakash K. Cheemplavam
2004-03-20 22:38       ` Prakash K. Cheemplavam
2004-03-22  8:32         ` Zilvinas Valinskas [this message]
2004-03-24 19:24           ` Prakash K. Cheemplavam
2004-03-20 12:18 ` [patch] 2.6.5-rc2: fix scsi_transport_spi.c with gcc 2.95 Adrian Bunk
2004-03-20 13:43   ` James Bottomley
2004-03-21 20:21 ` Linux 2.6.5-rc2 (compile stats) John Cherry
2004-03-22 21:38   ` Jos Hulzink

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=1079944371.2064.1.camel@swoop.gemtek.lt \
    --to=zilvinas@gemtek.lt \
    --cc=PrakashKC@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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