From: Vivek Goyal <vgoyal@in.ibm.com>
To: Neil Horman <nhorman@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: Timer interrupt lost on some x86_64 systems
Date: Tue, 13 Nov 2007 13:01:28 +0530 [thread overview]
Message-ID: <20071113073128.GB24067@in.ibm.com> (raw)
In-Reply-To: <20071112154119.GC11751@hmsendeavour.rdu.redhat.com>
On Mon, Nov 12, 2007 at 10:41:19AM -0500, Neil Horman wrote:
[..]
>
>
> Although, as I look at it, it would appear that time_init from start_kernel does
> seem to init the hpet if its available, and it silently fails if that doesn't
> work, moving on to the pmtimer and pit. I wonder if there is some extra magic
> to resetting the hpet to run on a different cpu for some systems...
> Neil
>
Any idea what kind of timer devices this motherborad has got? Which timer
device gets activated in first kernel? Then we can focus on why the
interrupts from same device are not coming in second kernel.
In the past I have found issues with interrupt routing on IOPAPIC and
interrupt lockup on LAPIC. But these issues are already solved. I would
also think of priting LAPIC and IOAPIC entries to see how timer interrupt
routing changes from first kernel to second.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2007-11-13 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 14:00 Timer interrupt lost on some x86_64 systems Neil Horman
2007-11-12 4:49 ` Vivek Goyal
2007-11-12 15:17 ` Neil Horman
2007-11-12 15:41 ` Neil Horman
2007-11-13 7:31 ` Vivek Goyal [this message]
2007-11-13 14:33 ` Neil Horman
2007-11-14 6:39 ` Vivek Goyal
2007-11-14 11:51 ` Neil Horman
2007-11-22 20:04 ` Eric W. Biederman
2007-11-13 7:22 ` Vivek Goyal
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=20071113073128.GB24067@in.ibm.com \
--to=vgoyal@in.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.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