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

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

Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

Started byLennert Van Alboom <lennert@vanalboom.org>
First post2020-01-16 08:50 +0100
Last post2020-06-25 14:30 +0200
Articles 13 — 4 participants

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

Contents

  Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Lennert Van Alboom <lennert@vanalboom.org> - 2020-01-16 08:50 +0100
    Processed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64:  Poweroff/suspend doesn't work in 5.5.0-rc5 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-04-17 11:30 +0200
    Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Uwe Kleine-König <uwe@kleine-koenig.org> - 2020-04-17 11:30 +0200
      Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Uwe Kleine-König <uwe@kleine-koenig.org> - 2020-04-18 13:30 +0200
        Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Uwe Kleine-König <uwe@kleine-koenig.org> - 2020-04-18 15:30 +0200
          Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Uwe Kleine-König <uwe@kleine-koenig.org> - 2020-04-19 00:50 +0200
            Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Lennert Van Alboom <lennert@vanalboom.org> - 2020-04-19 01:40 +0200
              Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Uwe Kleine-König <uwe@kleine-koenig.org> - 2020-04-19 16:00 +0200
                Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Lennert Van Alboom <lennert@vanalboom.org> - 2020-04-19 17:20 +0200
                  Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Lennert Van Alboom <lennert@vanalboom.org> - 2020-04-21 15:10 +0200
                    Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5 Uwe Kleine-König <uwe@kleine-koenig.org> - 2020-05-11 22:30 +0200
    Processed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64:  Poweroff/suspend doesn't work in 5.5.0-rc5 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-05-11 22:30 +0200
    Bug#949020: linux-image-5.6.0-2-amd64: Lenovo poweroff/suspend failure Bjørn Mork <bjorn@mork.no> - 2020-06-25 14:30 +0200

#66102 — Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

FromLennert Van Alboom <lennert@vanalboom.org>
Date2020-01-16 08:50 +0100
SubjectBug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Message-ID<zp84F-4zh-3@gated-at.bofh.it>
Package: src:linux
Version: 5.5~rc5-1~exp1
Severity: normal

Neither shutdown nor suspend works in this kernel version. Systemd seems
to indicate it is trying at least, but the system hangs either right
before shutdown (clean situation, requiring a poweroff with the power
button) or before sleep (hung system, can't do anything except also hard
powering off and rebooting later).

Syslog from a suspend action:

Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6342] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6345] manager: NetworkManager state is now ASLEEP
Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...





-- Package-specific info:
** Version:
Linux version 5.5.0-rc5-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 20200104 (Debian 9.2.1-22)) #1 SMP Debian 5.5~rc5-1~exp1 (2020-01-06)

** Command line:
BOOT_IMAGE=/vmlinuz-5.5.0-rc5-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet

** Not tainted

** Kernel log:
[   11.240204] usb 3-10: config 1 interface 1 altsetting 0 endpoint 0x3 has wMaxPacketSize 0, skipping
[   11.240207] usb 3-10: config 1 interface 1 altsetting 0 endpoint 0x83 has wMaxPacketSize 0, skipping
[   11.240213] usb 3-10: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02
[   11.240215] usb 3-10: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   11.268290] mc: Linux media interface: v0.10
[   11.269619] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[   11.272214] SCSI subsystem initialized
[   11.275443] usb-storage 4-1:1.0: USB Mass Storage device detected
[   11.275734] scsi host0: usb-storage 4-1:1.0
[   11.275814] videodev: Linux video capture interface: v2.00
[   11.275824] usbcore: registered new interface driver usb-storage
[   11.277009] usbcore: registered new interface driver uas
[   11.285112] uvcvideo: Found UVC 1.00 device Integrated Camera (13d3:56b2)
[   11.303110] uvcvideo 3-1:1.0: Entity type for entity Extension 4 was not initialized!
[   11.303111] uvcvideo 3-1:1.0: Entity type for entity Extension 3 was not initialized!
[   11.303112] uvcvideo 3-1:1.0: Entity type for entity Processing 2 was not initialized!
[   11.303112] uvcvideo 3-1:1.0: Entity type for entity Camera 1 was not initialized!
[   11.303150] input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:14.0/usb3/3-1/3-1:1.0/input/input21
[   11.303195] usbcore: registered new interface driver uvcvideo
[   11.303195] USB Video Class driver (1.1.1)
[   11.309377] Bluetooth: Core ver 2.22
[   11.309386] NET: Registered protocol family 31
[   11.309386] Bluetooth: HCI device and connection manager initialized
[   11.309388] Bluetooth: HCI socket layer initialized
[   11.309390] Bluetooth: L2CAP socket layer initialized
[   11.309391] Bluetooth: SCO socket layer initialized
[   11.313933] usbcore: registered new interface driver btusb
[   11.315171] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017
[   11.316154] Bluetooth: hci0: Device revision is 2
[   11.316169] Bluetooth: hci0: Secure boot is enabled
[   11.316169] Bluetooth: hci0: OTP lock is enabled
[   11.316169] Bluetooth: hci0: API lock is enabled
[   11.316170] Bluetooth: hci0: Debug lock is disabled
[   11.316170] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   11.317265] bluetooth hci0: firmware: direct-loading firmware intel/ibt-19-32-4.sfi
[   11.317267] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi
[   12.307973] scsi 0:0:0:0: Direct-Access     USB      Disk 3.0         0009 PQ: 0 ANSI: 6
[   12.318811] scsi 0:0:0:0: Attached scsi generic sg0 type 0
[   12.321712] sd 0:0:0:0: [sda] 60825600 512-byte logical blocks: (31.1 GB/29.0 GiB)
[   12.322349] sd 0:0:0:0: [sda] Write Protect is off
[   12.322367] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00
[   12.323064] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   12.346647]  sda: sda1
[   12.347847] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   12.400600] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   12.419559] audit: type=1400 audit(1579159022.895:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=734 comm="apparmor_parser"
[   12.420287] audit: type=1400 audit(1579159022.895:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="torbrowser_tor" pid=730 comm="apparmor_parser"
[   12.420374] audit: type=1400 audit(1579159022.895:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=733 comm="apparmor_parser"
[   12.420376] audit: type=1400 audit(1579159022.895:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=733 comm="apparmor_parser"
[   12.420698] audit: type=1400 audit(1579159022.895:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=732 comm="apparmor_parser"
[   12.420700] audit: type=1400 audit(1579159022.895:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=732 comm="apparmor_parser"
[   12.420701] audit: type=1400 audit(1579159022.895:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=732 comm="apparmor_parser"
[   12.421055] audit: type=1400 audit(1579159022.895:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=729 comm="apparmor_parser"
[   12.423923] audit: type=1400 audit(1579159022.899:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=738 comm="apparmor_parser"
[   12.423926] audit: type=1400 audit(1579159022.899:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=739 comm="apparmor_parser"
[   12.533497] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.533498] Bluetooth: BNEP filters: protocol multicast
[   12.533505] Bluetooth: BNEP socket layer initialized
[   12.568076] hid-sensor-hub 001F:8087:0AC2.0003: hid_field_extract() called with n (192) > 32! (kworker/3:0)
[   12.852750] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[   12.908235] Bluetooth: hci0: Waiting for firmware download to complete
[   12.909140] Bluetooth: hci0: Firmware loaded in 1557797 usecs
[   12.909198] Bluetooth: hci0: Waiting for device to boot
[   12.922241] Bluetooth: hci0: Device booted in 12730 usecs
[   12.922807] bluetooth hci0: firmware: direct-loading firmware intel/ibt-19-32-4.ddc
[   12.922809] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-32-4.ddc
[   12.937263] Bluetooth: hci0: Applying Intel DDC parameters completed
[   12.939399] Bluetooth: hci0: Firmware revision 0.0 build 62 week 31 2019
[   12.998622] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[   13.002153] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[   13.027396] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM
[   13.172737] iwlwifi 0000:00:14.3: FW already configured (0) - re-configuring
[   13.176888] iwlwifi 0000:00:14.3: BIOS contains WGDS but no WRDS
[   13.302395] broken atomic modeset userspace detected, disabling atomic
[   13.512040] sof-audio-pci 0000:00:1f.3: error: cl_copy_fw: timeout HDA_DSP_SRAM_REG_ROM_STATUS read
[   13.512593] sof-audio-pci 0000:00:1f.3: error: load fw failed ret: -110
[   13.512626] sof-audio-pci 0000:00:1f.3: error: status = 0x0000002c panic = 0x00000000
[   13.512634] sof-audio-pci 0000:00:1f.3: error: failed to reset DSP
[   13.512637] sof-audio-pci 0000:00:1f.3: error: failed to boot DSP firmware -110
[   13.512639] sof-audio-pci 0000:00:1f.3: error: sof_probe_work failed err: -110
[   14.300578] Bluetooth: RFCOMM TTY layer initialized
[   14.300585] Bluetooth: RFCOMM socket layer initialized
[   14.300588] Bluetooth: RFCOMM ver 1.11
[   14.319424] fuse: init (API version 7.31)
[   17.348855] wlan0: authenticate with e8:65:49:8d:5e:11
[   17.350843] wlan0: send auth to e8:65:49:8d:5e:11 (try 1/3)
[   17.373454] wlan0: authenticated
[   17.374408] wlan0: associate with e8:65:49:8d:5e:11 (try 1/3)
[   17.376484] wlan0: RX AssocResp from e8:65:49:8d:5e:11 (capab=0x431 status=0 aid=4)
[   17.380629] wlan0: associated
[   17.380650] wlan0: Limiting TX power to 1 dBm as advertised by e8:65:49:8d:5e:11
[   17.511409] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   17.590486] Guest personality initialized and is inactive
[   17.590518] VMCI host device registered (name=vmci, major=10, minor=52)
[   17.590518] Initialized host personality
[   17.603850] NET: Registered protocol family 40
[   18.803995] NET: Registered protocol family 38
[   19.564231] input: M720 Triathlon Keyboard as /devices/virtual/misc/uhid/0005:046D:B015.0005/input/input22
[   19.564494] input: M720 Triathlon Mouse as /devices/virtual/misc/uhid/0005:046D:B015.0005/input/input23
[   19.564710] hid-generic 0005:046D:B015.0005: input,hidraw2: BLUETOOTH HID v0.13 Keyboard [M720 Triathlon] on 7C:B2:7D:AF:55:F9

** Model information
sys_vendor: LENOVO
product_name: 81Q9
product_version: Lenovo Yoga C940-14IIL
chassis_vendor: LENOVO
chassis_version: Lenovo Yoga C940-14IIL
bios_vendor: LENOVO
bios_version: AUCN45WW
board_vendor: LENOVO
board_name: LNVNB161216
board_version: SDK0R32862 WIN

** Loaded modules:
uhid
algif_hash
algif_skcipher
af_alg
vmw_vsock_vmci_transport
vsock
vmw_vmci
ctr
ccm
fuse
rfcomm
cmac
cpufreq_powersave
cpufreq_userspace
cpufreq_conservative
bnep
sd_mod
sg
btusb
btrtl
btbcm
btintel
bluetooth
uvcvideo
videobuf2_vmalloc
videobuf2_memops
videobuf2_v4l2
videobuf2_common
uas
usb_storage
videodev
drbg
scsi_mod
mc
ansi_cprng
ecdh_generic
ecc
joydev
hid_sensor_accel_3d
hid_sensor_trigger
hid_sensor_iio_common
industrialio_triggered_buffer
kfifo_buf
industrialio
hid_sensor_custom
hid_sensor_hub
wacom
usbhid
hid_multitouch
hid_generic
intel_ishtp_hid
snd_soc_hdac_hdmi
snd_hda_codec_realtek
x86_pkg_temp_thermal
intel_powerclamp
snd_soc_dmic
coretemp
snd_hda_codec_generic
kvm_intel
kvm
iTCO_wdt
iTCO_vendor_support
snd_sof_pci
irqbypass
watchdog
snd_sof_intel_hda_common
snd_sof_intel_hda
snd_sof_intel_byt
snd_sof_intel_ipc
snd_sof
crct10dif_pclmul
crc32_pclmul
snd_sof_xtensa_dsp
snd_soc_hdac_hda
snd_hda_ext_core
i2c_designware_platform
i2c_designware_core
snd_soc_acpi_intel_match
snd_soc_acpi
snd_soc_core
iwlmvm
snd_compress
efi_pstore
ledtrig_audio
intel_rapl_msr
ghash_clmulni_intel
mac80211
snd_hda_intel
snd_intel_dspcfg
intel_cstate
snd_hda_codec
snd_hda_core
libarc4
intel_uncore
snd_hwdep
snd_pcm
intel_rapl_perf
snd_timer
pcspkr
snd
mei_me
efivars
wmi_bmof
intel_wmi_thunderbolt
i2c_i801
iwlwifi
soundcore
mei
cfg80211
xhci_pci
xhci_hcd
intel_lpss_pci
intel_lpss
idma64
mfd_core
usbcore
processor_thermal_device
intel_ish_ipc
intel_rapl_common
ucsi_acpi
i2c_hid
typec_ucsi
thunderbolt
intel_ishtp
usb_common
intel_soc_dts_iosf
typec
hid
ideapad_laptop
sparse_keymap
rfkill
battery
int3403_thermal
int340x_thermal_zone
tpm_crb
tpm_tis
tpm_tis_core
tpm
rng_core
int3400_thermal
acpi_thermal_rel
acpi_tad
acpi_pad
ac
parport_pc
ppdev
sunrpc
lp
parport
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
i915
crc32c_intel
i2c_algo_bit
nvme
drm_kms_helper
drm
aesni_intel
glue_helper
crypto_simd
nvme_core
cryptd
serio_raw
wmi
evdev
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:8a12] (rev 03)
	Subsystem: Lenovo Device [17aa:3801]
	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: icl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3801]
	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 126
	Region 0: Memory at 601c000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: [virtual] Memory at 4000000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 3000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:8a03] (rev 03)
	Subsystem: Lenovo Device [17aa:3802]
	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 16
	Region 0: Memory at 601d150000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: proc_thermal

00:07.0 PCI bridge [0604]: Intel Corporation Ice Lake Thunderbolt 3 PCI Express Root Port #0 [8086:8a1d] (rev 03) (prog-if 00 [Normal decode])
	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 122
	Bus: primary=00, secondary=01, subordinate=2a, sec-latency=0
	I/O behind bridge: 00004000-00004fff [size=4K]
	Memory behind bridge: 54000000-601fffff [size=194M]
	Prefetchable memory behind bridge: 0000006000000000-000000601bffffff [size=448M]
	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:07.1 PCI bridge [0604]: Intel Corporation Ice Lake Thunderbolt 3 PCI Express Root Port #1 [8086:8a1f] (rev 03) (prog-if 00 [Normal decode])
	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 B routed to IRQ 123
	Bus: primary=00, secondary=2b, subordinate=54, sec-latency=0
	I/O behind bridge: 00005000-00005fff [size=4K]
	Memory behind bridge: 46000000-521fffff [size=194M]
	Prefetchable memory behind bridge: 0000006020000000-000000603bffffff [size=448M]
	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:0d.0 USB controller [0c03]: Intel Corporation Ice Lake Thunderbolt 3 USB Controller [8086:8a13] (rev 03) (prog-if 30 [XHCI])
	Subsystem: Lenovo Ice Lake Thunderbolt 3 USB Controller [17aa:380a]
	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 ? routed to IRQ 151
	Region 0: Memory at 601d140000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd

00:0d.2 System peripheral [0880]: Intel Corporation Ice Lake Thunderbolt 3 NHI #0 [8086:8a17] (rev 03)
	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 16
	Region 0: Memory at 601d100000 (64-bit, non-prefetchable) [size=256K]
	Region 2: Memory at 601d172000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: thunderbolt

00:12.0 Serial controller [0700]: Intel Corporation Device [8086:34fc] (rev 30) (prog-if 00 [8250])
	Subsystem: Lenovo Device [17aa:384d]
	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 16
	Region 0: Memory at 601d16a000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: intel_ish_ipc

00:14.0 USB controller [0c03]: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host Controller [8086:34ed] (rev 30) (prog-if 30 [XHCI])
	Subsystem: Lenovo Ice Lake-LP USB 3.1 xHCI Host Controller [17aa:3844]
	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 152
	Region 0: Memory at 52300000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd

00:14.2 RAM memory [0500]: Intel Corporation Device [8086:34ef] (rev 30)
	Subsystem: Lenovo Device [17aa:3846]
	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
	Region 0: Memory at 601d168000 (64-bit, non-prefetchable) [size=8K]
	Region 2: Memory at 601d171000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>

00:14.3 Network controller [0280]: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) [8086:34f0] (rev 30)
	Subsystem: Intel Corporation Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW) [8086:0074]
	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 16
	Region 0: Memory at 601d164000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi

00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #0 [8086:34e8] (rev 30)
	Subsystem: Lenovo Ice Lake-LP Serial IO I2C Controller [17aa:3840]
	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 16
	Region 0: [virtual] Memory at 4010000000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss

00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #1 [8086:34e9] (rev 30)
	Subsystem: Lenovo Ice Lake-LP Serial IO I2C Controller [17aa:3841]
	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 B routed to IRQ 17
	Region 0: [virtual] Memory at 4010001000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss

00:15.2 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO I2C Controller #2 [8086:34ea] (rev 30)
	Subsystem: Lenovo Ice Lake-LP Serial IO I2C Controller [17aa:3842]
	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 18
	Region 0: [virtual] Memory at 4010002000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: intel-lpss

00:16.0 Communication controller [0780]: Intel Corporation Management Engine Interface [8086:34e0] (rev 30)
	Subsystem: Lenovo Management Engine Interface [17aa:383a]
	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 163
	Region 0: Memory at 601d16d000 (64-bit, non-prefetchable) [size=4K]
	Capabilities: <access denied>
	Kernel driver in use: mei_me

00:1d.0 PCI bridge [0604]: Intel Corporation Ice Lake-LP PCI Express Root Port #9 [8086:34b0] (rev 30) (prog-if 00 [Normal decode])
	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 124
	Bus: primary=00, secondary=55, subordinate=55, sec-latency=0
	I/O behind bridge: None
	Memory behind bridge: 52200000-522fffff [size=1M]
	Prefetchable memory behind bridge: None
	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:1f.0 ISA bridge [0601]: Intel Corporation Ice Lake-LP LPC Controller [8086:3482] (rev 30)
	Subsystem: Lenovo Ice Lake-LP LPC Controller [17aa:380e]
	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

00:1f.3 Multimedia audio controller [0401]: Intel Corporation Smart Sound Technology Audio Controller [8086:34c8] (rev 30)
	Subsystem: Lenovo Smart Sound Technology Audio Controller [17aa:382e]
	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: 32, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 164
	Region 0: Memory at 601d160000 (64-bit, non-prefetchable) [size=16K]
	Region 4: Memory at 601d000000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: sof-audio-pci

00:1f.4 SMBus [0c05]: Intel Corporation Ice Lake-LP SMBus Controller [8086:34a3] (rev 30)
	Subsystem: Lenovo Ice Lake-LP SMBus Controller [17aa:3811]
	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 A routed to IRQ 16
	Region 0: Memory at 601d16c000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at 3040 [size=32]
	Kernel driver in use: i801_smbus

00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI Controller [8086:34a4] (rev 30)
	Subsystem: Lenovo Ice Lake-LP SPI Controller [17aa:3812]
	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
	Region 0: Memory at <ignored> (32-bit, non-prefetchable)

55:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808] (prog-if 02 [NVM Express])
	Subsystem: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a801]
	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 16
	NUMA node: 0
	Region 0: Memory at 52200000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme


** USB devices:
Bus 004 Device 002: ID 1f75:0918 Innostor Technology Corporation Disk 3.0
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 06cb:00be Synaptics, Inc. 
Bus 003 Device 004: ID 8087:0026 Intel Corp. 
Bus 003 Device 002: ID 13d3:56b2 IMC Networks Integrated Camera
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


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

Kernel: Linux 5.5.0-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-5.5.0-rc5-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.135
ii  kmod                                    26+20191223-1
ii  linux-base                              4.6

Versions of packages linux-image-5.5.0-rc5-amd64 recommends:
ii  apparmor             2.13.3-7
ii  firmware-linux-free  3.4

Versions of packages linux-image-5.5.0-rc5-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-efi-amd64          2.04-5
pn  linux-doc-5.5           <none>

Versions of packages linux-image-5.5.0-rc5-amd64 is related to:
ii  firmware-amd-graphics     20190717-2
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>
ii  firmware-iwlwifi          20190717-2
pn  firmware-libertas         <none>
ii  firmware-linux-nonfree    20190717-2
ii  firmware-misc-nonfree     20190717-2
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]

#66791 — Processed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-04-17 11:30 +0200
SubjectProcessed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Message-ID<zWvtU-29R-13@gated-at.bofh.it>
In reply to#66102
Processing control commands:

> found -1 5.5.13-2
Bug #949020 [src:linux] linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Marked as found in versions linux/5.5.13-2.

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

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

#66792

FromUwe Kleine-König <uwe@kleine-koenig.org>
Date2020-04-17 11:30 +0200
Message-ID<zWvtU-29R-11@gated-at.bofh.it>
In reply to#66102

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

Control: found -1 5.5.13-2

On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote:
> Package: src:linux
> Version: 5.5~rc5-1~exp1
> Severity: normal
> 
> Neither shutdown nor suspend works in this kernel version. Systemd seems
> to indicate it is trying at least, but the system hangs either right
> before shutdown (clean situation, requiring a poweroff with the power
> button) or before sleep (hung system, can't do anything except also hard
> powering off and rebooting later).
> 
> Syslog from a suspend action:
> 
> Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6342] manager: sleep: sleep requested (sleeping: no  enabled: yes)
> Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
> Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6345] manager: NetworkManager state is now ASLEEP
> Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
> Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
> Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
> Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...

I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with
4.19 from buster there is no such problem. I didn't debug any further
yet.

Best regards
Uwe

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

#66824

FromUwe Kleine-König <uwe@kleine-koenig.org>
Date2020-04-18 13:30 +0200
Message-ID<zWTPz-dM-3@gated-at.bofh.it>
In reply to#66792

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

Hello again,

On Fri, Apr 17, 2020 at 11:15:28AM +0200, Uwe Kleine-König wrote:
> Control: found -1 5.5.13-2
> 
> On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote:
> > Package: src:linux
> > Version: 5.5~rc5-1~exp1
> > Severity: normal
> > 
> > Neither shutdown nor suspend works in this kernel version. Systemd seems
> > to indicate it is trying at least, but the system hangs either right
> > before shutdown (clean situation, requiring a poweroff with the power
> > button) or before sleep (hung system, can't do anything except also hard
> > powering off and rebooting later).
> > 
> > Syslog from a suspend action:
> > 
> > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6342] manager: sleep: sleep requested (sleeping: no  enabled: yes)
> > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
> > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6345] manager: NetworkManager state is now ASLEEP
> > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
> > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
> > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
> > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...
> 
> I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with
> 4.19 from buster there is no such problem. I didn't debug any further
> yet.

I just reconfirmed: linux-image-4.19.0-8-amd64 4.19.98-1 doesn't suffer
from this problem, but linux-image-5.6.0-trunk-amd64-unsigned
5.6.4-1~exp1 has the same problem.

On thing I noticed: When I send my Laptop in suspend, the power LED
starts blinking slowly (as it does with 4.19), but the FnLk LED stays on
which on 4.19 goes off shortly after suspend is reached. So I think the
problem is in the going to sleep step, not only when (not) waking up.

Best regards
Uwe

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

#66825

FromUwe Kleine-König <uwe@kleine-koenig.org>
Date2020-04-18 15:30 +0200
Message-ID<zWVHH-1ne-1@gated-at.bofh.it>
In reply to#66824

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

hello,

On Sat, Apr 18, 2020 at 01:22:26PM +0200, Uwe Kleine-König wrote:
> On Fri, Apr 17, 2020 at 11:15:28AM +0200, Uwe Kleine-König wrote:
> > Control: found -1 5.5.13-2
> > 
> > On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote:
> > > Package: src:linux
> > > Version: 5.5~rc5-1~exp1
> > > Severity: normal
> > > 
> > > Neither shutdown nor suspend works in this kernel version. Systemd seems
> > > to indicate it is trying at least, but the system hangs either right
> > > before shutdown (clean situation, requiring a poweroff with the power
> > > button) or before sleep (hung system, can't do anything except also hard
> > > powering off and rebooting later).
> > > 
> > > Syslog from a suspend action:
> > > 
> > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6342] manager: sleep: sleep requested (sleeping: no  enabled: yes)
> > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
> > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6345] manager: NetworkManager state is now ASLEEP
> > > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
> > > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
> > > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
> > > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...
> > 
> > I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with
> > 4.19 from buster there is no such problem. I didn't debug any further
> > yet.
> 
> I just reconfirmed: linux-image-4.19.0-8-amd64 4.19.98-1 doesn't suffer
> from this problem, but linux-image-5.6.0-trunk-amd64-unsigned
> 5.6.4-1~exp1 has the same problem.

I started bisecting (but didn't complete yet, the weather is too good to
sit inside :-). Currently I see

	bad: 5.2.17-1+b1
	good: 5.2.6-1

So this is either a regression (also) in stable or something
Debian-specific (or I did something wrong).

Best regards
Uwe

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

#66830

FromUwe Kleine-König <uwe@kleine-koenig.org>
Date2020-04-19 00:50 +0200
Message-ID<zX4rD-6D4-3@gated-at.bofh.it>
In reply to#66825

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

Hello,

On Sat, Apr 18, 2020 at 03:18:35PM +0200, Uwe Kleine-König wrote:
> On Sat, Apr 18, 2020 at 01:22:26PM +0200, Uwe Kleine-König wrote:
> > On Fri, Apr 17, 2020 at 11:15:28AM +0200, Uwe Kleine-König wrote:
> > > Control: found -1 5.5.13-2
> > > 
> > > On Thu, Jan 16, 2020 at 08:39:44AM +0100, Lennert Van Alboom wrote:
> > > > Package: src:linux
> > > > Version: 5.5~rc5-1~exp1
> > > > Severity: normal
> > > > 
> > > > Neither shutdown nor suspend works in this kernel version. Systemd seems
> > > > to indicate it is trying at least, but the system hangs either right
> > > > before shutdown (clean situation, requiring a poweroff with the power
> > > > button) or before sleep (hung system, can't do anything except also hard
> > > > powering off and rebooting later).
> > > > 
> > > > Syslog from a suspend action:
> > > > 
> > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6342] manager: sleep: sleep requested (sleeping: no  enabled: yes)
> > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6343] device (p2p-dev-wlan0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
> > > > Jan 16 06:43:53 Nesbitt NetworkManager[749]: <info>  [1579153433.6345] manager: NetworkManager state is now ASLEEP
> > > > Jan 16 06:43:53 Nesbitt systemd[1]: Reached target Sleep.
> > > > Jan 16 06:43:53 Nesbitt systemd[1]: Starting Suspend...
> > > > Jan 16 06:43:53 Nesbitt kernel: [55203.294410] PM: suspend entry (s2idle)
> > > > Jan 16 06:43:53 Nesbitt systemd-sleep[19110]: Suspending system...
> > > 
> > > I have the same problem with 5.5.13-2 on a Lenovo Thinkpad T460p, with
> > > 4.19 from buster there is no such problem. I didn't debug any further
> > > yet.
> > 
> > I just reconfirmed: linux-image-4.19.0-8-amd64 4.19.98-1 doesn't suffer
> > from this problem, but linux-image-5.6.0-trunk-amd64-unsigned
> > 5.6.4-1~exp1 has the same problem.
> 
> I started bisecting (but didn't complete yet, the weather is too good to
> sit inside :-). Currently I see
> 
> 	bad: 5.2.17-1+b1
> 	good: 5.2.6-1
> 

I checked the remaining versions in between the two above and the bisect
result is that

	5.2.7-1 is the last good; and
	5.2.9-1 is the first bad

kernel image. The relevant change between these two is:

	  * [x86] iommu: Enable INTEL_IOMMU_DEFAULT_ON (Closes: #934309)

. At least 5.2.7-1 shows the problematic behaviour when I add
"intel_iommu=on" on the kernel command line. I suspect I can boot newer
kernels with "intel_iommu=off", but didn't try that yet.

Related:

	https://bugzilla.kernel.org/show_bug.cgi?id=197029

@Lennert: I assume you can still reproduce the problem. Do you care to
test with intel_iommu=off and report about the result? Just to make sure
you and I see the same problems?

Best regards
Uwe

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

#66833

FromLennert Van Alboom <lennert@vanalboom.org>
Date2020-04-19 01:40 +0200
Message-ID<zX5e2-78a-5@gated-at.bofh.it>
In reply to#66830

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

\-------- Original Message --------
On 19 Apr 2020, 00:42, Uwe Kleine-König < uwe@kleine-koenig.org> wrote:
@Lennert: I assume you can still reproduce the problem. Do you care to test with intel\_iommu=off and report about the result? Just to make sure you and I see the same problems? Best regards Uwe

I'm afraid I can't test this anymore - due to serious i915 issues I've been building and running my own kernel packages. Currently running 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh) . I haven't seen the poweroff/suspend problem in a good while.

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

#66837

FromUwe Kleine-König <uwe@kleine-koenig.org>
Date2020-04-19 16:00 +0200
Message-ID<zXiEh-7aS-3@gated-at.bofh.it>
In reply to#66833

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

Hello Lennert,

On Sat, Apr 18, 2020 at 11:29:42PM +0000, Lennert Van Alboom wrote:
> \-------- Original Message --------
> On 19 Apr 2020, 00:42, Uwe Kleine-König < uwe@kleine-koenig.org> wrote:
> > @Lennert: I assume you can still reproduce the problem. Do you care to
> > test with intel_iommu=off and report about the result? Just to make
> > sure you and I see the same problems?
> 
> I'm afraid I can't test this anymore - due to serious i915 issues I've
> been building and running my own kernel packages.  Currently running
> 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh).

So the newer kernels don't fix your problems? In my experience the i915
guys are quite responsive and willing to help if you run a recent
kernel.

> . I haven't seen the poweroff/suspend problem in a good while.

Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
custom kernel? (If only the former: Do you suffer from the reported
problem when you add intel_iommu=on to the kernel command line?)

Best regards
Uwe

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

#66838

FromLennert Van Alboom <lennert@vanalboom.org>
Date2020-04-19 17:20 +0200
Message-ID<zXjTH-85O-3@gated-at.bofh.it>
In reply to#66837

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

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 19 April 2020 15:56, Uwe Kleine-König <uwe@kleine-koenig.org> wrote:

> Hello Lennert,
> 

> On Sat, Apr 18, 2020 at 11:29:42PM +0000, Lennert Van Alboom wrote:
> 

> > \-------- Original Message --------
> > On 19 Apr 2020, 00:42, Uwe Kleine-König < uwe@kleine-koenig.org> wrote:
> > 

> > > @Lennert: I assume you can still reproduce the problem. Do you care to
> > > test with intel_iommu=off and report about the result? Just to make
> > > sure you and I see the same problems?
> > 

> > I'm afraid I can't test this anymore - due to serious i915 issues I've
> > been building and running my own kernel packages. Currently running
> > 5.7.0-rc1 (which is still just as broken as 5.4, 5.5 and 5.6... sigh).
> 

> So the newer kernels don't fix your problems? In my experience the i915
> guys are quite responsive and willing to help if you run a recent
> kernel.

They don't. I've reported a bug for it a good while back:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949021

https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/183
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2352

Awfully quiet there. There seem to be multiple similar bugs around; so far the only response I got upstream was the bug being closed and moved to "mesa" (which I don't really get either). Debian bug didn't get any acknowledgement or comment.


> > . I haven't seen the poweroff/suspend problem in a good while.
> 

> Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
> custom kernel? (If only the former: Do you suffer from the reported
> problem when you add intel_iommu=on to the kernel command line?)

I started with the stock Debian 5.5-rc config, and just did make oldconfig from there on (don't like to stray too far from the official packages). So the option should be identical to the Debian kernels.

$ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config
CONFIG_INTEL_IOMMU=y
CONFIG_INTEL_IOMMU_SVM=y
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y


I don't reboot often, but I'll very likely run into the i915 hang above again soon, so I'll try the intel_iommu=on then.

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

#66854

FromLennert Van Alboom <lennert@vanalboom.org>
Date2020-04-21 15:10 +0200
Message-ID<zY0P0-GT-5@gated-at.bofh.it>
In reply to#66838

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

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, 19 April 2020 17:02, Lennert Van Alboom <lennert@vanalboom.org> wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, 19 April 2020 15:56, Uwe Kleine-König uwe@kleine-koenig.org wrote:
> > Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
> > custom kernel? (If only the former: Do you suffer from the reported
> > problem when you add intel_iommu=on to the kernel command line?)
> 

> I started with the stock Debian 5.5-rc config, and just did make oldconfig from there on (don't like to stray too far from the official packages). So the option should be identical to the Debian kernels.
> 

> $ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config
> CONFIG_INTEL_IOMMU=y
> CONFIG_INTEL_IOMMU_SVM=y
> 

> CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> 

> =========================================
> 

> CONFIG_INTEL_IOMMU_FLOPPY_WA=y
> CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y
> 

> I don't reboot often, but I'll very likely run into the i915 hang above again soon, so I'll try the intel_iommu=on then.


Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without issues.

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

#67063

FromUwe Kleine-König <uwe@kleine-koenig.org>
Date2020-05-11 22:30 +0200
Message-ID<A5ndM-8mh-17@gated-at.bofh.it>
In reply to#66854

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

Control: forwarded -1 https://lore.kernel.org/r/20200506144558.GA4019@taurus.defre.kleine-koenig.org

Hello,

On Tue, Apr 21, 2020 at 12:59:15PM +0000, Lennert Van Alboom wrote:
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Sunday, 19 April 2020 17:02, Lennert Van Alboom <lennert@vanalboom.org> wrote:
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > On Sunday, 19 April 2020 15:56, Uwe Kleine-König uwe@kleine-koenig.org wrote:
> > > Do you have INTEL_IOMMU and INTEL_IOMMU_DEFAULT_ON included in your
> > > custom kernel? (If only the former: Do you suffer from the reported
> > > problem when you add intel_iommu=on to the kernel command line?)
> > 
> 
> > I started with the stock Debian 5.5-rc config, and just did make oldconfig from there on (don't like to stray too far from the official packages). So the option should be identical to the Debian kernels.
> > 
> 
> > $ grep INTEL_IOMMU Build/kernel/linux-5.7-rc1/.config
> > CONFIG_INTEL_IOMMU=y
> > CONFIG_INTEL_IOMMU_SVM=y
> > 
> 
> > CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
> > 
> 
> > =========================================
> > 
> 
> > CONFIG_INTEL_IOMMU_FLOPPY_WA=y
> > CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON=y
> > 
> 
> > I don't reboot often, but I'll very likely run into the i915 hang above again soon, so I'll try the intel_iommu=on then.
> 
> 
> Verified: my 5.7.0-rc1 system with intel_iommu=on can suspend/resume without issues.

I brought this problem to the attention of the x86 guys; see above URL
for the conversation.

Up to now no breaking insights.

@Lennert: Did you change your BIOS settings since the problem occured to
you? Lenny Szubowicz hinted it might be related to the TPM chip and
indeed switching it in the BIOS settings from 2.0 to 1.2 mode makes the
problem go away for me.

Best regards
Uwe

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

#67064 — Processed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-05-11 22:30 +0200
SubjectProcessed: Re: Bug#949020: linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Message-ID<A5ndN-8mh-27@gated-at.bofh.it>
In reply to#66102
Processing control commands:

> forwarded -1 https://lore.kernel.org/r/20200506144558.GA4019@taurus.defre.kleine-koenig.org
Bug #949020 [src:linux] linux-image-5.5.0-rc5-amd64: Poweroff/suspend doesn't work in 5.5.0-rc5
Set Bug forwarded-to-address to 'https://lore.kernel.org/r/20200506144558.GA4019@taurus.defre.kleine-koenig.org'.

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

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

#67387 — Bug#949020: linux-image-5.6.0-2-amd64: Lenovo poweroff/suspend failure

FromBjørn Mork <bjorn@mork.no>
Date2020-06-25 14:30 +0200
SubjectBug#949020: linux-image-5.6.0-2-amd64: Lenovo poweroff/suspend failure
Message-ID<AlzaV-ra-3@gated-at.bofh.it>
In reply to#66102
Package: src:linux
Followup-For: Bug #949020

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Just confirming that this issue is still present, causing a terrible
user experience when upgrading from Buster to Bullseye on a Lenovo
laptop. Verified on a 4th Gen Thinkpad X1 Carbon.

Setting intel_iommu=off is confirmed as workaround.

I understand from the upstream discussion that this is mostly a
Lenovo firmware issue.  But I still believe something needs to be
done in Debian to avoid every Lenovo user having to discover this
bug report and implement the workaround manually.  After first
experiencing a complete system failure when trying to suspend 
the system.  A feature which worked without a flaw on Debian
Buster.


- -- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (700, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-----BEGIN PGP SIGNATURE-----

iIQEARYKACwWIQRoe+CASfFh7aZ6shIiBE7Lv6RhXQUCXvSVXQ4cYmpvcm5AbW9y
ay5ubwAKCRAiBE7Lv6RhXd/GAQCIsozUqKlBr9BkIXoOXp7lFk9WouEh0QSYMm1F
oqluMwEA34mOpMqJL7bZWRAydIEctD1rWSAg7r1kpPAel1IwxAc=
=hTTU
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

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

csiph-web