:: The address is not in kernel space. Either you
:: mis{copied,typed} it or
:: it really was wrong. In the latter case it would cause the oops.
Bugger. 0s look very like 8s with ATI VGA... ;-). OK, here we are:
md 0xca02da80
0xca02da80 00000000 00000000 00001000 00000307
0xca02da90 00000000 00000307 0000000c 00001ee8
0xca02daa0 ca0dec20 ca521980 ca02da80 00000000
0xca02dab0 00000000 cb836000 c130efbc c017d9d0
0xca02dac0 cbd86be0 00000000 00000001 ca02dacc
0xca02dad0 ca02dacc 00000000 cb269838 cb553c18
0xca02dae0 00000000 00008e53 00001000 00000308
0xca02daf0 00000000 00000308 00000019 00000000
Make sense?
:: At the kdb prompt, set LOGGING=1. The kdb output is stored in the
:: syslog buffer as well as written to screen, when you type go
:: the syslog
:: data is written to disk. Two problems, the syslog buffer is
:: limited in
:: size and this only works if the kernel can continue and do disk I/O
:: after the oops.
OK, worth a try.
|