Início / user-149203

Luis A. Florit's questions

Martin Hope
Luis A. Florit
Asked: 2024-08-09 02:48:51 +0800 CST
  • 5

Tenho um arquivo criptografado LUKS com cerca de 160 GB de dados que uso muito. Por segurança, criei o arquivo com 400 GB. Isso é, obviamente, muito espaço desperdiçado. Então mudei para um arquivo esparso, basicamente seguindo o conselho aqui , simplesmente criando o arquivo com a opção de busca:

dd if=/dev/zero of= <arquivo> bs=1G contagem=0 search=400

Mas aí pensei: o que acontece se o arquivo começar a ficar fragmentado? Normalmente isso não é um problema, pois não tenho arquivos muito grandes e, quando tenho, são arquivos de mídia que geralmente não mudam. Mas uma coisa criptografada que uso com tanta frequência provavelmente será fragmentada em breve...

Portanto, minha pergunta é: existe alguma desvantagem real em usar um arquivo esparso em vez de um arquivo de tamanho fixo na minha situação? A fragmentação é realmente um problema? Você tem mais algum conselho?

performance
Martin Hope
Luis A. Florit
Asked: 2024-07-25 22:54:22 +0800 CST
  • 5

Frequentemente, ao alternar meu usuário por root com su -, recebo bashmensagens de erro estranhas no rxvtconsole, ou mesmo em um TTY. Elas acontecem mesmo após uma atualização completa do sistema do zero, então provavelmente é algo no rootHOME.

Por exemplo, estes:

sh: error importing function definition for `_file'
sh: _file: line 3: syntax error near unexpected token `('
sh: _file: line 3: ` --help | --version | --separator | -!(-*)[vF])'

Quando faço logout, recebo vários erros como:

/bin/bash: _sudo: line 19: syntax error near unexpected token `('
/bin/bash: _sudo: line 19: ` --user | --other-user | -!(-*)[uU])'
/bin/bash: error importing function definition for `_sudo'

Mesmo que eu faça shno console eu recebo

/bin/bash: _file: line 3: syntax error near unexpected token `('
/bin/bash: _file: line 3: ` --help | --version | --separator | -!(-*)[vF])'
/bin/bash: error importing function definition for `_file'

Então eu saio e entro novamente, e o comportamento normal é restaurado. Até que começa a se comportar estranhamente...

Achei que fosse um problema com '~/.bashrc' ou algo parecido, mas esses arquivos são compartilhados com meu usuário normal, que nunca mostra erros no console.

Obviamente há um bashscript com erros, mas não sei nem por onde começar a procurar. O que é _sudo?? Os comandos grep _sudo $(find . -type f)e find . -name _sudonão mostram nada...

EDITAR

Este é o conteúdo do meu arquivo /usr/share/bash-completion/completions/sudo:

# bash completion for sudo(8)                              -*- shell-script -*-

_sudo()
{
    local cur prev words cword split
    _init_completion -s || return

    local i mode=normal
    [[ $1 == *sudoedit ]] && mode=edit

    [[ $mode == normal ]] &&
        for ((i = 1; i <= cword; i++)); do
            if [[ ${words[i]} != -* ]]; then
                local PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin
                local root_command=${words[i]}
                _command_offset $i
                return
            fi
            if [[ ${words[i]} == -@(!(-*)e*|-edit) ]]; then
                mode=edit
                break
            fi
            [[ ${words[i]} == \
            -@(user|other-user|group|close-from|prompt|!(-*)[uUgCp]) ]] &&
                ((i++))
        done

    case "$prev" in
        --user | --other-user | -!(-*)[uU])
            COMPREPLY=($(compgen -u -- "$cur"))
            return
            ;;
        --group | -!(-*)g)
            COMPREPLY=($(compgen -g -- "$cur"))
            return
            ;;
        --close-from | --prompt | -!(-*)[Cp])
            return
            ;;
    esac

    $split && return

    if [[ $cur == -* ]]; then
        local opts=$(_parse_help "$1")
        COMPREPLY=($(compgen -W '${opts:-$(_parse_usage "$1")}' -- "$cur"))
        [[ ${COMPREPLY-} == *= ]] && compopt -o nospace
        return
    fi
    if [[ $mode == edit ]]; then
        _filedir
    fi
} &&
    complete -F _sudo sudo sudoedit

# ex: filetype=sh
linux
Martin Hope
Luis A. Florit
Asked: 2024-07-23 19:48:14 +0800 CST
  • 10

Podemos usar o comando stty -echocom um script shell bash para evitar que caracteres sejam ecoados no console, por exemplo, para entrada de senha.

Existe uma maneira de imprimir um *para cada caractere de entrada e excluí-los ao pressionar backspace?

bash
Martin Hope
Luis A. Florit
Asked: 2024-05-20 12:08:38 +0800 CST
  • 6

Atualizei do Fedora 38 para o Fedora 40 de forma mais ou menos tranquila. No entanto, quando novos kernels são instalados, a configuração do grub não é atualizada.

O comando grep vmlinuz /boot/grub2/grub.cfgmostra

 linux /boot/vmlinuz-6.8.8-300.fc40.x86_64 root=UUID=0e08d465-d601-478f-be17-a2663626588c ro
 linux /boot/vmlinuz-6.8.8-100.fc38.x86_64 root=UUID=0e08d465-d601-478f-be17-a2663626588c ro
 linux /boot/vmlinuz-6.3.12-200.fc38.x86_64 root=UUID=0e08d465-d601-478f-be17-a2663626588c ro

mas não tenho o 6.3.12 instalado e ls /boot/loader/entriesme dá

 vmlinuz-6.8.8-100.fc38.x86_64
 vmlinuz-6.8.8-300.fc40.x86_64
 vmlinuz-6.8.9-300.fc40.x86_64

concordando rpm -q kerneltambém com:

 kernel-6.8.8-100.fc38.x86_64
 kernel-6.8.8-300.fc40.x86_64
 kernel-6.8.9-300.fc40.x86_64

Sim, grub2-mkconfig -o /boot/grub2/grub.cfgrestaura a configuração, com o comando grep vmlinuz /boot/grub2/grub.cfgagora dando

 linux /boot/vmlinuz-6.8.9-300.fc40.x86_64 root=UUID=0e08d465-d601-478f-be17-a2663626588c ro
 linux /boot/vmlinuz-6.8.8-300.fc40.x86_64 root=UUID=0e08d465-d601-478f-be17-a2663626588c ro
 linux /boot/vmlinuz-6.8.8-100.fc38.x86_64 root=UUID=0e08d465-d601-478f-be17-a2663626588c ro

mas grub2-mkconfignão deve ser executado toda vez que um kernel for instalado.

O que está acontecendo?

fedora
Martin Hope
Luis A. Florit
Asked: 2023-05-23 04:42:17 +0800 CST
  • 6

Quero ter comigo um Fedora Live UEFI boot USB para emergências, mas não quero carregar duas unidades USB. Então, eu quero uma unidade USB com duas partições, uma para inicialização do Fedora Live e outra para minhas coisas. Sempre tive comigo um pen drive assim com o Fedora Live 26, e agora quero um para o Fedora 38 (mais ou menos).

Os problemas:

mediawriter, a maneira padrão de gravar Live USBs no Fedora, grava apenas em um dispositivo USB, não em uma partição.

livecd-iso-to-diskfuncionaria, mas tem um bug muito antigo e não funciona .

unetbootinfunciona apenas para inicialização herdada, não para UEFI. E os novos computadores Dell inicializam apenas UEFI. Há um pedido aberto para isso desde 2015...

dd: Eu tentei várias vezes com, ddmas falhei miseravelmente.

Alguma ideia? Deve haver uma maneira fácil de fazer isso apenas com dd!!!

############ EDITAR #############

Seguindo alguns dos links postados por @oldfred, consegui inicializar o UEFI a partir de uma partição de pen drive com o seguinte recibo:

Fedora USB LIVE para uma partição em um pen drive (digamos, /dev/sda1):

  1. Usando gparted ou similar, certifique-se que a primeira partição do pen drive é gpt, e tem label <YOURLABEL>(isso pode ser alterado de forma não destrutiva);

  2. Adicione o sinalizador de inicialização à partição com:

    parted /dev/sda set 1 boot on

  3. Monte /dev/sda1em a <MountPoint>e extraia todo o conteúdo ISO com, digamos, 7z:

    7z x <PATH/TO/ISOFILE.iso> -o<MountPoint>

  4. Mude <MountPoint>/efi/boot/grub.cfge <MountPoint>/boot/grub2/grub.cfgpara refletir o dispositivo correto:

    menuentry 'Fedora-KDE-Live 38 EFI' --class fedora --class gnu-linux --class gnu --class os {
   linuxefi /images/pxeboot/vmlinuz root=live:LABEL=<YOURLABEL>  rd.live.image quiet rhgb
   initrdefi /images/pxeboot/initrd.img
}

Observação. A entrada correspondente no menu grub do computador pode ser adicionada adicionando ao arquivo /etc/grub.d/40_custom:

menuentry 'Fedora-KDE-Live 38 EFI' --class fedora --class gnu-linux --class gnu --class os {
    search --no-floppy --label <YOURLABEL> --set=root
    linuxefi /images/pxeboot/vmlinuz root=live:LABEL=<YOURLABEL>  rd.live.image quiet rhgb
    initrdefi /images/pxeboot/initrd.img
}

Observação 2. Infelizmente, não consegui inicializar a partir do ISO diretamente quando o ISO está no pen drive. De acordo com este post, há um bug impedindo isso desde o Fedora 33.

fedora
Martin Hope
Luis A. Florit
Asked: 2023-05-03 05:11:07 +0800 CST
  • 5

Eu tenho um HDD que deseja montar usando um cabo de alimentação USB +. Ao conectar, vejo a mensagem:

usb 1-2: New USB device found, idVendor=1f75, idProduct=0621, bcdDevice= 0.36
usb 1-2: New USB device strings: Mfr=4, Product=5, SerialNumber=6
usb 1-2: SerialNumber: 20211228
usb-storage 1-2:1.0: USB Mass Storage device detected
scsi host6: usb-storage 1-2:1.0

No entanto, lsblk, dmesge journalctl -fnão mostra nenhuma correspondência de dispositivo /dev/sd*atribuída a ele.

Como posso montar então? Fedora 38 totalmente atualizado.

linux
Martin Hope
Luis A. Florit
Asked: 2022-06-22 16:23:07 +0800 CST
  • 1

Eu sempre usei inicialização de texto + console sem interface gráfica. Isso inclui o login, que também é apenas texto, pois faço algumas coisas de sincronização no momento do login, especificamente tty1onde tenho um script de login automático, que executa o seguinte comando através do arquivo /etc/systemd/system/[email protected]/override.conf:

/usr/sbin/agetty --autologin <myusername> --noclear %I 38400 linux

Acabei de atualizar para o Fedora 36 (de 35), e a inicialização vai bem até a última etapa. Em vez de me mostrar um prompt de login de texto, ele mostra uma tela preta com um sublinhado no canto superior esquerdo.

Por quê?

O comando systemctlvai bem, exceto precisamente por uma linha vermelha:

● [email protected]    loaded failed failed    Getty on tty1

Nos logs, vejo um erro:

agetty[4565]: /dev/tty1: "cannot get controlling tty: Operation not permitted"
agetty[4565]: setting terminal attributes failed: Input/output error

Eu posso ver esse erro no console toda vez que tento como root

 service [email protected] start

Não sei o que deu errado, mas parece que o comando agetty mudou?

EDITAR :

Se eu colocar a linha:

ExecStart=-/usr/sbin/agetty --autologin <myusername> --noclear tty1 38400 linux

no arquivo /etc/systemd/system/[email protected]/override.confo autologin funciona. No entanto, se eu mudar para

ExecStart=-/home/<myusername>/bin/myautologinscript.sh

com a mesma linha, não!!

linux fedora
Martin Hope
Luis A. Florit
Asked: 2021-09-10 08:58:37 +0800 CST
  • 1

Desde a última atualização para o Android Studio (Android Studio Arctic Fox | 2020.3.1 Patch 2 Build #AI-203.7717.56.2031.7678000), estou enfrentando frequentes congelamentos do sistema global no Fedora 33. Nada respondendo, mesmo o servidor SSH, então o única solução é uma reinicialização forçada. Sempre trava durante a digitação.

Em ai alguém aqui com o mesmo problema?

EDITAR

A pedido, estou adicionando a saída de dmesg --level=alert,crit,err,warn. Espero que a informação necessária ainda esteja lá:

[    0.165884] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.165948]  #5 #6 #7
[    0.172490] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[    0.173015] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.287753] wait_for_initramfs() called before rootfs_initcalls
[    4.213705] systemd-sysv-generator[573]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    4.214895] systemd-sysv-generator[573]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    4.216144] systemd-sysv-generator[573]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    4.899093] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210331/utaddress-204)
[    4.899732] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    4.900844] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204)
[    4.901495] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    4.901500] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL)
[    4.902664]  (20210331/utaddress-204)
[    4.902704] ACPI Warning: 
[    4.903893] SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    4.903896] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    5.178789] at24 13-0050: supply vcc not found, using dummy regulator
[    5.179916] at24 13-0051: supply vcc not found, using dummy regulator
[    5.181186] at24 13-0052: supply vcc not found, using dummy regulator
[    5.182506] at24 13-0053: supply vcc not found, using dummy regulator
[    5.459435] kauditd_printk_skb: 96 callbacks suppressed
[    5.740341] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[    7.154729] Bluetooth: hci0: command 0x1005 tx timeout
[    9.202670] Bluetooth: hci0: command 0x0c23 tx timeout
[   11.250636] Bluetooth: hci0: command 0x0c14 tx timeout
[   13.298596] Bluetooth: hci0: command 0x0c25 tx timeout
[   15.346559] Bluetooth: hci0: command 0x0c38 tx timeout
[   17.394520] Bluetooth: hci0: command tx timeout
[ 1832.091017] IRQ 29: no longer affine to CPU4
[ 1832.093063] IRQ 28: no longer affine to CPU5
[ 1832.093066] IRQ 30: no longer affine to CPU5
[ 1832.094878] IRQ 23: no longer affine to CPU6
[ 1832.094882] IRQ 25: no longer affine to CPU6
[ 1832.094885] IRQ 32: no longer affine to CPU6
[ 1832.096684] IRQ 18: no longer affine to CPU7
[ 1832.096687] IRQ 19: no longer affine to CPU7
[ 1832.096690] IRQ 27: no longer affine to CPU7
[ 1834.430082] Bluetooth: hci0: command 0x0c16 tx timeout
[ 1836.478094] Bluetooth: hci0: command 0x2002 tx timeout
[ 1837.499045] ata3: link is slow to respond, please be patient (ready=0)
[ 1837.500053] ata1: link is slow to respond, please be patient (ready=0)
[ 1838.525986] Bluetooth: hci0: command 0x2003 tx timeout
[ 1840.574009] Bluetooth: hci0: command 0x201c tx timeout
[ 1842.495776] Bluetooth: hci0: command tx timeout
[18453.352264] IRQ 29: no longer affine to CPU4
[18453.354087] IRQ 23: no longer affine to CPU5
[18453.354091] IRQ 25: no longer affine to CPU5
[18453.355958] IRQ 16: no longer affine to CPU6
[18453.355963] IRQ 26: no longer affine to CPU6
[18453.355967] IRQ 32: no longer affine to CPU6
[18453.357790] IRQ 19: no longer affine to CPU7
[18453.357796] IRQ 28: no longer affine to CPU7
[18453.357799] IRQ 30: no longer affine to CPU7
[18455.781051] done.
[18457.872004] Bluetooth: hci0: command 0x1001 tx timeout
[18458.761887] ata1: link is slow to respond, please be patient (ready=0)
[18458.762881] ata3: link is slow to respond, please be patient (ready=0)
[18459.919872] Bluetooth: hci0: command 0x1009 tx timeout

EDIÇÃO 2

Acabou de travar novamente. Saída de dmesg --level=alert,crit,err,warn:

[    0.165915] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.165973]  #5 #6 #7
[    0.172521] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[    0.173044] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.287783] wait_for_initramfs() called before rootfs_initcalls
[    7.086711] usb 3-5: device descriptor read/64, error -110
[    8.324313] kauditd_printk_skb: 5 callbacks suppressed
[    8.940835] systemd-sysv-generator[574]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.942438] systemd-sysv-generator[574]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    8.944077] systemd-sysv-generator[574]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    9.619007] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210331/utaddress-204)
[    9.619640] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    9.621931] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204)
[    9.622116] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    9.623233] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204)
[    9.624779] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    9.625544] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    9.786915] at24 13-0050: supply vcc not found, using dummy regulator
[    9.789823] at24 13-0051: supply vcc not found, using dummy regulator
[    9.791691] at24 13-0052: supply vcc not found, using dummy regulator
[    9.793324] at24 13-0053: supply vcc not found, using dummy regulator
[   10.174554] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[   13.354089] kauditd_printk_skb: 87 callbacks suppressed

EDIÇÃO 3

Eu experimentei cerca de 10 congela em alguns dias. Receio que o Studio vá danificar meu computador. O congelamento continua apesar de eu ter atualizado todo o sistema para o último Fedora 34.

Última saída de dmesg --level=alert,crit,err,warn:

[    0.166421] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.166484]  #5 #6 #7
[    0.173036] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[    0.173550] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.287346] wait_for_initramfs() called before rootfs_initcalls
[    3.397929] systemd-sysv-generator[567]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.399641] systemd-sysv-generator[567]: SysV service '/etc/rc.d/init.d/network' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.400982] systemd-sysv-generator[567]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[    3.713080] systemd-journald[593]: File /var/log/journal/9ff77e59cfd04f078e4b747742c5981e/system.journal corrupted or uncleanly shut down, renaming and replacing.
[    4.036564] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210331/utaddress-204)
[    4.037179] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    4.038257] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204)
[    4.038808] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    4.039932] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210331/utaddress-204)
[    4.041794] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210331/utaddress-204)
[    4.042527] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    4.468471] at24 13-0050: supply vcc not found, using dummy regulator
[    4.470405] at24 13-0051: supply vcc not found, using dummy regulator
[    4.474870] at24 13-0052: supply vcc not found, using dummy regulator
[    4.476069] at24 13-0053: supply vcc not found, using dummy regulator
[    4.637421] ext4 filesystem being mounted at /boot supports timestamps until 2038 (0x7fffffff)
[    5.321533] kauditd_printk_skb: 100 callbacks suppressed

EDIT 4 Outro congelamento. saída journalctl da falha do kernel:

$ journalctl -S '2021-09-16 13:30:00'

13:43:57 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#1] SMP PTI
13:43:57 Orion kernel: CPU: 4 PID: 2724 Comm: Xorg Not tainted 5.13.15-200.fc34.x86_64 #1
13:43:57 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014
13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220
13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48>
13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206
13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1
13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0
13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018
13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0
13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce
13:43:57 Orion kernel: FS:  00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000
13:43:57 Orion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0
13:43:57 Orion kernel: Call Trace:
13:43:57 Orion kernel:  nvkm_mem_new_type+0xae/0x2a0 [nouveau]
13:43:57 Orion kernel:  nvkm_umem_new+0x130/0x220 [nouveau]
13:43:57 Orion kernel:  nvkm_ioctl_new+0x129/0x1e0 [nouveau]
13:43:57 Orion kernel:  ? nvkm_umem_search+0xe0/0xe0 [nouveau]
13:43:57 Orion kernel:  nvkm_ioctl+0xdc/0x180 [nouveau]
13:43:57 Orion kernel:  nvif_object_ctor+0x122/0x1c0 [nouveau]
13:43:57 Orion kernel:  nvif_mem_ctor_type+0xc2/0x180 [nouveau]
13:43:57 Orion kernel:  ? nvkm_vmm_ptes_get_map+0x2c/0x90 [nouveau]
13:43:57 Orion kernel:  ? nvkm_vmm_map+0x18d/0x350 [nouveau]
13:43:57 Orion kernel:  nouveau_mem_host+0xf3/0x190 [nouveau]
13:43:57 Orion kernel:  nouveau_sgdma_bind+0x30/0x80 [nouveau]
13:43:57 Orion kernel:  nouveau_bo_move+0x3c1/0x820 [nouveau]
13:43:57 Orion kernel:  ? ttm_pool_type_take+0x7d/0x90 [ttm]
13:43:57 Orion kernel:  ? ttm_pool_alloc+0xe6/0x590 [ttm]
13:43:57 Orion kernel:  ttm_bo_handle_move_mem+0x90/0x170 [ttm]
13:43:57 Orion kernel:  ttm_bo_validate+0x11c/0x150 [ttm]
13:43:57 Orion kernel:  ttm_bo_init_reserved+0x239/0x2c0 [ttm]
13:43:57 Orion kernel:  ttm_bo_init+0x4a/0xc0 [ttm]
13:43:57 Orion kernel:  ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau]
13:43:57 Orion kernel:  nouveau_bo_init+0x7c/0x90 [nouveau]
13:43:57 Orion kernel:  ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau]
13:43:57 Orion kernel:  ? nouveau_gem_new+0xf0/0xf0 [nouveau]
13:43:57 Orion kernel:  nouveau_gem_new+0x7f/0xf0 [nouveau]
13:43:57 Orion kernel:  nouveau_gem_ioctl_new+0x45/0xe0 [nouveau]
13:43:57 Orion kernel:  ? nouveau_gem_new+0xf0/0xf0 [nouveau]
13:43:57 Orion kernel:  drm_ioctl_kernel+0x86/0xd0 [drm]
13:43:57 Orion kernel:  drm_ioctl+0x220/0x3e0 [drm]
13:43:57 Orion kernel:  ? nouveau_gem_new+0xf0/0xf0 [nouveau]
13:43:57 Orion kernel:  ? __ia32_sys_timer_getoverrun+0x40/0x50
13:43:57 Orion kernel:  nouveau_drm_ioctl+0x55/0xa0 [nouveau]
13:43:57 Orion kernel:  __x64_sys_ioctl+0x82/0xb0
13:43:57 Orion kernel:  do_syscall_64+0x40/0x80
13:43:57 Orion kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
13:43:57 Orion kernel: RIP: 0033:0x7f32b84540ab
13:43:57 Orion kernel: Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73>
13:43:57 Orion kernel: RSP: 002b:00007ffdd87e5148 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
13:43:57 Orion kernel: RAX: ffffffffffffffda RBX: 00007ffdd87e51a0 RCX: 00007f32b84540ab
13:43:57 Orion kernel: RDX: 00007ffdd87e51a0 RSI: 00000000c0306480 RDI: 000000000000000f
13:43:57 Orion kernel: RBP: 00000000c0306480 R08: 0000556e9a4293d0 R09: 0000000000000016
13:43:57 Orion kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000556e994bc7e0
13:43:57 Orion kernel: R13: 000000000000000f R14: 00007ffdd87e51a0 R15: 0000000000003000
13:43:57 Orion kernel: Modules linked in: tun cdc_acm md4 nls_utf8 cifs dns_resolver fscache netfs libdes snd_seq_dummy snd_hrtimer dm_crypt trusted asn1_encoder xt_nat iptable_>
13:43:57 Orion kernel:  drm_ttm_helper ttm i2c_algo_bit mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel wmi drm_kms_helper ghash_clmulni_intel cec drm r8169 video uas usb_sto>
13:43:57 Orion kernel: ---[ end trace 6a741c284e912584 ]---
13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220
13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48>
13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206
13:43:57 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#1] SMP PTI
13:43:57 Orion kernel: CPU: 4 PID: 2724 Comm: Xorg Not tainted 5.13.15-200.fc34.x86_64 #1
13:43:57 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014
13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220
13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48>
13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206
13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1
13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0
13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018
13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0
13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce
13:43:57 Orion kernel: FS:  00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000
13:43:57 Orion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0
13:43:57 Orion kernel: Call Trace:
13:43:57 Orion kernel:  nvkm_mem_new_type+0xae/0x2a0 [nouveau]
13:43:57 Orion kernel:  nvkm_umem_new+0x130/0x220 [nouveau]
13:43:57 Orion kernel:  nvkm_ioctl_new+0x129/0x1e0 [nouveau]
13:43:57 Orion kernel:  ? nvkm_umem_search+0xe0/0xe0 [nouveau]
13:43:57 Orion kernel:  nvkm_ioctl+0xdc/0x180 [nouveau]
13:43:57 Orion kernel:  nvif_object_ctor+0x122/0x1c0 [nouveau]
13:43:57 Orion kernel:  nvif_mem_ctor_type+0xc2/0x180 [nouveau]
13:43:57 Orion kernel:  ? nvkm_vmm_ptes_get_map+0x2c/0x90 [nouveau]
13:43:57 Orion kernel:  ? nvkm_vmm_map+0x18d/0x350 [nouveau]
13:43:57 Orion kernel:  nouveau_mem_host+0xf3/0x190 [nouveau]
13:43:57 Orion kernel:  nouveau_sgdma_bind+0x30/0x80 [nouveau]
13:43:57 Orion kernel:  nouveau_bo_move+0x3c1/0x820 [nouveau]
13:43:57 Orion kernel:  ? ttm_pool_type_take+0x7d/0x90 [ttm]
13:43:57 Orion kernel:  ? ttm_pool_alloc+0xe6/0x590 [ttm]
13:43:57 Orion kernel:  ttm_bo_handle_move_mem+0x90/0x170 [ttm]
13:43:57 Orion kernel:  ttm_bo_validate+0x11c/0x150 [ttm]
13:43:57 Orion kernel:  ttm_bo_init_reserved+0x239/0x2c0 [ttm]
13:43:57 Orion kernel:  ttm_bo_init+0x4a/0xc0 [ttm]
13:43:57 Orion kernel:  ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau]
13:43:57 Orion kernel:  nouveau_bo_init+0x7c/0x90 [nouveau]
13:43:57 Orion kernel:  ? nv10_bo_put_tile_region.isra.0+0x80/0x80 [nouveau]
13:43:57 Orion kernel:  ? nouveau_gem_new+0xf0/0xf0 [nouveau]
13:43:57 Orion kernel:  nouveau_gem_new+0x7f/0xf0 [nouveau]
13:43:57 Orion kernel:  nouveau_gem_ioctl_new+0x45/0xe0 [nouveau]
13:43:57 Orion kernel:  ? nouveau_gem_new+0xf0/0xf0 [nouveau]
13:43:57 Orion kernel:  drm_ioctl_kernel+0x86/0xd0 [drm]
13:43:57 Orion kernel:  drm_ioctl+0x220/0x3e0 [drm]
13:43:57 Orion kernel:  ? nouveau_gem_new+0xf0/0xf0 [nouveau]
13:43:57 Orion kernel:  ? __ia32_sys_timer_getoverrun+0x40/0x50
13:43:57 Orion kernel:  nouveau_drm_ioctl+0x55/0xa0 [nouveau]
13:43:57 Orion kernel:  __x64_sys_ioctl+0x82/0xb0
13:43:57 Orion kernel:  do_syscall_64+0x40/0x80
13:43:57 Orion kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xae
13:43:57 Orion kernel: RIP: 0033:0x7f32b84540ab
13:43:57 Orion kernel: Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73>
13:43:57 Orion kernel: RSP: 002b:00007ffdd87e5148 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
13:43:57 Orion kernel: RAX: ffffffffffffffda RBX: 00007ffdd87e51a0 RCX: 00007f32b84540ab
13:43:57 Orion kernel: RDX: 00007ffdd87e51a0 RSI: 00000000c0306480 RDI: 000000000000000f
13:43:57 Orion kernel: RBP: 00000000c0306480 R08: 0000556e9a4293d0 R09: 0000000000000016
13:43:57 Orion kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000556e994bc7e0
13:43:57 Orion kernel: R13: 000000000000000f R14: 00007ffdd87e51a0 R15: 0000000000003000
13:43:57 Orion kernel: Modules linked in: tun cdc_acm md4 nls_utf8 cifs dns_resolver fscache netfs libdes snd_seq_dummy snd_hrtimer dm_crypt trusted asn1_encoder xt_nat iptable_>
13:43:57 Orion kernel:  drm_ttm_helper ttm i2c_algo_bit mxm_wmi crct10dif_pclmul crc32_pclmul crc32c_intel wmi drm_kms_helper ghash_clmulni_intel cec drm r8169 video uas usb_sto>
13:43:57 Orion kernel: ---[ end trace 6a741c284e912584 ]---
13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220
13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48>
13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206
13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1
13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0
13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018
13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0
13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce
13:43:57 Orion kernel: FS:  00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000
13:43:57 Orion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0
13:44:32 Orion kernel: usb 4-5: USB disconnect, device number 2
13:44:32 Orion kernel: sd 6:0:0:0: [sde] Synchronizing SCSI cache
13:44:32 Orion kernel: sd 6:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
13:44:32 Orion kernel: usb 4-5: new SuperSpeed USB device number 3 using xhci_hcd
13:44:32 Orion kernel: usb 4-5: New USB device found, idVendor=0781, idProduct=5580, bcdDevice= 0.10
13:44:32 Orion kernel: usb 4-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
13:44:32 Orion kernel: usb 4-5: Product: Extreme
13:44:32 Orion kernel: usb 4-5: Manufacturer: SanDisk
13:44:32 Orion kernel: usb 4-5: SerialNumber: AA010527142139551888
13:44:32 Orion kernel: usb-storage 4-5:1.0: USB Mass Storage device detected
13:44:32 Orion kernel: scsi host9: usb-storage 4-5:1.0
13:44:32 Orion mtp-probe[251591]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-5"
13:44:32 Orion mtp-probe[251591]: bus: 4, device: 3 was not an MTP device
13:44:32 Orion mtp-probe[251597]: checking bus 4, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb4/4-5"
13:44:32 Orion mtp-probe[251597]: bus: 4, device: 3 was not an MTP device
13:44:33 Orion kernel: scsi 9:0:0:0: Direct-Access     SanDisk  Extreme          0001 PQ: 0 ANSI: 6
13:44:33 Orion kernel: sd 9:0:0:0: Attached scsi generic sg4 type 0
13:44:33 Orion kernel: sd 9:0:0:0: [sdn] 125045424 512-byte logical blocks: (64.0 GB/59.6 GiB)
13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Write Protect is off
13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Mode Sense: 33 00 00 08
13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
13:44:33 Orion kernel:  sdn: sdn1 sdn2
13:44:33 Orion kernel: sd 9:0:0:0: [sdn] Attached SCSI disk
13:45:01 Orion CROND[251616]: (root) CMD ([[ "`pgrep -x each5min`" ]] || each5min >& /dev/console)
13:45:01 Orion CROND[251615]: (root) CMDEND ([[ "`pgrep -x each5min`" ]] || each5min >& /dev/console)
13:45:06 Orion sshd[251632]: rexec line 123: Deprecated option UsePrivilegeSeparation
13:45:06 Orion audit[251633]: CRYPTO_KEY_USER pid=251633 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=destroy kind=server fp=SHA256:ee:51:4b:d5:b0:6a:97:cd:fa:74:d8:>
13:45:06 Orion audit[251632]: CRYPTO_SESSION pid=251632 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=start direction=from-server [email protected] ksize=>
13:45:06 Orion audit[251632]: CRYPTO_SESSION pid=251632 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='op=start direction=from-client [email protected] ksize=>
13:45:06 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#2] SMP PTI
13:45:06 Orion kernel: CPU: 4 PID: 251632 Comm: sshd Tainted: G      D           5.13.15-200.fc34.x86_64 #1
13:45:06 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014
13:45:06 Orion kernel: RIP: 0010:__kmalloc+0xc7/0x260
13:45:06 Orion kernel: Code: 05 de 1d d1 44 49 8b 00 49 83 78 10 00 48 89 04 24 0f 84 70 01 00 00 48 85 c0 0f 84 67 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48>
13:45:06 Orion kernel: RSP: 0018:ffffb7d90d6a78c0 EFLAGS: 00010206
13:45:06 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000000 RCX: 108ddb743acd5eb1
13:45:06 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000d40 RDI: 00000000000300c0
13:45:06 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000002
13:45:06 Orion kernel: R10: 00000000002c4051 R11: 0000000000000001 R12: 0000000000000d40
13:45:06 Orion kernel: R13: 0000000000000060 R14: ffff8dd200042600 R15: ffffffffbb4003b1
13:45:06 Orion kernel: FS:  00007f77fe857900(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000
13:45:06 Orion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
13:45:06 Orion kernel: CR2: 00007f77ff4ed49f CR3: 000000010469c002 CR4: 00000000001706e0
13:43:57 Orion kernel: general protection fault, probably for non-canonical address 0x108ddb743acd5eb1: 0000 [#1] SMP PTI
13:43:57 Orion kernel: CPU: 4 PID: 2724 Comm: Xorg Not tainted 5.13.15-200.fc34.x86_64 #1
13:43:57 Orion kernel: Hardware name: Dell Inc. XPS 8700/0KWVT8, BIOS A07 03/13/2014
13:43:57 Orion kernel: RIP: 0010:kmem_cache_alloc_trace+0xac/0x220
13:43:57 Orion kernel: Code: aa 20 d1 44 49 8b 00 49 83 78 10 00 48 89 44 24 08 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 8b 4d 28 48 8b 7d 00 48 01 c1 <48> 8b 19 48 89 ce 48>
13:43:57 Orion kernel: RSP: 0018:ffffb7d901f3f700 EFLAGS: 00010206
13:43:57 Orion kernel: RAX: 108ddb743acd5e81 RBX: 0000000000000002 RCX: 108ddb743acd5eb1
13:43:57 Orion kernel: RDX: 0000000000728bcf RSI: 0000000000000dc0 RDI: 00000000000300c0
13:43:57 Orion kernel: RBP: ffff8dd200042600 R08: ffff8dd50ed300c0 R09: 0000000000000018
13:43:57 Orion kernel: R10: ffff8dd12d26f208 R11: ffffb7d901f3f988 R12: 0000000000000dc0
13:43:57 Orion kernel: R13: ffff8dd200042600 R14: 0000000000003000 R15: ffffffffc06922ce
13:43:57 Orion kernel: FS:  00007f32b7bcea80(0000) GS:ffff8dd50ed00000(0000) knlGS:0000000000000000
13:43:57 Orion kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
13:43:57 Orion kernel: CR2: 00007f32b778d000 CR3: 000000010984e003 CR4: 00000000001706e0
13:43:57 Orion kernel: Call Trace:
13:43:57 Orion kernel:  nvkm_mem_new_type+0xae/0x2a0 [nouveau]
13:43:57 Orion kernel:  nvkm_umem_new+0x130/0x220 [nouveau]
13:43:57 Orion kernel:  nvkm_ioctl_new+0x129/0x1e0 [nouveau]
13:43:57 Orion kernel:  ? nvkm_umem_search+0xe0/0xe0 [nouveau]
13:43:57 Orion kernel:  nvkm_ioctl+0xdc/0x180 [nouveau]
13:43:57 Orion kernel:  nvif_object_ctor+0x122/0x1c0 [nouveau]
13:43:57 Orion kernel:  nvif_mem_ctor_type+0xc2/0x180 [nouveau]
13:43:57 Orion kernel:  ? nvkm_vmm_ptes_get_map+0x2c/0x90 [nouveau]

....

fedora nvidia