Olá, pessoal.
Estou reabrindo essa discussão em um novo tópico porque minha situação de hardware mudou completamente, mas o problema persiste. Anteriormente, eu rodava o sistema em dual-boot (Windows no SSD e Linux Mint no HD). Detalhei esse cenário anterior neste post.
Agora, fiz uma instalação limpa e única do Linux Mint diretamente no SSD, deixando o HD configurado apenas para armazenar meus arquivos pessoais. Mesmo com o sistema rodando direto do SSD do zero, o comportamento estranho continua: ao tentar suspender, a tela apaga, mas os leds do teclado continuam acesos, as ventoinhas continuam girando e o computador simplesmente trava, me forçando a desligar segurando o botão de energia.
Um agravante importante: Ontem aconteceu um evento novo. O computador congelou exatamente da mesma forma ao tentar desligar o sistema pelo menu (e não apenas ao suspender). Isso me faz pensar que o problema pode não ser exclusivo do modo de suspensão, mas sim algo relacionado ao gerenciamento de energia (ACPI), drivers de vídeo ou ao encerramento de algum processo do sistema.
Aqui estão as informações atualizadas do meu hardware e sistema:
─➤ inxi -F --filter
System:
Kernel: 6.17.0-35-generic arch: x86_64 bits: 64
Desktop: Cinnamon v: 6.6.7 Distro: Linux Mint 22.3 Zena
Machine:
Type: Laptop System: Acer product: Nitro AN515-51 v: V1.22
serial: <superuser required>
Mobo: KBL model: Freed_KLS v: V1.22 serial: <superuser required>
UEFI: Insyde v: 1.22 date: 03/15/2019
Battery:
ID-1: BAT1 charge: 18.2 Wh (100.0%) condition: 18.2/48.9 Wh (37.3%)
volts: 15.5 min: 15.2
CPU:
Info: quad core model: Intel Core i7-7700HQ bits: 64 type: MT MCP cache:
L2: 1024 KiB
Speed (MHz): avg: 1144 min/max: 800/3800 cores: 1: 1001 2: 1000 3: 1001
4: 1254 5: 1181 6: 1361 7: 1172 8: 1189
Graphics:
Device-1: Intel HD Graphics 630 driver: i915 v: kernel
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: N/A
Device-3: Chicony Integrated HD WebCam driver: uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
resolution: 1920x1080~60Hz
API: EGL v: 1.5 drivers: iris,swrast platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa
v: 25.2.8-0ubuntu0.24.04.2 renderer: Mesa Intel HD Graphics 630 (KBL GT2)
API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib
Audio:
Device-1: Intel CM238 HD Audio driver: snd_hda_intel
Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel
API: ALSA v: k6.17.0-35-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: active
Network:
Device-1: Intel Wireless 7265 driver: iwlwifi
IF: wlp2s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp3s0f1 state: down mac: <filter>
Bluetooth:
Device-1: Intel Bluetooth wireless interface driver: btusb type: USB
Report: hciconfig ID: hci0 rfk-id: 2 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: <filter>
Drives:
Local Storage: total: 1.13 TiB used: 63.27 GiB (5.5%)
ID-1: /dev/sda vendor: Seagate model: WDC WDS240G2G0B-00EPW0
size: 223.57 GiB
ID-2: /dev/sdb vendor: Western Digital model: WD10SPZX-21Z10T0
size: 931.51 GiB
Partition:
ID-1: / size: 218.51 GiB used: 45.93 GiB (21.0%) fs: ext4 dev: /dev/sda2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 56.0 C pch: 40.5 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.5 GiB used: 6.77 GiB (43.7%)
Processes: 272 Uptime: 2h 21m Shell: Bash inxi: 3.3.34
Alguém que já passou por isso nessa nova base do Mint 22.1 saberia me indicar por onde começar a diagnosticar? Se é caso de mexer em parâmetros do Grub, testar outro Kernel ou alguma configuração específica de energia?
Agradeço desde já pela ajuda!
Você poderia usar o journalctl pra começar a ver os logs do sistema quando vc faz o procedimento no qual o computador trava
Obrigado pela sugestão! Rodei os comandos para puxar os logs da inicialização anterior (da última vez que o sistema travou antes de eu forçar o botão de energia).
Aqui estão os erros e alertas graves encontrados no final do último boot:
─➤ journalctl -b -1 -p 3..0
jun 24 15:00:25 mjfn-Nitro-AN515-51 kernel: x86/cpu: SGX disabled or unsupported by BIOS.
jun 24 15:00:25 mjfn-Nitro-AN515-51 kernel: integrity: Problem loading X.509 certificate -65
jun 24 15:00:25 mjfn-Nitro-AN515-51 kernel: integrity: Problem loading X.509 certificate -65
jun 24 15:00:28 mjfn-Nitro-AN515-51 bluetoothd[913]: profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
jun 24 15:00:28 mjfn-Nitro-AN515-51 bluetoothd[913]: sap-server: Operation not permitted (1)
jun 24 15:00:28 mjfn-Nitro-AN515-51 bluetoothd[913]: Failed to set mode: Failed (0x03)
jun 24 15:00:39 mjfn-Nitro-AN515-51 systemd[1]: Failed to start casper-md5check.service - casper-md5check Verify Live ISO checksums.
jun 24 15:00:40 mjfn-Nitro-AN515-51 kernel: snd_hda_intel 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
jun 24 15:00:43 mjfn-Nitro-AN515-51 lightdm[1403]: gkr-pam: couldn't unlock the login keyring.
jun 24 15:00:45 mjfn-Nitro-AN515-51 kernel: snd_hda_intel 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
jun 24 15:00:53 mjfn-Nitro-AN515-51 lightdm[1520]: gkr-pam: unable to locate daemon control file
jun 24 15:00:54 mjfn-Nitro-AN515-51 kernel: snd_hda_intel 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
jun 24 14:32:58 mjfn-Nitro-AN515-51 cinnamon-screensaver-pam-helper[15001]: pam_ecryptfs: seteuid error
jun 24 16:40:18 mjfn-Nitro-AN515-51 cinnamon-screensaver-pam-helper[24351]: pam_ecryptfs: seteuid error
jun 24 18:49:59 mjfn-Nitro-AN515-51 cinnamon-screensaver-pam-helper[35195]: pam_unix(cinnamon-screensaver:auth): conversation failed
jun 24 18:49:59 mjfn-Nitro-AN515-51 cinnamon-screensaver-pam-helper[35195]: pam_unix(cinnamon-screensaver:auth): auth could not identify password for [mjfneto]
jun 24 18:51:38 mjfn-Nitro-AN515-51 cinnamon-screensaver-pam-helper[35271]: pam_ecryptfs: seteuid error
jun 24 21:29:52 mjfn-Nitro-AN515-51 cinnamon-screensaver-pam-helper[47759]: pam_ecryptfs: seteuid error
jun 24 21:30:57 mjfn-Nitro-AN515-51 kernel: snd_hda_intel 0000:01:00.1: Unable to change power state from D3cold to D0, device inaccessible
E aqui estão as últimas 50 linhas registradas antes do sistema congelar de vez:
─➤ journalctl -b -1 -n 50
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: proc-sys-fs-binfmt_misc.automount: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Unset automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-sysctl.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-sysctl.service - Apply Kernel Variables.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-coredump.socket: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Closed systemd-coredump.socket - Process Core Dump Socket.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-modules-load.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-modules-load.service - Load Kernel Modules.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: proc-sys-fs-binfmt_misc.mount: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-update-utmp.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-update-utmp.service - Record System Boot/Shutdown in UTMP.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-backlight@backlight:intel_backlight.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-backlight@backlight:intel_backlight.service - Load/Save Screen Backlight Brightness of backlight:intel_backlight.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Removed slice system-systemd\x2dbacklight.slice - Slice /system/systemd-backlight.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-tmpfiles-setup.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-tmpfiles-setup.service - Create Volatile Files and Directories.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped target local-fs.target - Local File Systems.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Unmounting boot-efi.mount - /boot/efi...
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: boot-efi.mount: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Unmounted boot-efi.mount - /boot/efi.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Reached target umount.target - Unmount All Filesystems.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-fsck@dev-disk-by\x2duuid-51C7\x2d8AFF.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-fsck@dev-disk-by\x2duuid-51C7\x2d8AFF.service - File System Check on /dev/disk/by-uuid/51C7-8AFF.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Removed slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped target local-fs-pre.target - Preparation for Local File Systems.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopping lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-remount-fs.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-tmpfiles-setup-dev-early.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Received SIGRTMIN+20 from PID 48789 (plymouthd).
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: lvm2-monitor.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Reached target shutdown.target - System Shutdown.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Started plymouth-poweroff.service - Show Plymouth Power Off Screen.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Starting casper.service - Shuts down the "live" preinstalled system cleanly...
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Starting plymouth-switch-root-initramfs.service - Tell Plymouth To Jump To initramfs...
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: casper.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Finished casper.service - Shuts down the "live" preinstalled system cleanly.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Reached target final.target - Late Shutdown Services.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: systemd-poweroff.service: Deactivated successfully.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Finished systemd-poweroff.service - System Power Off.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Reached target poweroff.target - System Power Off.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd[1]: Shutting down.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd-shutdown[1]: Syncing filesystems and block devices.
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd-journald[327]: Received SIGTERM from PID 1 (systemd-shutdow).
jun 24 21:31:05 mjfn-Nitro-AN515-51 systemd-journald[327]: Journal stopped
Passando para dar uma excelente notícia: o problema parece ter sido resolvido de maneira satisfatória! Agora, eu só gostaria da avaliação dos membros mais experientes sobre os dois procedimentos abaixo.
Procedimento 1
Investigando os logs do kernel (dmesg), percebi que o driver da Nvidia estava carregado, mas gerando o seguinte erro ao tentar gerenciar a tela:
[drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] Failed to grab modeset ownership
Isso indicava uma briga pelo controle do modesetting de vídeo na hora de alternar as placas para suspender ou desligar.
A “Solução”:
Forcei o Kernel a carregar o modeset da Nvidia logo na inicialização do sistema através dos parâmetros do Grub. O passo a passo foi:
-
Editei o arquivo de configuração do Grub:
sudo nano /etc/default/grub
-
Adicionei o parâmetro nvidia-drm.modeset=1 na linha principal, deixando-a assim:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1"
-
Atualizei o Grub e reiniciei:
sudo update-grub
Agora, ao rodar o inxi -F --filter, a placa dedicada finalmente sai do “limbo” e mostra o driver correto ativo:
Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia v: 535.309.01
Tanto a suspensão quanto o desligamento pelo menu voltaram a funcionar instantaneamente e sem nenhum engasgo.
Procedimento 2
Por fim, como o Secure Boot ativado estava bloqueando o carregamento correto do driver da Nvidia após a correção do modeset, optei por deixá-lo desativado na BIOS, o que resolveu o problema em definitivo e estabilizou o sistema.
Desabilitar o Secure Boot é um procedimento seguro?
Que bom que resolveu! Marque como solucionado.
Ele é uma camada de segurança a mais, mas deixar desativado não vai deixar você em risco.