Processing control commands:
> clone -1 -2
Bug #1076372 [src:linux] Corruption of Longsys/Lexar NM790 NVMe drive with
Linux 6.5+
Bug 1076372 cloned as bug 1090717
> retitle -1
Unknown command or malformed arguments to command.
> retitle -1 Corruption of Longsys/Kingston NVMe drive
Bug #1076372 [
Control: clone -1 -2
Control: retitle -1
Control: retitle -1 Corruption of Longsys/Kingston NVMe drive
Control: retitle -2 Corruption of Lexar NM790 NVMe drive with Linux 6.5+
Control: found -2 6.11.5-1
Hi Stefan,
On Tue, Dec 10, 2024 at 09:12:59PM +0100, Salvatore Bonaccorso wrote:
> Hi Stefan,
Hi Stefan,
On Tue, Nov 26, 2024 at 12:58:24PM +0100, Stefan wrote:
>
> Hi,
>
> here are more test results.
>
> Configuration 1: Kingston read error in 1st M.2 socket:
>
> * I ran f3 tests in a loop for several days. The read errors with
> 6.1.112 kernel could only be reproduced one time. (f3
Hi,
I did not received the test script. Therefore I tried to to test several
6.1 kernels with the f3. Without success, I could not reproduce the errors.
The corruption of the Kingston NVMe in first M.2 Socket with 6.1.94
kernel (6.1.0-22-amd64) was first noticed in a lengthy computation where
th
Hi,
currently the Lexar SSD is installed in rear M.2 socket and
Kingston is installed in primary one. (With 6.10 kernel that
configuration works).
ATM I would like to focus on 6.1 read issues with the Kingston SSD in
primary M.2 socket, because that can be done remotely and without
removing th
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 M
6 matches
Mail list logo
