Quoting James Hunt (<email address hidden>):
> @Serge: following on from comments #54 and #57 - could you possibly add
> a line after the "udevadm control --exit" so we can see the ps output at
> that point?
>
> echo "XXX: POST udevd: ps=`ps -ef`, /dev=`ls -l /dev`" > /dev/kmsg
I already had that:
!# Stop udevd, we'll miss a few events while we run init, but we catch up
!udevadm control --exit
!
!# Move /dev to the real filesystem
!mount -n -o move /dev ${rootmnt}/dev
!
!ps -ef > /run/initramfs/udevps.log 2>&1
!ps -ef > /dev/.initramfs/udevps.log 2>&1
That file however did not show up in the cases of the hang.
Is the scripts/init-bottom/udev file itself being killed?
Quoting James Hunt (<email address hidden>):
> @Serge: following on from comments #54 and #57 - could you possibly add
> a line after the "udevadm control --exit" so we can see the ps output at
> that point?
>
> echo "XXX: POST udevd: ps=`ps -ef`, /dev=`ls -l /dev`" > /dev/kmsg
I already had that:
!# Stop udevd, we'll miss a few events while we run init, but we catch up udevps. log 2>&1 /udevps. log 2>&1
!udevadm control --exit
!
!# Move /dev to the real filesystem
!mount -n -o move /dev ${rootmnt}/dev
!
!ps -ef > /run/initramfs/
!ps -ef > /dev/.initramfs
That file however did not show up in the cases of the hang.
Is the scripts/ init-bottom/ udev file itself being killed?