Comment 74 for bug 818177

Quoting Steve Langasek (<email address hidden>):
> Serge,
>
> Picking that log apart, I see one worker thread (pid 94) not exiting
> cleanly, whereas all the others do. No clear indication of why this
> worker would have failed to exit since its own log output shows it
> completely processing an event (seq 1072) and doesn't show it picking up
> another one; but we're definitely left with references to the worker,
> which is why we see the 'worker exit' message without the 'worker
> cleaned up' message (and why the worker list is never empty).

Will do. Right now I'm trying one more time to print out the worker info.

> Could you do a test that would correlate this udev output with a 'ps
> -ef' at the end of scripts/init-bottom/udev? It doesn't look to me like
> the output from the two tests we have here match in the slightest - one
> reports all worker threads exited, the other shows dozens of processes
> still running...

Are you sure, though? Some of the output from my other test looked garbled,
I'm wondering whether the ps -ef output simply got cut such that the main
worker thread wasn't listed.

> Could you (and others) also try the udev from ppa:vorlon/ppa, and see if
> this makes a difference in bootability? This adds the pkill after
> udevadm control --exit. If it works, we know udevd is losing track of
> its worker threads...

(Will try)