public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Livingston <jujutama@comcast.net>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>,
	linux-kernel@vger.kernel.org
Subject: Re: How to find if BIOS has already enabled the device
Date: Fri, 27 May 2005 23:24:37 -0400	[thread overview]
Message-ID: <4297E475.3040906@comcast.net> (raw)
In-Reply-To: <200505272150.15109.kernel-stuff@comcast.net>


>
>The offending code is in hcd-pci.c - which 
>seems to be executed unconditionally. usb_hcd_pci_probe() calls 
>pci_enable_device() which hangs if there was already a device present, 
>attached to the controller. 
>  
>
Have you attempted more generic fix-hardware-hang solutions?  I've known 
more than a few times where a good old "noapic nolapic" snapped a box 
out of some strange and seemingly unrelated problems...

Also, is your BIOS fully up to date/modern?  A quick Google search found 
a few things like this:
http://www.techspot.com/vb/all/windows/t-18940-USB-Hub-And-Boot-Problems.html
The problem might be more generic than a bad interaction between drive 
and kernel.

~John Livingston

  reply	other threads:[~2005-05-28  3:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-28  1:34 How to find if BIOS has already enabled the device Aleksey Gorelov
2005-05-28  1:50 ` Parag Warudkar
2005-05-28  3:24   ` John Livingston [this message]
2005-05-28 13:57     ` Parag Warudkar
2005-05-28 14:04       ` Alan Cox
2005-05-28 14:18         ` Parag Warudkar
2005-05-28 14:37           ` Parag Warudkar
2005-05-28 16:15           ` Alan Cox
2005-05-28 17:01             ` Parag Warudkar
2005-05-29  0:06               ` Lee Revell
2005-05-29  0:17                 ` Parag Warudkar
2005-05-30  3:22                   ` Michael Sterrett -Mr. Bones.-
2005-06-01  1:12             ` Parag Warudkar
  -- strict thread matches above, loose matches on Subject: below --
2005-05-30 14:49 Parag Warudkar
2005-07-12  2:55 Parag Warudkar

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=4297E475.3040906@comcast.net \
    --to=jujutama@comcast.net \
    --cc=Aleksey_Gorelov@Phoenix.com \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.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