Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#51 Le 06/03/2023, à 21:12

xubu1957

Re : Reboot intempestif et absence de wifi

Bonjour,

Pour la sortie de veille, il faudrait voir la Doc veille_et_hibernation.

Montre la carte graphique :

lspci -vnn | grep -A 12 '\''[030[02]\]' | grep -Ei "vga|3d|display|kernel"

Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#52 Le 06/03/2023, à 21:14

jfbch2000

Re : Reboot intempestif et absence de wifi

07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller])
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

Voici la réponse. Merci beaucoup.

Hors ligne

#53 Le 06/03/2023, à 21:15

xubu1957

Re : Reboot intempestif et absence de wifi

Montre aussi :

echo $XDG_SESSION_TYPE

pour voir si c'est Wayland ou x11.


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#54 Le 06/03/2023, à 21:17

jfbch2000

Re : Reboot intempestif et absence de wifi

wayland

Voici

Hors ligne

#55 Le 06/03/2023, à 21:30

xubu1957

Re : Reboot intempestif et absence de wifi

Il y avait eu une série avec des problèmes d'extinction.


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#56 Le 07/03/2023, à 00:20

jfbch2000

Re : Reboot intempestif et absence de wifi

Bonsoir et merci,
J'ai tenté de mettre à jour l'ensemble des dépôts, (toujours 4 "non mis à jour" et je ne comprends pas quoi faire, mais enfin) et toujours ces messages d'erreurs au démarrage :
Je ne sais pas ce à quoi ça correspond ni comment le corriger.
Merci !

mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
mars 06 23:17:20 FERRERBARTOMEU kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.WMI6], AE_ALREADY_EXISTS (20220331/dswload2-326)
-- Boot 1d980240c4284c0e9f13b180f0076037 --
mars 06 23:09:05 FERRERBARTOMEU gdm3[1105]: Gdm: Failed to contact accountsservice: Erreur lors de l’appel de StartServiceByName pour org.freedesktop.Accounts : Transaction for accounts-daemon.service>
mars 06 20:58:02 FERRERBARTOMEU systemd[12189]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
mars 06 20:58:02 FERRERBARTOMEU systemd[12152]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
mars 06 20:31:32 FERRERBARTOMEU wpa_supplicant[1005]: bgscan simple: Failed to enable signal strength monitoring
mars 06 19:56:31 FERRERBARTOMEU gdm-launch-environment][1506]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 06 19:56:29 FERRERBARTOMEU systemd[2314]: Failed to start Application launched by gnome-session-binary.
mars 06 19:56:29 FERRERBARTOMEU systemd[2314]: Failed to start Application launched by gnome-session-binary.
mars 06 19:56:29 FERRERBARTOMEU systemd[2314]: Failed to start Application launched by gnome-session-binary.
mars 06 19:56:28 FERRERBARTOMEU gdm-password][2207]: gkr-pam: unable to locate daemon control file
mars 06 19:56:19 FERRERBARTOMEU wpa_supplicant[1005]: bgscan simple: Failed to enable signal strength monitoring
mars 06 19:56:18 FERRERBARTOMEU bluetoothd[948]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
mars 06 19:56:18 FERRERBARTOMEU systemd[1]: Failed to start Service for snap application bluez.obex.
mars 06 19:56:18 FERRERBARTOMEU systemd[1]: Failed to start Service for snap application bluez.bluez.
mars 06 19:56:18 FERRERBARTOMEU bluetoothd[1743]: Unable to get on D-Bus
mars 06 19:56:18 FERRERBARTOMEU obexd[1742]: manager_init failed
mars 06 19:56:17 FERRERBARTOMEU gnome-session-binary[1776]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
mars 06 19:56:17 FERRERBARTOMEU gnome-session-binary[1776]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
mars 06 19:56:17 FERRERBARTOMEU bluetoothd[1539]: Unable to get on D-Bus
mars 06 19:56:17 FERRERBARTOMEU obexd[1542]: manager_init failed
mars 06 19:56:17 FERRERBARTOMEU bluetoothd[1409]: Unable to get on D-Bus
mars 06 19:56:17 FERRERBARTOMEU obexd[1410]: manager_init failed
mars 06 19:56:17 FERRERBARTOMEU bluetoothd[1325]: Unable to get on D-Bus
mars 06 19:56:17 FERRERBARTOMEU obexd[1326]: manager_init failed
mars 06 19:56:16 FERRERBARTOMEU bluetoothd[1051]: Unable to get on D-Bus
mars 06 19:56:16 FERRERBARTOMEU obexd[1055]: manager_init failed
lines 50-87

mars 06 23:18:09 FERRERBARTOMEU wpa_supplicant[960]: bgscan simple: Failed to enable signal strength monitoring
mars 06 23:17:45 FERRERBARTOMEU wpa_supplicant[960]: bgscan simple: Failed to enable signal strength monitoring
mars 06 23:17:36 FERRERBARTOMEU gdm-launch-environment][1454]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
mars 06 23:17:35 FERRERBARTOMEU systemd[2318]: Failed to start Application launched by gnome-session-binary.
mars 06 23:17:34 FERRERBARTOMEU systemd[2318]: Failed to start Application launched by gnome-session-binary.
mars 06 23:17:34 FERRERBARTOMEU systemd[2318]: Failed to start Application launched by gnome-session-binary.
mars 06 23:17:34 FERRERBARTOMEU systemd[2318]: Failed to start Application launched by gnome-session-binary.
mars 06 23:17:34 FERRERBARTOMEU gdm-password][2231]: gkr-pam: unable to locate daemon control file
mars 06 23:17:27 FERRERBARTOMEU wpa_supplicant[960]: bgscan simple: Failed to enable signal strength monitoring
mars 06 23:17:24 FERRERBARTOMEU wpa_supplicant[960]: bgscan simple: Failed to enable signal strength monitoring
mars 06 23:17:23 FERRERBARTOMEU systemd[1]: Failed to start Service for snap application bluez.obex.
mars 06 23:17:23 FERRERBARTOMEU systemd[1]: Failed to start Service for snap application bluez.bluez.
mars 06 23:17:23 FERRERBARTOMEU bluetoothd[1844]: Unable to get on D-Bus
mars 06 23:17:23 FERRERBARTOMEU obexd[1845]: manager_init failed
mars 06 23:17:23 FERRERBARTOMEU bluetoothd[912]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
mars 06 23:17:23 FERRERBARTOMEU bluetoothd[1721]: Unable to get on D-Bus
mars 06 23:17:23 FERRERBARTOMEU obexd[1722]: manager_init failed
mars 06 23:17:23 FERRERBARTOMEU gnome-session-binary[1728]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
mars 06 23:17:23 FERRERBARTOMEU gnome-session-binary[1728]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
mars 06 23:17:23 FERRERBARTOMEU bluetoothd[1502]: Unable to get on D-Bus
mars 06 23:17:23 FERRERBARTOMEU obexd[1506]: manager_init failed
mars 06 23:17:22 FERRERBARTOMEU bluetoothd[1334]: Unable to get on D-Bus
mars 06 23:17:22 FERRERBARTOMEU obexd[1335]: manager_init failed
mars 06 23:17:22 FERRERBARTOMEU bluetoothd[1078]: Unable to get on D-Bus
mars 06 23:17:22 FERRERBARTOMEU obexd[1081]: manager_init failed
mars 06 23:17:20 FERRERBARTOMEU systemd[371]: /usr/lib/systemd/system-generators/netplan failed with exit status 1.
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)
mars 06 23:17:20 FERRERBARTOMEU kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
mars 06 23:17:20 FERRERBARTOMEU kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.WMI6], AE_ALREADY_EXISTS (20220331/dswload2-326)

Hors ligne

#57 Le 07/03/2023, à 00:30

xubu1957

Re : Reboot intempestif et absence de wifi


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#58 Le 07/03/2023, à 00:57

jfbch2000

Re : Reboot intempestif et absence de wifi

Merci, je ne m'inquiète pas donc pour les messages

mars 06 23:17:20 FERRERBARTOMEU kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
mars 06 23:17:20 FERRERBARTOMEU kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.WMI6], AE_ALREADY_EXISTS (20220331/dswload2-326)

Même si je me demande ce qui se cache derrière celui-là

mars 06 23:17:20 FERRERBARTOMEU kernel: blacklist: Problem blacklisting hash (-13)

Mais effectivement, à part des problèmes fréquents de sorties de veille, rien à signaler.

Hors ligne

#59 Le 07/03/2023, à 08:30

xubu1957

Re : Reboot intempestif et absence de wifi

Bonjour,

Pour :

blacklist: Problem blacklisting hash (-13)

Je lis dans lore.kernel.org/lkml/c8c65713-5cda-43ad-8018-20f2e32e4432@t-8ch.de/T/ :

Cela se produit parce que le micrologiciel contient des entrées de liste noire en double.

et un bug > launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2008188


Montre :

cat /etc/modprobe.d/blacklist.conf

Dernière modification par xubu1957 (Le 07/03/2023, à 08:34)


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#60 Le 07/03/2023, à 10:19

jfbch2000

Re : Reboot intempestif et absence de wifi

Voici la réponse :

# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.

# evbug is a debug tool that should be loaded explicitly
blacklist evbug

# these drivers are very simple, the HID drivers are usually preferred
blacklist usbmouse
blacklist usbkbd

# replaced by e100
blacklist eepro100

# replaced by tulip
blacklist de4x5

# causes no end of confusion by creating unexpected network interfaces
blacklist eth1394

# snd_intel8x0m can interfere with snd_intel8x0, doesn't seem to support much
# hardware on its own (Ubuntu bug #2011, #6810)
blacklist snd_intel8x0m

# Conflicts with dvb driver (which is better for handling this device)
blacklist snd_aw2

# replaced by p54pci
blacklist prism54

# replaced by b43 and ssb.
blacklist bcm43xx

# most apps now use garmin usb driver directly (Ubuntu: #114565)
blacklist garmin_gps

# replaced by asus-laptop (Ubuntu: #184721)
blacklist asus_acpi

# low-quality, just noise when being used for sound playback, causes
# hangs at desktop session start (Ubuntu: #246969)
blacklist snd_pcsp

# ugly and loud noise, getting on everyone's nerves; this should be done by a
# nice pulseaudio bing (Ubuntu: #77010)
blacklist pcspkr

# EDAC driver for amd76x clashes with the agp driver preventing the aperture
# from being initialised (Ubuntu: #297750). Blacklist so that the driver
# continues to build and is installable for the few cases where its
# really needed.
blacklist amd76x_edac

Hors ligne

#61 Le 07/03/2023, à 10:27

xubu1957

Re : Reboot intempestif et absence de wifi

C'est pas là-dedans.

Je ne sais pas aider plus !  ¯∖_(ツ)_/¯


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#62 Le 07/03/2023, à 11:32

LukePerp

Re : Reboot intempestif et absence de wifi

Les reboot aléatoires peuvent prendre origines dans dysfonctionnements de la carte mère ou du disque dur ayant Linux. Peux tu utiliser cette documentation pour nous donner les rapports d'analyse du disque dur contenant Ubuntu :
https://doc.ubuntu-fr.org/smartmontools


Gamer inside - Ubuntu Mate dernière LTS - Intel i5, 16 Go - Dual boot Windows - Utilisateur de Dapps sur Ethereum

Hors ligne

#63 Le 07/03/2023, à 15:22

jfbch2000

Re : Reboot intempestif et absence de wifi

Merci,

Voici les infos :

$  sudo smartctl -s on -a /dev/nvme0n1
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.19.0-35-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       UMIS RPETJ512MGE2QDQ
Serial Number:                      SS0L25217X1RC18P22PD
Firmware Version:                   1.5Q0630
PCI Vendor/Subsystem ID:            0x1cc4
IEEE OUI Identifier:                0x044a50
Controller ID:                      0
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512110190592 [512 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            044a50 01819019e3
Local Time is:                      Tue Mar  7 14:14:39 2023 CET
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         64 Pages
Warning  Comp. Temp. Threshold:     80 Celsius
Critical Comp. Temp. Threshold:     83 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     9.00W       -        -    0  0  0  0        0       0
 1 +     4.60W       -        -    1  1  1  1        0       0
 2 +     3.80W       -        -    2  2  2  2        0       0
 3 -   0.0450W       -        -    3  3  3  3     2000    2000
 4 -   0.0040W       -        -    4  4  4  4    15000   15000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        22 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    2%
Data Units Read:                    11779785 [6,03 TB]
Data Units Written:                 13372658 [6,84 TB]
Host Read Commands:                 106597877
Host Write Commands:                205419846
Controller Busy Time:               1589
Power Cycles:                       2389
Power On Hours:                     3574
Unsafe Shutdowns:                   88
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0

Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
sudo nvme error-log /dev/nvme0n1
Error Log Entries for device:nvme0n1 entries:64
.................
 Entry[ 0]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 1]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 2]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 3]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 4]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 5]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 6]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 7]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 8]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[ 9]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[10]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[11]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[12]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[13]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[14]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[15]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[16]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[17]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[18]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[19]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[20]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[21]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[22]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[23]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[24]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[25]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[26]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[27]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[28]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[29]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[30]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[31]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[32]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[33]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[34]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[35]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[36]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[37]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[38]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[39]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[40]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[41]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[42]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[43]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[44]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[45]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[46]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[47]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[48]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[49]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[50]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[51]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[52]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[53]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[54]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[55]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[56]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[57]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[58]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[59]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[60]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[61]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[62]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
 Entry[63]   
.................
error_count	: 0
sqid		: 0
cmdid		: 0
status_field	: 0(SUCCESS: The command completed successfully)
phase_tag	: 0
parm_err_loc	: 0
lba		: 0
nsid		: 0
vs		: 0
trtype		: The transport type is not indicated or the error is not transport related.
cs		: 0
trtype_spec_info: 0
.................
$ sudo nvme smart-log /dev/nvme0n1
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning			: 0
temperature				: 23 C (296 Kelvin)
available_spare				: 100%
available_spare_threshold		: 10%
percentage_used				: 2%
endurance group critical warning summary: 0
data_units_read				: 11780036
data_units_written			: 13372939
host_read_commands			: 106599963
host_write_commands			: 205425753
controller_busy_time			: 1589
power_cycles				: 2389
power_on_hours				: 3574
unsafe_shutdowns			: 88
media_errors				: 0
num_err_log_entries			: 0
Warning Temperature Time		: 0
Critical Composite Temperature Time	: 0
Thermal Management T1 Trans Count	: 0
Thermal Management T2 Trans Count	: 0
Thermal Management T1 Total Time	: 0
Thermal Management T2 Total Time	: 0
sudo nvme sanitize-log /dev/nvme0n1
Sanitize Progress                      (SPROG) :  65535
Sanitize Status                        (SSTAT) :  0
Sanitize Command Dword 10 Information (SCDW10) :  0
Estimated Time For Overwrite                   :  4294967295 (No time period reported)
Estimated Time For Block Erase                 :  4294967295 (No time period reported)
Estimated Time For Crypto Erase                :  4294967295 (No time period reported)
Estimated Time For Overwrite (No-Deallocate)   :  0
Estimated Time For Block Erase (No-Deallocate) :  0
Estimated Time For Crypto Erase (No-Deallocate):  0

Hors ligne

#64 Le 07/03/2023, à 17:54

xubu1957

Re : Reboot intempestif et absence de wifi

Dans Strange kernel errors during boot after 5.19 :

le 08/11/2022, mickael a écrit :

Ces messages du noyau doivent être traités comme des avertissements et non comme des erreurs. Vous ne devez pas supprimer les hachages de la liste noire (c'est-à-dire ne pas effacer les clés de démarrage sécurisées) , il s'agit d'une mesure de sécurité pour vous protéger contre les signatures malveillantes. Ces messages du noyau s'affichent maintenant parce que nous avons renforcé ce mécanisme de sécurité, et il révèle maintenant des problèmes avec certains firmwares. Il existe un patch noyau en cours pour mettre à jour ce message d'erreur lore.kernel.org/lkml/


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne