Your message dated Sun, 27 May 2018 10:25:44 +0200
with message-id <[email protected]>
and subject line Re: Bug#790561: After upgrading udev from 215-18 to 220-7 or
221-1, the system is unbootable afterwards
has caused the Debian Bug report #790561,
regarding Slow boot times with v222 / possibly related to USB detection
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
790561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790561
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Package: udev
Version: 220-7
Severity: critical
After upgrading my system from 215-18 to 220-7 or 221-1, (only udev
changes), my system is not bootable anymore.
Here is all the informations I have:
I first upgraded to 221-1 and then did the reboot. After that, the
system freezes after the SCSI initialisation.
After several tries the system finally booted (after ~5 minutes) with
many errors and showing many timeout of nonexisting devices with an
sequence counter aroung 3000(!) that shows that udev tries to loop over
all available and unavailable USB devices and freezes there with one or
another nonexisting device combination. It craped out, for example,
trying to find a joystick device on a keyboard (the system has no
joystick at all).
Downgrading to 220-7 makes the problem even worse. Then it seems to loop
over all USB devices twice what has twice the change to freeze.
Downgrading to 215-18 solves the problem (After an one hour restart
nightmare).
- -- Package-specific info:
- -- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (800, 'unstable'), (500, 'testing'), (110, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.4 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to
de_DE)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages udev depends on:
ii adduser 3.113+nmu3
ii debconf [debconf-2.0] 1.5.56
ii libacl1 2.2.52-2
ii libblkid1 2.26.2-6
ii libc6 2.19-18
ii libkmod2 20-1
ii libselinux1 2.3-2+b1
ii libudev1 215-18
ii lsb-base 4.1+Debian13+nmu1
ii procps 2:3.3.10-2
ii util-linux 2.26.2-6
udev recommends no packages.
udev suggests no packages.
- -- debconf information:
udev/reboot_needed:
udev/title/upgrade:
udev/new_kernel_needed: false
udev/sysfs_deprecated_incompatibility:
- --
Klaus Ethgen http://www.ethgen.ch/
pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <[email protected]>
Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCgAGBQJVklC6AAoJEKZ8CrGAGfas8FAMALiSGXM397rlmDJPbAKREAli
7leRiS1Rq9qQYhuQqrqtaCYyAE4QHJDkz/U/iSsjzJmfkCYGdLtTdcLXvblY6Fx7
P0Gne7Ti/w9+A/WezBWCcn6SY4585zk+hGd+7fj75FUGNiCyteAFJRDTWNH+RrbH
DS+XZ7sJ7XoAGs7MdVCo1QqTQRed2CzkNEnNje9eMRsnBVcrE/J/RO3sYFwEnOnG
C9rGYzA6PCbmILJmkPDjwgR4dLChHeKKtWp/zOJ8we4wgz8wyeFUPms54N7PqJek
xUtO917bQX+34Lt1u2skrA+4sYzg4WNwG/eW+QFOyW4I+PCSUeVnh1mnUw77Dyq9
R0BWIGg8mpnipoer6IUPg7qSuyYPGgb9VQvmmkeeQU06GKj4ljbRNQCiCzMPKgZh
muj5m9zKu+HZRQId06IzbuIZvLWNPsIkl11moq2KkvOJiPNaCKYhJf2wrABWpx2e
/vnXewoJLBbSMilZz7BnNQgfoh6tIWp+9RBUyOv9+g==
=7Peg
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Fri, 3 Jul 2015 21:58:09 +0200 Michael Biebl <[email protected]> wrote:
> 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).
>
Afaics we never received such a debug log, so we can't really reasonably
investigate this further.
If you are available for further debugging and willing to test with a
recent version like v232 or v238 from buster, we can reopen the bug report.
Michael
--
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
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
