Is this problem something new to you after .27?SGI folks should test this patchset to ensure no surprise is introduced to their servers.
Cheers, jay----- Original Message ----- From: "Hidetoshi Seto" <seto.hidetoshi@xxxxxxxxxxxxxx>
To: <linux-ia64@xxxxxxxxxxxxxxx>; <linux-kernel@xxxxxxxxxxxxxxx>Cc: "Haren Myneni" <hbabu@xxxxxxxxxx>; <kexec@xxxxxxxxxxxxxxxxxxx>; "Vivek Goyal" <vgoyal@xxxxxxxxxx>
Sent: Wednesday, June 17, 2009 11:44 PM Subject: [PATCH 0/7] Patches for kdump vs. INIT
Hi Tony-san, and kdump folks, I got some trouble on kdump on IPF with INIT, and my investigation proves there are some bugs and races in startup of kdump. Here are fixes based on .30, for issues I found. Since it must be serious problem for (likely big) IPF servers if we could fail to retrieve crashdump via kdump, so I believe these patches should be applied asap. Thanks, H.Seto === Hidetoshi Seto (7): ia64, kdump: Mask MCA/INIT on freezing cpus ia64, kexec: Make INIT safe while kdump/kexec ia64, kexec: Unregister MCA handler before kexec ia64, kdump: Don't offline APs ia64, kdump: Mask INIT first in panic-kdump path ia64, kdump: Try INIT regardless of kdump_on_init ia64, kdump: Short path to freeze CPUsarch/ia64/kernel/crash.c | 85 ++++++++++++++++++++++++++------------arch/ia64/kernel/machine_kexec.c | 17 ++++++++ arch/ia64/kernel/mca.c | 15 ++++++- arch/ia64/kernel/mca_asm.S | 47 +++++++++++++++++++++ 4 files changed, 136 insertions(+), 28 deletions(-) _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
-- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |