I am a user of an SSD that identifies as HS-SSD-FUTURE 2048G, powered by the MAXIO MAP1602 controller that is affected by thme same zero CRTO bug. I am on Ubuntu Jammy.
I have installed linux-image-6.5.0-1009-oem (6.5.0-1009.10) and rebooted a few times. Every boot, the SSD is initialized correctly.
The bug title mentions a Samsung SSD so I’m hesitant to mark it verified right away, but will do it tomorrow evening as the bot is threatening to revert the fix on Tuesday.
I am a user of an SSD that identifies as HS-SSD-FUTURE 2048G, powered by the MAXIO MAP1602 controller that is affected by thme same zero CRTO bug. I am on Ubuntu Jammy.
I have installed linux-image- 6.5.0-1009- oem (6.5.0-1009.10) and rebooted a few times. Every boot, the SSD is initialized correctly.
The bug title mentions a Samsung SSD so I’m hesitant to mark it verified right away, but will do it tomorrow evening as the bot is threatening to revert the fix on Tuesday.