Sigwinch appears to trigger a panic in 2.6.14.7. Here’s the GDB backtrace

 

#0  0xffffe410 in ?? ()

#1  0x0806d53d in stop () at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/os-Linux/tt.c:67

#2  0x0805dd98 in panic_waitonerr (self=0x82394e8, unused1=0, unused2=0x82716c0) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/kernel/um_arch.c:523

#3  0x0808655a in notifier_call_chain (n=0xfffffdfc, val=0, v=0x82375c0) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/kernel/sys.c:179

#4  0x0807803c in panic (fmt=0x81f6bdc "BUG!") at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/kernel/panic.c:97

#5  0x08096201 in ack_none (irq=10) at hardirq.h:22

#6  0x080962e0 in __do_IRQ (irq=136541632, regs=0x8238fcc) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/kernel/irq/handle.c:134

#7  0x0805948f in do_IRQ (irq=-516, regs=0xa34ff4) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/kernel/irq.c:374

#8  0x0805d60e in winch (sig=28, regs=0x8238fcc) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/kernel/trap.c:246

#9  0x080709a6 in sig_handler_common_skas (sig=28, sc_ptr=0x805d600) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/os-Linux/skas/trap.c:52

#10 0x0806cb27 in sig_handler (sig=28) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/os-Linux/signal.c:61

#11 <signal handler called>

#12 0x0804f7c6 in __alloc_bootmem_core (bdata=0x823eec0, size=6291488, align=32, goal=151089152, limit=136541632) at string.h:373

#13 0x0804fd95 in __alloc_bootmem_node_limit (pgdat=0x0, size=6291488, align=32, goal=0, limit=0) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/mm/bootmem.c:418

#14 0x0805035b in alloc_node_mem_map (pgdat=0x823eec0) at bootmem.h:134

#15 0x080503af in free_area_init_node (nid=0, pgdat=0x823eec0, zones_size=0x8237bd0, node_start_pfn=0, zholes_size=0x0) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/mm/page_alloc.c:2007

#16 0x080503d7 in free_area_init (zones_size=0x8237bd0) at mem.h:19

#17 0x0805972f in paging_init () at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/kernel/mem.c:228

#18 0x0804d245 in setup_arch (cmdline_p=0x0) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/kernel/um_arch.c:555

#19 0x08049481 in start_kernel () at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/init/main.c:464

#20 0x0805e55a in start_kernel_proc (unused=0x0) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/kernel/skas/process_kern.c:173

#21 0x0806c148 in run_kernel_thread (fn=0x805e530 <start_kernel_proc>, arg=0x0, jmp_ptr=0x8234000) at /ccase/wrlinux/build/mxs_cm_t0/build/linux-2.6.14-cgl/arch/um/os-Linux/process.c:285

#22 0x0805e24c in new_thread_handler (sig=10) at thread_info.h:49

#23 <signal handler called>

#24 0xffffe410 in ?? ()

(gdb)

 

Control ends up in ack_bad_irq() in asm-um/hardirq.h:

 

static inline void ack_bad_irq(unsigned int irq)

{

                printk(KERN_ERR "unexpected IRQ %02x\n", irq);

                BUG();

}

 

Did the correct handler fail to get assigned, or should sigwinch have been blocked?

 

James T. Bradshaw

Firmware Engineer

Enterasys Networks

50 Minuteman Rd.

Andover, MA 01810

USA

Tel. (978) 684-1544