From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Chuck Ebbert" <76306.1226@compuserve.com>,
agalanin@mera.ru, take@libero.it
Cc: "Andrew Morton" <akpm@osdl.org>,
"Zhang Yanmin" <yanmin.zhang@intel.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
bugme-daemon@bugzilla.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bug 7505] Linux-2.6.18 fails to boot on AMD64 machine
Date: Wed, 20 Dec 2006 01:11:35 -0800 [thread overview]
Message-ID: <86802c440612200111j611445cdpb972e7cd6a0c5486@mail.gmail.com> (raw)
In-Reply-To: <200612200145_MC3-1-D5AF-61E@compuserve.com>
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
On 12/19/06, Chuck Ebbert <76306.1226@compuserve.com> wrote:
> So an external interrupt occurred, the system tried to use interrupt
> descriptor #39 decimal (irq 7), but the descriptor was invalid.
but the irq is disabled at that time.
can you use attached diff to verify if the irq is enable somehow?
YH
[-- Attachment #2: test_init_isa_irqs.diff --]
[-- Type: text/x-patch, Size: 497 bytes --]
diff --git a/arch/x86_64/kernel/i8259.c b/arch/x86_64/kernel/i8259.c
index d73c79e..fedde34 100644
--- a/arch/x86_64/kernel/i8259.c
+++ b/arch/x86_64/kernel/i8259.c
@@ -421,7 +421,11 @@ void __init init_ISA_irqs (void)
{
int i;
+ if (!irqs_disabled())
+ printk("init_ISA_irqs(): -1 bug: interrupts were enabled early\n");
init_bsp_APIC();
+ if (!irqs_disabled())
+ printk("init_ISA_irqs(): -2 bug: interrupts were enabled early\n");
init_8259A(0);
for (i = 0; i < NR_IRQS; i++) {
next prev parent reply other threads:[~2006-12-20 9:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 6:42 [Bug 7505] Linux-2.6.18 fails to boot on AMD64 machine Chuck Ebbert
2006-12-20 9:11 ` Yinghai Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 4:41 Zhang, Yanmin
2006-12-22 8:22 ` Ard -kwaak- van Breemen
2006-12-22 8:30 ` Andrew Morton
2006-12-22 9:32 ` Stefano Takekawa
2006-12-22 9:43 ` Andrew Morton
2006-12-22 13:23 ` Stefano Takekawa
2006-12-22 10:30 ` Ard -kwaak- van Breemen
2006-12-22 14:00 ` Ard -kwaak- van Breemen
2006-12-22 14:16 ` Ard -kwaak- van Breemen
2006-12-22 19:10 ` Andrew Morton
2006-12-22 14:35 ` Ard -kwaak- van Breemen
2006-12-29 15:08 ` Ard -kwaak- van Breemen
2006-12-22 14:41 ` Ard -kwaak- van Breemen
2006-12-22 15:42 ` Ard -kwaak- van Breemen
2006-12-28 23:51 ` Andrew Morton
2006-12-29 10:18 ` Stefano Takekawa
2006-12-29 12:51 ` Ard -kwaak- van Breemen
2006-12-29 13:27 ` Ard -kwaak- van Breemen
2006-12-29 14:10 ` Ard -kwaak- van Breemen
2006-12-29 15:01 ` Ard -kwaak- van Breemen
2006-12-29 15:05 ` Ard -kwaak- van Breemen
2006-12-29 15:24 ` Ard -kwaak- van Breemen
2006-12-29 15:42 ` Ard -kwaak- van Breemen
2006-12-21 8:04 Zhang, Yanmin
2006-12-21 19:52 ` Ard -kwaak- van Breemen
2006-12-21 20:11 ` Andrew Morton
2006-12-21 21:05 ` Ard -kwaak- van Breemen
2006-12-22 18:42 ` Ard -kwaak- van Breemen
2006-12-22 19:39 ` Stefano Takekawa
2006-12-20 9:59 Chuck Ebbert
2006-12-20 10:12 ` Yinghai Lu
2006-12-20 10:37 ` Andrew Morton
2006-12-20 10:55 ` Arjan van de Ven
[not found] <200612181543.kBIFhcIc001555@fire-2.osdl.org>
2006-12-18 16:48 ` Eric W. Biederman
2006-12-20 1:29 ` Andrew Morton
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=86802c440612200111j611445cdpb972e7cd6a0c5486@mail.gmail.com \
--to=yinghai.lu@amd.com \
--cc=76306.1226@compuserve.com \
--cc=agalanin@mera.ru \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=take@libero.it \
--cc=yanmin.zhang@intel.com \
/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