dmesg and segmentation fault

ARM platform (running in a telnet - not the console):

# uname -a Linux (none) 2.4.21-rmk1-crus1.4.3 #4 Mon Jul 17 11:57:01 MDT 2006 armv4l unknown # .-wgcrash Segmentation fault # dmesg Jul 17 11:57:01 MDT 2006 CPU: Arm920Tid(wb) revision 0 Machine: edb9302 On node 0 totalpages: 8192 zone(0): 22528 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=-dev-ram Relocating machine vectors to 0xffff0000 Calibrating delay loop... 49.40 BogoMIPS . . . wgcrash: unhandled page fault at pc=0x00008568, lr=0x400f14e8 (bad address=0x00000000, code 2055) sp : bffffe50 ip : 00010850 fp : bffffe68 r10: 4014cf70 r9 : 00000000 r8 : 00008520 r7 : 000085fc r6 : 00000001 r5 : 00008590 r4 : bffffe94 r3 : ffffffff r2 : 00000000 r1 : 00031000 r0 : 00000001 Flags: nZCv IRQs on FIQs on Mode USER32 Segment user Control: 717F Table: 045E4000 DAC: 00000015 #

PC platform:

$ uname -a Linux eowyn 2.6.8.1-12mdk #1 Fri Oct 1 12:53:41 CEST 2004 i686 Intel(R) Celeron(R) CPU 2.00GHz unknown GNU-Linux $ .-wgcrash Segmentation fault $ dmesg eth1: link down eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 eth1: Promiscuous mode enabled. . . . eth1: link down eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 eth1: Promiscuous mode enabled. device eth1 entered promiscuous mode device eth1 left promiscuous mode eth1: Promiscuous mode enabled. device eth1 entered promiscuous mode device eth1 left promiscuous mode $

On the ARM, the crash is reported via dmesg and on the console. I ran the above in a telnet window which is why the dump didn't output to the screen, only dmesg. The messages are coming from linux-arch-arm-kernel-traps.c and linux-arch-arm-kernel-process.c for the ARM platform and fom linux-arch-i386-kernel-traps.c on the i386 platform. Both are using printk with no priority specified so I think that means to use the default. If I catproc-sys-kernel-printk both platforms show the same verbosity levels.