Am 30.06.2015 um 22:53 schrieb Klaus Ethgen: > 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.
With systemd, those early boot messages would end up in the journal. I don't use sysvinit anymore, so I don't know if there is a way to get early boot message but you could probably hack the /etc/init.d/udev sysv init script and add "export SYSTEMD_LOG_TARGET=console" before the systemd-udevd daemon is started and redirect stderr of the daemon to a file in /run (which should be a tmpfs and writable early during boot). 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. I don't think that would be particularly helpful. > 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. I'm a bit confused though: how can you get a dmesg output from a "bad" boot, when the system did not boot? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
