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

Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

Started by	Cyril Brulebois <kibi@debian.org>
First post	2024-04-09 01:10 +0200
Last post	2024-04-10 21:50 +0200
Articles	19 — 4 participants

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

  Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-09 01:10 +0200
    Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Diederik de Haas <didi.debian@cknow.org> - 2024-04-09 15:50 +0200
      Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Salvatore Bonaccorso <carnil@debian.org> - 2024-04-10 12:10 +0200
        Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 15:00 +0200
          Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 15:40 +0200
            Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Salvatore Bonaccorso <carnil@debian.org> - 2024-04-10 15:50 +0200
              Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Salvatore Bonaccorso <carnil@debian.org> - 2024-04-10 16:00 +0200
                Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 16:10 +0200
                  Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 17:30 +0200
                    Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 19:10 +0200
                      Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 19:40 +0200
                      Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Salvatore Bonaccorso <carnil@debian.org> - 2024-04-10 20:50 +0200
                        Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-10 21:50 +0200
                Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Cyril Brulebois <kibi@debian.org> - 2024-04-11 10:10 +0200
            Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2) Diederik de Haas <didi.debian@cknow.org> - 2024-04-10 17:00 +0200
    Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of  SMART information: Device is in SLEEP mode, exit(2) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-04-10 12:10 +0200
    Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of  SMART information: Device is in SLEEP mode, exit(2) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-04-10 15:50 +0200
    Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of  SMART information: Device is in SLEEP mode, exit(2) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-04-10 20:50 +0200
    Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of  SMART information: Device is in SLEEP mode, exit(2) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-04-10 21:50 +0200

#82189 — Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-09 01:10 +0200
Subject	Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Message-ID	<Ir6hI-4ZkR-19@gated-at.bofh.it>

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

Hi,

Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64
leads to losing some SMART information, at least as queried by munin (in
Debian 12) when it comes to sensors.

I'm getting the following results on the 2 pairs of disks in this machine:
 - 2×ST4000VN008-2DR1 (sda, sdb)
 - 2×ST8000VN004-2M21 (sdc, sdd)

    root@anchorage:~# /usr/sbin/smartctl -A --nocheck=standby -d ata /dev/sda
    smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.0-19-amd64] (local build)
    Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
    
    Device is in SLEEP mode, exit(2)

For some reason, the “S.M.A.R.T values” graphs is still OK, while the
“HDD temperature” graph (using the aforementioned command) isn't
anymore.

The “Device is in SLEEP mode” status getting reported is obviously a
lie, since all disks are in use (one pair does system stuff, the other
pair does media stuff).

Rebooting a couple of time with this version gives consistent negative
results. Rebooting into linux-image-6.1.0-18-amd64 gives data back.

The trace that appears below seems to happen exactly once per boot (and
not even once per disk).


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant


-- Package-specific info:
** Version:
Linux version 6.1.0-19-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.82-1 (2024-03-28)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-19-amd64 root=/dev/mapper/data-root ro quiet

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[   23.726790] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   23.763253] EXT4-fs (dm-13): mounted filesystem with ordered data mode. Quota mode: none.
[   23.764773] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
[   23.765529] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[   23.765566] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[   23.765595] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[   23.765626] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[   23.785394] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[   23.786295] ACPI: video: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[   23.786473] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input10
[   23.798653] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[   23.801990] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
[   23.823066] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[   23.825531] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[   23.916595] XFS (dm-4): Deprecated V4 format (crc=0) will not be supported after September 2030.
[   23.920456] EXT4-fs (dm-14): mounted filesystem with ordered data mode. Quota mode: none.
[   23.941160] XFS (dm-4): Mounting V4 Filesystem
[   24.076883] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Quota mode: none.
[   24.152240] XFS (dm-4): Ending clean mount
[   24.152258] xfs filesystem being mounted at /data/media supports timestamps until 2038 (0x7fffffff)
[   24.160691] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Quota mode: none.
[   24.177491] intel_rapl_common: Found RAPL domain package
[   24.177494] intel_rapl_common: Found RAPL domain core
[   24.177495] intel_rapl_common: Found RAPL domain uncore
[   24.177496] intel_rapl_common: Found RAPL domain dram
[   24.177500] intel_rapl_common: RAPL package-0 domain package locked by BIOS
[   24.177505] intel_rapl_common: RAPL package-0 domain dram locked by BIOS
[   24.415347] audit: type=1400 audit(1712616841.356:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=867 comm="apparmor_parser"
[   24.415751] audit: type=1400 audit(1712616841.356:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=868 comm="apparmor_parser"
[   24.415755] audit: type=1400 audit(1712616841.356:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=868 comm="apparmor_parser"
[   24.430914] audit: type=1400 audit(1712616841.372:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=870 comm="apparmor_parser"
[   24.430919] audit: type=1400 audit(1712616841.372:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=870 comm="apparmor_parser"
[   24.430922] audit: type=1400 audit(1712616841.372:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=870 comm="apparmor_parser"
[   24.438207] audit: type=1400 audit(1712616841.380:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=869 comm="apparmor_parser"
[   24.438212] audit: type=1400 audit(1712616841.380:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=869 comm="apparmor_parser"
[   24.438215] audit: type=1400 audit(1712616841.380:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=869 comm="apparmor_parser"
[   24.438217] audit: type=1400 audit(1712616841.380:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/{,usr/}sbin/dhclient" pid=869 comm="apparmor_parser"
[   24.754923] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168g-2.fw (-2)
[   24.754931] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[   24.754938] r8169 0000:02:00.0: firmware: failed to load rtl_nic/rtl8168g-2.fw (-2)
[   24.754941] r8169 0000:02:00.0: Direct firmware load for rtl_nic/rtl8168g-2.fw failed with error -2
[   24.754944] r8169 0000:02:00.0: Unable to load firmware rtl_nic/rtl8168g-2.fw (-2)
[   24.780189] Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
[   24.904509] r8169 0000:02:00.0 eth0: Link is Down
[   25.026765] RPC: Registered named UNIX socket transport module.
[   25.026769] RPC: Registered udp transport module.
[   25.026770] RPC: Registered tcp transport module.
[   25.026770] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   25.783492] tun: Universal TUN/TAP device driver, 1.6
[   27.683793] r8169 0000:02:00.0 eth0: Link is Up - 1Gbps/Full - flow control off
[   27.683805] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   36.702818] ------------[ cut here ]------------
[   36.702821] WARNING: CPU: 0 PID: 2049 at drivers/scsi/scsi_lib.c:214 scsi_execute_cmd+0x42/0x2c0 [scsi_mod]
[   36.702840] Modules linked in: cpufreq_ondemand cpufreq_conservative cpufreq_userspace cpufreq_powersave tun nvme_fabrics sunrpc binfmt_misc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ghash_clmulni_intel xfs snd_hda_codec_realtek nls_ascii cryptd i915 nls_cp437 sha512_ssse3 snd_hda_codec_generic ledtrig_audio sha512_generic mei_hdcp vfat sha256_ssse3 fat sha1_ssse3 snd_hda_intel drm_buddy snd_intel_dspcfg drm_display_helper snd_intel_sdw_acpi rapl intel_cstate snd_hda_codec cec joydev evdev intel_uncore rc_core snd_hda_core snd_hwdep ttm iTCO_wdt intel_pmc_bxt mei_me at24 iTCO_vendor_support snd_pcm sg snd_timer watchdog mei snd drm_kms_helper i2c_algo_bit mxm_wmi soundcore intel_smartconnect button xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter drm loop efi_pstore fuse configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq
[   36.702882]  async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath linear dm_snapshot dm_bufio uas usb_storage raid1 md_mod hid_generic dm_mod usbhid hid sd_mod nvme ahci nvme_core libahci t10_pi xhci_pci xhci_hcd libata ehci_pci ehci_hcd crc64_rocksoft crc64 r8169 crc32_pclmul crc_t10dif realtek mdio_devres usbcore crct10dif_generic crc32c_intel libphy crct10dif_pclmul lpc_ich crct10dif_common i2c_i801 i2c_smbus scsi_mod scsi_common usb_common fan video wmi
[   36.702907] CPU: 0 PID: 2049 Comm: smartctl Not tainted 6.1.0-19-amd64 #1  Debian 6.1.82-1
[   36.702909] Hardware name: MSI MS-7817/H81M-P33 (MS-7817), BIOS V1.9 03/30/2015
[   36.702910] RIP: 0010:scsi_execute_cmd+0x42/0x2c0 [scsi_mod]
[   36.702923] Code: 55 48 89 fd 53 48 83 ec 10 4c 8b 64 24 50 48 89 0c 24 4d 85 e4 0f 84 02 02 00 00 49 83 3c 24 00 74 24 41 83 7c 24 08 60 74 1c <0f> 0b bd ea ff ff ff 48 83 c4 10 89 e8 5b 5d 41 5c 41 5d 41 5e 41
[   36.702924] RSP: 0018:ffffab15014e7c20 EFLAGS: 00010287
[   36.702926] RAX: ffffab15014e7c80 RBX: ffff91e07a3fb000 RCX: 0000000000000000
[   36.702927] RDX: 0000000000000022 RSI: 0000000000000022 RDI: ffff91e07a3fb000
[   36.702928] RBP: ffff91e07a3fb000 R08: 0000000000000000 R09: 00000000000009c4
[   36.702929] R10: 0000000000000000 R11: 0000000000000000 R12: ffffab15014e7c80
[   36.702930] R13: 0000000000000000 R14: 00000000000009c4 R15: ffffab15014e7cb0
[   36.702932] FS:  00007f4b66237840(0000) GS:ffff91e34fa00000(0000) knlGS:0000000000000000
[   36.702933] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   36.702934] CR2: 00007ffd2bf1eeb8 CR3: 000000013f396003 CR4: 00000000000706f0
[   36.702936] Call Trace:
[   36.702938]  <TASK>
[   36.702940]  ? __warn+0x7d/0xc0
[   36.702943]  ? scsi_execute_cmd+0x42/0x2c0 [scsi_mod]
[   36.702955]  ? report_bug+0xe2/0x150
[   36.702959]  ? handle_bug+0x41/0x70
[   36.702961]  ? exc_invalid_op+0x13/0x60
[   36.702963]  ? asm_exc_invalid_op+0x16/0x20
[   36.702965]  ? scsi_execute_cmd+0x42/0x2c0 [scsi_mod]
[   36.702977]  ata_cmd_ioctl+0x144/0x2f0 [libata]
[   36.703000]  scsi_ioctl+0x3f5/0x930 [scsi_mod]
[   36.703011]  ? scsi_block_when_processing_errors+0x22/0x100 [scsi_mod]
[   36.703021]  ? set_pte+0x5/0x10
[   36.703024]  ? __handle_mm_fault+0xd90/0xfa0
[   36.703026]  ? scsi_ioctl_block_when_processing_errors+0x45/0x50 [scsi_mod]
[   36.703036]  blkdev_ioctl+0x133/0x270
[   36.703040]  __x64_sys_ioctl+0x90/0xd0
[   36.703043]  do_syscall_64+0x5b/0xc0
[   36.703044]  ? handle_mm_fault+0xdb/0x2d0
[   36.703047]  ? do_user_addr_fault+0x1b0/0x580
[   36.703050]  ? exit_to_user_mode_prepare+0x40/0x1e0
[   36.703052]  entry_SYSCALL_64_after_hwframe+0x64/0xce
[   36.703056] RIP: 0033:0x7f4b65f1cc5b
[   36.703057] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[   36.703059] RSP: 002b:00007ffd2bf1e7e0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
[   36.703060] RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007f4b65f1cc5b
[   36.703061] RDX: 00007ffd2bf1ea40 RSI: 000000000000031f RDI: 0000000000000003
[   36.703062] RBP: 00007ffd2bf1eec0 R08: 0000000000000000 R09: 0000000000000000
[   36.703063] R10: 8ab5806c4492a8f0 R11: 0000000000000246 R12: 00005614c6be4600
[   36.703064] R13: 00007ffd2bf1ea40 R14: 00007ffd2bf1f160 R15: 0000000000000000
[   36.703066]  </TASK>
[   36.703067] ---[ end trace 0000000000000000 ]---

** Model information
sys_vendor: MSI
product_name: MS-7817
product_version: 1.0
chassis_vendor: MSI
chassis_version: 1.0
bios_vendor: American Megatrends Inc.
bios_version: V1.9
board_vendor: MSI
board_name: H81M-P33 (MS-7817)
board_version: 1.0

** Loaded modules:
tls
cpufreq_ondemand
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
tun
nvme_fabrics
sunrpc
binfmt_misc
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
ghash_clmulni_intel
xfs
snd_hda_codec_realtek
nls_ascii
cryptd
i915
nls_cp437
sha512_ssse3
snd_hda_codec_generic
ledtrig_audio
sha512_generic
mei_hdcp
vfat
sha256_ssse3
fat
sha1_ssse3
snd_hda_intel
drm_buddy
snd_intel_dspcfg
drm_display_helper
snd_intel_sdw_acpi
rapl
intel_cstate
snd_hda_codec
cec
joydev
evdev
intel_uncore
rc_core
snd_hda_core
snd_hwdep
ttm
iTCO_wdt
intel_pmc_bxt
mei_me
at24
iTCO_vendor_support
snd_pcm
sg
snd_timer
watchdog
mei
snd
drm_kms_helper
i2c_algo_bit
mxm_wmi
soundcore
intel_smartconnect
button
xt_tcpudp
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
iptable_filter
drm
loop
efi_pstore
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
efivarfs
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid0
multipath
linear
dm_snapshot
dm_bufio
uas
usb_storage
raid1
md_mod
hid_generic
dm_mod
usbhid
hid
sd_mod
nvme
ahci
nvme_core
libahci
t10_pi
xhci_pci
xhci_hcd
libata
ehci_pci
ehci_hcd
crc64_rocksoft
crc64
r8169
crc32_pclmul
crc_t10dif
realtek
mdio_devres
usbcore
crct10dif_generic
crc32c_intel
libphy
crct10dif_pclmul
lpc_ich
crct10dif_common
i2c_i801
i2c_smbus
scsi_mod
scsi_common
usb_common
fan
video
wmi

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
	Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor DRAM Controller [1462:7817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>
	Kernel driver in use: hsw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
	DeviceName:  Onboard IGD
	Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 35
	Region 0: Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at e0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at f000 [size=64]
	Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915
	Kernel modules: i915

00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05) (prog-if 30 [XHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family USB xHCI [1462:7817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 28
	Region 0: Memory at f7e00000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family MEI Controller [1462:7817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 33
	Region 0: Memory at f7e1a000 (64-bit, non-prefetchable) [size=16]
	Capabilities: <access denied>
	Kernel driver in use: mei_me
	Kernel modules: mei_me

00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05) (prog-if 20 [EHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family USB EHCI [1462:7817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f7e18000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05)
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset High Definition Audio Controller [1462:d817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 34
	Region 0: Memory at f7e10000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5) (prog-if 00 [Normal decode])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family PCI Express Root Port [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 24
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 2000-2fff [size=4K] [16-bit]
	Memory behind bridge: df200000-df3fffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: df400000-df5fffff [size=2M] [32-bit]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 [8086:8c14] (rev d5) (prog-if 00 [Normal decode])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family PCI Express Root Port [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin C routed to IRQ 25
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: e000-efff [size=4K] [16-bit]
	Memory behind bridge: f7d00000-f7dfffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: f0000000-f00fffff [size=1M] [32-bit]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5) (prog-if 00 [Normal decode])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family PCI Express Root Port [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 26
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: f7c00000-f7cfffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR+ NoISA- VGA- VGA16+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05) (prog-if 20 [EHCI])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family USB EHCI [1462:7817]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at f7e17000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci

00:1f.0 ISA bridge [0601]: Intel Corporation H81 Express LPC Controller [8086:8c5c] (rev 05)
	Subsystem: Micro-Star International Co., Ltd. [MSI] H81 Express LPC Controller [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich

00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05) (prog-if 01 [AHCI 1.0])
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 29
	Region 0: I/O ports at f0b0 [size=8]
	Region 1: I/O ports at f0a0 [size=4]
	Region 2: I/O ports at f090 [size=8]
	Region 3: I/O ports at f080 [size=4]
	Region 4: I/O ports at f060 [size=32]
	Region 5: Memory at f7e16000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci
	Kernel modules: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
	Subsystem: Micro-Star International Co., Ltd. [MSI] 8 Series/C220 Series Chipset Family SMBus Controller [1462:7817]
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at f7e15000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at f040 [size=32]
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0c)
	Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1462:7817]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at e000 [size=256]
	Region 2: Memory at f7d00000 (64-bit, non-prefetchable) [size=4K]
	Region 4: Memory at f0000000 (64-bit, prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

03:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P2 NVMe PCIe SSD [c0a9:540a] (rev 01) (prog-if 02 [NVM Express])
	Subsystem: Micron/Crucial Technology P2 [Nick P2] / P3 / P3 Plus NVMe PCIe SSD (DRAM-less) [c0a9:540a]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at f7c00000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme
	Kernel modules: nvme


** USB devices:
Bus 004 Device 002: ID 8087:8000 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 1a5a:0006 Tandberg Data RDX             
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


-- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-19-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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.1.0-19-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod                                    30+20221128-1
ii  linux-base                              4.9

Versions of packages linux-image-6.1.0-19-amd64 recommends:
ii  apparmor             3.0.8-3
ii  firmware-linux-free  20200122-1

Versions of packages linux-image-6.1.0-19-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  extlinux                3:6.04~git20190206.bf6db5b4+dfsg1-3+b1
ii  grub-efi-amd64          2.06-13+deb12u1
pn  linux-doc-6.1           <none>

Versions of packages linux-image-6.1.0-19-amd64 is related to:
pn  firmware-amd-graphics     <none>
pn  firmware-atheros          <none>
pn  firmware-bnx2             <none>
pn  firmware-bnx2x            <none>
pn  firmware-brcm80211        <none>
pn  firmware-cavium           <none>
pn  firmware-intel-sound      <none>
pn  firmware-intelwimax       <none>
pn  firmware-ipw2x00          <none>
pn  firmware-ivtv             <none>
pn  firmware-iwlwifi          <none>
pn  firmware-libertas         <none>
pn  firmware-linux-nonfree    <none>
pn  firmware-misc-nonfree     <none>
pn  firmware-myricom          <none>
pn  firmware-netxen           <none>
pn  firmware-qlogic           <none>
pn  firmware-realtek          <none>
pn  firmware-samsung          <none>
pn  firmware-siano            <none>
pn  firmware-ti-connectivity  <none>
pn  xen-hypervisor            <none>

-- no debconf information

[toc] | [next] | [standalone]

#82193

From	Diederik de Haas <didi.debian@cknow.org>
Date	2024-04-09 15:50 +0200
Message-ID	<Irk1j-58je-5@gated-at.bofh.it>
In reply to	#82189

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

Hi Cyril,

On Tuesday, 9 April 2024 01:06:43 CEST Cyril Brulebois wrote:
> Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64
> leads to losing some SMART information, at least as queried by munin (in
> Debian 12) when it comes to sensors.

Does the problem go away if you revert the following commits on top of -19?

db6338f45971b4285ea368432a84033690eaf53c
scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler

1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
scsi: core: Move scsi_host_busy() out of host lock if it is for per-command

cf33e6ca12d814e1be2263cb76960d0019d7fb94
scsi: core: Add struct for args to execution functions

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

#82208

From	Salvatore Bonaccorso <carnil@debian.org>
Date	2024-04-10 12:10 +0200
Message-ID	<IrD3X-5k5z-3@gated-at.bofh.it>
In reply to	#82193

Control: tags -1 + moreinfo 

Cyril,

On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> Hi Cyril,
> 
> On Tuesday, 9 April 2024 01:06:43 CEST Cyril Brulebois wrote:
> > Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64
> > leads to losing some SMART information, at least as queried by munin (in
> > Debian 12) when it comes to sensors.
> 
> Does the problem go away if you revert the following commits on top of -19?
> 
> db6338f45971b4285ea368432a84033690eaf53c
> scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
> 
> 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
> 
> cf33e6ca12d814e1be2263cb76960d0019d7fb94
> scsi: core: Add struct for args to execution functions

Or if that does not find the culprit, would you be able to bisect the
upstrema changes beweeen 6.1.76 and 6.1.82?

There would be for instance the following ata related change:

4b085736e44d ("ata: libata-core: Do not try to set sleeping devices to standby")

If you can test it with other kernels, does the same happens on
6.7.7-1 and 6.7.9-2?

Regards,
Salvatore

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

#82209

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 15:00 +0200
Message-ID	<IrFIt-5lrd-1@gated-at.bofh.it>
In reply to	#82208

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

Hi Salvatore,

Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > Hi Cyril,
> > 
> > On Tuesday, 9 April 2024 01:06:43 CEST Cyril Brulebois wrote:
> > > Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64
> > > leads to losing some SMART information, at least as queried by munin (in
> > > Debian 12) when it comes to sensors.
> > 
> > Does the problem go away if you revert the following commits on top of -19?
> > 
> > db6338f45971b4285ea368432a84033690eaf53c
> > scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
> > 
> > 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> > scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
> > 
> > cf33e6ca12d814e1be2263cb76960d0019d7fb94
> > scsi: core: Add struct for args to execution functions

Preparing that test right now, thanks Diederik.

> Or if that does not find the culprit, would you be able to bisect the
> upstrema changes beweeen 6.1.76 and 6.1.82?
> 
> There would be for instance the following ata related change:
> 
> 4b085736e44d ("ata: libata-core: Do not try to set sleeping devices to standby")
> 
> If you can test it with other kernels, does the same happens on
> 6.7.7-1 and 6.7.9-2?

I'm not really keen on playing kernel ping-pong on this particular
machine (which is important in my infrastructure), but I've verified
that adding a SATA disk to an existing VM running Debian 12 on a
QEMU/libvirt Debian 12 host gives me similar results with -18 and -19
kernels (some data in the former case, no data at all in the latter
one).

I think I'd rather stay with 6.1.y kernels if at all possible, to avoid
having to figure out other changes that might be possibly required to
cope with newer kernels.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82210

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 15:40 +0200
Message-ID	<IrGlb-5lTd-1@gated-at.bofh.it>
In reply to	#82209

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

Cyril Brulebois <kibi@debian.org> (2024-04-10):
> Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > Does the problem go away if you revert the following commits on top of -19?
> > > 
> > > db6338f45971b4285ea368432a84033690eaf53c
> > > scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
> > > 
> > > 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> > > scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
> > > 
> > > cf33e6ca12d814e1be2263cb76960d0019d7fb94
> > > scsi: core: Add struct for args to execution functions
> 
> Preparing that test right now, thanks Diederik.

This doesn't build, but I didn't try very hard:

    /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c: In function ‘sd_read_block_zero’:
    /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c:3300:9: error: implicit declaration of function ‘scsi_execute_cmd’; did you mean ‘scsi_execute_req’? [-Werror=implicit-function-declaration]

> > Or if that does not find the culprit, would you be able to bisect the
> > upstrema changes beweeen 6.1.76 and 6.1.82?

I think I'll try and pinpoint when that regression came up, then figure
out what to try to get rid of it. Also testing v6.1.84 while I'm at it.

> > > 4b085736e44d ("ata: libata-core: Do not try to set sleeping devices to standby")

Reverting that one got me a successful build but that didn't help.


I'll need to find some more time to switch from throwing a patch into
the packaging repository to bindeb-pkg'ing from the mainline repository,
and to automate testing as much as possible. I'm familiar with the
exercise with Raspberry Pi thingies, but I'd expect some tweaks to be
required in the amd64 case.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82212

From	Salvatore Bonaccorso <carnil@debian.org>
Date	2024-04-10 15:50 +0200
Message-ID	<IrGuR-5lWO-9@gated-at.bofh.it>
In reply to	#82210

Control: tags -1 - moreinfo
Control: tags -1 + confirmed

hi Cyril,

On Wed, Apr 10, 2024 at 03:32:02PM +0200, Cyril Brulebois wrote:
> Cyril Brulebois <kibi@debian.org> (2024-04-10):
> > Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > > Does the problem go away if you revert the following commits on top of -19?
> > > > 
> > > > db6338f45971b4285ea368432a84033690eaf53c
> > > > scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
> > > > 
> > > > 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> > > > scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
> > > > 
> > > > cf33e6ca12d814e1be2263cb76960d0019d7fb94
> > > > scsi: core: Add struct for args to execution functions
> > 
> > Preparing that test right now, thanks Diederik.
> 
> This doesn't build, but I didn't try very hard:
> 
>     /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c: In function ‘sd_read_block_zero’:
>     /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c:3300:9: error: implicit declaration of function ‘scsi_execute_cmd’; did you mean ‘scsi_execute_req’? [-Werror=implicit-function-declaration]
> 
> > > Or if that does not find the culprit, would you be able to bisect the
> > > upstrema changes beweeen 6.1.76 and 6.1.82?
> 
> I think I'll try and pinpoint when that regression came up, then figure
> out what to try to get rid of it. Also testing v6.1.84 while I'm at it.
> 
> > > > 4b085736e44d ("ata: libata-core: Do not try to set sleeping devices to standby")
> 
> Reverting that one got me a successful build but that didn't help.
> 
> 
> I'll need to find some more time to switch from throwing a patch into
> the packaging repository to bindeb-pkg'ing from the mainline repository,
> and to automate testing as much as possible. I'm familiar with the
> exercise with Raspberry Pi thingies, but I'd expect some tweaks to be
> required in the amd64 case.

FWIW, I can reproduce the issue myself as well, so that makes us both
already bit more independent to debug the issue.

Regards,
Salvatore

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

#82213

From	Salvatore Bonaccorso <carnil@debian.org>
Date	2024-04-10 16:00 +0200
Message-ID	<IrGEy-5m01-7@gated-at.bofh.it>
In reply to	#82212

On Wed, Apr 10, 2024 at 03:42:44PM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 - moreinfo
> Control: tags -1 + confirmed
> 
> hi Cyril,
> 
> On Wed, Apr 10, 2024 at 03:32:02PM +0200, Cyril Brulebois wrote:
> > Cyril Brulebois <kibi@debian.org> (2024-04-10):
> > > Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> > > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > > > Does the problem go away if you revert the following commits on top of -19?
> > > > > 
> > > > > db6338f45971b4285ea368432a84033690eaf53c
> > > > > scsi: core: Move scsi_host_busy() out of host lock for waking up EH handler
> > > > > 
> > > > > 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> > > > > scsi: core: Move scsi_host_busy() out of host lock if it is for per-command
> > > > > 
> > > > > cf33e6ca12d814e1be2263cb76960d0019d7fb94
> > > > > scsi: core: Add struct for args to execution functions
> > > 
> > > Preparing that test right now, thanks Diederik.
> > 
> > This doesn't build, but I didn't try very hard:
> > 
> >     /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c: In function ‘sd_read_block_zero’:
> >     /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c:3300:9: error: implicit declaration of function ‘scsi_execute_cmd’; did you mean ‘scsi_execute_req’? [-Werror=implicit-function-declaration]
> > 
> > > > Or if that does not find the culprit, would you be able to bisect the
> > > > upstrema changes beweeen 6.1.76 and 6.1.82?
> > 
> > I think I'll try and pinpoint when that regression came up, then figure
> > out what to try to get rid of it. Also testing v6.1.84 while I'm at it.
> > 
> > > > > 4b085736e44d ("ata: libata-core: Do not try to set sleeping devices to standby")
> > 
> > Reverting that one got me a successful build but that didn't help.
> > 
> > 
> > I'll need to find some more time to switch from throwing a patch into
> > the packaging repository to bindeb-pkg'ing from the mainline repository,
> > and to automate testing as much as possible. I'm familiar with the
> > exercise with Raspberry Pi thingies, but I'd expect some tweaks to be
> > required in the amd64 case.
> 
> FWIW, I can reproduce the issue myself as well, so that makes us both
> already bit more independent to debug the issue.

6.7.9-2 in unstable does not exibit the issue.

Regards,
Salvatore

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

#82214

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 16:10 +0200
Message-ID	<IrGOd-5miB-5@gated-at.bofh.it>
In reply to	#82213

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

Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> 6.7.9-2 in unstable does not exibit the issue.

v6.1.84 with stable's .config & bindeb-pkg still does; next up for me:
confirming good/bad and bisecting.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82216

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 17:30 +0200
Message-ID	<IrI3D-5mWx-1@gated-at.bofh.it>
In reply to	#82214

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

Cyril Brulebois <kibi@debian.org> (2024-04-10):
> v6.1.84 with stable's .config & bindeb-pkg still does; next up for me:
> confirming good/bad and bisecting.

Intermediate results based on upstream stable releases: v6.1.80 is good,
v6.1.81 is bad. Still ~200 commits to bisect.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82217

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 19:10 +0200
Message-ID	<IrJCp-5nZK-1@gated-at.bofh.it>
In reply to	#82216

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

Cyril Brulebois <kibi@debian.org> (2024-04-10):
> Intermediate results based on upstream stable releases: v6.1.80 is good,
> v6.1.81 is bad. Still ~200 commits to bisect.

Final results:

    kibi@genova:~/hack/linux.git ((cf33e6ca12d81...)|BISECTING)$ git bisect bad
    cf33e6ca12d814e1be2263cb76960d0019d7fb94 is the first bad commit
    commit cf33e6ca12d814e1be2263cb76960d0019d7fb94
    Author: Mike Christie <michael.christie@oracle.com>
    Date:   Thu Dec 29 13:01:40 2022 -0600
    
        scsi: core: Add struct for args to execution functions
        
        [ Upstream commit d0949565811f0896c1c7e781ab2ad99d34273fdf ]
        
        Move the SCSI execution functions to use a struct for passing in optional
        args. This commit adds the new struct, temporarily converts scsi_execute()
        and scsi_execute_req() ands a new helper, scsi_execute_cmd(), which takes
        the scsi_exec_args struct.
        
        There should be no change in behavior. We no longer allow users to pass in
        any request->rq_flags value, but they were only passing in RQF_PM which we
        do support by allowing users to pass in the BLK_MQ_REQ flags used by
        blk_mq_alloc_request().
        
        Subsequent commits will convert scsi_execute() and scsi_execute_req() users
        to the new helpers then remove scsi_execute() and scsi_execute_req().
        
        Signed-off-by: Mike Christie <michael.christie@oracle.com>
        Reviewed-by: Bart Van Assche <bvanassche@acm.org>
        Reviewed-by: Christoph Hellwig <hch@lst.de>
        Reviewed-by: John Garry <john.g.garry@oracle.com>
        Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
        Stable-dep-of: 321da3dc1f3c ("scsi: sd: usb_storage: uas: Access media prior to querying device properties")
        Signed-off-by: Sasha Levin <sashal@kernel.org>
    
     drivers/scsi/scsi_lib.c    | 52 ++++++++++++++++++++++------------------------
     include/scsi/scsi_device.h | 51 ++++++++++++++++++++++++++++++++-------------
     2 files changed, 62 insertions(+), 41 deletions(-)


That's one of the 3 commits suggested by Diederik, good hunch.

I know hindsight is always 100% but “There should be no change in
behavior.”… :D

Of course, since there are companion changes afterwards, it cannot be
simply reverted on top of either v6.1.82 (Debian) or v6.1.84 (upstream).


I'd appreciate if someone could carry the ball through the appropriate
channels upstream.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82218

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 19:40 +0200
Message-ID	<IrK5r-5o8X-5@gated-at.bofh.it>
In reply to	#82217

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

Cyril Brulebois <kibi@debian.org> (2024-04-10):
> Of course, since there are companion changes afterwards, it cannot be
> simply reverted on top of either v6.1.82 (Debian) or v6.1.84 (upstream).
> 
> 
> I'd appreciate if someone could carry the ball through the appropriate
> channels upstream.

And of course I only spotted minutes after sending the previous mail
that v6.1.85 got published while I was busy bisecting. It's also
affected by this bug.

For the sake of completeness: except for the initial report, all tests
were performed with the “SATA disk in a VM” setup described in my first
follow-up.


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82219

From	Salvatore Bonaccorso <carnil@debian.org>
Date	2024-04-10 20:50 +0200
Message-ID	<IrLbb-5oLI-3@gated-at.bofh.it>
In reply to	#82217

Control: tags -1 + upstream

Hi,

On Wed, Apr 10, 2024 at 07:00:14PM +0200, Cyril Brulebois wrote:
> Cyril Brulebois <kibi@debian.org> (2024-04-10):
> > Intermediate results based on upstream stable releases: v6.1.80 is good,
> > v6.1.81 is bad. Still ~200 commits to bisect.
> 
> Final results:
> 
>     kibi@genova:~/hack/linux.git ((cf33e6ca12d81...)|BISECTING)$ git bisect bad
>     cf33e6ca12d814e1be2263cb76960d0019d7fb94 is the first bad commit
>     commit cf33e6ca12d814e1be2263cb76960d0019d7fb94
>     Author: Mike Christie <michael.christie@oracle.com>
>     Date:   Thu Dec 29 13:01:40 2022 -0600
>     
>         scsi: core: Add struct for args to execution functions
>         
>         [ Upstream commit d0949565811f0896c1c7e781ab2ad99d34273fdf ]
>         
>         Move the SCSI execution functions to use a struct for passing in optional
>         args. This commit adds the new struct, temporarily converts scsi_execute()
>         and scsi_execute_req() ands a new helper, scsi_execute_cmd(), which takes
>         the scsi_exec_args struct.
>         
>         There should be no change in behavior. We no longer allow users to pass in
>         any request->rq_flags value, but they were only passing in RQF_PM which we
>         do support by allowing users to pass in the BLK_MQ_REQ flags used by
>         blk_mq_alloc_request().
>         
>         Subsequent commits will convert scsi_execute() and scsi_execute_req() users
>         to the new helpers then remove scsi_execute() and scsi_execute_req().
>         
>         Signed-off-by: Mike Christie <michael.christie@oracle.com>
>         Reviewed-by: Bart Van Assche <bvanassche@acm.org>
>         Reviewed-by: Christoph Hellwig <hch@lst.de>
>         Reviewed-by: John Garry <john.g.garry@oracle.com>
>         Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
>         Stable-dep-of: 321da3dc1f3c ("scsi: sd: usb_storage: uas: Access media prior to querying device properties")
>         Signed-off-by: Sasha Levin <sashal@kernel.org>
>     
>      drivers/scsi/scsi_lib.c    | 52 ++++++++++++++++++++++------------------------
>      include/scsi/scsi_device.h | 51 ++++++++++++++++++++++++++++++++-------------
>      2 files changed, 62 insertions(+), 41 deletions(-)
> 
> 
> That's one of the 3 commits suggested by Diederik, good hunch.
> 
> I know hindsight is always 100% but “There should be no change in
> behavior.”… :D
> 
> Of course, since there are companion changes afterwards, it cannot be
> simply reverted on top of either v6.1.82 (Debian) or v6.1.84 (upstream).
> 
> 
> I'd appreciate if someone could carry the ball through the appropriate
> channels upstream.

Great, thanks a lot for your bisecting work!

Yes, if you prefer to not do the forwarding upstream (stable list, CC
to involved people + regression list), then I can try to take care of
it. Obviously the former would be great, as you are the finder and
have done all the work.

Regards,
Salvatore

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

#82222

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-10 21:50 +0200
Message-ID	<IrM7f-5pjW-3@gated-at.bofh.it>
In reply to	#82219

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

Control: forwarded -1 https://lore.kernel.org/stable/20240410193207.qnb75osxuk4ovvm6@mraw.org/

Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> Yes, if you prefer to not do the forwarding upstream (stable list, CC
> to involved people + regression list), then I can try to take care of
> it. Obviously the former would be great, as you are the finder and
> have done all the work.

Thanks for nudging me into walking those extra few meters. Let's see how
that goes…


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82224

From	Cyril Brulebois <kibi@debian.org>
Date	2024-04-11 10:10 +0200
Message-ID	<IrXFn-5wEg-1@gated-at.bofh.it>
In reply to	#82213

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

Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> 6.7.9-2 in unstable does not exibit the issue.

Besides some reverts, the key fix seems to be
321da3dc1f3c92a12e3c5da934090d2992a8814c in master (v6.8-rc6~14^2~5),
which was backported as d97e1c3602240bd35c48ef9aa978e0c47a511d03
(v6.7.7~167), so that seems rather consistent with your findings.

Just got notified that the two reverts + cherry-pick reached the stable
queue for 6.1, so I'd expect this to be fixed upstream by the time
v6.1.86 is released.

  https://lore.kernel.org/linux-scsi/20240411044021.xejk54iznz3cdxem@mraw.org/
  https://lore.kernel.org/linux-scsi/2024041155-croon-dried-f649@gregkh/


Cheers,
-- 
Cyril Brulebois (kibi@debian.org)            <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

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

#82215

From	Diederik de Haas <didi.debian@cknow.org>
Date	2024-04-10 17:00 +0200
Message-ID	<IrHAB-5my4-9@gated-at.bofh.it>
In reply to	#82210

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

On Wednesday, 10 April 2024 15:32:02 CEST Cyril Brulebois wrote:
> Cyril Brulebois <kibi@debian.org> (2024-04-10):
> > Salvatore Bonaccorso <carnil@debian.org> (2024-04-10):
> > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote:
> > > > Does the problem go away if you revert the following commits on top of
> > > > -19?
> > > > 
> > > > db6338f45971b4285ea368432a84033690eaf53c
> > > > scsi: core: Move scsi_host_busy() out of host lock for waking up EH
> > > > handler
> > > > 
> > > > 1ebd75cefaac6fd74729a7d3157f6eaa59960ae2
> > > > scsi: core: Move scsi_host_busy() out of host lock if it is for
> > > > per-command
> > > > 
> > > > cf33e6ca12d814e1be2263cb76960d0019d7fb94
> > > > scsi: core: Add struct for args to execution functions
> > 
> > Preparing that test right now, thanks Diederik.
> 
> This doesn't build, but I didn't try very hard:
> 
>     /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c: In function
> ‘sd_read_block_zero’:
> /home/kibi/debian-kernel/linux.git/drivers/scsi/sd.c:3300:9: error:
> implicit declaration of function ‘scsi_execute_cmd’; did you mean
> ‘scsi_execute_req’? [-Werror=implicit-function-declaration]

Then it got troublesome even earlier then I expected ;-)
If you do `gitk -- drivers/scsi/` on 'master', then you'll see a huge list of 
recent commits ... which probably didn't get backported all ...
A lot of them landed in 6.8.

That Salvatore could confirm the issue should help.

Good luck,
  Diederik

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

#82207 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

From	"Debian Bug Tracking System" <owner@bugs.debian.org>
Date	2024-04-10 12:10 +0200
Subject	Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Message-ID	<IrD3X-5k5z-1@gated-at.bofh.it>
In reply to	#82189

Processing control commands:

> tags -1 + moreinfo
Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Added tag(s) moreinfo.

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

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

#82211 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

From	"Debian Bug Tracking System" <owner@bugs.debian.org>
Date	2024-04-10 15:50 +0200
Subject	Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Message-ID	<IrGuR-5lWO-7@gated-at.bofh.it>
In reply to	#82189

Processing control commands:

> tags -1 - moreinfo
Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Removed tag(s) moreinfo.
> tags -1 + confirmed
Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Added tag(s) confirmed.

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

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

#82220 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

From	"Debian Bug Tracking System" <owner@bugs.debian.org>
Date	2024-04-10 20:50 +0200
Subject	Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Message-ID	<IrLbb-5oLI-1@gated-at.bofh.it>
In reply to	#82189

Processing control commands:

> tags -1 + upstream
Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Added tag(s) upstream.

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

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

#82223 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

From	"Debian Bug Tracking System" <owner@bugs.debian.org>
Date	2024-04-10 21:50 +0200
Subject	Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Message-ID	<IrM7g-5pjW-7@gated-at.bofh.it>
In reply to	#82189

Processing control commands:

> forwarded -1 https://lore.kernel.org/stable/20240410193207.qnb75osxuk4ovvm6@mraw.org/
Bug #1068675 [src:linux] linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)
Set Bug forwarded-to-address to 'https://lore.kernel.org/stable/20240410193207.qnb75osxuk4ovvm6@mraw.org/'.

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

[toc] | [prev] | [standalone]

csiph-web

Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

Contents

#82189 — Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

#82193

#82208

#82209

#82210

#82212

#82213

#82214

#82216

#82217

#82218

#82219

#82222

#82224

#82215

#82207 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

#82211 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

#82220 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

#82223 — Processed: Re: Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)