Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #84977 > unrolled thread

Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Eric Degenetais <eric.4.debian@grabatoulnz.fr> - 2024-12-30 02:30 +0100
    Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Eric <eric.4.debian@grabatoulnz.fr> - 2025-01-09 19:30 +0100
      Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Eric <eric.4.debian@grabatoulnz.fr> - 2025-01-09 21:40 +0100
    Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Eric <eric.4.debian@grabatoulnz.fr> - 2025-03-01 16:40 +0100
      Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Salvatore Bonaccorso <carnil@debian.org> - 2025-03-02 17:20 +0100
        Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Salvatore Bonaccorso <carnil@debian.org> - 2025-03-02 17:20 +0100
          Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) Eric <eric.4.debian@grabatoulnz.fr> - 2025-03-02 19:00 +0100
    Processed: Re: Bug#1091696: linux-image-6.12.6-amd64: linux  6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-03-02 17:20 +0100
    Processed: Re: Bug#1091696: linux-image-6.12.6-amd64: linux  6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-03-02 17:20 +0100
    Bug#1091696: marked as done (linux-image-6.12.6-amd64: linux  6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-03-23 07:20 +0100

#84977 — Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)

Package: src:linux
Version: 6.12.6-1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I decided to give Trixie a try, to see how well it worked on my computer at this stage. After installing Trixie as a secondary OS, I installed my most used packaged and made some tests,
then decided to reboot to get back to my every day OS (Bookworm). The reboot failed.


   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I tried to reboot from trixie (kernel 6.12.6) using XFCE's reboot option.


   * What was the outcome of this action?
Grub failed. I discovered that my SSD was not seen by the UEFI, which had tried to fallback on my (secondary) HDD's bootsector. This disk still
had an old grub bootsector but no usable configuration anymore. The SSD only became usable again after I shutdown the computer then cold started it.


   * What outcome did you expect instead?
I expect rebooting to work properly, as it does with bookworm.

I have tried a few things to point to the culprit :

1 - I have looked for telltale errors in journals, with no luck.
2 - I have installed bookworm's 6.1.119-1 kernel : rebooting works.
3 - No that I was reasonnably sure the kernel was the culprit, I tried various versions using the snapshots repository :
  _ the last kernel to reboot sucessfully was 6.8.12+1
  _ the first kernel to misbehave was 6.9.7+1

As a result, I think that a regression between 6.8.12 and 6.9.7 causes the SSD or its controller to hang during the shutdown for reboot process,
so that at warm restart the UEFI firmware cannot detect it. It seems however purely volatile state, since complete shutdown then restart works. 


-- Package-specific info:
** Version:
Linux version 6.12.6-amd64 (debian-kernel@lists.debian.org) (x86_64-linux-gnu-gcc-14 (Debian 14.2.0-11) 14.2.0, GNU ld (GNU Binutils for Debian) 2.43.50.20241215) #1 SMP PREEMPT_DYNAMIC Debian 6.12.6-1 (2024-12-21)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.12.6-amd64 root=UUID=1d242d11-c210-4f74-827e-a73401e6ac6b ro systemd.gpt_auto=no

** Not tainted

** Kernel log:
[    8.104164] systemd[1]: Starting systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully...
[    8.106359] systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki).
[    8.107460] systemd[1]: Started systemd-journald.service - Journal Service.
[    8.140881] systemd-journald[376]: Received client request to flush runtime journal.
[    8.271369] random: crng init done
[    8.355442] sd 2:0:0:0: Attached scsi generic sg0 type 0
[    8.376604] sd 3:0:0:0: Attached scsi generic sg1 type 0
[    8.382007] sr 4:0:0:0: Attached scsi generic sg2 type 5
[    8.389204] sd 5:0:0:0: Attached scsi generic sg3 type 0
[    8.432090] mc: Linux media interface: v0.10
[    8.435944] input: PC Speaker as /devices/platform/pcspkr/input/input8
[    8.447583] acpi_cpufreq: overriding BIOS provided _PSD data
[    8.448171] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[    8.450393] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[    8.455491] sp5100-tco sp5100-tco: initialized. heartbeat=60 sec (nowayout=0)
[    8.456921] cryptd: max_cpu_qlen set to 1000
[    8.467662] at24 0-0050: supply vcc not found, using dummy regulator
[    8.471334] at24 0-0050: 256 byte spd EEPROM, read-only
[    8.472731] at24 0-0051: supply vcc not found, using dummy regulator
[    8.476266] at24 0-0051: 256 byte spd EEPROM, read-only
[    8.476299] at24 0-0052: supply vcc not found, using dummy regulator
[    8.478846] at24 0-0052: 256 byte spd EEPROM, read-only
[    8.481653] at24 0-0053: supply vcc not found, using dummy regulator
[    8.483973] at24 0-0053: 256 byte spd EEPROM, read-only
[    8.502423] videodev: Linux video capture interface: v2.00
[    8.504300] asus_wmi: ASUS WMI generic driver loaded
[    8.519599] asus_wmi: Initialization: 0x0
[    8.520690] asus_wmi: BIOS WMI version: 0.9
[    8.520730] asus_wmi: SFUN value: 0x0
[    8.520733] eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS
[    8.521193] AES CTR mode by8 optimization enabled
[    8.525311] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input9
[    8.566489] Bluetooth: Core ver 2.22
[    8.567477] NET: Registered PF_BLUETOOTH protocol family
[    8.568469] Bluetooth: HCI device and connection manager initialized
[    8.569450] Bluetooth: HCI socket layer initialized
[    8.570415] Bluetooth: L2CAP socket layer initialized
[    8.571398] Bluetooth: SCO socket layer initialized
[    8.604024] usb 8-1: Found UVC 1.00 device Microsoft\xc2\xae LifeCam HD-5000 (045e:076d)
[    8.611554] usbcore: registered new interface driver uvcvideo
[    8.615260] usbcore: registered new interface driver btusb
[    8.630275] snd_hda_intel 0000:01:00.1: Force to non-snoop mode
[    8.646399] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops radeon_audio_component_bind_ops [radeon])
[    8.652470] Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb
[    8.652474] Bluetooth: hci0: LMP ver=6 subver=22bb; manufacturer=10
[    8.656622] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card2/input10
[    8.657787] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card2/input11
[    8.658911] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card2/input12
[    8.660097] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card2/input13
[    8.660153] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card2/input14
[    8.660247] input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:02.0/0000:01:00.1/sound/card2/input15
[    8.673753] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC892: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[    8.674771] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    8.675798] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[    8.676788] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[    8.676794] snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x11/0x1e
[    8.676795] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    8.676797] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
[    8.676798] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
[    8.676800] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
[    8.754532] input: HDA ATI SB Rear Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input16
[    8.758570] input: HDA ATI SB Front Mic as /devices/pci0000:00/0000:00:14.2/sound/card1/input17
[    8.758688] usbcore: registered new interface driver snd-usb-audio
[    8.759731] input: HDA ATI SB Line as /devices/pci0000:00/0000:00:14.2/sound/card1/input18
[    8.761532] input: HDA ATI SB Line Out Front as /devices/pci0000:00/0000:00:14.2/sound/card1/input19
[    8.761668] input: HDA ATI SB Line Out Surround as /devices/pci0000:00/0000:00:14.2/sound/card1/input20
[    8.763544] input: HDA ATI SB Line Out CLFE as /devices/pci0000:00/0000:00:14.2/sound/card1/input21
[    8.765427] input: HDA ATI SB Line Out Side as /devices/pci0000:00/0000:00:14.2/sound/card1/input22
[    8.766616] input: HDA ATI SB Front Headphone as /devices/pci0000:00/0000:00:14.2/sound/card1/input23
[    8.815013] kvm_amd: TSC scaling supported
[    8.815965] kvm_amd: Nested Virtualization enabled
[    8.816919] kvm_amd: Nested Paging enabled
[    8.817874] kvm_amd: LBR virtualization supported
[    8.830330] MCE: In-kernel MCE decoding enabled.
[    9.540486] Adding 4011000k swap on /dev/sdb3.  Priority:-2 extents:1 across:4011000k 
[    9.597466] Adding 1023996k swap on /dev/sdb6.  Priority:-3 extents:1 across:1023996k 
[    9.818220] audit: type=1400 audit(1735517540.948:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=683 comm="apparmor_parser"
[    9.820776] audit: type=1400 audit(1735517540.948:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=681 comm="apparmor_parser"
[    9.823391] audit: type=1400 audit(1735517540.948:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oosplash" pid=680 comm="apparmor_parser"
[    9.826134] audit: type=1400 audit(1735517540.952:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=677 comm="apparmor_parser"
[    9.826138] audit: type=1400 audit(1735517540.952:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=678 comm="apparmor_parser"
[    9.826140] audit: type=1400 audit(1735517540.952:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=678 comm="apparmor_parser"
[    9.834884] audit: type=1400 audit(1735517540.956:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=679 comm="apparmor_parser"
[    9.834887] audit: type=1400 audit(1735517540.956:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=679 comm="apparmor_parser"
[    9.834889] audit: type=1400 audit(1735517540.956:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=679 comm="apparmor_parser"
[    9.834890] audit: type=1400 audit(1735517540.960:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=686 comm="apparmor_parser"
[   10.224378] NET: Registered PF_QIPCRTR protocol family
[   10.330153] RTL8211E Gigabit Ethernet r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
[   10.583321] r8169 0000:02:00.0 enp2s0: Link is Down
[   13.288648] r8169 0000:02:00.0 enp2s0: Link is Up - 1Gbps/Full - flow control rx/tx
[   17.090255] kauditd_printk_skb: 10 callbacks suppressed
[   17.090263] audit: type=1400 audit(1735517548.220:22): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=1056 comm="apparmor_parser"
[   17.160037] evm: overlay not supported
[   17.550253] Initializing XFRM netlink socket
[   17.603688] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   46.911827] audit: type=1400 audit(1735517578.033:23): apparmor="ALLOWED" operation="open" class="file" profile="libreoffice-soffice" name="/etc/paperspecs" pid=2177 comm="paperconf" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[   53.507362] audit: type=1400 audit(1735517584.625:24): apparmor="ALLOWED" operation="open" class="file" profile="libreoffice-soffice" name="/home/eric/.mozilla/firefox/e30kvro9.default/cert9.db" pid=2168 comm="soffice.bin" requested_mask="wc" denied_mask="wc" fsuid=1000 ouid=1000
[   53.507781] audit: type=1400 audit(1735517584.625:25): apparmor="ALLOWED" operation="file_lock" class="file" profile="libreoffice-soffice" name="/home/eric/.mozilla/firefox/e30kvro9.default/cert9.db" pid=2168 comm="soffice.bin" requested_mask="k" denied_mask="k" fsuid=1000 ouid=1000
[   53.508269] audit: type=1400 audit(1735517584.625:26): apparmor="ALLOWED" operation="open" class="file" profile="libreoffice-soffice" name="/home/eric/.mozilla/firefox/e30kvro9.default/key4.db" pid=2168 comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
[   53.508650] audit: type=1400 audit(1735517584.625:27): apparmor="ALLOWED" operation="file_lock" class="file" profile="libreoffice-soffice" name="/home/eric/.mozilla/firefox/e30kvro9.default/key4.db" pid=2168 comm="soffice.bin" requested_mask="k" denied_mask="k" fsuid=1000 ouid=1000

** Model information
sys_vendor: To be filled by O.E.M.
product_name: To be filled by O.E.M.
product_version: To be filled by O.E.M.
chassis_vendor: To Be Filled By O.E.M.
chassis_version: To Be Filled By O.E.M.
bios_vendor: American Megatrends Inc.
bios_version: 2501
board_vendor: ASUSTeK COMPUTER INC.
board_name: M5A99X EVO R2.0
board_version: Rev 1.xx

** Loaded modules:
xt_conntrack
nft_chain_nat
xt_MASQUERADE
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
bridge
stp
llc
xfrm_user
xfrm_algo
xt_addrtype
nft_compat
nf_tables
libcrc32c
overlay
qrtr
binfmt_misc
edac_mce_amd
kvm_amd
ccp
kvm
snd_hda_codec_realtek
snd_hda_codec_generic
snd_hda_codec_hdmi
snd_hda_scodec_component
snd_hda_intel
btusb
snd_intel_dspcfg
snd_intel_sdw_acpi
snd_usb_audio
uvcvideo
btrtl
snd_hda_codec
btintel
btbcm
crct10dif_pclmul
ghash_clmulni_intel
videobuf2_vmalloc
btmtk
sha512_ssse3
uvc
sha256_ssse3
videobuf2_memops
snd_hda_core
sha1_ssse3
snd_usbmidi_lib
videobuf2_v4l2
snd_rawmidi
bluetooth
aesni_intel
eeepc_wmi
snd_hwdep
snd_seq_device
asus_wmi
snd_pcm
videodev
gf128mul
at24
sparse_keymap
platform_profile
crypto_simd
snd_timer
battery
cryptd
wmi_bmof
sp5100_tco
snd
videobuf2_common
acpi_cpufreq
rfkill
pcspkr
watchdog
k10temp
fam15h_power
mc
soundcore
joydev
sg
evdev
parport_pc
ppdev
lp
parport
efi_pstore
configfs
nfnetlink
ip_tables
x_tables
autofs4
ext4
mbcache
jbd2
crc32c_generic
amdgpu
amdxcp
drm_exec
gpu_sched
drm_buddy
crc16
hid_generic
usbhid
sr_mod
hid
cdrom
sd_mod
radeon
video
i2c_algo_bit
drm_suballoc_helper
drm_display_helper
cec
rc_core
drm_ttm_helper
ttm
ahci
xhci_pci
ohci_pci
drm_kms_helper
r8169
libahci
ohci_hcd
ehci_pci
xhci_hcd
ehci_hcd
realtek
libata
drm
mdio_devres
mxm_wmi
crc32_pclmul
usbcore
scsi_mod
e100
crc32c_intel
libphy
mii
i2c_piix4
i2c_smbus
scsi_common
usb_common
wmi
button

** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.12.6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-6.12.6-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.145
ii  kmod                                    33+20240816-2
ii  linux-base                              4.10.1

Versions of packages linux-image-6.12.6-amd64 recommends:
ii  apparmor  3.1.7-1+b3

Versions of packages linux-image-6.12.6-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  firmware-linux-free     20241210-1
ii  grub-pc                 2.12-5
pn  linux-doc-6.12          <none>

Versions of packages linux-image-6.12.6-amd64 is related to:
ii  firmware-amd-graphics      20241210-1
pn  firmware-atheros           <none>
pn  firmware-bnx2              <none>
pn  firmware-bnx2x             <none>
pn  firmware-brcm80211         <none>
pn  firmware-cavium            <none>
pn  firmware-cirrus            <none>
ii  firmware-intel-graphics    20241210-1
ii  firmware-intel-misc        20241210-1
pn  firmware-intel-sound       <none>
pn  firmware-ipw2x00           <none>
pn  firmware-ivtv              <none>
pn  firmware-iwlwifi           <none>
pn  firmware-libertas          <none>
pn  firmware-marvell-prestera  <none>
ii  firmware-mediatek          20241210-1
ii  firmware-misc-nonfree      20241210-1
pn  firmware-myricom           <none>
pn  firmware-netronome         <none>
pn  firmware-netxen            <none>
ii  firmware-nvidia-graphics   20241210-1
pn  firmware-qcom-soc          <none>
pn  firmware-qlogic            <none>
ii  firmware-realtek           20241210-1
pn  firmware-samsung           <none>
pn  firmware-siano             <none>
pn  firmware-ti-connectivity   <none>
pn  xen-hypervisor             <none>

-- no debconf information

[toc] | [next] | [standalone]

#85067

On 30/12/2024 02:22, Eric Degenetais wrote:
> 3 - No that I was reasonnably sure the kernel was the culprit, I tried various versions using the snapshots repository :
>    _ the last kernel to reboot sucessfully was 6.8.12+1
>    _ the first kernel to misbehave was 6.9.7+1
>
> As a result, I think that a regression between 6.8.12 and 6.9.7 causes the SSD or its controller to hang during the shutdown for reboot process,
> so that at warm restart the UEFI firmware cannot detect it. It seems however purely volatile state, since complete shutdown then restart works.

git bisect points to the commit below. I am no expert, but it looks 
indeed related (maybe this combination of controller & drive leads to an 
unusable state after due to modified power management).

Next step : I'll see if I can build a 6.12.6 + reverted 
7627a0edef548c4c4dea62df51cc26bfe5bbcab8 kernel and see if it works.

---------------------------------------------------------------------------------------------------------

7627a0edef548c4c4dea62df51cc26bfe5bbcab8 is the first bad commit
commit 7627a0edef548c4c4dea62df51cc26bfe5bbcab8
Author: Mario Limonciello <mario.limonciello@amd.com>
Date:   Tue Feb 6 22:13:46 2024 +0100

     ata: ahci: Drop low power policy board type

     The low power policy board type was introduced to allow systems
     to get into deep states reliably.  Before it was introduced `min_power`
     was causing problems for a number of drives.  New power policies
     `min_power_with_partial` and `med_power_with_dipm` have been introduced
     which provide a more stable baseline for systems.

     Tested-by: Damien Le Moal <dlemoal@kernel.org>
     Tested-by: Jian-Hong Pan <jhp@endlessos.org>
     Acked-by: Jian-Hong Pan <jhp@endlessos.org>
     Acked-by: Christoph Hellwig <hch@lst.de>
     Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
     Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
     Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
     Suggested-by: Christoph Hellwig <hch@infradead.org>
     Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
     [cassel: rebase patch and fix trivial conflicts]
     Signed-off-by: Niklas Cassel <cassel@kernel.org>

  drivers/ata/Kconfig |   5 +--
  drivers/ata/ahci.c  | 109 
+++++++++++++++++++++++-----------------------------
  drivers/ata/ahci.h  |   9 ++---

  3 files changed, 53 insertions(+), 70 deletions(-)

[toc] | [prev] | [next] | [standalone]

#85070

On 09/01/2025 19:19, Eric wrote:
> git bisect points to the commit below. I am no expert, but it looks 
> indeed related (maybe this combination of controller & drive leads to 
> an unusable state after due to modified power management).
>
> Next step : I'll see if I can build a 6.12.6 + reverted 
> 7627a0edef548c4c4dea62df51cc26bfe5bbcab8 kernel and see if it works.

Turns out I won't : there are other conflicting changes, and I don't 
have the necessary knowledge to merge (and I'm not comfortable running 
random junk in power management code, which result wouldn't mean 
anything anyway).


Eric

[toc] | [prev] | [next] | [standalone]

#86238

Hi for what it's worth the problem is reproduced on each new kernel 
version up to now (6.12.12-1).

I understand the bug is marked for upstream, are we just waiting for 
them to get back to us ? I am not trying to rush people here, just 
making sure I have not missed something I should do.


Thanks for your work


Eric

[toc] | [prev] | [next] | [standalone]

#86303

Control: tags -1 + upstream
Control: forwarded -1 https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u
Hi Eric,

On Sat, Mar 01, 2025 at 04:14:15PM +0100, Eric wrote:
> Hi for what it's worth the problem is reproduced on each new kernel version
> up to now (6.12.12-1).
> 
> I understand the bug is marked for upstream, are we just waiting for them to
> get back to us ? I am not trying to rush people here, just making sure I
> have not missed something I should do.
> 
> 
> Thanks for your work

Let's see what upstream say. You are looped in directly in the
upstream report as you are in best position to answer followup
questions. 

I have reported your issue here:
https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#86306

Control: tags -1 + moreinfo

On Sun, Mar 02, 2025 at 05:09:57PM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + upstream
> Control: forwarded -1 https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u
> Hi Eric,
> 
> On Sat, Mar 01, 2025 at 04:14:15PM +0100, Eric wrote:
> > Hi for what it's worth the problem is reproduced on each new kernel version
> > up to now (6.12.12-1).
> > 
> > I understand the bug is marked for upstream, are we just waiting for them to
> > get back to us ? I am not trying to rush people here, just making sure I
> > have not missed something I should do.
> > 
> > 
> > Thanks for your work
> 
> Let's see what upstream say. You are looped in directly in the
> upstream report as you are in best position to answer followup
> questions. 
> 
> I have reported your issue here:
> https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u

What would be already helpful and we missed to collect in the buglog:
What SSD is exposing the problem? Please provide this information
about the vendor, product, type of the SSD.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#86310

Hi Salvatore,

Le 02/03/2025 à 17:15, Salvatore Bonaccorso a écrit :
> Control: tags -1 + moreinfo
>
> On Sun, Mar 02, 2025 at 05:09:57PM +0100, Salvatore Bonaccorso wrote:
>> Control: tags -1 + upstream
>> Control: forwarded -1https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u
>> Hi Eric,
> What would be already helpful and we missed to collect in the buglog:
> What SSD is exposing the problem? Please provide this information
> about the vendor, product, type of the SSD.

Would that do the trick :

sudo smartctl -i /dev/disk/by-id/ata-Samsung_SSD_870_QVO_2TB_S5RPNF0T419459E
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.12-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 870 QVO 2TB
Serial Number:    S5RPNF0T419459E
LU WWN Device Id: 5 002538 f4243493c
Firmware Version: SVQ02B6Q
User Capacity:    2 000 398 934 016 bytes [2,00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Mar  2 18:46:44 2025 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

> Regards,
> Salvatore

[toc] | [prev] | [next] | [standalone]

#86302 — Processed: Re: Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)

Processing control commands:

> tags -1 + upstream
Bug #1091696 [src:linux] linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)
Ignoring request to alter tags of bug #1091696 to the same tags previously set
> forwarded -1 https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u
Bug #1091696 [src:linux] linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)
Set Bug forwarded-to-address to 'https://lore.kernel.org/regressions/Z8SBZMBjvVXA7OAK@eldamar.lan/T/#u'.

-- 
1091696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091696
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#86304 — Processed: Re: Bug#1091696: linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)

Processing control commands:

> tags -1 + moreinfo
Bug #1091696 [src:linux] linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)
Added tag(s) moreinfo.

-- 
1091696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091696
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#86564 — Bug#1091696: marked as done (linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios))

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sun, 23 Mar 2025 06:11:28 +0000
with message-id <E1twEYS-008rap-SU@fasolo.debian.org>
and subject line Bug#1091696: fixed in linux 6.13.8-1~exp1
has caused the Debian Bug report #1091696,
regarding linux-image-6.12.6-amd64: linux 6.12.6 (Trixie) fails to reboot (SATA SSD not seen by bios)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1091696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091696
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web