On Friday, 07/27/2012 at 11:33 EDT, Sebastian Ott <[email protected]> wrote: > The process of setting the device online involves generic path > verification work done by the Common IO Layer and device specific > online processing done by the device driver (DASD in this case). Once > the DASD driver finished its work and created a block device, userspace > is informed about this via uevents. After that chccwdev returns. The > only thing that's missing now is udev creating a device node and that's > covered via udev settle.
Is it possible that the udev settle timeout is set to zero, preventing it from waiting? (I see that you can set up a udev debug log to see what udev is doing.) Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 [email protected] IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] 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/
