slacky.eu

ieri ho spento il pc dopo 12 giorni per poter provare stamani Win11 pro, dopo mezz'ora mi son stufato, ho riavviato e tornato alla Slack, però ho avuto la sgradita sorpresa che né la sospensione, né lo spegnimento e né il riavvio funzionano -fatti da KDE;
dopo l'ultimo Spegni in messages trovo:

Apr 15 15:40:04 darkstar last message buffered 2 times
Apr 15 15:40:04 darkstar kernel: pcieport 0000:00:1d.4: AER: Multiple Corrected error received: 0000:00:1d.4
Apr 15 15:40:05 darkstar last message buffered 1 times
Apr 15 15:46:52 darkstar kernel: pcieport 0000:00:1d.4: AER: Corrected error received: 0000:00:1d.4
Apr 15 15:46:54 darkstar last message buffered 1 times

CTRL+ALT+CANC non va, se provo CTRL+ALT+F1 dopo il login come root ci pensa un po' e poi:
timed out after 60 seconds

in syslog:

Apr 15 15:40:05 darkstar kernel: pcieport 0000:00:1d.4: [ 0] RxErr
Apr 15 15:46:52 darkstar kernel: pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Receiver ID)
Apr 15 15:46:52 darkstar kernel: pcieport 0000:00:1d.4: device [8086:9db4] error status/mask=00000080/00000000
Apr 15 15:46:52 darkstar kernel: pcieport 0000:00:1d.4: [ 7] BadDLLP
Apr 15 15:46:54 darkstar kernel: pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Apr 15 15:46:54 darkstar kernel: pcieport 0000:00:1d.4: device [8086:9db4] error status/mask=00000081/00000000
Apr 15 15:46:54 darkstar kernel: pcieport 0000:00:1d.4: [ 0] RxErr
Apr 15 15:46:54 darkstar kernel: pcieport 0000:00:1d.4: [ 7] BadDLLP

vedi il link se ti e' utile: https://unix.stackexchange.com/question ... er-bad-tlp

ho guardato ma vo a tentoni ;-P
mi ero segnato di cambiare la modalità di PCIE16_3 da auto a x8 e disabilitare AER, presumo nel bios;
solo che spento (col tasto) e riavviato nel bios non ho trovato le voci;
riavviato e la sospensione funziona, ora do un'occhiata ai log...
nulla in messages;
molto in syslog:

Apr 15 18:08:44 darkstar kernel: x86/cpu: SGX disabled by BIOS.
Apr 15 18:08:44 darkstar kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/ ... n/mds.html for more details.
Apr 15 18:08:44 darkstar kernel: MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/ ... _data.html for more details.
Apr 15 18:08:44 darkstar kernel: #5 #6 #7
Apr 15 18:08:44 darkstar kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.XDCI], AE_NOT_FOUND (20210730/dswload2-162)
Apr 15 18:08:44 darkstar kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR01._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR02._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR03._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR04._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR05._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR06._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PR00._CPC], AE_NOT_FOUND (20210730/psargs-330)
Apr 15 18:08:44 darkstar kernel: ACPI Error: Aborting method \_SB.PR07._CPC due to previous error (AE_NOT_FOUND) (20210730/psparse-529)
Apr 15 18:08:44 darkstar kernel: ata2.00: supports DRM functions and may not be fully accessible
Apr 15 18:08:44 darkstar last message buffered 1 times
Apr 15 18:08:49 darkstar kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Apr 15 18:08:51 darkstar kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Apr 15 18:08:53 darkstar kernel: snd_hda_codec_hdmi hdaudioC0D2: Monitor plugged-in, Failed to power up codec ret=[-13]
Apr 15 18:09:07 darkstar kernel: vboxdrv: loading out-of-tree module taints kernel.
Apr 15 18:09:08 darkstar kernel: VBoxNetFlt: Successfully started.
Apr 15 18:09:08 darkstar kernel: VBoxNetAdp: Successfully started.
Apr 15 18:09:20 darkstar pulseaudio[1898]: [pulseaudio] cli-command.c: stat('/etc/pulse/default.pa.d'): File o directory non esistente
Apr 15 18:09:20 darkstar pulseaudio[1947]: [pulseaudio] pid.c: Daemon already running.
Apr 15 18:09:41 darkstar kernel: ata2.00: supports DRM functions and may not be fully accessible
Apr 15 18:09:41 darkstar last message buffered 1 times
Apr 15 18:09:41 darkstar kernel: thermal thermal_zone2: failed to read out thermal zone (-61)
Apr 15 18:09:47 darkstar gnome-keyring-daemon[1687]: module_instances: assertion 'funcs != NULL && "instances"' failed
Apr 15 18:09:47 darkstar last message buffered 1 times
Apr 15 18:09:47 darkstar gnome-keyring-daemon[1687]: lookup_login_keyring: assertion 'GCK_IS_SESSION (session)' failed
Apr 15 18:09:47 darkstar gnome-keyring-daemon[1687]: create_credential: assertion 'GCK_IS_SESSION (session)' failed
Apr 15 18:09:47 darkstar gnome-keyring-daemon[1687]: egg_error_message: assertion 'error' failed
Apr 15 18:09:47 darkstar gnome-keyring-daemon[1687]: couldn't create login credential: (unknown)

seguendo questa guida https://www.kernel.org/doc/html/latest/ ... _data.html
non c'è il processore i5-8279U Coffee Lake ma in file:///sys/devices/system/cpu/vulnerabilities/mmio_stale_data ho
Mitigation: Clear CPU buffers; SMT vulnerable
secondo il sito significa The processor is vulnerable and the CPU buffer clearing mitigation is enabled.
ma dovrei disabilitare SMT (qualunque cosa sia)?

EDIT
è il multithreading, le prestazioni crollerebbero se lo disabilito?

se hai current fai l'upgrade del kernel, SMT e' l'ipertreading di intel e' strano esiste ancora?hai provato ad aggiungere questo al kernel boot
By using pci=nommconf, the configuration space of all devices will be accessed in the original way, and changing the access methods works around this problem. So if you want, it's both resolving and suppressing it.

pci=nommconf andrebbe aggiunto al bootloader?
purtroppo dovrei pasticciare con elilo che non conosco affatto;

EDIT
questo potrebbe servire?
https://www.intel.it/content/www/it/it/ ... etect.html

no, non è servito;

erio ha scritto: ↑

sab 15 apr 2023, 18:46

hai provato ad aggiungere questo al kernel boot
By using pci=nommconf

ho provato ma sembra che non abbia alcun bootloader: grub ha solo la dir Themes, elilo niente, lilo.conf non c'è;
è un mistero come si avvii;

beh! hai debian slackware e windows non e' che parte dall'ultimo,se e' cosi non so che dirti,ogni volta che parte il portatile mi prende l'acido a vedere sta rotellina che gira gira....

da bios ho impostato la Slack, se voglio scegliere le altre devo premere F7, ma può darsi che in realtà sia Debian ad occuparsene;
però l'ho messa dopo la Debian che mi gestiva la Slack quando l'avevo sul secondo disco;

guarda, magari non sarà così, ma io ho avuto lo stesso problema ed era dovuto al pacchetto di Skype (non ci crederai, lo capisco, dopo un mese di analisi ero incredulo anche io). Se ce l'hai, prova a disinstallarlo (io poi ho ricompilato a mano)

per essere precisi, ti linko il thread:
viewtopic.php?f=51&t=41361&p=355786#p355786

non ho Skype;
al momento il problema non si è ripresentato;