On Friday 01 August 2003 15:02, [EMAIL PROTECTED] wrote: > On Fri, 1 Aug 2003, Andrey Borzenkov wrote: > > no, more likely it is different issues. If /lib/dev-state/log exists - > > remove it (and do not forget updating to teh latest devfsd). > > (Andrey: forget first mail). > If this is true, why does it only happed when he has that card plugged in? > a /lib/dev-state/log would always freeze the system at boot I assume? >
unfortunately, not every time. it happens when there are several tasks doing syslog output at the same time (more than 5) and minilogd tries to exit. This is apparently dependent on which hardware people have and what is run by devfsd for this hardware etc. That said, original devfs deadlock is still valid and needs to be applied. all my devfs fixes are now in 2.6 (either mainstream or -mm). -andrey PS after I have seen module loading by hotplug script failing because it hapened at the same time as depmod -a in rc.sysinit (and depmod -a removes files before recreating them) nothing can surprise me :) > d.
