From mboxrd@z Thu Jan 1 00:00:00 1970 From: md@Linux.IT (Marco d'Itri) Date: Wed, 04 May 2011 15:20:51 +0000 Subject: Re: udev regression from 167 to 168 on notion ink adam Message-Id: <20110504152051.GA24683@bongo.bofh.it> List-Id: References: <809580245.144501.1304521074555.JavaMail.fmail@mwmweb069> In-Reply-To: <809580245.144501.1304521074555.JavaMail.fmail@mwmweb069> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On May 04, Johannes Schauer wrote: > now my question is: how do I debug this? how do I find out The best way to debug this kind of problems is to boot with init=/bin/bash, start a shell on tty2 or a serial port with openvt or getty and then exec /sbin/init. Then you can find out from the second shell what the udevd processes are waiting for. OTOH, I remember that udevadm settle was supposed to print the uevents still queued when the timeout expires, did it stop doing this? -- ciao, Marco