Leland, Not for me. I issued the command, and it worked just fine. No errors in dmesg or anything.
# cat /proc/s390dbf/dasd/sprintf 00 01055273287:534983 0 - 00 00212336 debug area created 00 01055273287:535076 1 - 00 002122f6 Registered successfully to major no 94 00 01055273287:535131 1 - 00 001096e8 DIAG discipline initializing 00 01055273287:558783 1 - 00 002121ae Registered DIAG discipline successfully 00 01055273287:558828 1 - 00 00100764 ECKD discipline initializing 00 01055273287:579826 1 - 00 000fa714 waiting for responses... 00 01055273287:614369 1 - 00 0010074e We are interested in: CU 3880/00 00 01055273287:614418 1 - 00 0010074e We are interested in: CU 3990/00 00 01055273287:614468 1 - 00 0010074e We are interested in: CU 2105/00 00 01055273287:614520 1 - 00 0010074e We are interested in: CU 9343/00 00 01055273287:614574 1 - 00 00212198 Registered ECKD discipline successfully 00 01055273287:614627 1 - 00 00108764 FBA discipline initializing 00 01055273287:614697 1 - 00 0010874e We are interested in: Dev 9336/00 @ CU 6310/00 00 01055273287:614899 1 - 00 0010874e We are interested in: Dev 3370/00 @ CU 3880/00 00 01055273287:614914 1 - 00 00212182 Registered FBA discipline successfully 00 01055273287:614928 1 - 00 00211fec initialization finished 00 01055305585:232606 1 - 00 000fc286 /proc/dasd/devices: '' What version of the kernel are you running? Mark Post -----Original Message----- From: Lucius, Leland [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2003 5:51 PM To: [EMAIL PROTECTED] Subject: Any of you not seen a kernel OOPs wanna see one? !!!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
