Bug#1065112: Acknowledgement (linux-image-6.1.0-18-amd64: System unresponsive after resume from suspend when WoWLAN enabled in iwlwifi)

2024-03-03 Thread David Balch
Some more data...

Testing various kernels from https://snapshot.debian.org/binary/?cat=l , I
have found that:

• linux-image-6.0.0-0.deb11.2-amd64 - has an error, but stays responsive
(log except below, full dmesg at http://paste.debian.net/1309322/).
• linux-image-6.0.0-1-amd64 - has an error, and is unresponsive except for
(some) sysrq keys (stack trace photo at https://imgur.com/a/1R6gYLh ).

Although there is some sort of error/crash in both kernels, only
linux-image-6.0.0-1-amd64 becomes unusable, so that's probably more urgent.

Log excerpt for linux-image-6.0.0-0.deb11.2-amd6 ...

[9.755992] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[   10.556787] wlp3s0: Limiting TX power to 20 (20 - 0) dBm as advertised
by 4c:22:f3:aa:0a:c3
[  127.171444] PM: suspend entry (deep)
[  127.180424] Filesystems sync: 0.008 seconds
[  127.205820] (NULL device *): firmware: direct-loading firmware
regulatory.db
[  127.205857] (NULL device *): firmware: direct-loading firmware
regulatory.db.p7s
[  127.206064] (NULL device *): firmware: direct-loading firmware
iwlwifi-7265D-29.ucode
[  127.206147] (NULL device *): firmware: direct-loading firmware
i915/skl_dmc_ver1_27.bin
[  127.206217] Freezing user space processes ... (elapsed 0.001 seconds)
done.
[  127.207668] OOM killer disabled.
[  127.207677] Freezing remaining freezable tasks ... (elapsed 0.001
seconds) done.
[  127.210388] serial 00:01: disabled
[  127.210518] e1000e: EEE TX LPI TIMER: 0011
[  127.232775] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  127.232926] sd 0:0:0:0: [sda] Stopping disk
[  127.236750] iwlwifi :03:00.0: Applying debug destination
EXTERNAL_DRAM
[  127.696949] ACPI: PM: Preparing to enter system sleep state S3
[  127.698270] ACPI: PM: Saving platform NVS memory
[  127.698427] Disabling non-boot CPUs ...
[  127.700468] smpboot: CPU 1 is now offline
[  127.703320] smpboot: CPU 2 is now offline
[  127.705876] smpboot: CPU 3 is now offline
[  127.708599] ACPI: PM: Low-level resume complete
[  127.708642] ACPI: PM: Restoring platform NVS memory
[  127.709314] Enabling non-boot CPUs ...
[  127.709350] x86: Booting SMP configuration:
[  127.709352] smpboot: Booting Node 0 Processor 1 APIC 0x2
[  127.710109] CPU1 is up
[  127.710136] smpboot: Booting Node 0 Processor 2 APIC 0x4
[  127.710779] CPU2 is up
[  127.710813] smpboot: Booting Node 0 Processor 3 APIC 0x6
[  127.711515] CPU3 is up
[  127.712376] ACPI: PM: Waking up from system sleep state S3
[  127.720256] pcieport :00:1b.0: Intel SPT PCH root port ACS
workaround enabled
[  127.720642] pcieport :00:1d.0: Intel SPT PCH root port ACS
workaround enabled
[  127.724156] i915 :00:02.0: [drm] [ENCODER:94:DDI B/PHY B] is
disabled/in DSI mode with an ungated DDI clock, gate it
[  127.724168] i915 :00:02.0: [drm] [ENCODER:103:DDI C/PHY C] is
disabled/in DSI mode with an ungated DDI clock, gate it
[  127.724172] i915 :00:02.0: [drm] [ENCODER:114:DDI D/PHY D] is
disabled/in DSI mode with an ungated DDI clock, gate it
[  127.724175] i915 :00:02.0: [drm] [ENCODER:124:DDI E/PHY E] is
disabled/in DSI mode with an ungated DDI clock, gate it
[  127.724389] ACPI BIOS Error (bug): AE_AML_BUFFER_LIMIT, Field [DRQL] at
bit offset/length 136/8 exceeds size of target Buffer (128 bits)
(20220331/dsopcode-198)
[  127.724397] ACPI Error: Aborting method \_SB.PCI0.LPCB.SIO1.DSRS due to
previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
[  127.724403] ACPI Error: Aborting method \_SB.PCI0.LPCB.UAR1._SRS due to
previous error (AE_AML_BUFFER_LIMIT) (20220331/psparse-529)
[  127.724409] serial 00:01: activation failed
[  127.724411] serial 00:01: PM: dpm_run_callback():
pnp_bus_resume+0x0/0xa0 returns -5
[  127.724417] serial 00:01: PM: failed to resume: error -5
[  127.733272] sd 0:0:0:0: [sda] Starting disk
[  127.743867] [ cut here ]
[  127.743869] Timeout waiting for hardware access (CSR_GP_CNTRL 0x080403d8)
[  127.743883] WARNING: CPU: 2 PID: 1113 at
drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2128
__iwl_trans_pcie_grab_nic_access+0x1ef/0x220 [iwlwifi]
[  127.743899] Modules linked in: snd_seq_dummy snd_hrtimer snd_seq
snd_seq_device ctr ccm qrtr snd_hda_codec_hdmi binfmt_misc intel_rapl_msr
intel_rapl_common nls_ascii nls_cp437 vfat fat x86_pkg_temp_thermal
intel_powerclamp coretemp kvm_intel snd_ctl_led kvm iwlmvm irqbypass
snd_hda_codec_realtek ghash_clmulni_intel mac80211 snd_hda_codec_generic
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi libarc4 aesni_intel
crypto_simd snd_hda_codec cryptd mei_hdcp mei_wdt snd_hda_core iwlwifi
snd_hwdep rapl snd_pcm intel_cstate dell_wmi sparse_keymap ledtrig_audio
intel_uncore snd_timer iTCO_wdt dell_smbios dcdbas intel_pmc_bxt cfg80211
wmi_bmof dell_wmi_descriptor pcspkr snd mei_me iTCO_vendor_support watchdog
ee1004 rfkill soundcore mei intel_pch_thermal intel_pmc_core acpi_pad evdev
sg msr parport_pc ppdev lp parport fuse efi_pstore loop dm_mod configfs
efivarfs ip_tables x_tables 

Bug#1065112: Acknowledgement (linux-image-6.1.0-18-amd64: System unresponsive after resume from suspend when WoWLAN enabled in iwlwifi)

2024-02-29 Thread David Balch
Clarification:

The above step: "3. After suspend, press a key" is to wake the system up.
(I had tried magic packet and it didn't work, so pressed a key to wake and
got a lit screen but no interactivity.)

With WoWLAN disabled, pressing a key would successfully wake.
With WoWLAN enabled, WoWLAN didn't work, and pressing a key would wake it
enough to light the display - but not respond except to sysrq.

On Thu, 29 Feb 2024 at 21:18, Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1065112:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065112.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   da...@balch.co.uk
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
>
> If you wish to submit further information on this problem, please
> send it to 1065...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1065112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065112
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>