http://bugzilla.suse.com/show_bug.cgi?id=963241 http://bugzilla.suse.com/show_bug.cgi?id=963241#c8 --- Comment #8 from sd fs ---

http://ubuntuforums.org/showthread.php?t=2280968

Interesting catch!

Call: udevadm info -q all -p /sys/class/net/eno1 -a

and look at the 2nd entry (pci device / first one with KERNELS variable), e.g. [from my NIC here]:

here it's looking at device '/devices/pci0000:00/0000:00:19.0/net/eno1': KERNEL=="eno1" SUBSYSTEM=="net" looking at parent device '/devices/pci0000:00/0000:00:19.0': KERNELS=="0000:00:19.0" SUBSYSTEMS=="pci" DRIVERS=="e1000e"

The path (with /sys in the front) should contain a "reset" file: ls /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/reset

ls /sys/devices/pci0000:00/0000:00:19.0/reset /sys/devices/pci0000:00/0000:00:19.0/reset

In your case, it should be something like this:

vi /etc/udev/rules.d/69-net-reset-hack.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", KERNELS=="0000:00:19.0", RUN+="/root/reset-nic.sh" vi /root/reset-nic.sh (do not forget "chmod +x /root/reset-nic.sh"): #!/bin/bash p="/sys${DEVPATH/net\/*/reset}" echo 1 > "$p" /usr/bin/logger -t udev-hack -- "resetting '$p' done" chmod +x /root/reset-nic.sh udevadm test -a add /sys/class/net/eno1 ... 3070 strings (37233 bytes), 2131 de-duplicated (20077 bytes), 940 trie nodes used

...

RUN '/root/reset-nic.sh' /etc/udev/rules.d/69-net-reset-hack.rules:1 IMPORT builtin 'net_id' /usr/lib/udev/rules.d/75-net-description.rules:6 IMPORT builtin 'hwdb' /usr/lib/udev/rules.d/75-net-description.rules:12 ...

reboot

When this does not help,

after reboot, maybe a little? systemd-analyze blame 1min 41.341s wicked.service ...

please do not remove it, but continue with the following steps:

...

Which log configuration are you using? Is there some syslog daemon running (systemctl status syslog),

Yep, systemctl status syslog rsyslog.service - System Logging Service Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled) Active: active (running) since Mon 2016-02-01 06:11:44 PST; 8min ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 1362 ExecStartPre=/usr/sbin/rsyslog-service-prepare (code=exited, status=0/SUCCESS) Main PID: 1372 (rsyslogd) CGroup: /system.slice/rsyslog.service └─1372 /usr/sbin/rsyslogd -n

and user database in e.g. ldap?

Nope, not that I setup. I'll work on the rest now -- You are receiving this mail because: You are on the CC list for the bug.