public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] Input update for 2.6.17
Date: Mon, 26 Jun 2006 23:37:34 -0700	[thread overview]
Message-ID: <20060627063734.GA28135@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606262247040.3927@g5.osdl.org>

On Mon, Jun 26, 2006 at 11:13:19PM -0700, Linus Torvalds wrote:
> 
> 
> On Mon, 26 Jun 2006, Dmitry Torokhov wrote:
> > 
> > Please pull from:
> > 
> > ????????git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git
> 
> I think this (or USB) may have problems.
> 
> I get a spinlock debugging fault with the current kernel on one of my 
> machines at bootup, with the trace-back being:
> 
>   Process: khubd
> 	spin_bug
> 	_raw_spin_lock
> 	_spin_lock
> 	__mutex_lock_slowpath
> 	mutex_lock
> 	input_unregister_device
> 	hidinput_disconnect
> 	hid_disconnect
> 	usb_unbind_interface
> 	__device_release
> 	device_release_driver
> 	bus_remove_device
> 	device_del
> 	usb_disable_device
> 	usb_disconnect
> 	hub_thread
> 	kthread
> 
> it happens pretty early after bootup, but I don't know what triggers that 
> usb disconnect (it may be the hand-over from UHCI->EHCI. Greg? Does that 
> make sense?)

Yes, if you have the UHCI driver loaded first, then when EHCI is loaded,
it disconnects everything on the bus and re-enumerates it.

But EHCI is built into the kernel first, before UHCI, so unless you are
using modules, nothing should be getting disconnected at boot time.

I really doubt you are using modules, so I don't know why it would be
disconnected.  What does the kernel log show right before this happened?
Any chance to enable CONFIG_USB_DEBUG?

thanks,

greg k-h

  reply	other threads:[~2006-06-27  6:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26  6:35 [git pull] Input update for 2.6.17 Dmitry Torokhov
2006-06-27  6:13 ` Linus Torvalds
2006-06-27  6:37   ` Greg KH [this message]
2006-06-27 18:36     ` Linus Torvalds
2006-06-27 19:16       ` Linus Torvalds
2006-06-27 19:35         ` Linus Torvalds
2006-06-27 19:40           ` Dmitry Torokhov
2006-06-27 21:03             ` Linus Torvalds
2006-06-27 19:46           ` Marcel Holtmann
2006-06-28  4:07             ` Linus Torvalds
2006-06-28  4:36               ` Linus Torvalds
2006-06-28  7:03                 ` Jeff Garzik
2006-06-28 22:05                   ` Linus Torvalds
2006-06-28 23:03                     ` Marcel Holtmann
2006-06-28 23:40                     ` Jeff Garzik
2006-06-28 23:55                       ` Linus Torvalds
2006-06-27 19:33       ` Marcel Holtmann
2006-06-27 12:30   ` Dmitry Torokhov
  -- strict thread matches above, loose matches on Subject: below --
2006-06-28  3:50 Dmitry Torokhov
2006-04-02  5:56 Dmitry Torokhov

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=20060627063734.GA28135@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --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