On Wednesday 14 June 2006 23:04, Tom Shilson wrote: > > rmmod vmcp > > rm /dev/vmcp > > modprobe vmcp > Yes it does! I have no idea of why, but thank you!
Great. I suspect you had a stale device node. The udev version in SLES9 does not clean up device nodes in a case of crash, z/VM reipl or something similar. Linux does not use the name of device nodes, it only uses the major and minor number. Imagine this scenario: - boot up - load vmcp.ko--> a new device with major 10 and a dynamic minor - udev creates /dev/vmcp with major 10 and dynamic minor - for some reason linux does not shut down cleanly, /dev/vmcp stays - another boot up - load another module with major 10 (misc device) which gets the same minor as the old minor - load vmcp.ko --> a new device with major 10 and a dynamic minor (a different one!) - udev sees that there is already a /dev/vmcp and does not create a new one, but the old device node points to the wrong device. -- Mit freundlichen Grüßen / Best Regards Christian Borntraeger Linux Software Engineer zSeries Linux & Virtualization ---------------------------------------------------------------------- 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
