Am Di den 30. Jun 2015 um 20:22 schrieb Michael Biebl: > Booting with udev.log-priority=debug udev.children-max=1 on the kernel > command line should give you a more verbose log. Please attach that.
I did that. And it seems that the bug does not happen with that settings. It just take over 10 minutes for all that messages to scroll over the screen. Unfortunately, the messages gets not written anywhere so there is no way to attach them to a mail. Maybe I can film the boot screen with all that messages and send you the movie about it. That is the only idea that I have to provide you with that informations. However, I'll attach you the dmesg from that boot try and a clean dmesg from a good udev. In the last one I mark the position where new udev breaks. (Note that the order of the messages is completely different between the two dmesg outputs.) Please note also that I get different counts of the following messages with every boot: usb 2-3.2: device descriptor read/64, error -110 usb 8-3.2: device descriptor read/64, error -110 usb 8-3.2: device descriptor read/64, error -110 usb 8-3.2: device descriptor read/64, error -110 (Just a random selection) Regards Klaus -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.de> Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
dmesg.bad.xz
Description: application/xz
dmesg.good.xz
Description: application/xz
signature.asc
Description: Digital signature