Package: linux-image-6.11.5+debian+tj
Version: 6.11.5-265
Followup-For: Bug #1076372
X-Debbugs-Cc: tj.iam...@proton.me

Thanks for the response - very useful.

I suspect the cause may be a conjunction of several issues that in
themselves are relatively minor.

Observations:

1. That Lexar has the Maxio 1602 controller. There were quite a lot of
problems in-kernel with that controller and it took a while to resolve
those (device didn't initialise within timeout) with a quirk (commit
a3a9d63dcd15535e7i v6.4) that is model specific since the problem doesn't
affect all Maxio 1602 based devices (suggests a device firmware
incompatibility somewhere).

2. Lexar specific firmware bugs that require kernel workarounds suggest
the device firmware isn't entirely robust: 
1231363aec86704a6b04 NM760
b65d44fa0fe072c91bf4 NM620

2. It appears with that mobo M2_1 Gen5 x4 might be part of the problem
mix here, since M2_2 Gen4 x4 seems to be fine.

Logs:

Can you attach a kernel log from boot to when system services are
started - this is so we can see exactly how the PCIe and NVME are
configuring. Doesn't matter which kernel version and doesn't matter if
the devices are currently in different sockets provided it shows the
Lexar device being initialised. `journalctl --dmesg --boot ${boot_id}`

Also, for the Lexar, what scheduler is in use?
`cat /sys/block/nvme*n?/queue/scheduler`

Testing:
I wrote a shell script that does something similar to f3; if I modify it
to target your situation would you be able to run it and report results?

My thinking is for it to pre-build 128KiB blocks in tmpfs with a
deterministic human-recognisable ASCII pattern in each then use dd to do
various write+read tests to a single large file and detect when corruption
occurs, where, and if the timing or patterns used reveal how it has gone wrong.

I'd also want it to be able to tell us where on the device (logical
block) address) the writes end up in case it is related.

As I said previously it is often possible to deduce what is going wrong
from the type of corruption. We need this to know where to focus
attention.

Reply via email to