public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Parag Warudkar <kernel-stuff@comcast.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John Livingston <jujutama@comcast.net>,
	Aleksey Gorelov <Aleksey_Gorelov@Phoenix.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: How to find if BIOS has already enabled the device
Date: Tue, 31 May 2005 21:12:55 -0400	[thread overview]
Message-ID: <200505312112.56014.kernel-stuff@comcast.net> (raw)
In-Reply-To: <1117296905.2356.23.camel@localhost.localdomain>

On Saturday 28 May 2005 12:15, Alan Cox wrote:
> On Sad, 2005-05-28 at 15:18, Parag Warudkar wrote:
> > dmesg is perfectly normal, not even timestamp differences before and
> > after call to pci_enable_device - since the machine is completely hung
> > for that period - not even the clock is ticking?
>
> A spurious jammed IRQ is one candidate - but you haven't provided dmesg
> data
>
Whoa - 2.6.12-rc5 automagically fixes this one! 2 *minutes* cut from boot 
time!! BTW - this was present from 2.6.9.

Parag

  parent reply	other threads:[~2005-06-01  1:13 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
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 [this message]
  -- 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=200505312112.56014.kernel-stuff@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=Aleksey_Gorelov@Phoenix.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jujutama@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