From: Fernando Luis Vazquez Cao <fernando@intellilink.co.jp>
To: ebiederm@xmission.com
Cc: akpm@osdl.org, fastboot@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [Fastboot] kdump's dump capture kernel fails (APICs & linux-2.6.15-rc1)
Date: Mon, 21 Nov 2005 16:24:03 +0900 [thread overview]
Message-ID: <1132557843.4806.27.camel@localhost.localdomain> (raw)
In-Reply-To: <1132501594.2432.132.camel@localhost.localdomain>
On Mon, 2005-11-21 at 00:46 +0900, Fernando Luis Vazquez Cao wrote:
> Hi Eric,
>
> It seems there are still some problems with the initialization of the
> APICs in the second kernel. As you can see from the serial line captures
> below, early during the boot process the kernel is flooded with
> "unexpected IRQ trap at vector ##" errors and fails to boot.
>
> Some basic details about the machine:
> - Dual Xeon Hyper-Threading 2.4GHz
> - 1GB RAM
>
> In this particular machine the problem could be solved by reintroducing
> the APICs shutdown patch. The drawback with this approach is that
> LAPIC/IOAPIC registers setup for the legacy PIC mode differs a lot
> between mother boards and the somewhat hackish shutdown code fails to
> set the APICs properly under certain configurations.
I have just realized that the "move apic init in init_IRQs" patches by
Eric were reverted back. Besides, APICs shutdown code made it back into
linux-2.6.15-rc2.
This is a desirable stopgap solution that will solve the problem for
some machines and configurations.
Anyway, up to now, the "LAPIC/IO-APIC save/restore" solution is the only
one that has worked reliably for us (even with badly broken BIOSes).
I will test Eric's patches and report the results.
Regards,
Fernando
prev parent reply other threads:[~2005-11-21 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 15:46 kdump's dump capture kernel fails (APICs & linux-2.6.15-rc1) Fernando Luis Vazquez Cao
2005-11-21 7:24 ` Fernando Luis Vazquez Cao [this message]
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=1132557843.4806.27.camel@localhost.localdomain \
--to=fernando@intellilink.co.jp \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=fastboot@osdl.org \
--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