Problem at start

hi all
I’m experiencing a problem with my leap 15.2. When I switch on my laptop, all the boot procedure goes well but it take quite long time (approx 5 minutes) to display the login mask.
This problem has arisen recently :’(

Do you have a solution?

Question: if I reinstall leap 15.2 over the same distro, I will lose my data or the installation will preserve them?

please help


systemd-analyze blame

give you any useful information?

That depends on how the partition scheme on your disk – if you have a separate partition for the user directories then, you can re-install with whatever is needed regarding the system partition.

  • If however, the user directories are located included in the system partition, you can only overwrite the system files in that partition – you can not perform a “clean” re-installation including re-formatting and possibly re-sizing the system partition.

[HR][/HR]Can you please tell us which file-system or, file-systems, you’re using on the Laptop’s disk?
Does the Laptop have UEFI or, is it an older BIOS-only device?

this is what I get with that line of code

       6.372s NetworkManager-wait-online.service          3.448s mandb.service
      2.892s dracut-initqueue.service
      2.396s btrfsmaintenance-refresh.service
       892ms backup-rpmdb.service
       807ms postfix.service
       677ms apparmor.service
       622ms display-manager.service
       550ms firewalld.service

those are the most time consuming task, I don’t think the problem is there

I assume you looked at what happens using the Esc key. When it really stands still for 5 mins, then you must be able to write down the last few lines before the stand still, and maybe even the first line after it runs again.


this is what I have on screen during the 5 min stand period

[ok] Started Permit user session.
Starting Hold until boot process finishes up…
Starting X Display manager…
Starting Locale Service…
[ok] Started Locale Service.

after that, the splash screen with login mask appear

Have you any idea?


Show as root:

systemctl list-units --all failed

And please use Code-tags for that:

this is what I get as root

voyager:/home/gca # systemctl list-units --all failed0 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

You can see inside the boot.log and see, where the time is not continued:
as root:

journalctl -b

Use the Cursor keys to navigate and use q to abort.

Copy it at:
and post the URL you get there here in this thread

Agreed but, there are some clues in there:

  • The system partition on the Laptop seems to have a Btrfs file system.
  • It’s a Laptop – therefore absolutely no need to have the Network Manager’s “wait until we’re on-line” service enabled – if it’s being done properly, and there’s a WLAN involved, the network connection first happens when the user logs in …


  1. Please check what “btrfs filesystem df /
    ” is indicating – the system partition (with a Btrfs file system) may well have a free space issue … 1. Even if some space seems to be available, do some Btrfs system partition housekeeping:
  • Drop the system into the systemd Rescue mode: “systemctl rescue” – user “root” from a VT (tty1 … tty6) – log everyone out beforehand …
  • After typing in the password of the user “root”, execute, one after the other, and check that each housekeeping task has completed before beginning the next one:
  • “systemctl start btrfs-defrag.service”
  • “systemctl start btrfs-scrub.service”
  • “btrfs balance start -dusage=85 /”
  • “btrfs balance start -musage=70 /”
  • “btrfs scrub start -B /”

Note Bene: “/” …

here is the url


When the X.Org screen starts, there’s an AMD graphic driver issue:

  • Please determine which AMD Graphics hardware is present on the Laptop.
  • Please check which generation of AMD Graphics hardware is present on the Laptop.
  • You may have to black list either the amdgpu driver or, the radeon driver in the Kernel’s command line.
  • And, if Radeon then, you may have to deal with Southern Islands or Sea Islands support in the amdgpu driver …

Take a look in ‘/var/log/Xorg.0.log’ to check what’s going on with the AMD Graphics driver.

Also to the thread of dcurtisfra:
This is the error

Oct 02 18:52:01 voyager kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
Oct 02 18:52:01 voyager kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing C0E2 (len 1136, WS 0, PS 0) @ 0xC10C
Oct 02 18:55:01 voyager kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting
Oct 02 18:55:01 voyager kernel: [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CA9C (len 62, WS 0, PS 0) @ 0xCAB8

3 minutes…

Can you add


to your grub-cmdline at the end and start then?

Or if any tlp package is installed delete them.

thanks for the tip, sorry but I’m a newbye in linux, can you explain how I can add something to the grub-command line?

In Grub press the key e, goto the line beginning with linux and add there at the end of the line the parameter I posted with a space to the one before.
Hit than F10 to start.

Does it now start faster?

But this is onla a workaround to see if it is working, works only up to the next boot.
Only for testing.

yes it does, faster as before. How can I make this definitively?

Use: Yast Boot Loader

and look at the Kernel Parameters tab.

Thanks to all of you guys, it works well now