From: Chris Rankin <rankincj@yahoo.com>
To: Kay Sievers <kay.sievers@vrfy.org>,
Stephen Hemminger <shemminger@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?
Date: Fri, 22 Feb 2008 09:41:54 +0000 (GMT) [thread overview]
Message-ID: <769836.91421.qm@web52909.mail.re2.yahoo.com> (raw)
In-Reply-To: <3ae72650802220111s11e68f1ft149d7832e9bebbd6@mail.gmail.com>
--- Kay Sievers <kay.sievers@vrfy.org> wrote:
> Greg,
> it seems that:
> arch/x86/pci/legacy.c :: pci_legacy_init()
>
> tries to create already created "bridge" symlinks in 2.6.24. So we
> discover the same devices twice? Can this be a reason for the hang?
No, it can't be because it's *not* hanging in this configuration :-). It hangs when I *don't* add
the acpi=noirq option, whereas here it's just adding noise to the dmesg log. (I'm guessing Linux
doesn't call pci_legacy_init() when ACPI takes charge of the IRQs.)
Cheers,
Chris
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2008-02-22 9:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 0:54 Linux 2.6.24.1 - kernel does not boot; IRQ trouble? Chris Rankin
2008-02-18 13:00 ` Andrew Morton
2008-02-18 13:16 ` Chris Rankin
2008-02-18 16:53 ` Stephen Hemminger
2008-02-18 19:42 ` Chris Rankin
2008-02-18 20:06 ` Stephen Hemminger
2008-02-19 8:47 ` Kay Sievers
2008-02-22 9:11 ` Kay Sievers
2008-02-22 9:41 ` Chris Rankin [this message]
2008-02-18 13:00 ` Andrew Morton
2008-02-18 13:13 ` Chris Rankin
2008-02-26 22:36 ` Chris Rankin
2008-02-26 23:40 ` Greg KH
2008-02-27 0:55 ` Chris Rankin
2008-02-27 2:52 ` Andrew Morton
2008-02-27 8:39 ` Chris Rankin
2008-03-02 2:43 ` Linux 2.6.24.1 - kernel does not boot; Solution! Chris Rankin
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=769836.91421.qm@web52909.mail.re2.yahoo.com \
--to=rankincj@yahoo.com \
--cc=akpm@linux-foundation.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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