IA64 Kexec-Kdump kernel patch
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
Changes since last patch include:
1. re-base the patch to 2.6.18-rc4
2. per-cpu register dumping, so that user space tool can unwind kernel stack. This should really done by INIT event. But unfortunately it seems that the firmware on the machine I am using does not handle INIT event correctly... So current I dump per-cpu registers by simple IPI.
3. fix on_line_cpu issue,
previous patch stop APs by smp_send_stop. AP will clear his bit in cpu_online_map, then crash tools will see a cpu_online_map which only contains 1 cpu in vmcore file.
4. reserve efi memmap area and ia64 boot param area for the first kernel.
To test crash dump.
Compile a kernel with CONFIG_KEXEC CONFIG_CRASH_DUMP CONFIG_PROC_VMCORE enabled.
using this kernel for both host kernel and crash dumping kernel.
Boot this kernel with kernel parameter "crashkernel=XXX@YYY".
XXX should be a size big enough for crash kernel to run, YYY should be a physical address which contains more than XXX memory and aligned to 64M. you can check it in /proc/iomem.
Be careful of choosing the size and address to reserve.
The second kernel may hang silently if there is too few memory to use.
After the first kernel boots, the "Crash kernel" region will show in /proc/iomem. then load the same kernel with command.
kexec -p vmlinux.gz --initrd=initrd --append="root=... maxcpus=1"
trigger a crash with echo c > /proc/sysrq-trigger
after the crash kernel boots,
copy /proc/vmcore to disk
gdb vmlinux-of-first-kernel vmcore
then you can check the stack and variables of first kernel.
kexec -l + kexec -e may not work.
That is because of a recent change in mpt-fusion driver
shutdown code.
There was some delay in mptscsih_remove path.
the code was removed in 2.6.17, that cause MPT fusion driver unable to reinitialize. add a delay back to mptscsih_remove can solve this problem.
Signed-off-by:
Zou Nan hai <[email protected]>
arch/ia64/hp/common/sba_iommu.c +22 -0
@@ -1623,6 +1623,28 @@ ioc_iova_init(struct ioc *ioc)READ_REG (ioc->ioc_hpa +IOC_IBASE ); } +#ifdef CONFIG_KEXEC +void +ioc_iova_disable (void ) +{ +struct ioc *ioc; + + ioc = ioc_list; + +while (ioc !=NULL ) { +/* Disable IOVA translation */ +WRITE_REG (ioc->ibase &0xfffffffffffffffe , ioc->ioc_hpa +IOC_IBASE ); +READ_REG (ioc->ioc_hpa +IOC_IBASE ); + +/* Clear I/O TLB of any possible entries */ +WRITE_REG (ioc->ibase | (get_iovp_order (ioc->iov_size) + iovp_shift), ioc->ioc_hpa +IOC_PCOM ); +READ_REG (ioc->ioc_hpa +IOC_PCOM ); + + ioc = ioc->next; + } +} +#endif +static void __init ioc_resource_init (struct ioc *ioc) {
arch/ia64/Kconfig +23 -0
@@ -427,6 +427,29 @@ config SGI_SN source "drivers/sn/Kconfig" +config KEXEC + bool "kexec system call (EXPERIMENTAL)" + depends on EXPERIMENTAL + help + kexec is a system call that implements the ability to shutdown your + current kernel, and to start another kernel. It is like a reboot + but it is indepedent of the system firmware. And like a reboot + you can start any kernel with it, not just Linux. + + The name comes from the similiarity to the exec system call. + + It is an ongoing process to be certain the hardware in a machine + is properly shutdown, so do not be surprised if this code does not + initially work for you. It may help to enable device hotplugging + support. As of this writing the exact hardware interface is + strongly in flux, so no good recommendation can be made. + +config CRASH_DUMP + bool "kernel crash dumps (EXPERIMENTAL)" + depends on EXPERIMENTAL + help + Generate crash dump after being started by kexec. + source "drivers/firmware/Kconfig" source "fs/Kconfig.binfmt"
arch/ia64/kernel/crash.c +129 -0
129 lines not on this page · raw message
arch/ia64/kernel/efi.c +16 -3
@@ -26,6 +26,7 @@#include <linux/types.h> #include <linux/time.h> #include <linux/efi.h> +#include <linux/kexec.h> #include <asm/io.h> #include <asm/kregs.h>
@@ -41,7 +42,7 @@ extern efi_status_t efi_call_phys (voidstruct efi efi;EXPORT_SYMBOL (efi);static efi_runtime_services_t *runtime; -static unsigned long mem_limit = ~0UL , max_addr = ~0UL ; +static unsigned long mem_limit = ~0UL , max_addr = ~0UL , min_addr =0UL ; #define efi_call_virt(f, args...) (*(f))(args)
@@ -421,6 +422,8 @@ efi_init (void) mem_limit =memparse (cp +4 , &cp); }else if (memcmp (cp,"max_addr=" ,9 ) =0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); + }else if (memcmp (cp,"min_addr=" ,9 ) =0 ) { + min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {while (*cp !=' ' && *cp) ++cp;
@@ -428,6 +431,8 @@ efi_init (void) ++cp; } } +if (min_addr !=0UL ) +printk (KERN_INFO "Ignoring memory below %luMB\n" , min_addr >>20 );if (max_addr != ~0UL )printk (KERN_INFO "Ignoring memory above %luMB\n" , max_addr >>20 );
@@ -894,7 +899,8 @@ find_memmap_space (void) as =max (contig_low, md->phys_addr); ae =min (contig_high,efi_md_end (md)); -/* keep within max_addr= command line arg */ +/* keep within max_addr= and min_addr= command line arg */ + as =max (as, min_addr); ae =min (ae, max_addr);if (ae <= as)continue ;
@@ -1004,7 +1010,8 @@ efi_memmap_init(unsigned long *s, unsign }else ae =efi_md_end (md); -/* keep within max_addr= command line arg */ +/* keep within max_addr= and min_addr= command line arg */ + as =max (as, min_addr); ae =min (ae, max_addr);if (ae <= as)continue ;
@@ -1116,6 +1123,12 @@ efi_initialize_iomem_resources(struct re*/ insert_resource (res, code_resource);insert_resource (res, data_resource); +#ifdef CONFIG_KEXEC +insert_resource (res, &efi_memmap_res); +insert_resource (res, &boot_param_res); +if (crashk_res.end > crashk_res.start) +insert_resource (res, &crashk_res); +#endif } } }
arch/ia64/kernel/entry.S +1 -1
@@ -1575,7 +1575,7 @@ sys_call_table: data8 sys_mq_timedreceive // 1265 data8 sys_mq_notify data8 sys_mq_getsetattr - data8 sys_ni_syscall // reserved for kexec_load + data8 sys_kexec_load data8 sys_ni_syscall // reserved for vserver data8 sys_waitid // 1270 data8 sys_add_key
arch/ia64/kernel/machine_kexec.c +131 -0
131 lines not on this page · raw message
arch/ia64/kernel/Makefile +1 -0
@@ -28,6 +28,7 @@ obj-$(CONFIG_IA64_CYCLONE) += cyclone.o obj-$(CONFIG_CPU_FREQ) += cpufreq/ obj-$(CONFIG_IA64_MCA_RECOVERY) += mca_recovery.o obj-$(CONFIG_KPROBES) += kprobes.o jprobes.o +obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o crash.o obj-$(CONFIG_IA64_UNCACHED_ALLOCATOR) += uncached.o obj-$(CONFIG_AUDIT) += audit.o mca_recovery-y += mca_drv.o mca_drv_asm.o
arch/ia64/kernel/relocate_kernel.S +490 -0
490 lines not on this page · raw message
arch/ia64/kernel/setup.c +45 -0
63 lines not on this page · raw message
arch/ia64/kernel/smp.c +46 -1
77 lines not on this page · raw message
include/asm-ia64/kexec.h +38 -0
@@ -0,0 +1,38 @@ +#ifndef _ASM_IA64_KEXEC_H +#define _ASM_IA64_KEXEC_H + + +/* Maximum physical address we can use pages from */ +#define KEXEC_SOURCE_MEMORY_LIMIT (-1UL) +/* Maximum address we can reach in physical address mode */ +#define KEXEC_DESTINATION_MEMORY_LIMIT (-1UL) +/* Maximum address we can use for the control code buffer */ +#define KEXEC_CONTROL_MEMORY_LIMIT TASK_SIZE + +#define KEXEC_CONTROL_CODE_SIZE (8192 + 8192 + 4096) + +/* The native architecture */ +#define KEXEC_ARCH KEXEC_ARCH_IA_64 + +#define MAX_NOTE_BYTES 1024 + +#define pte_bits 3 +#define vmlpt_bits (impl_va_bits - PAGE_SHIFT + pte_bits) +#define POW2 (n) (1ULL << (n)) + +DECLARE_PER_CPU (u64, ia64_mca_pal_base); +const extern unsigned int relocate_new_kernel_size; +volatile extern long kexec_rendez; +extern void relocate_new_kernel (unsigned long ,unsigned long , +struct ia64_boot_param *,unsigned long ); +extern void kexec_fake_sal_rendez (void *start,unsigned long wake_up, +unsigned long pal_base); +static inline void +crash_setup_regs (struct pt_regs *newregs,struct pt_regs *oldregs) +{ +} +extern struct resource efi_memmap_res; +extern struct resource boot_param_res; +extern void kdump_smp_send_stop (void ); +extern void crash_save_this_cpu (void ); +#endif /* _ASM_IA64_KEXEC_H */
include/asm-ia64/machvec_hpzx1.h +2 -0
@@ -34,4 +34,6 @@ extern ia64_mv_dma_mapping_error sba_dma#define platform_dma_supported sba_dma_supported#define platform_dma_mapping_error sba_dma_mapping_error +extern void ioc_iova_disable (void ); +#endif /* _ASM_IA64_MACHVEC_HPZX1_h */
include/asm-ia64/meminit.h +2 -1
@@ -15,11 +15,12 @@* - initrd (optional) * - command line string * - kernel code & data +* - crash dumping code reserved region * - Kernel memory map built from EFI memory map * * More could be added if necessary */ -#define IA64_MAX_RSVD_REGIONS 6 +#define IA64_MAX_RSVD_REGIONS 7struct rsvd_region {unsigned long start;/* virtual address of beginning of element */
include/asm-ia64/smp.h +3 -0
@@ -128,6 +128,9 @@ extern void smp_send_reschedule (int cpuextern void lock_ipi_calllock (void );extern void unlock_ipi_calllock (void );extern void identify_siblings (struct cpuinfo_ia64 *); +#ifdef CONFIG_KEXEC +extern void kexec_stop_this_cpu (void *); +#endif #else
kernel/irq/manage.c +0 -1
@@ -475,4 +475,3 @@ int request_irq(unsigned int irq,return retval; }EXPORT_SYMBOL (request_irq); -
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
Contrary to expectations, my experience with this patch on a 2.6.18-rc4 kernel is that kexec -l, kexec -e is now working without my adding any delays to mptscsih, and the kexec -p, echo c >/proc/sysrq-trigger case hangs.
My "got here" printk's on the console indicate:
SysRq : Trigger a crashdumpmachine_crash_shutdowndevice_shootdownmachine_kexec type: 1
And then it hangs.
My test system: hp A6870A server rx2600
From /proc/iomem:
04a1f000-3f5e3fff : System RAM
10000000-17ffffff : Crash kernel
# cat /proc/cmdline BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz-2.6.18-rc4-bobm root=/dev/sda4 raid=noautodetect crashkernel8M@256M panic=1 ro
relevant CONFIG settings (from /proc/config.gz)
CONFIG_HOTPLUG=yCONFIG_IA64_HP_ZX1=y
# CONFIG_IA64_HP_ZX1_SWIOTLB is not setCONFIG_HOTPLUG_CPU=yCONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
# CONFIG_SPARSEMEM_MANUAL is not set
# CONFIG_SPARSEMEM_STATIC is not setCONFIG_ARCH_SPARSEMEM_ENABLE=yCONFIG_KEXEC=yCONFIG_CRASH_DUMP=yCONFIG_ACPI_HOTPLUG_CPU=y
# CONFIG_HOTPLUG_PCI is not setCONFIG_AGP_HP_ZX1=yCONFIG_PROC_VMCORE=y
Bob Montgomery
Quoted 8 lines · Jay Lan
Quoted 5 lines · Bob Montgomery
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
...
Jay,
Thanks very much, please try the following updated patch which
simplify the device_shootdown code.
diff -Nraup linux-2.6.18-rc4/arch/ia64/hp/common/sba_iommu.c linux-2.6.18-rc4-kdump/arch/ia64/hp/common/sba_iommu.c
arch/ia64/hp/common/sba_iommu.c +22 -0
@@ -1623,6 +1623,28 @@ ioc_iova_init(struct ioc *ioc)READ_REG (ioc->ioc_hpa +IOC_IBASE ); } +#ifdef CONFIG_KEXEC +void +ioc_iova_disable (void ) +{ +struct ioc *ioc; + + ioc = ioc_list; + +while (ioc !=NULL ) { +/* Disable IOVA translation */ +WRITE_REG (ioc->ibase &0xfffffffffffffffe , ioc->ioc_hpa +IOC_IBASE ); +READ_REG (ioc->ioc_hpa +IOC_IBASE ); + +/* Clear I/O TLB of any possible entries */ +WRITE_REG (ioc->ibase | (get_iovp_order (ioc->iov_size) + iovp_shift), ioc->ioc_hpa +IOC_PCOM ); +READ_REG (ioc->ioc_hpa +IOC_PCOM ); + + ioc = ioc->next; + } +} +#endif +static void __init ioc_resource_init (struct ioc *ioc) {
arch/ia64/Kconfig +23 -0
@@ -427,6 +427,29 @@ config SGI_SN source "drivers/sn/Kconfig" +config KEXEC + bool "kexec system call (EXPERIMENTAL)" + depends on EXPERIMENTAL + help + kexec is a system call that implements the ability to shutdown your + current kernel, and to start another kernel. It is like a reboot + but it is indepedent of the system firmware. And like a reboot + you can start any kernel with it, not just Linux. + + The name comes from the similiarity to the exec system call. + + It is an ongoing process to be certain the hardware in a machine + is properly shutdown, so do not be surprised if this code does not + initially work for you. It may help to enable device hotplugging + support. As of this writing the exact hardware interface is + strongly in flux, so no good recommendation can be made. + +config CRASH_DUMP + bool "kernel crash dumps (EXPERIMENTAL)" + depends on EXPERIMENTAL + help + Generate crash dump after being started by kexec. + source "drivers/firmware/Kconfig" source "fs/Kconfig.binfmt"
arch/ia64/kernel/crash.c +125 -0
125 lines not on this page · raw message
arch/ia64/kernel/efi.c +16 -3
@@ -26,6 +26,7 @@#include <linux/types.h> #include <linux/time.h> #include <linux/efi.h> +#include <linux/kexec.h> #include <asm/io.h> #include <asm/kregs.h>
@@ -41,7 +42,7 @@ extern efi_status_t efi_call_phys (voidstruct efi efi;EXPORT_SYMBOL (efi);static efi_runtime_services_t *runtime; -static unsigned long mem_limit = ~0UL , max_addr = ~0UL ; +static unsigned long mem_limit = ~0UL , max_addr = ~0UL , min_addr =0UL ; #define efi_call_virt(f, args...) (*(f))(args)
@@ -421,6 +422,8 @@ efi_init (void) mem_limit =memparse (cp +4 , &cp); }else if (memcmp (cp,"max_addr=" ,9 ) =0 ) { max_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); + }else if (memcmp (cp,"min_addr=" ,9 ) =0 ) { + min_addr =GRANULEROUNDDOWN (memparse (cp +9 , &cp)); }else {while (*cp !=' ' && *cp) ++cp;
@@ -428,6 +431,8 @@ efi_init (void) ++cp; } } +if (min_addr !=0UL ) +printk (KERN_INFO "Ignoring memory below %luMB\n" , min_addr >>20 );if (max_addr != ~0UL )printk (KERN_INFO "Ignoring memory above %luMB\n" , max_addr >>20 );
@@ -894,7 +899,8 @@ find_memmap_space (void) as =max (contig_low, md->phys_addr); ae =min (contig_high,efi_md_end (md)); -/* keep within max_addr= command line arg */ +/* keep within max_addr= and min_addr= command line arg */ + as =max (as, min_addr); ae =min (ae, max_addr);if (ae <= as)continue ;
@@ -1004,7 +1010,8 @@ efi_memmap_init(unsigned long *s, unsign }else ae =efi_md_end (md); -/* keep within max_addr= command line arg */ +/* keep within max_addr= and min_addr= command line arg */ + as =max (as, min_addr); ae =min (ae, max_addr);if (ae <= as)continue ;
@@ -1116,6 +1123,12 @@ efi_initialize_iomem_resources(struct re*/ insert_resource (res, code_resource);insert_resource (res, data_resource); +#ifdef CONFIG_KEXEC +insert_resource (res, &efi_memmap_res); +insert_resource (res, &boot_param_res); +if (crashk_res.end > crashk_res.start) +insert_resource (res, &crashk_res); +#endif } } }
arch/ia64/kernel/entry.S +1 -1
@@ -1575,7 +1575,7 @@ sys_call_table: data8 sys_mq_timedreceive // 1265 data8 sys_mq_notify data8 sys_mq_getsetattr - data8 sys_ni_syscall // reserved for kexec_load + data8 sys_kexec_load data8 sys_ni_syscall // reserved for vserver data8 sys_waitid // 1270 data8 sys_add_key
arch/ia64/kernel/iosapic.c +18 -0
@@ -288,6 +288,24 @@ nop (unsigned int irq)/* do nothing... */ } +#ifdef CONFIG_CRASH_DUMP +void +kdump_disable_irq (unsigned int irq) +{ +u32 low32; +ia64_vector vec =irq_to_vector (irq); +struct iosapic_rte_info *rte; + + low32 = iosapic_intr_info[vec].low32 |=IOSAPIC_MASK ; +list_for_each_entry (rte, &iosapic_intr_info[vec].rtes, + rte_list) { +iosapic_write (rte->addr, +IOSAPIC_RTE_LOW (rte->rte_index), low32); +iosapic_eoi (rte->addr, vec); + } +} +#endif +static void mask_irq (unsigned int irq) {
arch/ia64/kernel/machine_kexec.c +131 -0
131 lines not on this page · raw message
arch/ia64/kernel/Makefile +1 -0
@@ -28,6 +28,7 @@ obj-$(CONFIG_IA64_CYCLONE) += cyclone.o obj-$(CONFIG_CPU_FREQ) += cpufreq/ obj-$(CONFIG_IA64_MCA_RECOVERY) += mca_recovery.o obj-$(CONFIG_KPROBES) += kprobes.o jprobes.o +obj-$(CONFIG_KEXEC) += machine_kexec.o relocate_kernel.o crash.o obj-$(CONFIG_IA64_UNCACHED_ALLOCATOR) += uncached.o obj-$(CONFIG_AUDIT) += audit.o mca_recovery-y += mca_drv.o mca_drv_asm.o
arch/ia64/kernel/relocate_kernel.S +490 -0
490 lines not on this page · raw message
arch/ia64/kernel/setup.c +45 -0
63 lines not on this page · raw message
arch/ia64/kernel/smp.c +46 -1
77 lines not on this page · raw message
include/asm-ia64/kexec.h +40 -0
@@ -0,0 +1,40 @@ +#ifndef _ASM_IA64_KEXEC_H +#define _ASM_IA64_KEXEC_H + + +/* Maximum physical address we can use pages from */ +#define KEXEC_SOURCE_MEMORY_LIMIT (-1UL) +/* Maximum address we can reach in physical address mode */ +#define KEXEC_DESTINATION_MEMORY_LIMIT (-1UL) +/* Maximum address we can use for the control code buffer */ +#define KEXEC_CONTROL_MEMORY_LIMIT TASK_SIZE + +#define KEXEC_CONTROL_CODE_SIZE (8192 + 8192 + 4096) + +/* The native architecture */ +#define KEXEC_ARCH KEXEC_ARCH_IA_64 + +#define MAX_NOTE_BYTES 1024 + +#define pte_bits 3 +#define vmlpt_bits (impl_va_bits - PAGE_SHIFT + pte_bits) +#define POW2 (n) (1ULL << (n)) + +DECLARE_PER_CPU (u64, ia64_mca_pal_base); +const extern unsigned int relocate_new_kernel_size; +volatile extern long kexec_rendez; +extern void relocate_new_kernel (unsigned long ,unsigned long , +struct ia64_boot_param *,unsigned long ); +extern void kexec_fake_sal_rendez (void *start,unsigned long wake_up, +unsigned long pal_base); +static inline void +crash_setup_regs (struct pt_regs *newregs,struct pt_regs *oldregs) +{ +} +extern struct resource efi_memmap_res; +extern struct resource boot_param_res; +extern void kdump_smp_send_stop (void ); +extern void kdump_disable_irq (unsigned int irq); +extern void crash_save_this_cpu (void ); + +#endif /* _ASM_IA64_KEXEC_H */
include/asm-ia64/machvec_hpzx1.h +2 -0
@@ -34,4 +34,6 @@ extern ia64_mv_dma_mapping_error sba_dma#define platform_dma_supported sba_dma_supported#define platform_dma_mapping_error sba_dma_mapping_error +extern void ioc_iova_disable (void ); +#endif /* _ASM_IA64_MACHVEC_HPZX1_h */
include/asm-ia64/meminit.h +2 -1
@@ -15,11 +15,12 @@* - initrd (optional) * - command line string * - kernel code & data +* - crash dumping code reserved region * - Kernel memory map built from EFI memory map * * More could be added if necessary */ -#define IA64_MAX_RSVD_REGIONS 6 +#define IA64_MAX_RSVD_REGIONS 7struct rsvd_region {unsigned long start;/* virtual address of beginning of element */
include/asm-ia64/smp.h +3 -0
@@ -128,6 +128,9 @@ extern void smp_send_reschedule (int cpuextern void lock_ipi_calllock (void );extern void unlock_ipi_calllock (void );extern void identify_siblings (struct cpuinfo_ia64 *); +#ifdef CONFIG_KEXEC +extern void kexec_stop_this_cpu (void *); +#endif #else
kernel/irq/manage.c +0 -1
@@ -475,4 +475,3 @@ int request_irq(unsigned int irq,return retval; }EXPORT_SYMBOL (request_irq); -
Quoted 10 lines · Bob Montgomery
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
Contrary to expectations, my experience with this patch on a 2.6.18-rc4 kernel is that kexec -l, kexec -e is now working without my adding any delays to mptscsih, and the kexec -p, echo c >/proc/sysrq-trigger case hangs.
Quoted 8 lines
My "got here" printk's on the console indicate:
SysRq : Trigger a crashdump
machine_crash_shutdowndevice_shootdownmachine_kexectype: 1And then it hangs.
Hi,
I got it further down.
Quoted 6 lines
My test system: hp A6870A server rx2600
Quoted 1 line
From
/proc/iomem:04a1f000-3f5e3fff : System RAM
10000000-17ffffff : Crash kernel
My test system is a zx6000.
Here is from /proc/iomem:
04aaf000-3e417fff : System RAM
10000000-17ffffff : Crash kernel
I used 'make tiger_defconfig', then set on CONFIG_KEXEC, CONFIG_CRASH_DUMP, and CONFIG_PROC_VMCOR.
Here are shown on console:
SysRq : Trigger a crashdump
kernel BUG at kernel/irq/migration.c:39!
bash[4846]: bugcheck! 0 [1]
Modules linked in: radeon drm agpgart nfs lockd sunrpc binfmt_misc
dm_mirror dmi
Pid: 4846, CPU 0, comm: bash
psr : 00001010085a2010 ifs : 800000000000038b ip : [<a0000001000e2520>]
Notdip is at move_native_irq+0x1a0/0x360unat: 0000000000000000 pfs : 000000000000038b rsc : 0000000000000003
rnat: 0000000000000000 bsps: 0000000000000000 pr : 000000000059a999
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr: 0009804c8a70033f csd : 0000000000000000 ssd : 0000000000000000
b0 : a0000001000e2520 b6 : a0000001000bc7c0 b7 : a00000010004ec60 f6 : 1003e00000000000000a0 f7 : 1003e20c49ba5e353f7cf f8 : 1003e00000000000004e2 f9 : 1003e000000000fa00000 f10 : 1003e000000003b9aca00 f11 : 1003e431bde82d7b634db r1 : a000000100b663c0 r2 : 0000000000001000 r3 : a000000100910e88 r8 : 000000000000002c r9 : 00000000000000fd r10 : a00000010097c750 r11 : 0000000000000000 r12 : e00000001c157c60 r13 : e00000001c150000 r14 : 0000000000004000 r15 : a000000100910e88 r16 : a000000100910e90 r17 : 0000000000004000 r18 : 0000000000000000 r19 : 0000000000000001 r20 : a000000100985f98 r21 : a000000100985f98 r22 : 0000000000000004 r23 : 0000000000000000 r24 : e00000003f3e0f64 r25 : 0000000000000000 r26 : e00000003f3e0f6c r27 : e00000003f3e0f50 r28 : e00000003f3e0008 r29 : 0000000000000000 r30 : 0000000000000000 r31 : 0000000000000000
Call Trace:
[<a0000001000138e0>] show_stack+0x40/0xa0
spà0000001c1577f0 bspà0000001c1514a8
[<a000000100014540>] show_regs+0x840/0x880
spà0000001c1579c0 bspà0000001c151450
[<a000000100036400>] die+0x1c0/0x2c0
spà0000001c1579c0 bspà0000001c151408
[<a000000100036550>] die_if_kernel+0x50/0x80
spà0000001c1579e0 bspà0000001c1513d0
[<a000000100037c50>] ia64_bad_break+0x270/0x4a0
spà0000001c1579e0 bspà0000001c1513a8
[<a00000010000c320>] ia64_leave_kernel+0x0/0x280
spà0000001c157a90 bspà0000001c1513a8
[<a0000001000e2520>] move_native_irq+0x1a0/0x360
spà0000001c157c60
bspà0000001c151350
[<a00000010004ec90>] iosapic_end_level_irq+0x30/0xe0
spà0000001c157c60
bspà0000001c151330
[<a00000010005d4e0>] machine_crash_shutdown+0x120/0x220
spà0000001c157c60
bspà0000001c151300
[<a0000001000d5890>] crash_kexec+0x70/0xc0
spà0000001c157c60
bspà0000001c1512e0
[<a00000010045ee00>] sysrq_handle_crashdump+0x20/0x40
spà0000001c157e20
bspà0000001c1512b8
[<a00000010045efe0>] __handle_sysrq+0x160/0x300
spà0000001c157e20
bspà0000001c151268
[<a0000001001ba0b0>] write_sysrq_trigger+0xb0/0xe0
spà0000001c157e20
bspà0000001c151238
[<a00000010012fad0>] vfs_write+0x1b0/0x340
spà0000001c157e20
bspà0000001c1511e0
[<a000000100130750>] sys_write+0x70/0xe0
spà0000001c157e20
bspà0000001c151168
[<a00000010000c180>] ia64_ret_from_syscall+0x0/0x20
spà0000001c157e30
bspà0000001c151168
[<a000000000010620>] __kernel_syscall_via_break+0x0/0x20
spà0000001c158000 bspà0000001c151168
<4>hda: lost interrupt
mptscsih: ioc0: attempting task abort! (scà0000003e42ba00) sd 0:0:0:0:
command: cdb[0]=0x4d: 4d 00 6f 00 00 00 00 00 04 00
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: task abort: SUCCESS (scà0000003e42ba00)
mptscsih: ioc0: attempting task abort! (scà0000003e42ba00) sd 0:0:0:0:
command: cdb[0]=0x0: 00 00 00 00 00 00
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: task abort: SUCCESS (scà0000003e42ba00)
mptscsih: ioc0: attempting task abort! (scà0000003e429c00) sd 0:0:0:0:
command: cdb[0]=0x0: 00 00 00 00 00 00
mptbase: Initiating ioc0 recovery
mptscsih: ioc0: task abort: SUCCESS (scà0000003e429c00)
mptscsih: ioc0: attempting task abort! (scà0000003e42bd00) sd 0:0:0:0:
command: cdb[0]=0x0: 00 00 00 00 00 00
ide-cd: cmd 0x3 timed out
hda: lost interrupt
...
Quoted 5 lines · Zou Nan hai
Quoted 1 line
...
Jay,
Thanks very much, please try the following updated patch which
simplify thedevice_shootdowncode.
My system continues to hang with the new patch. I can get a printk just before jumping to the new code in machine_kexec. We're going to try hooking up the ITP now.
Bob Montgomery
Quoted 11 lines · Zou Nan hai
Quoted 8 lines · Jay Lan
Quoted 6 lines · Bob Montgomery
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
Quoted 9 lines
Quoted 1 line
...
Jay,
Thanks very much, please try the following updated patch which
simplify thedevice_shootdowncode.Signed-off-by Zou Nan hai <[email protected]>
Since you did not indicate version number different from the previous one, i would call it 2.6.18-rc4-v2.
With this version, the crash dump kernel tried to boot... and failed at "exec of init()" for "No such file or directory".
Here is the output at the console:
SysRq : Trigger a crashdump
Linux version 2.6.18-rc4 ([email protected]) (gcc version 4.1.0 200603046
Ignoring memory below 256MB
Ignoring memory above 384MB
EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCD0
PCDP: v0 at 0x3fb2c000
Explicit "console="; ignoring PCDPefi_memmap start 17fd4000 17fd47e0
Initial ramdisk at: 0xe000000017e6c000 (1420052 bytes)
SAL 3.1: HP version 2.31
SAL Platform features: None
SAL: AP wakeup using external interrupt vector 0xff
No logical to physical processor mapping available
ACPI: Local APIC address c0000000fee00000
GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
2 CPUs available, 2 CPUs total
MCA related initialization done
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists. Total pages: 8191
Kernel command line: root=LABEL=/ init 1 irqpoll console=ttyS0,38400n8 maxcpus=M
Misrouted IRQ fixup and polling support enabled
This may significantly impact system performance
PID hash table entries: 512 (order: 9, 4096 bytes)
irq 51, desc: a00000010082e380, depth: 1, count: 0, unhandled: 0 ->handle_irq(): a0000001007bf9c0, __stop___param+0x3a70/0x1c0b0 ->chip(): a000000100946468, no_irq_chip+0x0/0x80
->action(): 0000000000000000
IRQ_DISABLED set
Unexpected irq vector 0x33 on CPU 0!
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 3, 131072 bytes) Inode-cache hash table entries: 8192 (order: 2, 65536 bytes) Placing software IO TLB between 0x11124000 - 0x15124000
Memory: 46144k/131056k available (6965k code, 84912k reserved, 2751k data, 256k)
McKinley Errata 9 workaround not needed; disabling it Mount-cache hash table entries: 1024
ACPI: Core revision 20060707
Boot processor id 0x0/0x0
Brought up 1 CPUs
Total of 1 processors activated (1945.60 BogoMIPS). migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 1376kB freed
DMI 2.3 present.
NET: Registered protocol family 16
ACPI: bus type pci registered
ACPI: Interpreter enabled
ACPI: Using IOSAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
ACPI: PCI Root Bridge [PCI1] (0000:20)
ACPI: PCI Root Bridge [PCI2] (0000:40)
ACPI: PCI Root Bridge [PCI3] (0000:60)
ACPI: PCI Root Bridge [PCI4] (0000:80)
ACPI: PCI Root Bridge [PCI6] (0000:c0)
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
GSI 34 (edge, high) -> CPU 0 (0x0000) vector 49
GSI 35 (edge, high) -> CPU 0 (0x0000) vector 50
pnp: PnP ACPI: found 10 devices
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: -1, 8192 bytes) TCP established hash table entries: 4096 (order: 2, 65536 bytes) TCP bind hash table entries: 2048 (order: 1, 32768 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
perfmon: version 2.0 IRQ 238
perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits) PAL Information Facility v0.5
perfmon: added sampling format default_formatperfmon_default_smpl: default_format v2.0 registered
Total HugeTLB memory allocated, 0
SGI XFS with large block/inode numbers, no debug enabled Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
EFI Time Services Driver v0.4
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled 00:04: ttyS0 at MMIO 0xff5e0000 (irq = 49) is a 16550A
00:05: ttyS1 at MMIO 0xff5e2000 (irq = 50) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Intel(R) PRO/1000 Network Driver - version 7.1.9-k4
Copyright (c) 1999-2006 Intel Corporation.
tg3.c:v3.64 (July 31, 2006)
GSI 29 (level, low) -> CPU 0 (0x0000) vector 51
ACPI: PCI Interrupt 0000:20:02.0[A] -> GSI 29 (level, low) -> IRQ 51
eth0: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)] (PCI:66MHz:64-bit) 10/100/e
eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[0]
eth0: dma_rwctrl[76ff2d0f] dma_mask[64-bit]
netconsole: not configured, aborting
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
CMD649: IDE controller at PCI slot 0000:00:02.0
GSI 21 (level, low) -> CPU 0 (0x0000) vector 52
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 21 (level, low) -> IRQ 52
CMD649: chipset revision 2
CMD649: 100% native mode on irq 52
ide0: BM-DMA at 0x0d40-0x0d47, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x0d48-0x0d4f, BIOS settings: hdc:pio, hdd:piohda: DV-28E-C, ATAPI CD/DVD-ROM drive
ide0 at 0xd58-0xd5f,0xd66 on irq 52
hda: ATAPI 24X DVD-ROM drive, 256kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
Fusion MPT base driver 3.04.01
Copyright (c) 1999-2005 LSI Logic Corporation
Fusion MPT SPI Host driver 3.04.01
GSI 27 (level, low) -> CPU 0 (0x0000) vector 53
ACPI: PCI Interrupt 0000:20:01.0[A] -> GSI 27 (level, low) -> IRQ 53
mptbase: Initiating ioc0 bringup
ioc0: 53C1030: Capabilities={Initiator,Target}
scsi0 : ioc0: LSI53C1030, FwRev032300h, Ports=1, MaxQ%5, IRQS
Vendor: HP 73.4G Model: MAS3735NC Rev: HPC3
Type: Direct-Access ANSI SCSI revision: 03
target0:0:0: Beginning Domain Validation
target0:0:0: Ending Domain Validation
target0:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RTI PCOMP (6.25
ns, offse)
SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write through w/ FUA
SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write through w/ FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: Attached scsi disk sda
GSI 28 (level, low) -> CPU 0 (0x0000) vector 54
ACPI: PCI Interrupt 0000:20:01.1[B] -> GSI 28 (level, low) -> IRQ 54
mptbase: Initiating ioc1 bringup
ioc1: 53C1030: Capabilities={Initiator,Target}
scsi1 : ioc1: LSI53C1030, FwRev032300h, Ports=1, MaxQ%5, IRQT Fusion MPT FC Host driver 3.04.01
Fusion MPT misc device (ioctl) driver 3.04.01
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor,220)
USB Universal Host Controller Interface driver v3.0
usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
EFI Variables Facility v0.08 2004-May-17
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 256kB freed
Red Hat nash version 5.0.32 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Creating root device.
Mounting root filesystem.EXT3-fs: INFO: recovery required on readonly filesyste.
EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode. Setting up other filesystems.
Setting up new root fs
Kernel panic - not syncing: Attempted to kill init!
Switching to ne w root and running init. unmounting old /dev
unmounting old /proc
unmounting old /sys
WARNING: can't access
exec of init () failed!!!: No such file or directory
Regards,
- jay
Quoted 9 lines · Keshavamurthy Anil S
Quoted 8 lines · Bob Montgomery
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
Contrary to expectations, my experience with this patch on a 2.6.18-rc4 kernel is that kexec -l, kexec -e is now working without my adding any delays to mptscsih, and the kexec -p, echo c >/proc/sysrq-trigger case hangs.
Quoted 6 lines
Quoted 3 lines
# cat /proc/cmdline BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz-2.6.18-rc4-bobm root=/dev/sda4 raid=noautodetect crashkernel8M@256M panic=1 roCan you change crashkernelQ2M@256 and try
kexec -p, echo c >/proc/sysrq-triggercase.
04a40000-3f5e3fff : System RAM
10000000-2fffffff : Crash kernel
bobm@urlp2:~$ cat /proc/cmdline root=/dev/sda4 crashkernelQ2M@256M panic=1 ro
# kexec -p vmlinux.strip --append="root=/dev/sda4 maxcpus=1 panic=1 irqpoll ro"
# echo c >/proc/sysrq-trigger
Still hangs with no indication on the console after my printk("bye\n") just before the br.call at the end of machine_kexec.
Bob M.
Quoted 11 lines · Bob Montgomery
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
Contrary to expectations, my experience with this patch on a 2.6.18-rc4 kernel is that kexec -l, kexec -e is now working without my adding any delays to mptscsih, and the kexec -p, echo c >/proc/sysrq-trigger case hangs.
# cat /proc/cmdline BOOT_IMAGE=scsi0:/EFI/debian/boot/vmlinuz-2.6.18-rc4-bobm root=/dev/sda4 raid=noautodetect crashkernel8M@256M panic=1 ro
Can you change crashkernelQ2M@256 and try
kexec -p, echo c > /proc/sysrq-trigger case.
Quoted 8 lines · Jay Lan
Quoted 7 lines · Zou Nan hai
Quoted 5 lines · Jay Lan
Quoted 3 lines · Bob Montgomery
On Mon, 2006-08-14 at 14:47 +0800, Zou Nan hai wrote:
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines
Quoted 3 lines
Quoted 1 line
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
WARNING: can't access
exec of init () failed!!!: No such file or directory
Did you pass the correct kernel parameter to --append? It seems that root filesystem was not able to be mounted.
Quoted 2 lines
Regards,
- jay
Thanks
Zou Nan hai
Quoted 7 lines · Bob Montgomery
Quoted 5 lines · Zou Nan hai
Quoted 1 line
...
Jay,
Thanks very much, please try the following updated patch which
simplify thedevice_shootdowncode.
Quoted 5 lines
My system continues to hang with the new patch. I can get a printk just before jumping to the new code in
machine_kexec. We're going to try hooking up the ITP now.Bob Montgomery
If you are not seeing "I am in purgatory" in console, that probably
means crash kernel segments and purgatory code was copied into some wrong physical address.
Can you check the crashkernel="..." parameter
Thanks
Zou Nan hai
Quoted 10 lines · Zou Nan hai
Quoted 1 line · Bob Montgomery
On Tue, 2006-08-15 at 08:47 +0800, Zou Nan hai wrote:
If you are not seeing "I am in purgatory" in console, that probably
means crash kernel segments and purgatory code was copied into some wrong physical address.Can you check the crashkernel="..." parameter
Thanks
Today, we have had success by changing the configuration of our kernels from zx1 to tiger. Now we'll try to figure out what it is about the zx1 config parameters that causes the crash_kexec path to break.
Bob Montgomery
Quoted 8 lines · Zou Nan hai
Quoted 2 lines · Jay Lan
Zou Nan hai wrote:
Did you pass the correct kernel parameter to --append? It seems that root filesystem was not able to be mounted.
I finally was able to boot up the crash dump kernel. Unfortunately the 'cp vmcore /var/tmp' crashed due to out of memory. :(
The memory on the regular kernel showed:
[root@holism tmp]# free
total used free shared buffers cached
Mem: 805312 443520 361792 0 36288 295936 -/+ buffers/cache: 111296 694016
Swap: 6143968 0 6143968
and the memory on the crash dump kernel showed:
[root@holism tmp]# free
total used free shared buffers cached
Mem: 47776 45952 1824 0 1056 11856 -/+ buffers/cache: 33040 14736 Swap: 6143968 54720 6089248
It came down from 805312 k to 47776 k with only 1824 free. How much memory do i need to do a 'cp /proc/vmcore /var/tmp'?
Thanks,
- jay
Quoted 11 lines · Bob Montgomery
Quoted 9 lines · Zou Nan hai
Quoted 1 line · Bob Montgomery
On Tue, 2006-08-15 at 08:47 +0800, Zou Nan hai wrote:
If you are not seeing "I am in purgatory" in console, that probably
means crash kernel segments and purgatory code was copied into some wrong physical address.
Quoted 7 lines
Quoted 2 lines
Can you check the crashkernel="..." parameter
ThanksToday, we have had success by changing the configuration of our kernels from zx1 to tiger. Now we'll try to figure out what it is about the zx1 config parameters that causes the
crash_kexecpath to break.
I had problem with the zx1 defconfig on my zx6000 also. Since i recalled Horms said he was successful with tiger config so i switched. :)
- jay
Quoted 7 lines
Bob Montgomery
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 7 lines · Jay Lan
Quoted 5 lines · Zou Nan hai
Quoted 2 lines · Jay Lan
Zou Nan hai wrote:
Quoted 7 lines
Quoted 3 lines
Did you pass the correct kernel parameter to --append? It seems that root filesystem was not able to be mounted.
I finally was able to boot up the crash dump kernel. Unfortunately the 'cp vmcore
/var/tmp' crashed due to out of memory. :(
Incresing boot parameter from 128M@256M to 256M@256M fixed the problem. :)
Thanks you, Nanhai!
- jay
Quoted 2 lines
Quoted 6 lines · Jay Lan
Quoted 5 lines · Zou Nan hai
Quoted 2 lines · Jay Lan
Zou Nan hai wrote:
Quoted 7 lines
Quoted 3 lines
Did you pass the correct kernel parameter to --append? It seems that root filesystem was not able to be mounted.
I finally was able to boot up the crash dump kernel. Unfortunately the 'cp vmcore
/var/tmp' crashed due to out of memory. :(
Why did the crash occur? Was the disk full? Otherwise, the cached pages _should_ have been written to disk.
Do you have a console log?
Quoted 27 lines
The memory on the regular kernel showed:
[root@holism tmp]# free
total used free shared buffers cachedMem: 805312 443520 361792 0 36288 295936 -/+ buffers/cache: 111296 694016Swap: 6143968 0 6143968
and the memory on the crash dump kernel showed:
[root@holism tmp]# free
total used free shared buffers cachedMem: 47776 45952 1824 0 1056 11856 -/+ buffers/cache: 33040 14736 Swap: 6143968 54720 6089248It came down from 805312 k to 47776 k with only 1824 free. How much memory do i need to do a 'cp
/proc/vmcore/var/tmp'?Thanks,
- jay-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 4 lines
Thanks Jack Steiner ([email protected]) 651-683-5302 Principal Engineer SGI - Silicon Graphics, Inc.
Quoted 1 line · Zou Nan hai
This patch is the kexec-kdump patch re-based to 2.6.18-rc4 kernel.
I will post incremental versions of these latest kexec patches, hopefully today. So anyone who is intrested, please be a little patient.
Signature · 3 lines
Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/
Quoted 9 lines · Bob Montgomery
Quoted 8 lines · Zou Nan hai
Quoted 1 line · Bob Montgomery
On Tue, 2006-08-15 at 08:47 +0800, Zou Nan hai wrote:
If you are not seeing "I am in purgatory" in console, that probably
means crash kernel segments and purgatory code was copied into some wrong physical address.
Quoted 8 lines
Quoted 2 lines
Can you check the crashkernel="..." parameter
ThanksToday, we have had success by changing the configuration of our kernels from zx1 to tiger. Now we'll try to figure out what it is about the zx1 config parameters that causes the
crash_kexecpath to break.Bob Montgomery
Hi Bob,
Could you take a look at the ioc_iova_disable code in crash path?
That piece of code is from HP.
It will only execute if CONFIG_IA64_HP_ZX1 is defined.
I don't have much knowledge of the I/O MMU stuff on HP machines....
Thanks
Zou Nan hai
Quoted 8 lines · Jack Steiner
Quoted 1 line · Jay Lan
Why did the crash occur? Was the disk full? Otherwise, the cached pages _should_ have been written to disk.
Do you have a console log?
Hi Jack,
I reserved insufficient memory for the crash dump kernel. Once i increased from 128M to 256M, the problem went away.
Thanks,
- jay
oom-killer: gfp_mask=0x200d2, order=0
Call Trace:
[<a0000001000138e0>] show_stack+0x40/0xa0
spà00000015d57a40 bspà00000015d514a0
[<a000000100013970>] dump_stack+0x30/0x60
spà00000015d57c10 bspà00000015d51488
[<a0000001000eb000>] out_of_memory+0x60/0x3a0
spà00000015d57c10 bspà00000015d51448
[<a0000001000eeb50>] __alloc_pages+0x3d0/0x520
spà00000015d57c20 bspà00000015d513d0
[<a0000001000e65d0>] generic_file_buffered_write+0x310/0xd00
spà00000015d57c30 bspà00000015d512f0
[<a0000001000e7620>] __generic_file_aio_write_nolock+0x660/0x740
spà00000015d57cc0 bspà00000015d51280
[<a0000001000e77f0>] generic_file_aio_write+0xf0/0x200
spà00000015d57d30 bspà00000015d51220
[<a0000001002343c0>] ext3_file_write+0x60/0x200
spà00000015d57d40 bspà00000015d511e0
[<a00000010012e470>] do_sync_write+0x170/0x1e0
spà00000015d57d40 bspà00000015d511a0
[<a00000010012fb30>] vfs_write+0x1b0/0x340
spà00000015d57e20 bspà00000015d51150
[<a0000001001307b0>] sys_write+0x70/0xe0
spà00000015d57e20 bspà00000015d510d8
[<a00000010000c180>] ia64_ret_from_syscall+0x0/0x20
spà00000015d57e30 bspà00000015d510d8
[<a000000000010620>] __kernel_syscall_via_break+0x0/0x20
spà00000015d58000 bspà00000015d510d8