Haz tu Pregunta
0

Fedora boot muy lento

preguntado 2016-09-15 06:47:51 -0500

Buenas,

Estoy corriendo fedora 24 junto con los drivers akmod-nvidia (tengo una geforce gtx 970). El problema es que después de la pantalla de login tarda unos 30 segundos en cargar el escritorio. También me pasa al hacer shutdown o reboot. Es como si se quedara encallado en algún proceso.

dmesg

[    0.000000] microcode: microcode updated early to revision 0x20, date = 2016-03-16
[    0.000000] Linux version 4.7.3-200.fc24.x86_64 (mockbuild@bkernel01.phx2.fedoraproject.org) (gcc version 6.1.1 20160621 (Red Hat 6.1.1-3) (GCC) ) #1 SMP Wed Sep 7 17:31:21 UTC 2016
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.7.3-200.fc24.x86_64 root=UUID=1d758a1b-14fd-45d9-8209-073356300f74 ro rd.md.uuid=1aea4eb6:0d8f3568:709cb7f8:3d3bfd36 rd.md.uuid=4c2986d9:95614b5b:107f45c0:df985170 rhgb quiet rd.driver.blacklist=nouveau nouveau.modeset=0 video=vesa:off
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] x86/fpu: Using 'eager' FPU context switches.
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
[    0.000000] BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000009f379fff] usable
[    0.000000] BIOS-e820: [mem 0x000000009f37a000-0x000000009f380fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000009f381000-0x000000009fea2fff] usable
[    0.000000] BIOS-e820: [mem 0x000000009fea3000-0x00000000a0416fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000a0417000-0x00000000bd567fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bd568000-0x00000000bd5fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000bd600000-0x00000000bd640fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bd641000-0x00000000bd704fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000bd705000-0x00000000beffefff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000befff000-0x00000000beffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000bf800000-0x00000000cf9fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000042f5fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] e820: update [mem 0x9f049018-0x9f06ae57] usable ==> usable
[    0.000000] e820: update [mem 0x9f038018-0x9f048057] usable ==> usable
[    0.000000] e820: update [mem 0x9f027018-0x9f037457] usable ==> usable
[    0.000000] e820: update [mem 0x9f017018-0x9f026857] usable ==> usable
[    0.000000] e820: update [mem 0x9eff9018-0x9f016c57] usable ==> usable
[    0.000000] extended physical RAM map:
[    0.000000] reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable
[    0.000000] reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000000059000-0x000000000009efff] usable
[    0.000000] reserve setup_data: [mem 0x000000000009f000-0x000000000009ffff] reserved
[    0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000009eff9017] usable
[    0.000000] reserve setup_data: [mem 0x000000009eff9018-0x000000009f016c57] usable
[    0.000000] reserve setup_data: [mem 0x000000009f016c58-0x000000009f017017] usable
[    0.000000] reserve setup_data: [mem 0x000000009f017018-0x000000009f026857] usable
[    0.000000] reserve setup_data: [mem 0x000000009f026858-0x000000009f027017] usable
[    0.000000] reserve setup_data: [mem 0x000000009f027018-0x000000009f037457] usable
[    0.000000] reserve setup_data: [mem 0x000000009f037458-0x000000009f038017] usable
[    0.000000] reserve setup_data: [mem 0x000000009f038018-0x000000009f048057] usable
[    0.000000] reserve setup_data: [mem 0x000000009f048058-0x000000009f049017] usable
[    0.000000] reserve setup_data: [mem 0x000000009f049018-0x000000009f06ae57] usable
[    0.000000] reserve ...
(more)
edit re-etiquetar marcar como ofensivo cerrar fusionar delete

Comments

you should run system-blame analyze to validate the boot time and see what is happening on boot

Imagen Gravatar de aeperezt aeperezt ( 2016-09-15 10:38:39 -0500 )edit

1 Responder

Ordenar por » viejos nuevas más votado
0

respondido 2016-09-15 15:15:28 -0500

systemd-analyze

Startup finished in 1.121s (kernel) + 3.110s (initrd) + 4.023s (userspace) = 8.256s

systemd-analyze blame

  2.955s dnf-makecache.service
  1.621s plymouth-start.service
  1.158s systemd-udev-settle.service
  1.153s plymouth-quit-wait.service
   857ms mnt-win_data.mount
   640ms docker.service
   501ms lvm2-pvscan@8:7.service
   497ms akmods.service
   439ms firewalld.service
   387ms lvm2-monitor.service
   346ms vboxdrv.service
   325ms libvirtd.service
   226ms systemd-fsck@dev-disk-by\x2duuid-8b411b60\x2dbe0d\x2d4e6a\x2d835e\x2dd9796bab8af3.service
   208ms dev-sda6.device
   189ms upower.service
   130ms mnt-win_system.mount
   113ms accounts-daemon.service
   101ms udisks2.service
    92ms dmraid-activation.service
    83ms systemd-journald.service
    81ms ModemManager.service
    72ms abrtd.service
    70ms proc-fs-nfsd.mount
    57ms home.mount
    54ms systemd-fsck@dev-disk-by\x2duuid-14B9\x2d4528.service
    52ms polkit.service
    52ms systemd-udevd.service
    49ms systemd-journal-flush.service
    46ms gssproxy.service
    43ms akmods-shutdown.service
    43ms docker-storage-setup.service
    42ms packagekit.service
    42ms mdmonitor.service
    40ms bluetooth.service
    37ms systemd-udev-trigger.service
    37ms systemd-fsck@dev-disk-by\x2duuid-dfbfee90\x2d2161\x2d4454\x2dbe58\x2de4fd1ad3266c.service
    34ms systemd-vconsole-setup.service
    27ms avahi-daemon.service
    26ms systemd-tmpfiles-setup-dev.service
    24ms gdm.service
    23ms abrt-ccpp.service
    23ms NetworkManager.service
    21ms fedora-readonly.service
    21ms cups.service
    19ms user@1000.service
    18ms iio-sensor-proxy.service
    17ms user@42.service
    16ms systemd-tmpfiles-clean.service
    14ms chronyd.service
    14ms systemd-logind.service
    13ms systemd-fsck-root.service
    13ms auditd.service
    12ms plymouth-read-write.service
    11ms dev-mqueue.mount
    10ms systemd-sysctl.service
    10ms wpa_supplicant.service
     9ms sys-kernel-debug.mount
     9ms dev-hugepages.mount
     8ms tmp.mount
     8ms livesys.service
     8ms systemd-backlight@backlight:acpi_video0.service
     7ms systemd-remount-fs.service
     7ms rtkit-daemon.service
     7ms livesys-late.service
     7ms boot-efi.mount
     7ms colord.service
     7ms boot.mount
     6ms systemd-tmpfiles-setup.service
     6ms fedora-import-state.service
     4ms systemd-update-utmp-runlevel.service
     4ms kmod-static-nodes.service
     4ms rpc-statd-notify.service
     4ms vboxweb-service.service
     3ms vboxballoonctrl-service.service
     3ms vboxautostart-service.service
     3ms nfs-config.service
     2ms systemd-rfkill.service
     2ms systemd-update-utmp.service
     2ms systemd-user-sessions.service
     2ms var-lib-nfs-rpc_pipefs.mount
     2ms systemd-random-seed.service
     2ms mdmon@md127.service
     1ms blk-availability.service
     1ms sys-fs-fuse-connections.mount
     1ms sys-kernel-config.mount
     1ms dracut-shutdown.service
edit marcar como ofensivo delete enlace mas

Herramientas de Preguntas

Estadisticas

Preguntado: 2016-09-15 06:47:51 -0500

Visto: 144 veces

Ultima actualización: Sep 15 '16