Como solicionar o que informa o dmesg --level=warn

FERSSA
(usa Debian)

Enviado em 31/01/2023 - 21:58h

Fiz (debian): dmesg --level=warn
E tenho essas mensagens, alguém sabe como solucionar?
[ 0.012824] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 0.012825] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[ 0.054863] TSC synchronization [CPU#0 -> CPU#1]:
[ 0.054864] Measured 16219794823 cycles TSC warp between CPUs, turning off TSC clock.
[ 0.003000] #2
[ 0.048050] 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.048142] #3
[ 0.062005] PCCT header not found.
[ 0.109660] pci 0000:00:02.0: BIOS left Intel GPU interrupts enabled; disabling
[ 0.591866] r8169 0000:02:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 1.806979] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20160831/utaddress-247)
[ 1.806990] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[ 1.806996] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[ 1.808981] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20160831/utaddress-247)
[ 1.808990] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 1.983524] uvcvideo 2-1.5:1.0: Entity type for entity Extension 5 was not initialized!
[ 1.983528] uvcvideo 2-1.5:1.0: Entity type for entity Extension 4 was not initialized!
[ 1.983530] uvcvideo 2-1.5:1.0: Entity type for entity Processing 3 was not initialized!
[ 1.983532] uvcvideo 2-1.5:1.0: Entity type for entity Camera 1 was not initialized!

alexabolada
(usa Debian)

Enviado em 31/01/2023 - 21:58h

{
"error": {
"message": "We could not parse the JSON body of your request. (HINT: This likely means you aren't using your HTTP library correctly. The OpenAI API expects a JSON payload, but what was sent was not valid JSON. If you have trouble figuring out how to fix this, please send an email to support@openai.com and include any relevant code you'd like help with.)",
"type": "invalid_request_error",
"param": null,
"code": null
}
}

leandropscardua
(usa Ubuntu)

Enviado em 31/01/2023 - 22:56h

O que precisa de atenção está na saída de dmesg --level=crit,err,emerg,err

FERSSA
(usa Debian)

Enviado em 01/02/2023 - 09:12h

Com o comando dmesg --level=emerg,crit,err,alert no dá nehuma mensagem.