Bug#1010343: linux-image-5.17.0-1-amd64 ACPI errors

2022-04-29 Thread debian-edid
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

Bug#995161: linux-image-5.14.0-1-amd64: SMART error with update to 5.14 and Samsung nvme

2021-11-19 Thread debian-edid
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

Bug#1000643: linux-image-5.15.0-1-amd64 generate samsung nvme errors

2021-11-26 Thread debian-edid
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

Bug#995161: linux-image-5.14.0-1-amd64: SMART error with update to 5.14 and Samsung nvme

2021-09-28 Thread debian-edid
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

Bug#996256: linux-image-5.14.0-2-amd64 generate samsung nvme errors

2021-10-12 Thread debian-edid
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