Boot excessivement long

[Frederix]

Amis de Linux Mint bonjour,
La machine que j'ai assemblé fonctionne mais le temps de boot est anormalement long.
A part les erreurs ACPI sans importance (dûes à des contrôles alims conçus pour W$ sans respecter les standards ACPI pour les autres OS), je ne sais pas trop interpréter les erreurs donc je ne vois pas d'où vient le ralentissment. Quelqu'un peut peut-être me souffler une direction?

Code : Tout sélectionner

bienveillant@bienveillant-pc:~$ sudo dmesg -l err,crit,warn
[    0.118739] x86/cpu: SGX disabled by BIOS.
[    0.141150] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[    0.141150]  #5 #6 #7
[    0.204295] ACPI BIOS Error (bug): Failure creating named object [\ADBG], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.204304] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[    1.891892] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGON.PBGE], AE_NOT_FOUND (20210730/psargs-330)

[    1.891900] No Local Variables are initialized for Method [PGON]

[    1.891901] Initialized Arguments for Method [PGON]:  (1 arguments defined for method invocation)
[    1.891902]   Arg0:   0000000030a1c56a <Obj>           Integer 0000000000000000

[    1.891907] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    1.891912] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    4.094970] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    4.096178] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    4.096242] platform eisa.0: EISA: Cannot allocate resource for mainboard
[    4.096243] platform eisa.0: Cannot allocate resource for EISA slot 1
[    4.096244] platform eisa.0: Cannot allocate resource for EISA slot 2
[    4.096244] platform eisa.0: Cannot allocate resource for EISA slot 3
[    4.096245] platform eisa.0: Cannot allocate resource for EISA slot 4
[    4.096246] platform eisa.0: Cannot allocate resource for EISA slot 5
[    4.096246] platform eisa.0: Cannot allocate resource for EISA slot 6
[    4.096247] platform eisa.0: Cannot allocate resource for EISA slot 7
[    4.096248] platform eisa.0: Cannot allocate resource for EISA slot 8
[    4.256734] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    4.256931] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    4.256989] acpi PNP0C14:04: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
[    4.628731] ata3.00: ATA Identify Device Log not supported
[    4.630928] ata3.00: ATA Identify Device Log not supported
[    7.492449] blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[   30.560280] r8188eu: module is from the staging directory, the quality is unknown, you have been warned.
[   32.159334] nvidia: loading out-of-tree module taints kernel.
[   32.159341] nvidia: module license 'NVIDIA' taints kernel.
[   32.159342] Disabling lock debugging due to kernel taint

[   32.289446] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.129.06  Thu May 12 22:52:02 UTC 2022
[   33.379904] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
[   56.451486] kauditd_printk_skb: 12 callbacks suppressed
bienveillant@bienveillant-pc:~$ 

bienveillant@bienveillant-pc:~$ ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001287sv00001462sd00008A9Fbc03sc00i00
vendor   : NVIDIA Corporation
model    : GK208B [GeForce GT 730]
driver   : nvidia-driver-470 - distro non-free recommended
driver   : nvidia-driver-390 - distro non-free
driver   : nvidia-driver-450-server - distro non-free
driver   : nvidia-340 - distro non-free
driver   : nvidia-driver-418-server - distro non-free
driver   : nvidia-driver-470-server - distro non-free
driver   : xserver-xorg-video-nouveau - distro free builtin

[arghlub]

Salut,

donne le retour de la commande :

Code : Tout sélectionner

systemd-analyze blame

[Frederix]

Merci de t'interesser au problème:

Code : Tout sélectionner

bienveillant@bienveillant-pc:~$ systemd-analyze blame
16.017s systemd-journal-flush.service                        
 9.959s networkd-dispatcher.service                          
 9.056s dev-sdb2.device                                      
 7.877s plymouth-start.service                               
 7.512s accounts-daemon.service                              
 6.856s udisks2.service                                      
 4.986s ubuntu-system-adjustments.service                    
 4.492s polkit.service                                       
 4.217s avahi-daemon.service                                 
 4.087s NetworkManager.service                               
 3.794s systemd-resolved.service                             
 3.525s ssh.service                                          
 3.244s ufw.service                                          
 3.219s systemd-udevd.service                                
 3.035s ModemManager.service                                 
 2.945s lightdm.service                                      
 2.941s alsa-restore.service                                 
 2.903s plymouth-quit-wait.service                           
 2.780s apparmor.service                                     
 2.756s secureboot-db.service                                
 2.709s gpu-manager.service                                  
 2.558s thermald.service                                     
 2.552s wpa_supplicant.service                               
 2.551s systemd-logind.service                               
 2.545s hddtemp.service                                      
 2.510s plymouth-read-write.service                          
 2.332s grub-common.service                                  
 2.293s lm-sensors.service                                   
 2.263s rsyslog.service                                      
 2.159s systemd-fsck@dev-disk-by\x2duuid-8FBA\x2d3399.service
 1.832s systemd-modules-load.service                         
 1.585s networking.service                                   
 1.566s e2scrub_reap.service                                 
 1.553s systemd-tmpfiles-clean.service                       
 1.152s nvidia-persistenced.service                          
 1.132s pppd-dns.service                                     
  946ms systemd-sysctl.service                               
  901ms systemd-tmpfiles-setup-dev.service                   
  856ms systemd-tmpfiles-setup.service                       
  790ms colord.service                                       
  733ms systemd-sysusers.service                             
  728ms dns-clean.service                                    
  664ms grub-initrd-fallback.service                         
  634ms keyboard-setup.service                               
  551ms systemd-random-seed.service                          
  455ms modprobe@drm.service                                 
  402ms ifupdown-pre.service                                 
  348ms dev-hugepages.mount                                  
  345ms dev-mqueue.mount                                     
  343ms sys-kernel-debug.mount                               
  342ms systemd-journald.service                             
  341ms sys-kernel-tracing.mount                             
  335ms blk-availability.service                             
  334ms kmod-static-nodes.service                            
  333ms lvm2-monitor.service                                 
  310ms systemd-udev-trigger.service                         
  269ms console-setup.service                                
  255ms swapfile.swap                                        
  234ms kerneloops.service                                   
  211ms upower.service                                       
  182ms systemd-timesyncd.service                            
  171ms systemd-update-utmp.service                          
  166ms systemd-remount-fs.service                           
  143ms boot-efi.mount                                       
  121ms openvpn.service                                      
  119ms setvtrgb.service                                     
   76ms user@1000.service                                    
   72ms systemd-user-sessions.service                        
   24ms motd-news.service                                    
   14ms rtkit-daemon.service                                 
    6ms finalrd.service                                      
    4ms user-runtime-dir@1000.service                        
    4ms systemd-update-utmp-runlevel.service                 
    2ms sys-fs-fuse-connections.mount                        
    1ms sys-kernel-config.mount                              
lines 53-75/75 (END)

[arghlub]

ton système me semble bien surchargé notamment avec :

• les logs «systemd-journal-flush.service»
• networkd-dispatcher.service
• dev-sdb2.device (où linux cherche un disque dur qui est compliqué à trouver)

j'en passe et des meilleures

[Frederix]

Pour le systemd-journal-flush.service le principal objet de lenteur au boot, plutôt que de limiter la taille du journal (il grossit et se fragmente sur le disque dur avec le temps) , j’ai opté pour :

Code : Tout sélectionner

$ find /var/log/journal -name "*.journal" | xargs sudo rm
$ sudo systemctl restart systemd-journald

Ce qui donne le blame suivant (je gagne déjà 10 sec.):

Code : Tout sélectionner

bienveillant@bienveillant-pc:~$ systemd-analyze blame
11.842s accounts-daemon.service                              
11.275s networkd-dispatcher.service                          
 9.907s dev-sdb2.device                                      
 7.926s udisks2.service                                      
 6.224s systemd-journal-flush.service                        
 6.090s plymouth-start.service   
etc.…

Je vais traiter le reste à l'avenant... merci pour cette commande... (blame).
A+

[Jennatux]

Salut Frederix

Donne le retour de

Code : Tout sélectionner

sudo journalctl --disk-usage

[Frederix]

Normalement il y a eu une remise à zéro par les commandes sus-nommée, donc la taille n'est pas très importante :

Code : Tout sélectionner

bienveillant@bienveillant-pc:~$ sudo journalctl --disk-usage
Archived and active journals take up 392.0M in the file system.
bienveillant@bienveillant-pc:~$ 

A titre de comparaison, sur mon portable le fichier fait 4Go!

[Frederix]

J'ai fais un fsck du disque incriminé. En dehors des erreurs SGX et ACPI sans importance, reste une erreur d'entrée sortie d'un device non identifié (sr0). En bref c'est encore un peu long au boot mais je vais m'en satisfaire pour le moment.

Code : Tout sélectionner

bienveillant@bienveillant-pc:~$ sudo dmesg -l crit
bienveillant@bienveillant-pc:~$ sudo dmesg -l err,crit
[    0.118801] x86/cpu: SGX disabled by BIOS.
[    0.203196] ACPI BIOS Error (bug): Failure creating named object [\ADBG], AE_ALREADY_EXISTS (20210730/dswload2-326)
[    0.203205] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20210730/psobject-220)
[    1.891979] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.PGON.PBGE], AE_NOT_FOUND (20210730/psargs-330)
[    1.891994] ACPI Error: Aborting method \_SB.PC00.PGON due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    1.891999] ACPI Error: Aborting method \_SB.PC00.PEG1.PG01._ON due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
[    7.703315] blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
bienveillant@bienveillant-pc:~$