Hi Linus,
I backed up my tree to before the evil HPET disable commit, and then
cherry-picked the stuff that follwed. So here's the revised pull without
the stupidity.
Note to anyone else using my GIT tree ... this means my tree jumped
sideways and you won't be able to pull from it if you had don
> Having looked closer, it looks like the magic actually disables some
> broken code from happening on other architectures.
Yes. The drivers/char/hpet.c clocksource code was added for ia64 as
part of the switch from the time interpolator to the generic clock
code ... but the patch had languished
Fix the problem that kdump on INIT hung up if kdump kernel image is
not configured.
The kdump_init_notifier() on monarch CPU stops its operation at
DIE_INIT_MONARCH_LEAVE time if the kdump kernel image is not
configured. On the other hand, kdump_init_notifier() on non-monarch
CPUs get into spin be
Fix the problem that kdump on INIT causes a kernel panic if kdump
kernel image is not configured. The cause of this problem is
machine_kexec_on_init() is using printk in INIT context. It should
use ia64_mca_printk() instead.
Signed-off-by: Kenji Kaneshige <[EMAIL PROTECTED]>
---
arch/ia64/kernel
Hi,
Here are patches for kdump on ia64 to fix the follwing problems:
- [PATCH 1/2] Fix kernel panic in kdump on INIT
I encountered the kernel panic when I sent an INIT without
configuring kdump kernel image. The cause of this problem seems
that machine_kdump_on_init() uses printk()