linux-kernel - Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <769836.91421.qm@web52909.mail.re2.yahoo.com>
Date:	Fri, 22 Feb 2008 09:41:54 +0000 (GMT)
From:	Chris Rankin <rankincj@...oo.com>
To:	Kay Sievers <kay.sievers@...y.org>,
	Stephen Hemminger <shemminger@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: Linux 2.6.24.1 - kernel does not boot; IRQ trouble?

--- Kay Sievers <kay.sievers@...y.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/