On Tue, 14 Aug 2012, Neale Ferguson wrote: > An app of ours will link to a disk, bring it online, check its contents, > take it offline, and then detach it. This works pretty well all the time but > on occasion the device gets linked but nothing appears in the /sys tree nor > a udev event generated. I checked the cio_ignore list and there are no > blocks. > > When the device is linked the device end triggers the kernel to determine > what type of device it is: > > CP LINK USERXYZ 21A 1000 RR > DASD 1000 LINKED R/O > -> 00000000003CC874' SSCH B2332000 000000001FE1E540 CC 0 > SCH 0008 DEV 1000 > CPA 1EF9D940 PARM 1EF9DC00 KEY 0 FPI C2 LPM 80 > VDEV 1000 CCW E4200028 1EF9D8B8 > CCW 1EF9D940 E4200028 1EF9D8B8 0000 E4240028 ........ > IDAL 000000011986E8B8 > > But there is no more I/O after that. udev control --log-priority=info > doesn't reveal anything of interest nor does udev monitor --kernel. > > It appears that the kernel has blackballed the device. Are there any > commands I can use to check the situation? Linking the device as a different > virtual address doesn't change the situation. >
vmcp d schib 0008 lscss 0008 mount -t debugfs debugfs /sys/kernel/debug/ cat /sys/kernel/debug/s390dbf/cio_msg/sprintf cat /sys/kernel/debug/s390dbf/cio_trace/hex_ascii Regards, Sebastian ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
