Bug#1024718: Fwd: Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when resuming from sleep

2022-12-23 Thread Stuart
-- Forwarded message -
From: Stuart 
Date: Fri, Dec 23, 2022 at 1:53 PM
Subject: Re: Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when
resuming from sleep
To: Salvatore Bonaccorso 


Well it seems as of this message, it won't be accepted upstream due to
their policy on not accepting quirks for issues fixed in firmware
https://lore.kernel.org/all/20221221083102.ga23...@lst.de/

On Wed, Nov 23, 2022 at 7:55 PM Salvatore Bonaccorso 
wrote:

> Hi Stuart,
>
> Thanks for the report!
>
> On Wed, Nov 23, 2022 at 06:31:48PM +, Stuart Hayhurst wrote:
> > Source: linux
> > Version: 5.19.6-1
> > Severity: important
> > Tags: patch upstream
> > X-Debbugs-Cc: stuart.a.hayhu...@gmail.com
> >
> > Dear Maintainer,
> >
> > The Samsung PM9B1 misreports its NID when resuming from sleep,
> > causing the root filesystem to be unmounted, and the system left in
> > an unstable state. Mostly this results in the device crashing, but
> > if the device somehow continues running, it's incredibly unstable,
> > where basically nothing works. It's an OEM drive found in some newer
> > laptops (like my Lenovo Yoga 7 Gen 7)
> > There's a bug report and patch upstream for this, but personally I
> > think it might be a good idea to include it in Debian until it's
> > accepted, as machines with this drive are near-unusable.
> > Upstream issue:
> https://lore.kernel.org/all/20221116171727.4083-1-...@augustwikerfors.se/
> > I've tested the patch against the current Debian 6.1-rc5 kernel on
> > my laptop, and this fixes the problem without any other issues.
>
> On the other hand, we only should include it once we are fairly
> confident that upstream accepts the fix and will include.
>
> Can you ping this bug once upstream maintainers have acked the change
> and queued it?
>
> If you have tested the patch, then you can as well reply to the thread
> mentioning you sucessfully tested the patch adding a Tested-by tag.
>
> Regards,
> Salvatore
>


Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when resuming from sleep

2022-11-23 Thread Salvatore Bonaccorso
Hi Stuart,

Thanks for the report!

On Wed, Nov 23, 2022 at 06:31:48PM +, Stuart Hayhurst wrote:
> Source: linux
> Version: 5.19.6-1
> Severity: important
> Tags: patch upstream
> X-Debbugs-Cc: stuart.a.hayhu...@gmail.com
> 
> Dear Maintainer,
> 
> The Samsung PM9B1 misreports its NID when resuming from sleep,
> causing the root filesystem to be unmounted, and the system left in
> an unstable state. Mostly this results in the device crashing, but
> if the device somehow continues running, it's incredibly unstable,
> where basically nothing works. It's an OEM drive found in some newer
> laptops (like my Lenovo Yoga 7 Gen 7)
> There's a bug report and patch upstream for this, but personally I
> think it might be a good idea to include it in Debian until it's
> accepted, as machines with this drive are near-unusable.
> Upstream issue: 
> https://lore.kernel.org/all/20221116171727.4083-1-...@augustwikerfors.se/
> I've tested the patch against the current Debian 6.1-rc5 kernel on
> my laptop, and this fixes the problem without any other issues.

On the other hand, we only should include it once we are fairly
confident that upstream accepts the fix and will include.

Can you ping this bug once upstream maintainers have acked the change
and queued it? 

If you have tested the patch, then you can as well reply to the thread
mentioning you sucessfully tested the patch adding a Tested-by tag.

Regards,
Salvatore



Bug#1024718: linux: Samsung PM9B1 NVMe fails changes NID when resuming from sleep

2022-11-23 Thread Stuart Hayhurst
Source: linux
Version: 5.19.6-1
Severity: important
Tags: patch upstream
X-Debbugs-Cc: stuart.a.hayhu...@gmail.com

Dear Maintainer,

The Samsung PM9B1 misreports its NID when resuming from sleep, causing the root 
filesystem to be unmounted, and the system left in an unstable state. Mostly 
this results in the device crashing, but if the device somehow continues 
running, it's incredibly unstable, where basically nothing works. It's an OEM 
drive found in some newer laptops (like my Lenovo Yoga 7 Gen 7)
There's a bug report and patch upstream for this, but personally I think it 
might be a good idea to include it in Debian until it's accepted, as machines 
with this drive are near-unusable.
Upstream issue: 
https://lore.kernel.org/all/20221116171727.4083-1-...@augustwikerfors.se/
I've tested the patch against the current Debian 6.1-rc5 kernel on my laptop, 
and this fixes the problem without any other issues.

Thanks :)

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled