From: Parag Warudkar <kernel-stuff@comcast.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: How to find if BIOS has already enabled the device
Date: Mon, 11 Jul 2005 22:55:07 -0400 [thread overview]
Message-ID: <200507112255.08080.kernel-stuff@comcast.net> (raw)
> On Sad, 2005-05-28 at 14:57, Parag Warudkar wrote:
> > This current problem of Hang-On-Boot if USB drive is attached does not
happen
> > with Windows - so it is some sort of additional (unnecessary?) thing which
> > Linux does and the BIOS doesn't like. (Like re-enabling the controller
even
> > if BIOS has already enabled it or some such.)
> > Alan Cox wrote:
> Provide dmesg output and we might be able to guess. The first obvious
> candidate would be the BIOS refusing to do a handover if it booted from
> USB disk.
Hi Alan
Sorry for digging this out so late - (Quick recap - My machine hangs for
couple minutes on boot if USB storage disk is attached - hang occurs in
pci_enable_device).
I have filed a bug to track this one -
http://bugme.osdl.org/show_bug.cgi?id=4711
Further analysis points towards wrong/differing IRQ assigments being the
cause of this hang. I observed that when the machine hangs, the IRQ
assignment looks like -
18: 379 IO-APIC-level eth0
19: 3 IO-APIC-level ohci1394
20: 1439 IO-APIC-level ohci_hcd, NVidia nForce3 Modem
21: 0 IO-APIC-level ohci_hcd, NVidia nForce3
22: 12884 IO-APIC-level ehci_hcd
And when it does NOT hang it looks like -
16: 3 IO-APIC-level ohci1394
18: 49277 IO-APIC-level nvidia
19: 1753 IO-APIC-level eth0
20: 6253 IO-APIC-level ohci_hcd
21: 646 IO-APIC-level ohci_hcd, NVidia nForce3
22: 2225 IO-APIC-level ehci_hcd, NVidia nForce3 Modem
Seems to me like the OHCI controller doesn't like to be assigned IRQ 19. Is
this difference in IRQ assignment normal or is it a bug somewhere?
Parag
next reply other threads:[~2005-07-12 2:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-12 2:55 Parag Warudkar [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-30 14:49 How to find if BIOS has already enabled the device Parag Warudkar
2005-05-28 1:34 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
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=200507112255.08080.kernel-stuff@comcast.net \
--to=kernel-stuff@comcast.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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