Bug#758808: udev: time out issue after wheezy->jessie upgrade
On 03/02/2016 07:01 PM, Michael Biebl wrote: 5 jobs in infinite cycle the following order: Starting udev Kernel Device manager... A start job is running for.. .. udev Kernel Device Manager .. dev-mapper-vg-name .. Apply Kernel Variables .. dev-disk-by- .. udev Wait for Complete Device Initialization Is that a virtual machine? Yes, kvm, but it happened also in physical computers. Can you follow the instructions at [1] and enable a debug shell on tty9. Boot with systemd.log_level=debug switch to tty9, store the output of systemctl list-jobs and journalctl -alb and attach those files to the but report. The emergency shell not working, no answer after typed systemctl or journalctl What exactly does "no answer" mean? I typed the command, and wait for the answer, but no answer given. I can break it with C-c. Do other commands like pstree work? no Can you strace the commands and attach the output. no, because strace also not working
Bug#758808: udev: time out issue after wheezy->jessie upgrade
Am 02.03.2016 um 17:50 schrieb Detrich Bertalan: > >> Control: tags -1 moreinfo unreproducible >> >> Hi >> >> Am 02.03.2016 um 16:24 schrieb detbe: >>> I upgraded a several machnies from wheezy to jessie. After the >>> upgrade the first boot was successfull, but sometimes later the boot >>> hangs on "A start job is running..". >> Which job exactly was it waiting for? For how long? > 5 jobs in infinite cycle the following order: > > Starting udev Kernel Device manager... > > A start job is running for.. > > .. udev Kernel Device Manager > .. dev-mapper-vg-name > .. Apply Kernel Variables > .. dev-disk-by- > .. udev Wait for Complete Device Initialization Is that a virtual machine? >> >> Can you follow the instructions at [1] and enable a debug shell on tty9. >> Boot with systemd.log_level=debug >> switch to tty9, store the output of >> systemctl list-jobs >> and >> journalctl -alb >> and attach those files to the but report. >> >> > The emergency shell not working, no answer after typed systemctl or > journalctl What exactly does "no answer" mean? Do other commands like pstree work? Can you strace the commands and attach the output. -- 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
Bug#758808: udev: time out issue after wheezy->jessie upgrade
Control: tags -1 moreinfo unreproducible Hi Am 02.03.2016 um 16:24 schrieb detbe: I upgraded a several machnies from wheezy to jessie. After the upgrade the first boot was successfull, but sometimes later the boot hangs on "A start job is running..". Which job exactly was it waiting for? For how long? 5 jobs in infinite cycle the following order: Starting udev Kernel Device manager... A start job is running for.. .. udev Kernel Device Manager .. dev-mapper-vg-name .. Apply Kernel Variables .. dev-disk-by- .. udev Wait for Complete Device Initialization Can you follow the instructions at [1] and enable a debug shell on tty9. Boot with systemd.log_level=debug switch to tty9, store the output of systemctl list-jobs and journalctl -alb and attach those files to the but report. The emergency shell not working, no answer after typed systemctl or journalctl I try to find what systemd processes running on infinite cycle. Found the systemd-udevd.service, systemd-udev-settle.service, lvm2-activation service. I suspected that the lvm2 service started before the udev process finish. I try to find the right bootup order to this services: systemd.udevd.service -> systemd-udev-settle.service -> lvm2-activation.service . Every process have to finish, before the next one started. Then i edit this services "Before=" lines to force the successfull exit before the next start. After many successful boot, finally i try to find out what the exactly missing option. (Only one needed) Here is the diff: (working dir /lib/systemd/system/) diff --git a/systemd-udevd.service b/systemd-udevd.service index 51497ce..eea7178 100644 --- a/systemd-udevd.service +++ b/systemd-udevd.service @@ -11,7 +11,7 @@ Documentation=man:systemd-udevd.service(8) man:udev(7) DefaultDependencies=no Wants=systemd-udevd-control.socket systemd-udevd-kernel.socket After=systemd-udevd-control.socket systemd-udevd-kernel.socket systemd-udev-hwdb-update.service systemd-sysusers.service -Before=sysinit.target +Before=sysinit.target systemd-udev-settle.service That ordering should not be necessary. systemd-udev-settle.service has After=systemd-udev-trigger.service which has After=systemd-udevd-kernel.socket systemd-udevd-control.socket Yes, i see that, but the reboot issue solved when i added the systemd-udevd.service before the systemd-udev-settle.service [1] https://freedesktop.org/wiki/Software/systemd/Debugging/
Bug#758808: udev: time out issue after wheezy->jessie upgrade
Control: tags -1 moreinfo unreproducible Hi Am 02.03.2016 um 16:24 schrieb detbe: > I upgraded a several machnies from wheezy to jessie. After the upgrade the > first boot was successfull, but sometimes later the boot hangs on "A start > job is running..". Which job exactly was it waiting for? For how long? Can you follow the instructions at [1] and enable a debug shell on tty9. Boot with systemd.log_level=debug switch to tty9, store the output of systemctl list-jobs and journalctl -alb and attach those files to the but report. > I try to find what systemd processes running on infinite cycle. Found the > systemd-udevd.service, systemd-udev-settle.service, lvm2-activation service. > I suspected that the lvm2 service started before the udev process finish. I > try to find the right bootup order to this services: systemd.udevd.service -> > systemd-udev-settle.service -> lvm2-activation.service . Every process have > to finish, before the next one started. > Then i edit this services "Before=" lines to force the successfull exit > before the next start. > After many successful boot, finally i try to find out what the exactly > missing option. (Only one needed) > > Here is the diff: (working dir /lib/systemd/system/) > > diff --git a/systemd-udevd.service b/systemd-udevd.service > index 51497ce..eea7178 100644 > --- a/systemd-udevd.service > +++ b/systemd-udevd.service > @@ -11,7 +11,7 @@ Documentation=man:systemd-udevd.service(8) man:udev(7) > DefaultDependencies=no > Wants=systemd-udevd-control.socket systemd-udevd-kernel.socket >After=systemd-udevd-control.socket systemd-udevd-kernel.socket > systemd-udev-hwdb-update.service systemd-sysusers.service >-Before=sysinit.target >+Before=sysinit.target systemd-udev-settle.service That ordering should not be necessary. systemd-udev-settle.service has After=systemd-udev-trigger.service which has After=systemd-udevd-kernel.socket systemd-udevd-control.socket [1] https://freedesktop.org/wiki/Software/systemd/Debugging/ -- 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
Bug#758808: udev: time out issue after wheezy->jessie upgrade
Package: udev Version: 215-17+deb8u3 Followup-For: Bug #758808 Hello, I upgraded a several machnies from wheezy to jessie. After the upgrade the first boot was successfull, but sometimes later the boot hangs on "A start job is running..". I try to find what systemd processes running on infinite cycle. Found the systemd-udevd.service, systemd-udev-settle.service, lvm2-activation service. I suspected that the lvm2 service started before the udev process finish. I try to find the right bootup order to this services: systemd.udevd.service -> systemd-udev-settle.service -> lvm2-activation.service . Every process have to finish, before the next one started. Then i edit this services "Before=" lines to force the successfull exit before the next start. After many successful boot, finally i try to find out what the exactly missing option. (Only one needed) Here is the diff: (working dir /lib/systemd/system/) diff --git a/systemd-udevd.service b/systemd-udevd.service index 51497ce..eea7178 100644 --- a/systemd-udevd.service +++ b/systemd-udevd.service @@ -11,7 +11,7 @@ Documentation=man:systemd-udevd.service(8) man:udev(7) DefaultDependencies=no Wants=systemd-udevd-control.socket systemd-udevd-kernel.socket After=systemd-udevd-control.socket systemd-udevd-kernel.socket systemd-udev-hwdb-update.service systemd-sysusers.service -Before=sysinit.target +Before=sysinit.target systemd-udev-settle.service ConditionPathIsReadWrite=/sys Kind regards, Bertalan P: /devices/LNXSYSTM:00 E: DEVPATH=/devices/LNXSYSTM:00 E: MODALIAS=acpi:LNXSYSTM: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:03 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:04 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:04 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:05 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:05 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:06 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:06 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:07 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:07 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXPWRBN:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00 E: DRIVER=button E: MODALIAS=acpi:LNXPWRBN: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 E: EV=3 E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME="Power Button" E: PHYS="LNXPWRBN/button/input0" E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: TAGS=:seat: E: USEC_INITIALIZED=4746 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3 N: input/event3 E: BACKSPACE=guess E: DEVNAME=/dev/input/event3 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=18434 E: XKBLAYOUT=hu E: XKBMODEL=pc105 P: /devices/LNXSYSTM:00/LNXSYBUS:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00 E: MODALIAS=acpi:LNXSYBUS: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/INT33A0:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/INT33A0:00 E: DRIVER=intel_smart_connect E: ID_VENDOR_FROM_DATABASE=Interphase Corporation E: MODALIAS=acpi:INT33A0: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=5387 P: /devices/LNXSYSTM:00/LNXSYBUS:00/INT340F:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/INT340F:00 E: ID_VENDOR_FROM_DATABASE=Interphase Corporation E: MODALIAS=acpi:INT340F: E: SUBSYSTEM=acpi E: USEC_INITIALIZED=5396 P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00 E: MODALIAS=acpi:PNP0A08:PNP0A03: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXPOWER:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXPOWER:01 E: MODALIAS=acpi:LNXPOWER: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXPOWER:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXPOWER:02 E: MODALIAS=acpi:LNXPOWER: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00 E: DRIVER=video E: MODALIAS=acpi:LNXVIDEO: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/device:00 E:
