06.12.2014 19:02 Uhr; "Andrei Borzenkov"
В Sat, 6 Dec 2014 13:24:49 +0100 ub22@gmx.net пишет:
Hi,
I installed Tumbleweed like this description: https://de.opensuse.org/Portal:Tumbleweed/Themen
After the Update, I the system don't boot anymore. The Kernel hangs with
A start job is running for Load Kernel Modules (.../no limit)
Looks like some kernel module hangs during initialization. What's in /etc/modules-load.d?
This directory is empty. # ls -l /etc/mod* /etc/modprobe.d: insgesamt 40 -rw-r--r-- 1 root root 3647 28. Sep 23:23 00-system.conf -rw-r--r-- 1 root root 532 14. Nov 2012 10-unsupported-modules.conf -rw-r--r-- 1 root root 181 24. Nov 18:40 50-alsa.conf -rw-r--r-- 1 root root 4584 7. Nov 09:17 50-blacklist.conf -rw-r--r-- 1 root root 128 26. Nov 12:38 50-bluetooth.conf -rw-r--r-- 1 root root 33 24. Nov 14:52 50-ipw2200.conf -rw-r--r-- 1 root root 34 24. Nov 14:52 50-iwl3945.conf -rw-r--r-- 1 root root 18 24. Nov 14:52 50-prism54.conf -rw-r--r-- 1 root root 47 22. Nov 2011 99-local.conf /etc/modules-load.d: insgesamt 0 In good old /var/log/boot.log I find following (after the boot of the old Kernel - which works): [ INFO ] Network Manager is not active. [DEPEND] Dependency failed for Network Manager Wait Online. Starting Authorization Manager... [ OK ] Reached target Host and Network Name Lookups. Mounting /tmp... [ OK ] Started wicked DHCPv6 supplicant service. [ OK ] Started wicked AutoIPv4 supplicant service. [ OK ] Started System Logging Service. [ OK ] Started wicked DHCPv4 supplicant service. Starting wicked network management service daemon... [ OK ] Started wicked network management service daemon. Starting wicked network nanny service... [ OK ] Started wicked network nanny service. Starting wicked managed network interfaces... [ OK ] Started Activation of LVM2 logical volumes. [ OK ] Started Authorization Manager. [ OK ] Mounted /tmp. [ OK ] Started Modem Manager. [ OK ] Started File System Check on /dev/disk/by-id/ata-ST...-part6. Mounting /mnt/images... [ OK ] Mounted /mnt/images. [* ] (1 of 2) A start job is running for wicked managed network interfaces (6s / no limit)^M[** ] (1 of 2) A start job is running for wicked managed network interfaces (6s / no limit)^M[*** ] (1 of 2) A start job is running for wicked managed network interfaces (7s / no limit)^M[ *** ] (2 of 2) A start job is running for dev-mapper-cr_my.crypt.device (7s / no limit)^M[ *** ] (2 of 2) A start job is running for dev-mapper-cr_my.crypt.device (8s / no limit)^M[ ***] (2 of 2) A start job is running for dev-mapper-cr_my.crypt.device (8s / no limit)^M[ **] (1 of 2) A start job is running for wicked managed network interfaces (8s / no limit)^M[ OK ] Started wicked managed network interfaces. [ OK ] Reached target Network. Starting NIS/YP Clients to NIS Domain Binder... Starting OpenSSH Daemon... Starting NTP Server Daemon... Starting CUPS Printing Service... [ OK ] Started CUPS Printing Service. [ OK ] Reached target Network is Online. Starting LSB: NFS client services... Starting Login and scanning of iSCSI devices... [ OK ] Started Login and scanning of iSCSI devices. Starting Activation of LVM2 logical volumes... [ OK ] Started OpenSSH Daemon. [ OK ] Started NIS/YP Clients to NIS Domain Binder. [ OK ] Reached target User and Group Name Lookups. Starting Command Scheduler... [ OK ] Started Command Scheduler. [ OK ] Started NTP Server Daemon. For me it looks like a sequencing error. The kernel will use the network before the network is present.
(I reboot after 1h).
A boot with the same Kernel (in the moment 3.17.4-1-desktop) in recovery mode - no deviation.
Only if I use the old Kernel 3.16.6-2-desktop - the system boots without truble.
Conditions: Tumbleweed /home is mounted via NFS 4.0 on openSUSE 13.2 (Harlequin) (x86_64) Kernel 3.17.1-53.gd944251-desktop (Tumbleweed) Encrypted Filesystem (created via yast2 disk) on a mounted drive
On my second desktop I've in the beginning the same trouble but works after a restart in recovery mode now fine.
I find in the new version nicer a systemctl (before rc...) function to restart this nor I can mount the encfs on the old kernel (segmentation fault). Also the /var/log/messages I can't find any more detailed information.
Any Idea? How I can find the right place in the log - now the log system is again changed :-(
Regards Ulf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org