-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Fr den 3. Jul 2015 um 20:58 schrieb Michael Biebl: > > 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 > > I don't see anything relevant in those logs.
Well, it clearly shows that it probes some unexisting USB stuff. > I'm a bit confused though: how can you get a dmesg output from a "bad" > boot, when the system did not boot? I already wrote that, from time to time the boot get through after really long time. That is the only way to fix it. (Ok, I could boot from a grml boot stick. But the first time it happened, I did not have such a stick pre-prepared. I did not expect an upgrade of udev breaking the whole system, that I never had that complete.) 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQGcBAEBCgAGBQJVmHtyAAoJEKZ8CrGAGfasv9IMAJruWwlEy21NnLzvFCq5L+uA Ln4oL9FFzb3/szEo8gAsiUw3+LodldajsbCanF2HdJSYiXlqvZDDaTS+k4c/TXja jf0y41vE7IGjQhFQhC2R8bGjI3gLzIJHBGRuYchVZVvrDlaUOk8lB1UxNLPECbBl 2Y+GRXoQgYfFAF/K4YiyRKlrIME7K2YjF7ocfuDjuEoe7JEA1dKVjIrqsk/gZQbH bu+zyjt6xljAfHwNpz6SADNSPsS4Mp+kqpWoqH4lp/xnH45U8iPKFanQeNIE54l7 wTMzGQtC828PGIQA0Yyu9K4brsZeK9DXRJ25Qi+LIfPkr8AcRlFPW6c9REIROflI fb3lzq5zVdNCh4P0MOhZ1Sff6BHNV6ONX6TKzihw9d0XKkpafWto5qkvDkIqpKwu n48QiBXpRkxrGrx+8wude4OhHd+qWS9DzxIuak3ljmshPVxyJAxckdTKdestS1fx BtynZx+DqfKJoacutmOp+tEc6X4qdv1bPsQJUvC6lQ== =sq3i -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
