Let's jump right into adb to get some initial information. Data that we use in subsequent adb commands is underlined for visibility. Hiya on s4-413... adb -k vmunix.0 vmcore.0 physmem 3ffd hostname/s _hostname: _hostname: server01 *boottime=Y 1994 Aug 11 10:52:19 *time=Y 1994 Aug 12 11:32:37 *panicstr/s _sizestr+0x89: Memory address alignment $c _panic(0xf8120eb1,0xf86e8cbc,0xffffffff,0x30,0x7c375,0xf7fffdf0) + 6c _trap(0x7, 0xf86e8cbc ,0xffffffff,0x30,0x0,0x0) + 2a0 st_have_window(?) _uiomove(0x0,0x0,0x1000,0x2,0x1002,0x2) + 98 _fifo_rdwr(0xfceaccb0,0xf86e8eac,0x0,0xfceb2525,0x2,0x0) + 5ac _vno_rw(0xf835bac8,0x1,0xf86e8eac,0x1000,0xfceaccb4,0x0) + a4 _rwuio(0xf835bac8,0xf86e8eac,0xf86e8ea4,0x1000,0x1000,0xf86e8eac) + 2b0 _write(0xf86e8fe0,0x20,0xf8114ad0,0xf8114af0,0xf86e9000,0xf8114af0) + 34 _syscall(0xf86e9000) + 3b4 0xf86e8cbc$<regs 0xf86e8cbc: psr pc npc 114000c1 f806f28c f806f290 0xf86e8cc8: y g1 g2 g3 0 f8000000 c30022fd fce07c90 0xf86e8cd8: g4 g5 g6 g7 c f86e9000 f812d000 f812d000 0xf86e8ce8: o0 o1 o2 o3 c00022fd f8064c10 0 c00022fd 0xf86e8cf8: o4 o5 o6 o7 ff84a000 0 f86e8d08 f76a2000 f806f28c/i _fifo_rdwr+0x5ec: ld [%i3], %i3 The failed instruction, ld [%i3], %i3 , generated a memory alignment error. |