[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061221195240.GS31882@telegraafnet.nl>
Date: Thu, 21 Dec 2006 20:52:40 +0100
From: Ard -kwaak- van Breemen <ard@...egraafnet.nl>
To: "Zhang, Yanmin" <yanmin.zhang@...el.com>
Cc: Andrew Morton <akpm@...l.org>,
Chuck Ebbert <76306.1226@...puserve.com>,
Yinghai Lu <yinghai.lu@....com>, take@...ero.it,
agalanin@...a.ru, linux-kernel@...r.kernel.org,
bugme-daemon@...zilla.kernel.org,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [Bug 7505] Linux-2.6.18 fails to boot on AMD64 machine
Hello,
On Thu, Dec 21, 2006 at 04:04:04PM +0800, Zhang, Yanmin wrote:
> I couldn't reproduce it on my EM64T machine. I instrumented function start_kernel and
> didn't find irq was enabled before calling init_IRQ. It'll be better if the reporter could
> instrument function start_kernel to capture which function enables irq.
Just diving into the sources.
Is that something like:
if(!raw_irqs_disabled_flags) printk "irqs are enabled";
(At that moment it might have crashed already.. :-)).
I don't see the complete context yet, but I hope the irq is
triggered after the irq is somehow enabled.
BTW: the panic occurs on half of my boards on tyan S2891 with 2
opterons, of which the only difference seems to be the purchase
date (and hence probably the motherboard revisions). (Haven't got
time yet to pull them out of the rack and compare the
motherboards).
--
program signature;
begin { telegraaf.com
} writeln("<ard@...egraafnet.nl> TEM2");
end
.
-
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/
Powered by blists - more mailing lists