Package: linux-image-5.17.0-1-amd64
Version: 5.17.3-1
After upgrading from kernel 5.16 to 5.17 there are *ACPI* errors like this :
kernel: ACPI Error: Aborting method \_PR.PR01._CPC due to previous error
(AE_NOT_FOUND) (20211217/psparse-529)
kernel: ACPI BIOS Error (bug): Could not resolve symb
Hi,
Can someone explain if this is a bug ? or maybe kernel try to talk to
nvme disk in non supported (by a disk) way ? or maybe there is a need
for some kind of exclude samsung disks from this kind of communication ?
Is anybody even working on this ?
Regards Edi
Package: linux-image-5.15.0-1-amd64
Version: 5.15.3-1
There are errors increased in smart after every boot in Samsung 970 evo
nvme disk.
*Error Information Log Entries: 41* <- increased after every boot
nvme error-log /dev/nvme0 :
status_field :*0x4004(INVALID_FIELD: A reserved code
Hi,
I have exactly the same error with Samsung 970 EVO and smart error
counter is incremented after every boot :
error_count : 38
status_field : 0x4004(INVALID_FIELD: A reserved coded value or an
unsupported value in a defined field)
Best regards
Edi
Package: linux-image-5.14.0-2-amd64
Version: 5.14.9-2
After upgrading from kernel 5.10 to 5.14 there are errors increased in
smart after every boot in Samsung 970 evo.
Error Information Log Entries: 41 <- increased after every boot
nvme error-log /dev/nvme0 :
status_field : 0x4004(I
Package: linux-image-6.12.21-amd64
Version: 6.12.21
Dear Maintainer,
I have usbhid bugs in journal while bootig concern usbhid driver like:
can't add hid device: -71
probe with driver usbhid failed with error -71
These errors concern usb keyboard which works normally despite these
err
Hi,
full kernel log:
kernel: usbhid 1-13:1.0: can't add hid device: -71
kernel: usbhid 1-13:1.0: probe with driver usbhid failed with error -71
kernel: usbhid 1-13:1.1: can't add hid device: -71
kernel: usbhid 1-13:1.1: probe with driver usbhid failed with error -71
kernel: usbhid 1-13:1.2: can'
I have just recompiled 6.13.11~exp with statically compiled usbhid and
xhci_hcd and after few reboots same errors appeared. Probably it will be
the same with upstream 6.14.1 but i didn't do enough reboots to observe
this. It is weird because on cold boot these errors never occur but
later after
8 matches
Mail list logo
