!!!DO NOT DO THIS ON A PRODUCTION IMAGE!!!
This is probably a know issue, but thought some of you more sadistic types
that have never seen one, might like to see a pretty little kernel OOPs.
(This is a fairly lame one though...)
Just modprobe any of the dasd_*_mod disciplines and then rmmod it. Now
enter "cat /proc/s390dbf/dasd/sprintf" and look on your console or log.
You should see something like this:
Unable to handle kernel pointer dereference at virtual kernel address
0000000004
93f000
Oops: 0011
CPU: 0 Tainted: P
Process cat (pid: 3652, task: 00000000025b4000, ksp: 00000000025b7e80)
Krnl PSW : 0700200180000000 00000000002e6d74
Krnl GPRS: 000000000493f678 0000000001f1d046 0000000001f1d047
00000000ffffffff
000000000493f3e0 00000000025b7b80 0000000000000000
0000000001f1d047
00000000025b7b80 0000000001f1d047 0000000101f1d045
0000000002581330
0000000001f1d047 00000000003031d0 00000000025b7a40
00000000025b7978
Krnl ACRS: 00000000 00000000 00000000 00000000
00000001 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
Krnl Code: bf 21 40 00 a7 84 00 1d 18 12 54 10 d0 00 a7 1e 00 25 a7 84
Call Trace: [<00000000002e75f6>] [<00000000002e766c>] [<000000000010df66>]
[<000000000010c318>] [<000000000010c406>] [<000000000015f926>]
[<00000000001050f2>]
Cool huh? Now for even more fun, use the "Call Trace" and your
"/boot/System.map" to track down where the problem occurred.
I know, I know...I need a life!!! :-D
Leland
