Announcement

Collapse
No announcement yet.

30 seconds hang at boot

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] 30 seconds hang at boot

    Trying to understand what's causing a hang on a PC connected to a TV in our living room with a freshly installed Kubuntu. Troubleshooted a bit, exported logs. Just wondering if anybody had a similar issue.

    PC specs:
    ASrock B450M Pro
    Ryzen 2600
    8GB Ram
    500GB Western Digital Black nVME SSD
    MSI RX580
    40in Philips TV connected with HDMI


    aoû 11 07:36:23 JeuxTV-PC kernel: audit: type=1400 audit(1786448183.161:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="babeld" pid=747 comm="apparmor_parser"

    aoû 11 07:36:23 JeuxTV-PC kernel: audit: type=1400 audit(1786448183.162:12): apparmor="STATUS" operation="profile_load" profile="unconfined" name="alsamixer" pid=746 comm="apparmor_parser"

    aoû 11 07:36:23 JeuxTV-PC kernel: audit: type=1400 audit(1786448183.162:13): apparmor="STATUS" operation="profile_load" profile="unconfined" name=4D6F6E676F444220436F6D70617373 pid=743 comm="apparmor_parser"

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: autoconfig for ALC892: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: mono: mono_out=0x0

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: inputs:

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: Rear Mic=0x18

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: Front Mic=0x19

    aoû 11 07:36:56 JeuxTV-PC kernel: snd_hda_codec_alc662 hdaudioC1D0: Line=0x1a

    aoû 11 07:36:56 JeuxTV-PC kernel: amdgpu: Virtual CRAT table created for CPU

    aoû 11 07:36:56 JeuxTV-PC kernel: amdgpu: Topology: Add CPU node

    aoû 11 07:36:56 JeuxTV-PC kernel: amdgpu 0000:07:00.0: enabling device (0006 -> 0007)

    aoû 11 07:36:56 JeuxTV-PC kernel: amdgpu 0000:07:00.0: initializing kernel modesetting (POLARIS10 0x1002:0x67DF 0x1462:0x3417 0xE7).

    aoû 11 07:36:56 JeuxTV-PC kernel: amdgpu 0000:07:00.0: register mmio base: 0xFCE00000

    #2
    In a konsole run: systemd-analyze-blame > blame.txt

    Then type: head blame.txt

    Copy and paste the output into your reply.
    Slava Ukraini! 🇺🇦
    Windows no longer obstruct my view.
    Using Kubuntu Linux since March 23, 2007.
    "It is a capital mistake to theorize before one has data." - Sherlock Holmes

    Comment


      #3
      45.539s ufw.service
      45.510s snapd.apparmor.service
      44.830s systemd-binfmt.service
      44.792s proc-sys-fs-binfmt_misc.mount
      5.441s NetworkManager-wait-online.service
      2.687s waydroid-container.service
      2.296s snapd.seeded.service
      2.201s snapd.service
      625ms accounts-daemon.service
      597ms NetworkManager.service
      578ms boot-efi.mount
      573ms udisks2.service
      572ms mnt-D.mount
      553ms snap-bare-5.mount
      536ms input-remapper-daemon.service
      531ms snap-core24-1643.mount
      517ms chrony.service
      513ms snap-core24-2124.mount
      508ms snap-firefox-8863.mount
      506ms dev-nvme0n1p7.device
      497ms snap-firefox-8929.mount
      495ms snap-gaming\x2dgraphics\x2dcore24-13.mount
      493ms polkit.service
      492ms snap-gnome\x2d46\x2d2404-153.mount
      490ms snap-gnome\x2d46\x2d2404-164.mount
      487ms snap-gtk\x2dcommon\x2dthemes-1535.mount
      485ms snap-gtk\x2dtheme\x2dbreeze-8.mount
      483ms snap-icon\x2dtheme\x2dbreeze-5.mount
      480ms snap-mesa\x2d2404-1165.mount
      467ms snap-mesa\x2d2404-1839.mount
      457ms lm-sensors.service
      439ms snap-snapd-27710.mount
      424ms snap-snapd-27738.mount
      396ms snap-steam-231.mount
      392ms rsyslog.service
      366ms snap-steam-271.mount
      360ms networkd-dispatcher.service
      358ms grub2-common.service
      354ms gpu-manager.service
      353ms avahi-daemon.service
      324ms grub-initrd-fallback.service
      321ms snap-thunderbird-1228.mount
      317ms user@1001.service
      304ms systemd-logind.service
      297ms systemd-udev-trigger.service
      296ms dbus.service
      281ms snap-thunderbird-1255.mount
      263ms dev-loop7.device
      263ms dev-loop4.device
      247ms secureboot-db.service
      234ms tmp.mount
      234ms apparmor.service
      219ms switcheroo-control.service
      217ms dev-loop0.device
      215ms dev-loop5.device
      215ms dev-loop6.device
      213ms dev-loop9.device
      212ms dev-loop10.device
      203ms dev-loop3.device
      201ms dev-loop8.device
      200ms dev-loop1.device
      199ms dev-loop15.device
      199ms dev-loop14.device
      198ms dev-loop12.device
      196ms dev-loop2.device
      193ms dev-loop13.device
      183ms dev-loop11.device
      162ms e2scrub_reap.service
      156ms lxc-net.service
      155ms dev-loop17.device
      151ms dev-loop18.device
      149ms dev-loop16.device
      147ms upower.service
      145ms systemd-tmpfiles-setup.service
      134ms lxcfs.service
      131ms systemd-hostnamed.service
      126ms ModemManager.service
      116ms sysstat.service
      110ms systemd-journald.service
      110ms alsa-restore.service
      108ms netplan-configure.service
      93ms systemd-journal-flush.service
      85ms systemd-udevd.service
      77ms thermald.service
      77ms smartmontools.service
      76ms keyboard-setup.service
      74ms lxc.service
      70ms systemd-fsck@dev-disk-by\x2duuid-12B8\x2d642B.service
      59ms systemd-resolved.service
      57ms power-profiles-daemon.service
      56ms lvm2-monitor.service
      54ms wpa_supplicant.service
      44ms systemd-modules-load.service
      42ms plymouth-start.service
      42ms cups.service
      40ms packagekit.service
      36ms systemd-remount-fs.service
      34ms console-setup.service
      32ms plymouth-read-write.service
      31ms rtkit-daemon.service
      30ms modprobe@efi_pstore.service
      29ms systemd-tmpfiles-setup-dev-early.service
      29ms plymouth-quit.service
      28ms kmod-static-nodes.service
      27ms sys-kernel-config.mount
      26ms user-runtime-dir@1001.service
      26ms systemd-udev-load-credentials.service
      26ms dev-mqueue.mount
      25ms dev-hugepages.mount
      25ms sys-kernel-debug.mount
      25ms sys-kernel-tracing.mount
      25ms sys-fs-fuse-connections.mount
      24ms blk-availability.service
      23ms sddm.service
      21ms snapd.socket
      19ms systemd-sysctl.service
      16ms systemd-tmpfiles-setup-dev.service
      11ms systemd-user-sessions.service
      10ms systemd-random-seed.service
      8ms openvpn.service
      8ms swapfile.swap
      7ms setvtrgb.service
      7ms polkit-agent-helper.socket
      3ms systemd-coredump.socket
      1ms systemd-sysext.socket
      939us systemd-mute-console.socket
      786us systemd-factory-reset.socket
      757us systemd-ask-password.socket
      582us systemd-creds.socket
      346us systemd-hostnamed.socket
      291us systemd-logind-varlink.socket
      277us avahi-daemon.socket
      206us uuidd.socket
      94us cups.socket
      85us dbus.socket
      54us systemd-journald.socket
      42us lvm2-lvmpolld.socket
      37us syslog.socket
      36us systemd-journald-dev-log.socket
      33us systemd-resolved-monitor.socket
      31us dm-event.socket
      29us systemd-udevd-control.socket
      27us systemd-udevd-varlink.socket
      22us systemd-rfkill.socket
      21us systemd-resolved-varlink.socket
      15us systemd-udevd-kernel.socket

      Comment


        #4
        Spent more time tonight. Installed boottchart and eventually found out it was due to input-remapper that was blocking boots due to multiple devices bug.

        Changed input remapper device to be non blocking

        /etc/udev/rules.d/60-input-remapper-daemon.rules

        RUN+="/usr/bin/systemd-run --no-block /bin/input-remapper-control --command autoload --device $env{DEVNAME}"

        Comment

        Users Viewing This Topic

        Collapse

        There are 0 users viewing this topic.

        Working...
        X