Hi,
I have Dell Precision M4800 and I have had OpenSuse 15.1 - it has worked nicely. So now, I have installed 15.3 and the laptop is feelable slow, the startup and wakeup are slow, the usage is not so comfortable.Is my laptot too old for this Opensuse version, or have I done something wrong (bad drives, etc…)?
Thank you for your answer
H.
lshw gets:
description: Laptop
product: Precision M4800 (05CC)
vendor: Dell Inc.
version: 00
serial: 3WK7F72
width: 64 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
configuration: boot=normal chassis=laptop sku=05CC uuid=44454C4C-5700-104B-8037-B3C04F463732
*-core
description: Motherboard
product: 0V5GVY
vendor: Dell Inc.
physical id: 0
version: A00
serial: /3WK7F72/CN129635C9025F/
*-firmware
description: BIOS
vendor: Dell Inc.
physical id: 0
version: A25
date: 10/08/2018
size: 64KiB
capacity: 12MiB
capabilities: pci pnp upgrade shadowing cdboot bootselect edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb smartbattery biosbootspecification netboot uefi
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz
vendor: Intel Corp.
physical id: 43
bus info: cpu@0
version: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz
slot: SOCKET 0
size: 2922MHz
capacity: 3900MHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts md_clear flush_l1d cpufreq
configuration: cores=4 enabledcores=4 threads=8
*-cache:0
description: L1 cache
physical id: 44
slot: CPU Internal L1
size: 256KiB
capacity: 256KiB
capabilities: internal write-back
configuration: level=1
*-cache:1
description: L2 cache
physical id: 45
slot: CPU Internal L2
size: 1MiB
capacity: 1MiB
capabilities: internal write-back unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: 46
slot: CPU Internal L3
size: 8MiB
capacity: 8MiB
capabilities: internal write-back unified
configuration: level=3
*-memory
description: System Memory
physical id: 47
slot: System board or motherboard
size: 16GiB
*-bank:0
description: SODIMM DDR3 Synchronous 1600 MHz (0,6 ns)
product: M471B1G73EB0-YK0
vendor: Samsung
physical id: 0
serial: 8AB2CAC0
slot: DIMM B
size: 8GiB
width: 64 bits
clock: 1600MHz (0.6ns)
*-bank:1
description: DIMM [empty]
product: [Empty]
vendor: [Empty]
physical id: 1
serial: [Empty]
slot: DIMM C
*-bank:2
description: SODIMM DDR3 Synchronous 1600 MHz (0,6 ns)
product: M471B1G73EB0-YK0
vendor: Samsung
physical id: 2
serial: A8B2CAC0
slot: DIMM A
size: 8GiB
width: 64 bits
clock: 1600MHz (0.6ns)
*-bank:3
description: DIMM [empty]
product: [Empty]
vendor: [Empty]
physical id: 3
serial: [Empty]
slot: DIMM D
*-pci
description: Host bridge
product: Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 06
width: 32 bits
clock: 33MHz
*-pci:0
description: PCI bridge
product: Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 06
width: 32 bits
clock: 33MHz
capabilities: pci pm msi pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:26 ioport:e000(size=4096) memory:f4000000-f50fffff ioport:e0000000(size=301989888)
*-display
description: VGA compatible controller
product: GK107GLM [Quadro K1100M]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nouveau latency=0
resources: irq:36 memory:f4000000-f4ffffff memory:e0000000-efffffff memory:f0000000-f1ffffff ioport:e000(size=128) memory:f5000000-f507ffff
*-multimedia
description: Audio device
product: GK107 HDMI Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@0000:01:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:17 memory:f5080000-f5083fff
*-display
description: VGA compatible controller
product: 4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:37 memory:f5400000-f57fffff memory:d0000000-dfffffff ioport:f000(size=64) memory:c0000-dffff
*-multimedia:0
description: Audio device
product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
vendor: Intel Corporation
physical id: 3
bus info: pci@0000:00:03.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:40 memory:f7834000-f7837fff
*-pci:2
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #3
vendor: Intel Corporation
physical id: 1c.2
bus info: pci@0000:00:1c.2
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:28 memory:f7700000-f77fffff
*-network
description: Wireless interface
product: Wireless 7260
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: wlan0
version: bb
serial: 7c:5c:f8:3c:c0:f3
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.3.18-59.19-default firmware=17.3216344376.0 7260-17.ucode ip=192.168.8.102 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:42 memory:f7700000-f7701fff
*-pci:3
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #4
vendor: Intel Corporation
physical id: 1c.3
bus info: pci@0000:00:1c.3
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:29 ioport:d000(size=4096) memory:f6c00000-f75fffff ioport:f3500000(size=10485760)
*-pci:6
description: PCI bridge
product: 8 Series/C220 Series Chipset Family PCI Express Root Port #8
vendor: Intel Corporation
physical id: 1c.7
bus info: pci@0000:00:1c.7
version: d4
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:32 memory:f7600000-f76fffff
*-generic
description: MMC Host
product: SD/MMC Card Reader Controller
vendor: O2 Micro, Inc.
physical id: 0
bus info: pci@0000:11:00.0
logical name: mmc0
version: 01
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=sdhci-pci latency=0
resources: irq:34 memory:f7601000-f7601fff memory:f7600000-f76007ff
*-isa
description: ISA bridge
product: QM87 Express LPC Controller
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 04
width: 32 bits
clock: 33MHz
capabilities: isa bus_master cap_list
configuration: driver=lpc_ich latency=0
resources: irq:0
*-raid
description: RAID bus controller
product: 82801 Mobile SATA Controller [RAID mode]
vendor: Intel Corporation
physical id: 1f.2
bus info: pci@0000:00:1f.2
logical name: scsi0
logical name: scsi1
version: 04
width: 32 bits
clock: 66MHz
capabilities: raid msi pm bus_master cap_list emulated
configuration: driver=ahci latency=0
resources: irq:33 ioport:f0d0(size=8) ioport:f0c0(size=4) ioport:f0b0(size=8) ioport:f0a0(size=4) ioport:f060(size=32) memory:f783a000-f783a7ff
*-disk
description: ATA Disk
product: ST1000LM035-1RK1
physical id: 0
bus info: scsi@0:0.0.0
logical name: /dev/sda
version: LFM3
serial: WKPHJQ14
size: 931GiB (1TB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=5 guid=e930395c-f6e7-44d5-8e05-39d021761097 logicalsectorsize=512 sectorsize=4096
*-volume:0
description: Windows FAT volume
vendor: mkfs.fat
physical id: 1
bus info: scsi@0:0.0.0,1
logical name: /dev/sda1
logical name: /boot/efi
version: FAT16
serial: d236-aaf3
size: 498MiB
capacity: 499MiB
capabilities: boot fat initialized
configuration: FATs=2 filesystem=fat mount.fstype=vfat mount.options=rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro state=mounted
*-volume:1
description: EXT4 volume
vendor: Linux
physical id: 2
bus info: scsi@0:0.0.0,2
logical name: /dev/sda2
logical name: /home
version: 1.0
serial: d2901452-ccc7-4b4e-9d5c-90850490497e
size: 579GiB
capabilities: journaled extended_attributes large_files huge_files dir_nlink recover extents ext4 ext2 initialized
configuration: created=2013-10-16 15:17:50 filesystem=ext4 lastmountpoint=/home modified=2021-08-30 14:52:02 mount.fstype=ext4 mount.options=rw,relatime,data=ordered mounted=2021-08-30 14:52:02 name=primary state=mounted
*-volume:2
description: EFI partition
physical id: 3
bus info: scsi@0:0.0.0,3
logical name: /dev/sda3
serial: c2a3f9be-56ff-4777-92c9-0a193cf77ce8
capacity: 129GiB
*-volume:3
description: EFI partition
physical id: 4
bus info: scsi@0:0.0.0,4
logical name: /dev/sda4
logical name: /
logical name: /.snapshots
logical name: /boot/grub2/i386-pc
logical name: /srv
logical name: /usr/local
logical name: /opt
logical name: /boot/grub2/x86_64-efi
logical name: /tmp
logical name: /root
logical name: /var
serial: 9a7b01fd-109a-459f-91e8-41b929e6921d
capacity: 121GiB
configuration: mount.fstype=btrfs mount.options=rw,relatime,space_cache,subvolid=258,subvol=/@/var state=mounted
*-volume:4
description: Linux swap volume
vendor: Linux
physical id: 5
bus info: scsi@0:0.0.0,5
logical name: /dev/sda5
version: 1
serial: 4d718675-c80d-4e7d-9977-64995869ed75
size: 99GiB
capacity: 99GiB
capabilities: nofs swap initialized
configuration: filesystem=swap pagesize=4095
marel
August 30, 2021, 5:40pm
#2
Hi, Welcome to the forum!
I would not expect any noticeable speed differences between 15.1 and 15.3, but as you are running on a labtop, I think the first to check is.
Can you report back what these two commands are returning (Using Code Tags Around Your Paste and please include the command itself)
$ cat /proc/sys/vm/laptop_mode
$ sudo cpupower frequency-info
Are you running the latop with the power connected?
Thank you for your reply!
$ cat /proc/sys/vm/laptop_mode
0
$ sudo cpupower frequency-info
CPU 0 wird analysiert:
driver: intel_pstate
CPUs, die mit der gleichen Hardwarefrequenz laufen: 0
CPUs, die ihre Frequenz mit Software koordinieren müssen: 0
Maximale Dauer eines Taktfrequenzwechsels: Cannot determine or is not supported.
Hardwarebegrenzungen: 800 MHz - 3.90 GHz
verfügbare cpufreq-Regler: performance powersave
momentane Richtlinie: Frequenz sollte innerhalb 800 MHz und 3.90 GHz.
sein. Der Regler "powersave" kann frei entscheiden,
welche Geschwindigkeit er in diesem Bereich verwendet.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.89 GHz (asserted by call to kernel)
boost state support:
Unterstützt: ja
Aktiv: ja
marel
August 30, 2021, 10:02pm
#4
Okay, nothing suspected as far as I can see related to special laptop power options.
Not too easy problem as there can be a lot op possible causes. For a slow boot there are good tools to diagnose things like:
$ sudo systemd-analyze blame
$ sudo systemd-analyze critical-chain
You can post the output here.
Not sure that will help, but maybe it gives a clue.
larryr
August 30, 2021, 10:40pm
#5
Did you do a fresh install or did you go 15.1 to 15.3 - without going to 15.2?
If fresh install you may have gone from ext4 file system and now have btrfs file system, which many feel slower on non SSD hard drives.
my 2 cents
please cat /etc/fstab to show what you have.
chamileo:
Hi,
I have Dell Precision M4800 and I have had OpenSuse 15.1 - it has worked nicely. So now, I have installed 15.3 and the laptop is feelable slow, the startup and wakeup are slow, the usage is not so comfortable.Is my laptot too old for this Opensuse version, or have I done something wrong (bad drives, etc…)?
I’m not certain but since Leap 15.3 shares sources with SLE the default kernel is compiled without the “voluntary kernel preemption”. Preemption is a CPU scheduler tuning aiming at better interactivity which is noticeable during desktop use but at the expense of throughput which is noticeable during server use. To check what preemption config options are compiled in or not in your currently running kernel, run:
$ zgrep -i preempt /proc/config.gz
CONFIG_PREEMPT_NONE is set on kernel-default so no preemption there.
One way to mitigate it is to install the kernel-preempt from official repositories. This kernel has the preemption compiled in but it is the “full-fledged” preemption for a change instead of the partial one (“CONFIG_PREEMPT_VOLUNTARY”) which would otherwise offer a sort of middle-ground preemption.
To fully make the behavior like it was pre-Leap-15.3 is to have the partial preemption but kernel-default nor kernel-preempt is compiled this way so we have to wait till the upgrade to kernel 5.12 where it’s possible to set partial preemption with the preempt=voluntary kernel flag: https://bugzilla.opensuse.org/show_bug.cgi?id=1185518.
Note that this won’t fix your startup & wakeup times since those relate more to your disk scheduler than the CPU one but it might fix your usage after the system is booted or woken up.
Hi
@chamileo , any reason your wanting a 99GB swap partition? Should only need 1.5xRAM, maybe that’s why it’s slow…
NVidia + Intel usually spells Optimus and requires suse-prime. Is it installed now? Were you using Bumblebee in 15.1? Please ensure xdpyinfo is installed and provide output from
inxi -SGay
run from Konsole, Xterm or equivalent GUI terminal. If kernel-default extra is not installed, install it, as the nouveau kernel module got moved into it from kernel-default with 15.3’s switch to the SLE kernel.
Thank you for your replies!
outputs:
$ sudo systemd-analyze blame
35.095s systemd-fsck@dev-disk-by\x2duuid-d2901452\x2dccc7\x2d4b4e\x2d9d5c\x2d90850490497e.service
16.680s udisks2.service
7.575s initrd-switch-root.service
5.622s display-manager.service
4.958s plymouth-quit-wait.service
4.623s apparmor.service
3.814s polkit.service
3.452s systemd-udevd.service
3.294s smartd.service
3.132s dracut-initqueue.service
2.998s firewalld.service
2.484s avahi-daemon.service
2.191s postfix.service
1.529s systemd-logind.service
1.248s upower.service
1.192s user@1000.service
1.186s rsyslog.service
1.141s NetworkManager.service
1.084s bluetooth.service
1.065s systemd-fsck@dev-disk-by\x2duuid-D236\x2dAAF3.service
946ms nscd.service
817ms systemd-random-seed.service
752ms systemd-journal-flush.service
661ms ModemManager.service
602ms sysroot.mount
472ms plymouth-switch-root.service
379ms mcelog.service
375ms boot-efi.mount
374ms systemd-tmpfiles-setup.service
356ms kbdsettings.service
332ms systemd-modules-load.service
308ms systemd-remount-fs.service
306ms modprobe@fuse.service
299ms home.mount
294ms auditd.service
291ms klog.service
281ms systemd-journald.service
276ms sound-extra.service
256ms dev-disk-by\x2duuid-4d718675\x2dc80d\x2d4e7d\x2d9977\x2d64995869ed75.swap
209ms root.mount
207ms var.mount
189ms tmp.mount
176ms systemd-tmpfiles-setup-dev.service
174ms chronyd.service
162ms systemd-udev-trigger.service
142ms modprobe@configfs.service
142ms systemd-backlight@backlight:intel_backlight.service
132ms plymouth-start.service
111ms initrd-parse-etc.service
92ms dev-hugepages.mount
91ms dev-mqueue.mount
91ms sys-kernel-debug.mount
90ms sys-kernel-tracing.mount
85ms systemd-sysctl.service
83ms wpa_supplicant.service
72ms boot-grub2-x86_64\x2defi.mount
71ms plymouth-read-write.service
70ms systemd-update-utmp.service
67ms systemd-user-sessions.service
61ms systemd-fsck-root.service
51ms opt.mount
44ms usr-local.mount
42ms dracut-shutdown.service
39ms srv.mount
31ms dracut-cmdline.service
27ms systemd-rfkill.service
18ms rtkit-daemon.service
15ms systemd-backlight@leds:dell::kbd_backlight.service
14ms user-runtime-dir@1000.service
$ sudo systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @55.418s
└─display-manager.service @49.795s +5.622s
└─time-sync.target @49.792s
└─chronyd.service @49.617s +174ms
└─network.target @49.616s
└─NetworkManager.service @48.475s +1.141s
└─network-pre.target @48.474s
└─wpa_supplicant.service @50.942s +83ms
└─dbus.service @41.653s
└─basic.target @41.650s
└─sockets.target @41.650s
└─pcscd.socket @41.650s
└─sysinit.target @41.569s
└─systemd-update-utmp.service @41.498s +70ms
└─auditd.service @41.203s +294ms
└─systemd-tmpfiles-setup.service @40.827s +374ms
└─local-fs.target @40.825s
└─home.mount @40.526s +299ms
└─systemd-fsck@dev-disk-by\x2duuid-d2901452\x2dccc7\x2d4b4e\x2d9d5c\x2d90850490497e.service @5.430s +35.095s
└─local-fs-pre.target @5.424s
└─systemd-tmpfiles-setup-dev.service @5.248s +176ms
└─kmod-static-nodes.service @4.934s +5ms
└─systemd-journald.socket
└─-.mount
└─system.slice
└─-.slice
$ cat /etc/fstab
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c / btrfs defaults 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=4d718675-c80d-4e7d-9977-64995869ed75 swap swap defaults 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /var btrfs subvol=/@/var 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /usr/local btrfs subvol=/@/usr/local 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /tmp btrfs subvol=/@/tmp 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /srv btrfs subvol=/@/srv 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /root btrfs subvol=/@/root 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /opt btrfs subvol=/@/opt 0 0
UUID=d2901452-ccc7-4b4e-9d5c-90850490497e /home ext4 data=ordered 0 2
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=D236-AAF3 /boot/efi vfat utf8 0 2
$ zgrep -i preempt /proc/config.gz
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_DRM_I915_PREEMPT_TIMEOUT=640
# CONFIG_PREEMPTIRQ_EVENTS is not set
CONFIG_PREEMPTIRQ_DELAY_TEST=m
$ inxi -SGay
Error 10: Unsupported value: 0 for option: y
Check -h for correct parameters.
$inxi -SGa
System: Host: localhost.localdomain Kernel: 5.3.18-59.19-default x86_64 bits: 64 compiler: gcc v: 7.5.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.19-default root=UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c
splash=silent resume=/dev/disk/by-uuid/4d718675-c80d-4e7d-9977-64995869ed75 mitigations=auto quiet
Desktop: KDE Plasma 5.18.6 tk: Qt 5.12.7 wm: kwin_x11 dm: SDDM Distro: openSUSE Leap 15.3
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0416
Device-2: NVIDIA GK107GLM [Quadro K1100M] vendor: Dell driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0ff6
Device-3: Microdia Integrated Webcam type: USB driver: uvcvideo bus ID: 1-1.5:3 chip ID: 0c45:64d0
Display: x11 server: X.Org 1.20.3 compositor: kwin_x11 driver: modesetting,nouveau unloaded: fbdev,vesa
alternate: intel,nv,nvidia display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.2.4 compat-v: 3.0 direct render: Yes
why I have so big swap - I have had smalled HDD before and copied the disc to new one per dd. It’s not SSD, neither this nor the older one. It was not possible for me to make the root partition so big as I wanted so the last free space I gave to swap and I wanted to resize the root and swap partition afterwards from a gparted live disc (but I haven’t done it yet). Maybe it was all not good idea…
I have read all your answers but I haven’t done any action yet for sure and let only the command outputs here… please don’t think I am “lazy” to do something, I only try to be “cautious” in what I do
I see the systemd-fsck in the list and I don’t know if this is common to this extent…
mrmazda
August 31, 2021, 9:58am
#11
This won’t happen again if you successfully run inxi -U first, to upgrade to the current version from upstream. Leap’s is old, missing options and a bunch of bug fixes found in recent versions.
marel
August 31, 2021, 10:24am
#12
The boot took long because fsck had to check your home partition, that is not a good sign.
I see that is a separate ext4 partition, can you try:
$ sudo dumpe2fs -b /dev/disk/by-uuid/d2901452-ccc7-4b4e-9d5c-90850490497e
$ sudo tune2fs -l /dev/disk/by-uuid/d2901452-ccc7-4b4e-9d5c-90850490497e
$ sudo hdparm -Tt /dev/sda
inxi -U was really the solution for inxi -SGay:
$ inxi -SGay
System:
Host: localhost.localdomain Kernel: 5.3.18-59.19-default x86_64 bits: 64
compiler: gcc v: 7.5.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.19-default
root=UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c splash=silent
resume=/dev/disk/by-uuid/4d718675-c80d-4e7d-9977-64995869ed75
mitigations=auto quiet
Desktop: KDE Plasma 5.18.6 tk: Qt 5.12.7 wm: kwin_x11 vt: 7 dm: SDDM
Distro: openSUSE Leap 15.3
Graphics:
Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Dell
driver: i915 v: kernel bus-ID: 00:02.0 chip-ID: 8086:0416 class-ID: 0300
Device-2: NVIDIA GK107GLM [Quadro K1100M] vendor: Dell driver: nouveau
v: kernel bus-ID: 01:00.0 chip-ID: 10de:0ff6 class-ID: 0300
Device-3: Microdia Integrated Webcam type: USB driver: uvcvideo
bus-ID: 1-1.5:3 chip-ID: 0c45:64d0 class-ID: 0e02
Display: x11 server: X.Org 1.20.3 compositor: kwin_x11 driver:
loaded: modesetting,nouveau unloaded: fbdev,vesa alternate: intel,nv,nvidia
display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2")
s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6")
diag: 395mm (15.5")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2)
v: 4.5 Mesa 20.2.4 compat-v: 3.0 direct render: Yes
/home partition - what can be the reason for fsck to check?
$ sudo dumpe2fs -b /dev/disk/by-uuid/d2901452-ccc7-4b4e-9d5c-90850490497e
dumpe2fs 1.43.8 (1-Jan-2018)
$ sudo tune2fs -l /dev/disk/by-uuid/d2901452-ccc7-4b4e-9d5c-90850490497e
tune2fs 1.43.8 (1-Jan-2018)
Filesystem volume name: <none>
Last mounted on: /home
Filesystem UUID: d2901452-ccc7-4b4e-9d5c-90850490497e
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 38010880
Block count: 152043008
Reserved block count: 7602150
Free blocks: 37348457
Free inodes: 35997820
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 987
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Wed Oct 16 15:17:50 2013
Last mount time: Mon Aug 30 14:52:02 2021
Last write time: Mon Aug 30 14:52:02 2021
Mount count: 6
Maximum mount count: -1
Last checked: Sat Aug 28 11:17:13 2021
Check interval: 0 (<none>)
Lifetime writes: 11 TB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
First orphan inode: 9324626
Default directory hash: half_md4
Directory Hash Seed: 64373e63-79ef-49b4-bf78-ec02c6c04991
Journal backup: inode blocks
$ sudo hdparm -Tt /dev/sda
/dev/sda:
Timing cached reads: 24728 MB in 1.99 seconds = 12425.43 MB/sec
Timing buffered disk reads: 308 MB in 3.00 seconds = 102.65 MB/sec
mrmazda
September 1, 2021, 8:14am
#14
Slowness/speed of the 1TB Seagate HDD can be investigated using hdparm for speed test, as you’ve done, and smartctl, to get feedback from the HDD’s firmware on the condition of the drive. Use smartctl -x /dev/sdX to check the current data, smartctl -t long /dev/sdX , to have a current thorough read test done. What you’re most interested in are several of the lines following these lines:
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
Mainly lines containing correct*, reallocated & pending indicate whether its remaining time may be short, or over.
There’s nothing obviously wrong showing in inxi output. It shows the required kernel drivers i915 and nouveau loaded, modesetting DIX (display) driver for the Intel, and nouveau DDX (display) driver for the NVidia. Uninstalling xorg-x11-driver-video and xf86-video-nouveau could possibly improve display output, but could possibly make it worse. Without xf86-video-nouveau installed, only the modesetting DIX would be needed for display output from either GPU. Modesetting is actually the default upstream, and it’s the only driver I use on NVidia GPUs it supports. If you have suse-prime installed and configured appropriately, display performance should be a non-issue.
marel
September 1, 2021, 8:44am
#15
Your tunefs output shows no real problems, only I see “orphan nodes” reported but that is no big problem I think, so smartctl like @mrmazda suggested is a good idea.
One further question: Do you see over multiple setups that systemd-fsck is taking a lot of time? It can happen once but should not happen every boot.
ok, I have started "smartctl -t long /dev/sda"
in “smartctl -x /dev/sda ”, there was:
$ **smartctl -x /dev/sda
(...)**
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 082 064 034 - 145194710
3 Spin_Up_Time PO---- 099 099 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 58
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 0
7 Seek_Error_Rate POSR-- 066 060 045 - 4304198
9 Power_On_Hours -O--CK 100 100 000 - 55 (45 150 0)
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 55
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
188 Command_Timeout -O--CK 100 100 000 - 0
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 073 054 040 - 27 (Min/Max 21/27)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 22
192 Power-Off_Retract_Count -O--CK 100 100 000 - 11
193 Load_Cycle_Count -O--CK 100 100 000 - 1033
194 Temperature_Celsius -O---K 027 046 000 - 27 (0 18 0 0 0)
196 Reallocated_Event_Count -O--CK 100 100 000 - 0
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours POSR-- 100 100 030 - 51 (191 241 0)
254 Free_Fall_Sensor -O--CK 100 100 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x04 GPL,SL R/O 8 Device Statistics log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 NCQ Command Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x24 GPL R/O 512 Current Device Internal Status Data log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 24 Device vendor specific log
0xa2 GPL VS 8160 Device vendor specific log
0xa8 GPL,SL VS 136 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xab GPL VS 1 Device vendor specific log
0xb0 GPL VS 8920 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL,SL VS 16 Device vendor specific log
0xc2 GPL,SL VS 240 Device vendor specific log
0xc3 GPL,SL VS 8 Device vendor specific log
0xc4 GPL,SL VS 24 Device vendor specific log
0xd3 GPL VS 1920 Device vendor specific log
0xdf GPL,SL VS 1 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 1
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1 [0] occurred at disk power-on lifetime: 9 hours (0 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
04 -- 51 00 00 00 00 46 f3 90 30 00 00
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
ea 00 00 00 00 00 00 00 00 00 00 00 00 03:40:15.719 FLUSH CACHE EXT
60 00 00 00 68 00 00 0c 7f f7 88 40 00 03:40:15.667 READ FPDMA QUEUED
60 00 00 00 80 00 00 0c 7f f7 00 40 00 03:40:15.667 READ FPDMA QUEUED
60 00 00 00 f8 00 00 0c 7f f6 00 40 00 03:40:15.667 READ FPDMA QUEUED
60 00 00 02 00 00 00 0c 7f f4 00 40 00 03:40:15.666 READ FPDMA QUEUED
(,,,)
What I can see, is that there is one error, but I am not able to understand what error it’s about?
… and yes, I have seen the fsck more times by startup
mrmazda
September 1, 2021, 10:18am
#18
IDK either, but the time it happened was when the device was a baby, which it isn’t since long ago, so should be nothing to be concerned about. Here’s one I’m writing this from, for comparison:
smartctl -x /dev/sdc
...
Model Family: Seagate Barracuda 7200.14 (AF)
Device Model: ST1000DM003-1CH162
...
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 118 099 006 - 182419656
3 Spin_Up_Time PO---- 097 097 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 16
5 Reallocated_Sector_Ct PO--CK 100 100 010 - 0
7 Seek_Error_Rate POSR-- 079 060 030 - 97930635
9 Power_On_Hours -O--CK 096 096 000 - 3555
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 16
183 Runtime_Bad_Block -O--CK 100 100 000 - 0
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 100 100 000 - 0
188 Command_Timeout -O--CK 100 100 000 - 0 0 0
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 069 064 045 - 31 (Min/Max 29/33)
191 G-Sense_Error_Rate -O--CK 100 100 000 - 0
192 Power-Off_Retract_Count -O--CK 100 100 000 - 7
193 Load_Cycle_Count -O--CK 100 100 000 - 208
194 Temperature_Celsius -O---K 031 040 000 - 31 (0 22 0 0 0)
197 Current_Pending_Sector -O--C- 100 100 000 - 0
198 Offline_Uncorrectable ----C- 100 100 000 - 0
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
240 Head_Flying_Hours ------ 100 253 000 - 3548h+35m+49.311s
241 Total_LBAs_Written ------ 100 253 000 - 3522184229
242 Total_LBAs_Read ------ 100 253 000 - 58158282355
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
...
chamileo:
Thank you for your replies!
outputs:
$ sudo systemd-analyze blame
35.095s systemd-fsck@dev-disk-by\x2duuid-d2901452\x2dccc7\x2d4b4e\x2d9d5c\x2d90850490497e.service
16.680s udisks2.service
7.575s initrd-switch-root.service
5.622s display-manager.service
4.958s plymouth-quit-wait.service
4.623s apparmor.service
3.814s polkit.service
3.452s systemd-udevd.service
3.294s smartd.service
3.132s dracut-initqueue.service
2.998s firewalld.service
2.484s avahi-daemon.service
2.191s postfix.service
1.529s systemd-logind.service
1.248s upower.service
1.192s user@1000.service
1.186s rsyslog.service
1.141s NetworkManager.service
1.084s bluetooth.service
1.065s systemd-fsck@dev-disk-by\x2duuid-D236\x2dAAF3.service
...
$ sudo systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @55.418s
└─display-manager.service @49.795s +5.622s
└─time-sync.target @49.792s
└─chronyd.service @49.617s +174ms
└─network.target @49.616s
└─NetworkManager.service @48.475s +1.141s
└─network-pre.target @48.474s
└─wpa_supplicant.service @50.942s +83ms
└─dbus.service @41.653s
└─basic.target @41.650s
└─sockets.target @41.650s
└─pcscd.socket @41.650s
└─sysinit.target @41.569s
└─systemd-update-utmp.service @41.498s +70ms
└─auditd.service @41.203s +294ms
└─systemd-tmpfiles-setup.service @40.827s +374ms
└─local-fs.target @40.825s
└─home.mount @40.526s +299ms
└─systemd-fsck@dev-disk-by\x2duuid-d2901452\x2dccc7\x2d4b4e\x2d9d5c\x2d90850490497e.service @5.430s +35.095s
└─local-fs-pre.target @5.424s
└─systemd-tmpfiles-setup-dev.service @5.248s +176ms
└─kmod-static-nodes.service @4.934s +5ms
└─systemd-journald.socket
└─-.mount
└─system.slice
└─-.slice
$ cat /etc/fstab
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c / btrfs defaults 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /.snapshots btrfs subvol=/@/.snapshots 0 0
UUID=4d718675-c80d-4e7d-9977-64995869ed75 swap swap defaults 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /var btrfs subvol=/@/var 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /usr/local btrfs subvol=/@/usr/local 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /tmp btrfs subvol=/@/tmp 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /srv btrfs subvol=/@/srv 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /root btrfs subvol=/@/root 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /opt btrfs subvol=/@/opt 0 0
UUID=d2901452-ccc7-4b4e-9d5c-90850490497e /home ext4 data=ordered 0 2
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /boot/grub2/x86_64-efi btrfs subvol=/@/boot/grub2/x86_64-efi 0 0
UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c /boot/grub2/i386-pc btrfs subvol=/@/boot/grub2/i386-pc 0 0
UUID=D236-AAF3 /boot/efi vfat utf8 0 2
$ zgrep -i preempt /proc/config.gz
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_NOTIFIERS=y
CONFIG_DRM_I915_PREEMPT_TIMEOUT=640
# CONFIG_PREEMPTIRQ_EVENTS is not set
CONFIG_PREEMPTIRQ_DELAY_TEST=m
$ inxi -SGay
Error 10: Unsupported value: 0 for option: y
Check -h for correct parameters.
$inxi -SGa
System: Host: localhost.localdomain Kernel: 5.3.18-59.19-default x86_64 bits: 64 compiler: gcc v: 7.5.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.19-default root=UUID=0544520c-d3c6-4fc6-bb07-8d94da0af64c
splash=silent resume=/dev/disk/by-uuid/4d718675-c80d-4e7d-9977-64995869ed75 mitigations=auto quiet
Desktop: KDE Plasma 5.18.6 tk: Qt 5.12.7 wm: kwin_x11 dm: SDDM Distro: openSUSE Leap 15.3
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Dell driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0416
Device-2: NVIDIA GK107GLM [Quadro K1100M] vendor: Dell driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0ff6
Device-3: Microdia Integrated Webcam type: USB driver: uvcvideo bus ID: 1-1.5:3 chip ID: 0c45:64d0
Display: x11 server: X.Org 1.20.3 compositor: kwin_x11 driver: modesetting,nouveau unloaded: fbdev,vesa
alternate: intel,nv,nvidia display ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9")
Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 142 size: 344x194mm (13.5x7.6") diag: 395mm (15.5")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.2.4 compat-v: 3.0 direct render: Yes
why I have so big swap - I have had smalled HDD before and copied the disc to new one per dd. It’s not SSD, neither this nor the older one. It was not possible for me to make the root partition so big as I wanted so the last free space I gave to swap and I wanted to resize the root and swap partition afterwards from a gparted live disc (but I haven’t done it yet). Maybe it was all not good idea…
Your outputs of ‘systemd-analyze blame’ as well as of ‘systemd-analyze critical-chain’ reveal abysmal performance. Compare the processors involved: https://www.cpubenchmark.net/compare/Intel-i7-4910MQ-vs-Intel-i3-4130/2220vs2015 Whlie your i7-4910MQ is twice as powerful than my i3-4130 the latter exhibits by far superior performance:
**i3-4130:~ #** systemd-analyze blame |head -22
934ms dracut-pre-udev.service
664ms display-manager.service
541ms postfix.service
448ms dracut-initqueue.service
365ms kbdsettings.service
343ms initrd-switch-root.service
285ms systemd-journal-flush.service
277ms systemd-resolved.service
275ms udisks2.service
242ms chronyd.service
231ms apache2.service
214ms systemd-udevd.service
183ms issue-generator.service
160ms systemd-logind.service
138ms mcelog.service
128ms initrd-parse-etc.service
127ms upower.service
105ms sound-extra.service
102ms [EMAIL="user@1000.servic"]user@1000.servic[/EMAIL]e
98ms polkit.service
90ms systemd-udev-trigger.service
74ms systemd-user-sessions.service
**i3-4130:~ #** systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @2.071s
└─**display-manager.service @1.406s +664ms**
└─**apache2.service @1.173s +231ms**
└─time-sync.target @1.166s
└─**chronyd.service @922ms +242ms**
└─nss-lookup.target @921ms
└─**systemd-resolved.service @643ms +277ms**
└─**systemd-tmpfiles-setup.service @605ms +35ms**
└─**systemd-journal-flush.service @318ms +285ms**
└─**var.mount @303ms +11ms**
└─local-fs-pre.target @295ms
└─**systemd-tmpfiles-setup-dev.service @248ms +46ms**
└─**kmod-static-nodes.service @209ms +31ms**
└─systemd-journald.socket
└─system.slice
└─-.slice
**i3-4130:~ #**
Presumably the drives of both systems make a big difference:
**i3-4130:~ #** inxi -Daz
**Drives: Local Storage:****total:** 232.89 GiB **used:** 17.11 GiB (7.3%)
**ID-1:** /dev/sda **maj-min:** 8:0 **vendor:** Crucial **model:** CT250MX500SSD1 **family:** Micron Client SSDs **size:** 232.89 GiB
**block-size:****physical:** 4096 B **logical:** 512 B **sata:** 3.3 **speed:** 6.0 Gb/s **rotation:** SSD **serial:** <filter> **rev:** 023
**scheme:** GPT
**SMART:** yes **state:** disabled
**i3-4130:~ #**