"Segmentation fault" error while running "zypper dup -l"--multiple times

English Applications
#1

Folks:

Been awhile since there was an issue enough to post here, but, this one is a qualifier . . . running “zypper ref && zypper dup -l” took me about 45 minutes today to get through a download of approx “515 packages” . . . had to run the “dup -l” command possibly 15 times to get through the whole list, because every so often it was terminated with an “segmentation fault” error, cursor returns to the blinking “please command me” position . . . . Did that 5 or 6 times, then tried yast for “online update” . . . that returned a “you need the ‘yast online updater update’” . . . something like that, which I ran, then yast showed an option to set up “automatic updating” . . . which I like using the Terminal . . . so I went back to the console and finished the upgrade . . . “very manually” . . . repeating the “zypper dup -l” comand, sometimes after only three packages, sometimes after 20 . . . nothing consistent on what caused the error . . . but, very time consuming . . . . On “reboot” the “tumfinity” splash window showed for several minutes, before rebooting, and then the same thing after the reboot . . . several minutes passed before getting to the log in window . . . . Then on resuming from suspend, the same thing . . . it doesn’t just spring to awake state . . . .

Yesterday, I had the exact same issues in a partition installed with Gecko Rolling . . . repeated “segmentation faults” . . . but didn’t take so many repeats of “dup -l” to get through the downloading . . . same problems with slow rebooting after the upgrade, but then I rebooted into TW to see if the same problems were happening, and it was. I hit a couple “segmentation faults” and I ran out of time, so I suspended it. This morning I revived TW and . . . trying to check emails . . . could not do that, "No internet connection, network manager is not working . . . " . . . so I rebooted into the Ubuntu MATE partition . . . quick boot up, no problems with internet–ran an update/upgrade with no errors reported.

After that I shut the computer down for a Sunday drive. When I returned I booted TW and while the internet was then working fine, the “segmentation fault” problem was very much “alive” . . . very time consuming to get done, slow reboot, slow boot, slow revive from suspend . . . TW has not been too “zyppy” lately, what’s up with the “segmentation fault” error? Also the mouse cursor seems “crashy” at times, when trying to mouse around it won’t respond to the motion for a second, before it “un-crashes” . . . .

non_space

#2

There have been several earlier threads on this.

In short, it was a bug (now fixed) in “libcurl4”. If you fully updated, then your system is likely fixed and this won’t happen again (until there’s a new bug).

Repeatedly running “zypper dup” until done does work around the problem, as you have found out.

If you had known, then:

zypper update libcurl4

would have fixed the problem and then the rest of your update would have been easier.

As for the other problems – the latest update introduce a 5.0.0 kernel. You might try booting the previous kernel to test whether the other problems are kernel related.

#3

@nrickert:

Thanks kindly for the reply . . . glad to hear that it’s “fixed” . . . I did search into this sub-forum a few pages checking to see if others had the same issue but didn’t find any in the last week. I did run the same ref/dup within a week and a half back and didn’t have any “segmentation fault” problems at that time.

Now it does seem like the upgrades are as new as possible, after running “dup -l” and going through all of them, running it again in both TW & Gecko . . . brought “nothing to do.” I did see that we are up to the “5” kernel . . . some of these user issues, slow boot, slow revive from suspend . . . have been happening for awhile . . . . I am running a multi-multi boot situation and it doesn’t seem like opensuse handles that as well as my ubuntu based options, both of them boot fast, revive fast . . . I like the opensuse systems, but possibly the TW & Rolling editions . . . are very “Sid” like, without the speed benefits of . . . Sid???

n_s

#4

That earlier update probably installed the buggy version of libcurl4.

I like the opensuse systems, but possibly the TW & Rolling editions . . . are very “Sid” like, without the speed benefits of . . . Sid???

I use Leap 15.0 for my normal computing. I like its stability. But I do play with Tumbleweed, to get an idea of what will be coming up.

#5

@nrickert:

Thanks again . . . it is a tad difficult to find that happy medium between “stability” and “too new to be practical daily user” or “testing out the newest buggy versions for fun times” . . . maybe I’ll check into Leap 15 . . . ???

#6

Relax! My system is fine. I have some 6600 packages installed. I run zypper dup whenever updates are pending and the machine is idle, which occurred several hundred times during three years of usage. zypper virtually never fails. It’s the fastest installer I ever encountered. When booting a typical message issued is: graphical.target reached after 5.279s in userspace. Thus I think there is lot of margin for improving your procedures.

Have a lot of fun.

#7

@karl:

OK, seems like you missed the point that zypper “failed” in its processes . . . “crashing” out with a “segmentation fault” error??? nrickert reported that others had the problem??? Perhaps you missed the upgrade that brought the buggy package into play?

And, sure, always room for improvement . . . but I’m mixing several OSX installs with several linux installs . . . have to go through Grub . . . and the opensuse installs are comparatively slower to boot up compared to the ubuntu side of things, possibly because ubuntu is now using a “swap file” rather than “swap partition” ?? Happy to hear how to get Opensuse “tuned” up . . . .

#8

I have Xubuntu, with default selection of software:

erlangen:~ # journalctl -b 2 --directory /Xubuntu/var/log/journal/|grep userspace
Oct 19 21:25:29 xubuntu-test systemd[1]: Startup finished in 2.053s (kernel) + 7.693s (userspace) = 9.747s.
erlangen:~ #

Tumbleweed has lots of additional software configured:

erlangen:~ # journalctl -b --directory /var/log/journal/|grep userspace
Mar 18 18:01:10 erlangen systemd[1]: Startup finished in 1.841s (kernel) + 1.266s (initrd) + 5.474s (userspace) = 8.582s.
erlangen:~ #

“Tuning” is mainly disabling wicked, NetworkManager and avahi-daemon. I enabled systemd-networkd using static address configuration only.

erlangen:~ # systemd-analyze blame
2.806s plymouth-quit-wait.service
2.718s display-manager.service
2.346s minidlna.service
1.658s apparmor.service
704ms postfix.service
667ms systemd-logind.service
567ms udisks2.service
457ms dev-nvme0n1p2.device
376ms initrd-switch-root.service
242ms plymouth-switch-root.service
202ms initrd-parse-etc.service
129ms user@1000.service
125ms systemd-vconsole-setup.service
104ms systemd-udev-trigger.service
88ms apache2.service
76ms home\x2dHDD.mount
73ms boot-efi.mount
70ms systemd-journal-flush.service
68ms systemd-udevd.service
64ms systemd-tmpfiles-clean.service
56ms upower.service
53ms kbdsettings.service
49ms polkit.service
43ms issue-generator.service
42ms ntpd.service
41ms systemd-networkd.service
39ms systemd-sysctl.service
39ms wpa_supplicant@wlp3s0.service
39ms mcelog.service
38ms dracut-cmdline.service
36ms alsa-restore.service
35ms systemd-tmpfiles-setup.service
34ms auditd.service
29ms sys-fs-fuse-connections.mount
28ms systemd-tmpfiles-setup-dev.service
26ms rtkit-daemon.service
25ms systemd-journald.service
24ms initrd-cleanup.service
24ms systemd-remount-fs.service
23ms systemd-fsck-root.service
22ms dev-disk-by\x2duuid-699eabfd\x2d107e\x2d488a\x2d9d9d\x2d9e5a280084bd.swap
20ms systemd-random-seed.service
20ms dracut-pre-trigger.service
19ms systemd-rfkill.service
18ms user-runtime-dir@1000.service
15ms systemd-modules-load.service
15ms systemd-user-sessions.service
14ms systemd-update-utmp.service
14ms home\x2dSSD.mount
14ms initrd-udevadm-cleanup-db.service
14ms plymouth-start.service
14ms systemd-update-utmp-runlevel.service
13ms colord.service
13ms iscsi.service
11ms plymouth-read-write.service
11ms home.mount
10ms sys-kernel-debug.mount
9ms dev-mqueue.mount
8ms kmod-static-nodes.service
8ms Tumbleweed\x2dSSD.mount
7ms dev-hugepages.mount
3ms sysroot.mount
1ms dracut-shutdown.service
erlangen:~ #

#9

@karl:

OK, thanks for posting that data, I’ll have to look into it . . . have to be a day or two before I can get back to that computer and run your commands to see what my system shows . . . . It is a “box stock” TW install, have not disabled wicked, network manager is still going, avahi-daemon . . . all still installed . . . .

I have a number of choices in operating systems . . . so I keep rolling through them . . . not dwelling on the details of them as far as moving away from stock . . . .

#10

Running the commands below . . . shows what a quick player TW can be . . . super quick time to userspace . . . .

sudo  journalctl -b --directory /var/log/journal/|grep userspace
[sudo] password for root: 
Mar 19 07:22:24 localhost systemd[1]: Startup finished in 2.663s (kernel) + 5.236s (initrd) + 3min 3.607s (userspace) = 3min 11.507s.

sudo systemd-analyze blame
         35.012s btrfsmaintenance-refresh.service
         30.336s wicked.service
         23.268s plymouth-quit-wait.service
         16.168s backup-rpmdb.service
         15.143s logrotate.service
          8.290s apparmor.service
          7.537s lvm2-monitor.service
          7.325s systemd-journal-flush.service
          6.278s dev-sdb8.device
          3.689s backup-sysconfig.service
          3.686s postfix.service
          3.335s initrd-switch-root.service
          3.181s ModemManager.service
          2.376s udisks2.service
          2.341s systemd-udevd.service
          2.060s wickedd-dhcp4.service
          2.055s wickedd-auto4.service
          2.054s avahi-daemon.service
          2.054s display-manager.service
          1.868s bluetooth.service
          1.865s systemd-fsck-root.service
          1.505s wickedd-dhcp6.service
          1.497s nscd.service
          1.312s plymouth-start.service
           852ms fwupd.service
           767ms systemd-tmpfiles-setup-dev.service
           633ms user@467.service
           585ms wpa_supplicant.service
           551ms polkit.service
           513ms systemd-logind.service
#11

could not figure out how to edit my previous post, but here is comparo to time to user space for Lubuntu Disco . . . .

systemd[1]: Startup finished in 6.860s (kernel) + 58.392s (userspace) = 1min 5.252s.
#12

Would you mind adding the the output of inxi?

erlangen:~ # inxi -zFmxx
System:    Host: erlangen Kernel: 5.0.2-1-default x86_64 bits: 64 compiler: gcc v: 8.3.1 Console: tty 0 wm: kwin_x11 dm: SDDM 
           Distro: openSUSE Tumbleweed 20190318 
Machine:   Type: Desktop Mobo: ASRock model: Z170 Pro4S serial: <filter> UEFI: American Megatrends v: P3.50 date: 06/23/2016 
CPU:       Topology: Quad Core model: Intel Core i7-6700K bits: 64 type: MT MCP arch: Skylake-S rev: 3 L1 cache: 256 KiB 
           L2 cache: 8192 KiB L3 cache: 8192 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 64128 
           Speed: 800 MHz min/max: 800/4200 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:  Device-1: Intel HD Graphics 530 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:1912 
           Display: server: X.Org 1.20.4 driver: intel unloaded: fbdev,modesetting,vesa compositor: kwin_x11 
           resolution: 1920x1200~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) v: 4.5 Mesa 18.3.4 compat-v: 3.0 direct render: Yes 
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a170 
           Sound Server: ALSA v: k5.0.2-1-default 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           chip ID: 8086:15b8 
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: <filter> 
           Device-2: Qualcomm Atheros AR9287 Wireless Network Adapter driver: ath9k v: kernel port: f040 bus ID: 03:00.0 
           chip ID: 168c:002e 
           IF: wlp3s0 state: up mac: <filter> 
Drives:    Local Storage: total: 4.56 TiB used: 1.87 TiB (41.0%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 950 PRO 512GB size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
           serial: <filter> temp: 36 C 
           ID-2: /dev/sda vendor: Western Digital model: WD40EZRX-22SPEB0 size: 3.64 TiB speed: 6.0 Gb/s serial: <filter> 
           temp: 28 C 
           ID-3: /dev/sdb vendor: Samsung model: SSD 850 EVO 500GB size: 465.76 GiB speed: 6.0 Gb/s serial: <filter> 
Partition: ID-1: / size: 31.37 GiB used: 17.50 GiB (55.8%) fs: ext4 dev: /dev/nvme0n1p2 
           ID-2: /home size: 406.34 GiB used: 206.89 GiB (50.9%) fs: ext4 dev: /dev/nvme0n1p3 
           ID-3: swap-1 size: 32.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 51.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 269 Uptime: 1h 54m Memory: 31.11 GiB used: 2.94 GiB (9.4%) Init: systemd v: 241 runlevel: 5 
           target: graphical.target Compilers: gcc: 8.3.1 alt: 7/8 clang: 7.0.1 Shell: bash v: 5.0.2 running in: konsole 
           inxi: 3.0.32 
erlangen:~ #
#13

@karlm:

Thanks for the follow up, I will get back to you with that data in a few hours, I’m over in U-MATE slice right now, then have to jump out . . . so I’ll get back to it then. Here’s our command enquiry running in Ubuntu-MATE 18.04 LTS . . . seems to be the quickest of those tested so far.

Mar 19 11:56:44 MacPro systemd[1]: Startup finished in 4.188s (kernel) + 45.887s (userspace) = 50.076s.
#14

@KarlM:

Here you go on the

inxi

request:

sudo inxi -zFmxx
[sudo] password for root: 
System:
  Host: localhost Kernel: 5.0.1-1-default x86_64 bits: 64 compiler: gcc 
  v: 8.3.1 Console: tty 0 dm: GDM Distro: openSUSE Tumbleweed 20190314 
Machine:
  Type: Desktop System: Apple product: MacPro5,1 v: 0.0 serial: <filter> 
  Chassis: type: 7 v: Mac-F221BEC8 serial: <filter> 
  Mobo: Apple model: Mac-F221BEC8 serial: <filter> UEFI: Apple 
  v: 138.0.0.0.0 date: 07/30/2018 
Memory:
  RAM: total: 15.65 GiB used: 1.48 GiB (9.5%) 
  Array-1: capacity: 64 GiB slots: 4 EC: Single-bit ECC 
  max module size: 16 GiB note: est. 
  Device-1: DIMM 1 size: 4 GiB speed: 1066 MT/s type: DDR3 
  manufacturer: 0x85F7 part-no: 0x463732353155363246393333334700520000 
  Device-2: DIMM 2 size: 4 GiB speed: 1066 MT/s type: DDR3 
  manufacturer: 0x85F7 part-no: 0x463732353155363246393333334700520000 
  Device-3: DIMM 3 size: 4 GiB speed: 1066 MT/s type: DDR3 
  manufacturer: 0x85F7 part-no: 0x463732353155363246393333334700520000 
  Device-4: DIMM 4 size: 4 GiB speed: 1066 MT/s type: DDR3 
  manufacturer: 0x85F7 part-no: 0x463732353155363246393333334700520000 
CPU:
  Topology: Quad Core model: Intel Xeon W3565 bits: 64 type: MT MCP 
  arch: Nehalem rev: 5 L1 cache: 512 KiB L2 cache: 8192 KiB L3 cache: 64 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 51070 
  Speed: 1596 MHz min/max: 1596/3325 MHz Core speeds (MHz): 1: 1596 2: 1596 
  3: 1596 4: 1596 5: 1596 6: 1596 7: 1596 8: 1596 
Graphics:
  Device-1: NVIDIA GK110 [GeForce GTX 780] vendor: eVga.com. driver: nouveau 
  v: kernel bus ID: 05:00.0 chip ID: 10de:1004 
  Display: server: X.org 1.20.4 driver: nouveau compositor: gnome-shell 
  tty: 80x24 
  Message: Advanced graphics data unavailable in console for root. 
Audio:
  Device-1: Intel 82801JI HD Audio driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:3a3e 
  Device-2: NVIDIA GK110 HDMI Audio vendor: eVga.com. driver: snd_hda_intel 
  v: kernel bus ID: 05:00.1 chip ID: 10de:0e1a 
  Sound Server: ALSA v: k5.0.1-1-default 
Network:
  Device-1: Intel 82574L Gigabit Network driver: e1000e v: 3.2.6-k 
  port: 2000 bus ID: 09:00.0 chip ID: 8086:10f6 
  IF: enp9s0 state: down mac: <filter> 
  Device-2: Intel 82574L Gigabit Network driver: e1000e v: 3.2.6-k 
  port: 1000 bus ID: 0a:00.0 chip ID: 8086:10f6 
  Device-3: Broadcom and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN 
  vendor: Apple AirPort Extreme driver: b43-pci-bridge v: N/A port: 1000 
  bus ID: 0d:00.0 chip ID: 14e4:432b 
  IF-ID-1: enp10s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  IF-ID-2: wlan0 state: down mac: <filter> 
Drives:
  Local Storage: total: 2.05 TiB used: 24.43 GiB (1.2%) 
  ID-1: /dev/sda model: Mercury Electra 3G SSD size: 232.89 GiB 
  speed: 3.0 Gb/s serial: <filter> 
  ID-2: /dev/sdb vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB 
  speed: 3.0 Gb/s serial: <filter> 
  ID-3: /dev/sdc vendor: Western Digital model: WD10EZEX-00BN5A0 
  size: 931.51 GiB speed: 3.0 Gb/s serial: <filter> 
Partition:
  ID-1: / size: 47.81 GiB used: 10.69 GiB (22.4%) fs: ext4 dev: /dev/sdb8 
  ID-2: /home size: 88.12 GiB used: 13.74 GiB (15.6%) fs: ext4 
  dev: /dev/sdb9 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A gpu: nouveau temp: 34 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 930 
Info:
  Processes: 285 Uptime: N/A Init: systemd v: 241 runlevel: 5 
  target: graphical.target Compilers: gcc: N/A Shell: bash v: 5.0.2 
  running in: tty 0 inxi: 3.0.32
#15

Output looks quite reasonable: Plenty of hardware, but slow interfaces.

You may check status of units affecting startup time:

erlangen:~ # systemctl list-unit-files btrfs* *wicked* NetworkManager* *avahi* *iscsi* systemd-networkd*
UNIT FILE                            STATE   
btrfsmaintenance-refresh.path        disabled
avahi-daemon.service                 disabled
avahi-dnsconfd.service               disabled
btrfs-balance.service                static  
btrfs-defrag.service                 static  
btrfs-scrub.service                  static  
btrfs-trim.service                   static  
btrfsmaintenance-refresh.service     disabled
NetworkManager-dispatcher.service    disabled
NetworkManager-wait-online.service   disabled
NetworkManager.service               disabled
systemd-networkd-wait-online.service **enabled **
systemd-networkd.service             **enabled **
wicked.service                       disabled
wickedd-auto4.service                disabled
wickedd-dhcp4.service                disabled
wickedd-dhcp6.service                disabled
wickedd-nanny.service                disabled
wickedd-pppd@.service                static  
wickedd.service                      indirect
avahi-daemon.socket                  disabled
systemd-networkd.socket              **enabled **
btrfs-balance.timer                  disabled
btrfs-defrag.timer                   disabled
btrfs-scrub.timer                    disabled
btrfs-trim.timer                     disabled

26 unit files listed.
erlangen:~ #
#16

@Karl:

Thanks for posting back, somehow didn’t get a notification on it . . . but, OK, I’ll check on that command in a bit. What’s interesting to me is that if you say “slow interfaces” . . . that seems to be exclusive to my two OpenSUSE based systems, but doesn’t seem to be affecting the two Ubuntu based options, which both boot pretty quickly . . . . Maybe what I’ll do is run the command in both options and see if anything shows up . . . .

This is the output for U-MATE that I’m running right now, which to my knowledge I haven’t changed anything from the “default” options . . . perhaps “obviously” or not, Ubuntu doesn’t have “btrfs” . . . .

UNIT FILE                            STATE   
avahi-daemon.service                 enabled 
NetworkManager-dispatcher.service    enabled 
NetworkManager-wait-online.service   enabled 
NetworkManager.service               enabled 
systemd-networkd-wait-online.service disabled
systemd-networkd.service             disabled
avahi-daemon.socket                  enabled 
systemd-networkd.socket              disabled

8 unit files listed.
#17

@Karl, et al:

Looks like “problems” are happening already, tried to post before and data was lost, requiring re-gathering data and re-posting it, adding to “degree of difficulty” aspects of the system, etc.

OK, ran an update/upgrade and that found an error with “btrfs-scrub.timer” with a suggested command to run, which I did . . . and that showed “timer lacks value. refusing.” . . . I then rebooted the system and ran your check on the services, which showed:

 sudo systemctl list-unit-files btrfs* *wicked* NetworkManager* *avahi* *iscsi* systemd-networkd*
 [sudo] password for root:  
 UNIT FILE                            STATE    

 btrfsmaintenance-refresh.path        enabled  

 avahi-daemon.service                 enabled  

 avahi-dnsconfd.service               disabled
 btrfs-balance.service                static   

 btrfs-defrag.service                 static   
 btrfs-scrub.service                  static   

 btrfs-trim.service                   static   

 btrfsmaintenance-refresh.service     enabled  
 iscsi.service                        enabled  
 iscsid.service                       disabled
 iscsiuio.service                     disabled
 NetworkManager-dispatcher.service    enabled  
 NetworkManager-wait-online.service   disabled
 NetworkManager.service               disabled
 systemd-networkd-wait-online.service disabled

 systemd-networkd.service             enabled  

 wicked.service                       enabled  

 wickedd-auto4.service                enabled  
 wickedd-dhcp4.service                enabled  
 wickedd-dhcp6.service                enabled  
 wickedd-nanny.service                enabled  
 wickedd-pppd@.service                static   
 wickedd.service                      indirect
 avahi-daemon.socket                  enabled

So, it’s showing that you have some of those services “disabled” . . . but, my question would be how to enable/disable some of those services, and if so, which ones . . .??? And, why are these services included if they slow the system down substantially as it appears to have done?

After the restart I again ran the “btrfs-timer” command and it now shows a different response, which kept repeating itself . . . had to “cntrl-c” out of it.

 sudo systemctl status btrfs-scrub.timer
 [sudo] password for root:  
 ● btrfs-scrub.timer - Scrub btrfs filesystem, verify block checksums
    Loaded: loaded (/usr/lib/systemd/system/btrfs-scrub.timer; enabled; vendor p>
   Drop-In: /etc/systemd/system/btrfs-scrub.timer.d
            └─schedule.conf

    Active: active (waiting) since Fri 2019-03-22 10:47:35 PDT; 17min ago

   Trigger: Mon 2019-04-01 00:00:00 PDT; 1 weeks 2 days left
      Docs: man:btrfs-scrub
~
~
~
~
~
~
~

The “~” were manually added because they didn’t show up in the copy/paste, but were there, and this data was continually running, multiple times. Again, not sure how I would edit that, if I would have to . . . “error” does not seem to be showing, but process continues to run w/o returning to boot prompt cursor, etc.

#18

When using wicked, try to disable and stop everything else in the above list. I uninstalled everything found by zypper se iscsi. You can install again if needed. Reboot and verify you disabled all but wicked.

Compare your inxi output to a budget (444€) laptop: https://forums.opensuse.org/showthread.php/533772-Running-Tumbleweed-on-HP-Laptop-15-da0xxx

Compare the processors:https://www.cpubenchmark.net/compare/Intel-i5-8250U-vs-Intel-Xeon-W3565/3042vs1270

The biggest bottleneck is the HDDs. The following compares the i7-6700K desktop SATA HDD and NVMe SSD:

erlangen:~ # cd /home-HDD/
erlangen:/home-HDD # fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=random_read_write.fio --bs=4k --iodepth=64 --size=4G --readwrite=randrw --rwmixread=75
test: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
fio-3.13
Starting 1 process
test: Laying out IO file (1 file / 4096MiB)
Jobs: 1 (f=1): [m(1)][100.0%][r=1977KiB/s,w=680KiB/s][r=494,w=170 IOPS][eta 00m:01s]
test: (groupid=0, jobs=1): err= 0: pid=9600: Sun Mar 24 08:20:39 2019
  **read: IOPS=265, BW=1063KiB/s (1089kB/s)(3070MiB/2956700msec)**
   bw (  KiB/s): min=  192, max= 2304, per=100.00%, avg=1063.07, stdev=169.19, samples=5913
   iops        : min=   48, max=  576, avg=265.76, stdev=42.30, samples=5913
**  write: IOPS=88, BW=355KiB/s (364kB/s)(1026MiB/2956700msec); 0 zone resets**
   bw (  KiB/s): min=   16, max=  856, per=100.00%, avg=355.29, stdev=80.85, samples=5913
   iops        : min=    4, max=  214, avg=88.80, stdev=20.21, samples=5913
  cpu          : usr=0.68%, sys=2.25%, ctx=1041207, majf=0, minf=8
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=785920,262656,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
   READ: bw=1063KiB/s (1089kB/s), 1063KiB/s-1063KiB/s (1089kB/s-1089kB/s), io=3070MiB (3219MB), run=2956700-2956700msec
  WRITE: bw=355KiB/s (364kB/s), 355KiB/s-355KiB/s (364kB/s-364kB/s), io=1026MiB (1076MB), run=2956700-2956700msec

Disk stats (read/write):
  sda: ios=784400/263680, merge=1616/784, ticks=162985594/25482674, in_queue=186375612, util=66.00%
erlangen:/home-HDD # cd /home
erlangen:/home # fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=random_read_write.fio --bs=4k --iodepth=64 --size=4G --readwrite=randrw --rwmixread=75
test: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=64
fio-3.13
Starting 1 process
test: Laying out IO file (1 file / 4096MiB)
Jobs: 1 (f=1): [m(1)][100.0%][r=478MiB/s,w=159MiB/s][r=122k,w=40.6k IOPS][eta 00m:00s]
test: (groupid=0, jobs=1): err= 0: pid=10505: Sun Mar 24 08:21:12 2019
 ** read: IOPS=123k, BW=482MiB/s (506MB/s)(3070MiB/6367msec)**
   bw (  KiB/s): min=455272, max=517536, per=100.00%, avg=496336.25, stdev=19864.30, samples=12
   iops        : min=113818, max=129384, avg=124084.00, stdev=4966.07, samples=12
**  write: IOPS=41.3k, BW=161MiB/s (169MB/s)(1026MiB/6367msec); 0 zone resets**
   bw (  KiB/s): min=151288, max=174016, per=100.00%, avg=166030.17, stdev=6731.51, samples=12
   iops        : min=37822, max=43504, avg=41507.50, stdev=1682.87, samples=12
  cpu          : usr=26.91%, sys=53.94%, ctx=100713, majf=0, minf=9
  IO depths    : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, >=64=100.0%
     submit    : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
     complete  : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, >=64=0.0%
     issued rwts: total=785920,262656,0,0 short=0,0,0,0 dropped=0,0,0,0
     latency   : target=0, window=0, percentile=100.00%, depth=64

Run status group 0 (all jobs):
   READ: bw=482MiB/s (506MB/s), 482MiB/s-482MiB/s (506MB/s-506MB/s), io=3070MiB (3219MB), run=6367-6367msec
  WRITE: bw=161MiB/s (169MB/s), 161MiB/s-161MiB/s (169MB/s-169MB/s), io=1026MiB (1076MB), run=6367-6367msec

Disk stats (read/write):
  nvme0n1: ios=759971/254160, merge=0/2, ticks=295951/3609, in_queue=17160, util=98.44%
erlangen:/home #
#19

@Karl:

When using wicked, try to disable and stop everything else in the above list. I uninstalled everything found by zypper se iscsi. You can install again if needed. Reboot and verify you disabled all but wicked.

Compare your inxi output to a budget (444€) laptop: https://forums.opensuse.org/showthre…ptop-15-da0xxx

Compare the processors:https://www.cpubenchmark.net/compare…565/3042vs1270

The biggest bottleneck is the HDDs. The following compares the i7-6700K desktop SATA HDD and NVMe SSD:

Thanks for the reply, I’ll try to look into that data, unfortunately I don’t know what “using wicked” is all about, but at this point TW has become an “albatross” . . . i.e., what’s “interesting” is that in spite of the “HDD bottleneck” . . . and the mass confusion that having a number of different “EFI” directories seems to create . . . the Ubuntu installs seem to be able to jump over that hurdle, but the OpenSUSE installs both are “stalled” and/or “heavily confused” . . . . TW takes the same amount of time to boot up as well as “resume” from suspend . . . sometimes taking several minutes to do that, sometimes not able to at all, prompting reboot, and then back into the several minutes thing . . . . Same computer, same multi-HD/SSD hardware and u_MATE boots up pretty quickly, resumes from suspend, etc . . . .

Anyway, the TW install is now “highly experimental” so I will try to figure out your suggestions on “disabling” stuff . . . and then see how that works out for TW boot times . . . . I’ll post back when/if there is something to report on . . . feel free to inform me on “tales from the land of wicked” . . . how “wicked” plays with others and so forth . . . .

#20

Your mileage always varies. Happened to update Ubuntu 18.04.2 LTS to kernel 4.15.0-45-generic:

erlangen:~ # journalctl -b -u 'Network*' --directory /Xubuntu/var/log/journal/ -o short-monotonic |grep Started
   33.972689] xubuntu-test systemd[1]: Started Network Manager.
   33.978862] xubuntu-test systemd[1]: Started Network Manager Script Dispatcher Service.
   38.886077] xubuntu-test systemd[1]: Started Network Manager Wait Online.
erlangen:~ #

vs. openSUSE Tumbleweed 20190322:

erlangen:~ # journalctl -b -u 'systemd-networkd*' --directory /var/log/journal/ -o short-monotonic |grep Started
    3.576977] erlangen systemd[1]: Started Network Service.
    9.505355] erlangen systemd[1]: Started Wait for Network to be Configured.
erlangen:~ # 


Startup finished in 32.949s (kernel) + 5.973s (userspace) = 38.922s
graphical.target reached after 5.966s in userspace

vs.

Startup finished in 1.829s (kernel) + 1.351s (initrd) + 6.667s (userspace) = 9.848s 
graphical.target reached after 6.327s in userspace