All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Baydarov <kbaidarov@ru.mvista.com>
To: vgoyal@in.ibm.com
Cc: RT <linux-rt-users@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [PATCH] kexec: reenable HPET before kexec
Date: Thu, 23 Aug 2007 15:49:36 +0400	[thread overview]
Message-ID: <20070823154936.3b7ae498@windmill.dev.rtsoft.ru> (raw)
In-Reply-To: <20070823090845.GA13065@in.ibm.com>

On Thu, 23 Aug 2007 14:38:45 +0530
Vivek Goyal <vgoyal@in.ibm.com> wrote:
> Does your kernel 2 boot normally? I mean through BIOS and boot-loader?
> This explanation seems to be suggesting that because PM and ACPI is
> disabled, kernel 2 does not search for HPET. If this is the case,
> this kernel will not boot even through normal boot-loader and will
> try to use PIT instead?
> 
> If so, it is not an kexec issue at all.
> 
> Thanks
> Vivek

kernel 2 boots normally through BIOS and boot-loader. I agree with your
explanation.
It seems that kernel 2 can't enable PIT, when it is executed by kexec.
As kernel 1 disabled HPET(IRQ0 source) and PIT is "broken"(or isn't
enabled) IRQ0 are not triggered at all, and kernel 2 hangs.
As kernel 2 boots normally through BIOS and boot-loader, than
additional code needed(in Linux kernel init code) for PIT or ACPI
or APIC initialization, I mean the same code as executed on BIOS stage.
I agree that it's not an kexec issue. But can we use my fix as a
workaround(to make kexec work) until PIT will be fixed?
Everything above is correct for i386/x86_64 RT(2.6.23-rc2-rt2) kernel
and for i368 "plain"(2.6.23-rc3) kernel. Bug isn't reproduced in 2.6.23-rc3
x86_64 kernel, because x86_64 code never disables HPET. So on every
boot(initiated by kexec or BIOS) IRQ0 are triggered.

  reply	other threads:[~2007-08-23 11:43 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-20 16:55 [PATCH] kexec: reenable HPET before kexec Konstantin Baydarov
2007-08-20 18:26 ` Andi Kleen
2007-08-20 21:10 ` Konstantin Baydarov
2007-08-20 21:31   ` Daniel Walker
2007-08-21 13:01     ` Konstantin Baydarov
2007-08-23  9:08 ` Vivek Goyal
2007-08-23 11:49   ` Konstantin Baydarov [this message]
2007-08-27  5:36     ` Vivek Goyal
2007-08-27 18:26       ` Pallipadi, Venkatesh
2007-08-27 18:33         ` Eric W. Biederman
2007-08-28 12:58         ` Konstantin Baydarov
2007-08-28 12:58           ` Konstantin Baydarov
2007-08-30  7:32           ` Eric W. Biederman
2007-08-30  7:32             ` Eric W. Biederman
2007-08-30 16:07             ` Konstantin Baydarov
2007-08-30 16:07               ` Konstantin Baydarov
2007-08-30 18:04               ` Eric W. Biederman
2007-08-30 18:04                 ` Eric W. Biederman
2007-08-30 18:04                 ` Eric W. Biederman
2007-08-31 10:31                 ` Konstantin Baydarov
2007-08-31 10:31                   ` Konstantin Baydarov
2007-09-17  9:47                   ` Konstantin Baydarov
2007-09-17  9:47                     ` Konstantin Baydarov

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=20070823154936.3b7ae498@windmill.dev.rtsoft.ru \
    --to=kbaidarov@ru.mvista.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=vgoyal@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.