Specifications

D
evice Driver Programming
15-12
CPU 1 breakpoint
00124808 [00124808] gdread+1c %*48000095 bl gdsize
CPU 0 halted
001baf5c [001baf5c] idle+84 % 80700014 lwz r3,0x14(r16)
#1>
#1>qs
sp --------- KERNEL STACK ---------
029c4140 gdread() at 124808(gdread+1c)
029c4190 spec_read() at c6908(spec_read+248)
029c4210 read() at 469bc(read+1ac)
029c42a0 systrap() at 204728(systrap+378)
029c4400 process_trapret() at 20bdb8(process_trapret)
#1>
System Panic 15
The scenario presented in this section shows the probable result of a bug in the device
driver that is being tested. Normally a system panic, which causes memory to be dumped,
occurs. You can later analyze the dump by using /usr/sbin/crash (see
crash(1M)).
Note that if a breakpoint is set in the panic routine, the fault can be analyzed directly
before a dump occurs. This procedure can be quicker than dumping, rebooting, and then
analyzing the crash.
00:
00: PANIC: kernel-mode address fault on kernel address 0x00000060
00:
00:
00: Dumping to dev 01980001 (d_dump=00126404)
00: Memory extent 0 to byte offset 0x04DC0000
00:
00: gd0 (hsa8 drive 0) : Resetting controller
00: dump succeeded
#0>fb
Reset Backplane
Initialize Interrupts
Set Run Mode
CPU 0 CPU 1
dsk(a,0,0,0)/.
dsk(a,0,0,0)/boot
NH Boot Loader
Boot
: /stand/unix
2997340+626016+2768732 start 0xE000
symbol table loaded
NightHawk Power_UNIX Release 2.1
egl0 at VME address FFFF0800
pg0 at VME address FFFF0200
rtc0 at address 9C000000
00:
00: The system is coming up. Please wait.