On Tue, Jul 21, 2015 at 09:11:57PM +0200, Bastian Blank wrote:
> So the next step could be debugging udev and see what it calls and when.
Please provide the complete udev db (udevadm info -e) and udev debugging
output (udev.log-priority=8 at the kernel command line) from a failed
boot.
As this bug only bites a small number of systems (I myself found none, I
was only able to produce similar effects by breaking udev rules), I
intend to downgrade this bug for now.
Bastian
--
It is necessary to have purpose.
-- Alice #1, "I, Mudd", stardate 4513.3
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
