Computer is frozen after suspend

Bug #1867983 reported by Glandos
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Critical
Unassigned
Bionic
Fix Released
Undecided
Unassigned
Eoan
Fix Committed
Undecided
Unassigned
Focal
Fix Released
Undecided
Unassigned

Bug Description

=== SRU Justification ===
[Impact]
Some systems with ATA drives freeze during suspend

[Fix]
Avoid circular sync dependency by using async cookie.

[Test]
User reports positive feedback.

[Regression Potential]
Low. This patch makes synchronize more targeted, prevents many potential
freeze.

=== Original Bug Report ===
I am using an old HP EliteBook 6930p with current Ubuntu.

When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping.

It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42.

I am holding kernel purge for now, but this is annoying.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-29-generic 5.3.0-29.31
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: isabelle 1010 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 18 20:46:35 2020
HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c
InstallationDate: Installed on 2015-03-15 (1830 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP EliteBook 6930p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-29-generic N/A
 linux-backports-modules-5.3.0-29-generic N/A
 linux-firmware 1.183.4
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago)
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCU Ver. F.12
dmi.board.name: 30DB
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.27
dmi.chassis.asset.tag: CZC939161W
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 6930p
dmi.product.sku: J1610781
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Glandos (glandos) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Glandos (glandos) wrote : Re: Computer is freezed after suspend

It is still happening with 5.3.0-45

Revision history for this message
Glandos (glandos) wrote :

I had time to bisect kernel:

# bad: [af7acadc09d232b50ef83011d9c6368c925ef32f] UBUNTU: Ubuntu-5.3.0-40.32
# good: [1ecdc2a4b15cf2032094966a30bc79992968beb2] UBUNTU: Ubuntu-5.3.0-29.31
git bisect start 'Ubuntu-5.3.0-40.32' 'Ubuntu-5.3.0-29.31'
# good: [ec8e731b6b8941cd561eb4cd5f987dbf0268edcb] md/raid0: avoid RAID0 data corruption due to layout confusion.
git bisect good ec8e731b6b8941cd561eb4cd5f987dbf0268edcb
# bad: [fb787b4169ee66faf0a78488476e0398f5e283a1] spi: gpio: prevent memory leak in spi_gpio_probe
git bisect bad fb787b4169ee66faf0a78488476e0398f5e283a1
# good: [b9a9d432b09d1100c8fe3982b4a53b9307f03466] x86/mce: Lower throttling MCE messages' priority to warning
git bisect good b9a9d432b09d1100c8fe3982b4a53b9307f03466
# bad: [b268b5877901fa69f4a34e94643108c0bb9112e0] tun: fix data-race in gro_normal_list()
git bisect bad b268b5877901fa69f4a34e94643108c0bb9112e0
# bad: [67e07f18209160bbabaf112cfefa4454d299949b] perf jevents: Fix resource leak in process_mapfile() and main()
git bisect bad 67e07f18209160bbabaf112cfefa4454d299949b
# good: [b5c04c65cafa25745356b85ace1c3b80b8ac5d58] s390/mm: add mm_pxd_folded() checks to pxd_free()
git bisect good b5c04c65cafa25745356b85ace1c3b80b8ac5d58
# bad: [99226e3d1768352047769426058c6fb922d05c89] media: rcar_drif: fix a memory disclosure
git bisect bad 99226e3d1768352047769426058c6fb922d05c89
# bad: [03edfe2eecb66a0b664f344df9478b0179733ba5] iio: dln2-adc: fix iio_triggered_buffer_postenable() position
git bisect bad 03edfe2eecb66a0b664f344df9478b0179733ba5
# bad: [2535c05ffda6d344eb4917178a8ecdf7835e87c2] libata: Ensure ata_port probe has completed before detach
git bisect bad 2535c05ffda6d344eb4917178a8ecdf7835e87c2
# good: [be64fadc7c51317046112a4b4c9895575343ced3] net: hns3: add struct netdev_queue debug info for TX timeout
git bisect good be64fadc7c51317046112a4b4c9895575343ced3
# first bad commit: [2535c05ffda6d344eb4917178a8ecdf7835e87c2] libata: Ensure ata_port probe has completed before detach

It seems that the first bad commit just force ata synchronization. I have no idea how I can test this more for now, but I am available for testing.

Glandos (glandos)
summary: - Computer is freezed after suspend
+ Computer is frozen after suspend
Revision history for this message
Glandos (glandos) wrote :

For the fun, I compiled Ubuntu-5.3.0-48.41 with 2535c05ffda6d344eb4917178a8ecdf7835e87c2 reverted, since it's a small change.

It works. So reverting this change on newer kernels will make me happy :)

Revision history for this message
Clemens Walter (w4lt3r) wrote :

it seams to be fixed in 20.04 with kernel 5.4.0.28.33+ or even 5.6.7. HP Elitebook x360 1040 g6.

Revision history for this message
Glandos (glandos) wrote :

I upgraded my notebook to 20.04 with the current available kernel in the repository.
The issue is not fixed, the computer is still frozen after wake up. I'm still building my kernel by reverting the mentioned commit.

By the way, in the focal repository, the faulty commit is now 08658bdff8725

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please test this patch

tags: added: patch
Revision history for this message
Glandos (glandos) wrote :

The patch works for me. Many thanks!

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please test patch v2, thanks!

Revision history for this message
Glandos (glandos) wrote :

I applied your last patch against 5.4.0-33.36 (git tag) and it still works.

Thanks for taking care of inclusion into mainline.

Revision history for this message
Glandos (glandos) wrote :

Is there anything to add?

I saw also no answer from you on the LKML, do you want me to answer that the patch is working for me? I'm not used to LKML, but I think I can try :)

description: updated
Changed in linux (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu Bionic):
status: New → Confirmed
Changed in linux (Ubuntu Eoan):
status: New → Confirmed
Changed in linux (Ubuntu Focal):
status: New → Confirmed
Changed in linux (Ubuntu Eoan):
status: Confirmed → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-xenial
Revision history for this message
bAlvarado (glaze182) wrote :

I am unable to try the updates at deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe. They are rejected with this:

The repository 'http://archive.ubuntu.com/ubuntu $(lsb_release Release' does not have a Release file.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.The repository 'http://ports.ubuntu.com/ubuntu-ports $(lsb_release Release' does not have a Release file.

I tried the latest 5.4.0-42 and still have issue. I am not a Linux wiz and cannot resolve the above error in the repository, but the bug still exists. It should not be closed.

Revision history for this message
bAlvarado (glaze182) wrote :

For the previous post I am the author of Bug #1887202, which is considered a duplicate.

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-bionic
Revision history for this message
Glandos (glandos) wrote :

@glaze182 you seems to have enter information incorrectly.
It should looks like:

deb http://archive.ubuntu.com/ubuntu/ focal-proposed restricted main multiverse universe

The $(lsb_release -cs) is a shell substitution so you should execute it like 'echo "deb http://archive.ubuntu.com/ubuntu/ $(lsb_release -cs)-proposed restricted main multiverse universe"'.

I have a question… It seems the fix have been committed in eoan, but not in focal, is it right?

By the way, I don't have any bionic nor xenial to test, and I didn't even know how to add the required tags…

Changed in linux (Ubuntu Bionic):
status: Confirmed → Fix Committed
Changed in linux (Ubuntu Focal):
status: Confirmed → Fix Committed
Revision history for this message
Glandos (glandos) wrote :

Many thanks!

Revision history for this message
Khaled El Mously (kmously) wrote :

@Glandos you are right, the fix was not committed to Focal. However, it has since been committed by Kelsey on Aug 3, and the Focal kernel with this fix should release on Aug 31. Thank you!

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-focal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (9.9 KiB)

This bug was fixed in the package linux - 4.4.0-187.217

---------------
linux (4.4.0-187.217) xenial; urgency=medium

  * xenial/linux: 4.4.0-187.217 -proposed tracker (LP: #1888274)

  * Regression in kernel 4.15.0-91 causes kernel panic with Bcache
    (LP: #1867916)
    - bcache: check and adjust logical block size for backing devices

  * Xenial update: v4.4.230 upstream stable release (LP: #1887011)
    - btrfs: cow_file_range() num_bytes and disk_num_bytes are same
    - btrfs: fix data block group relocation failure due to concurrent scrub
    - mm: fix swap cache node allocation mask
    - EDAC/amd64: Read back the scrub rate PCI register on F15h
    - mm/slub: fix stack overruns with SLUB_STATS
    - usb: usbtest: fix missing kfree(dev->buf) in usbtest_disconnect
    - kgdb: Avoid suspicious RCU usage warning
    - crypto: af_alg - fix use-after-free in af_alg_accept() due to bh_lock_sock()
    - sched/rt: Show the 'sched_rr_timeslice' SCHED_RR timeslice tuning knob in
      milliseconds
    - hwmon: (max6697) Make sure the OVERT mask is set correctly
    - hwmon: (acpi_power_meter) Fix potential memory leak in
      acpi_power_meter_add()
    - virtio-blk: free vblk-vqs in error path of virtblk_probe()
    - i2c: algo-pca: Add 0x78 as SCL stuck low status for PCA9665
    - Revert "ALSA: usb-audio: Improve frames size computation"
    - SMB3: Honor 'seal' flag for multiuser mounts
    - SMB3: Honor persistent/resilient handle flags for multiuser mounts
    - cifs: Fix the target file was deleted when rename failed.
    - MIPS: Add missing EHB in mtc0 -> mfc0 sequence for DSPen
    - netfilter: nf_conntrack_h323: lost .data_len definition for Q.931/ipv6
    - Linux 4.4.230

  * Xenial update: v4.4.229 upstream stable release (LP: #1885932)
    - s390: fix syscall_get_error for compat processes
    - clk: sunxi: Fix incorrect usage of round_down()
    - i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets
    - clk: qcom: msm8916: Fix the address location of pll->config_reg
    - ALSA: isa/wavefront: prevent out of bounds write in ioctl
    - scsi: qla2xxx: Fix issue with adapter's stopping state
    - i2c: pxa: clear all master action bits in i2c_pxa_stop_message()
    - usblp: poison URBs upon disconnect
    - ps3disk: use the default segment boundary
    - vfio/pci: fix memory leaks in alloc_perm_bits()
    - mfd: wm8994: Fix driver operation if loaded as modules
    - scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event
    - nfsd: Fix svc_xprt refcnt leak when setup callback client failed
    - powerpc/crashkernel: Take "mem=" option into account
    - yam: fix possible memory leak in yam_init_driver
    - mksysmap: Fix the mismatch of '.L' symbols in System.map
    - scsi: sr: Fix sr_probe() missing deallocate of device minor
    - scsi: ibmvscsi: Don't send host info in adapter info MAD after LPM
    - ALSA: usb-audio: Improve frames size computation
    - s390/qdio: put thinint indicator after early error
    - tty: hvc: Fix data abort due to race in hvc_open
    - staging: sm750fb: add missing case while setting FB_VISUAL
    - i2c: pxa: fix i2c_pxa_scream_blue_murder() debug output
    - serial: ...

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Stefan Bader (smb) wrote :

@Glandos, the fix is now in a proposed kernel for Focal and should be verified.

Revision history for this message
Stefan Bader (smb) wrote :

The asking for Xenial happened because the kernel fix came back via upstream stable and had the reference to this bug intact. Xenial was already released but included previous changes in the changelog to care for the case of that release not being done.

tags: removed: verification-needed-xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (97.9 KiB)

This bug was fixed in the package linux - 5.4.0-45.49

---------------
linux (5.4.0-45.49) focal; urgency=medium

  * focal/linux: 5.4.0-45.49 -proposed tracker (LP: #1893050)

  * [Potential Regression] dscr_inherit_exec_test from powerpc in
    ubuntu_kernel_selftests failed on B/E/F (LP: #1888332)
    - powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()

linux (5.4.0-44.48) focal; urgency=medium

  * focal/linux: 5.4.0-44.48 -proposed tracker (LP: #1891049)

  * Packaging resync (LP: #1786013)
    - [Packaging] update helper scripts

  * ipsec: policy priority management is broken (LP: #1890796)
    - xfrm: policy: match with both mark and mask on user interfaces

linux (5.4.0-43.47) focal; urgency=medium

  * focal/linux: 5.4.0-43.47 -proposed tracker (LP: #1890746)

  * Packaging resync (LP: #1786013)
    - update dkms package versions

  * Devlink - add RoCE disable kernel support (LP: #1877270)
    - devlink: Add new "enable_roce" generic device param
    - net/mlx5: Document flow_steering_mode devlink param
    - net/mlx5: Handle "enable_roce" devlink param
    - IB/mlx5: Rename profile and init methods
    - IB/mlx5: Load profile according to RoCE enablement state
    - net/mlx5: Remove unneeded variable in mlx5_unload_one
    - net/mlx5: Add devlink reload
    - IB/mlx5: Do reverse sequence during device removal

  * msg_zerocopy.sh in net from ubuntu_kernel_selftests failed (LP: #1812620)
    - selftests/net: relax cpu affinity requirement in msg_zerocopy test

  * Enlarge hisi_sec2 capability (LP: #1890222)
    - Revert "UBUNTU: [Config] Disable hisi_sec2 temporarily"
    - crypto: hisilicon - update SEC driver module parameter

  * Fix missing HDMI/DP Audio on an HP Desktop (LP: #1890441)
    - ALSA: hda/hdmi: Add quirk to force connectivity

  * Fix IOMMU error on AMD Radeon Pro W5700 (LP: #1890306)
    - PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken

  * ASoC:amd:renoir: the dmic can't record sound after suspend and resume
    (LP: #1890220)
    - SAUCE: ASoC: amd: renoir: restore two more registers during resume

  * No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7 CPU
    (LP: #1877757)
    - ASoC: SOF: Intel: hda: fix generic hda codec support

  * Fix right speaker of HP laptop (LP: #1889375)
    - SAUCE: hda/realtek: Fix right speaker of HP laptop

  * blk_update_request error when mount nvme partition (LP: #1872383)
    - SAUCE: nvme-pci: prevent SK hynix PC400 from using Write Zeroes command

  * soc/amd/renoir: detect dmic from acpi table (LP: #1887734)
    - ASoC: amd: add logic to check dmic hardware runtime
    - ASoC: amd: add ACPI dependency check
    - ASoC: amd: fixed kernel warnings

  * soc/amd/renoir: change the module name to make it work with ucm3
    (LP: #1888166)
    - AsoC: amd: add missing snd- module prefix to the acp3x-rn driver kernel
      module
    - SAUCE: remove a kernel module since its name is changed

  * Focal update: v5.4.55 upstream stable release (LP: #1890343)
    - AX.25: Fix out-of-bounds read in ax25_connect()
    - AX.25: Prevent out-of-bounds read in ax25_sendmsg()
    - dev: Defer free of skbs in flush_backlog
    - drivers/net/wan/x25_asy: Fix to make i...

Changed in linux (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (55.0 KiB)

This bug was fixed in the package linux - 4.15.0-115.116

---------------
linux (4.15.0-115.116) bionic; urgency=medium

  * bionic/linux: 4.15.0-115.116 -proposed tracker (LP: #1893055)

  * [Potential Regression] dscr_inherit_exec_test from powerpc in
    ubuntu_kernel_selftests failed on B/E/F (LP: #1888332)
    - powerpc/64s: Don't init FSCR_DSCR in __init_FSCR()

linux (4.15.0-114.115) bionic; urgency=medium

  * bionic/linux: 4.15.0-114.115 -proposed tracker (LP: #1891052)

  * ipsec: policy priority management is broken (LP: #1890796)
    - xfrm: policy: match with both mark and mask on user interfaces

linux (4.15.0-113.114) bionic; urgency=medium

  * bionic/linux: 4.15.0-113.114 -proposed tracker (LP: #1890705)

  * Packaging resync (LP: #1786013)
    - update dkms package versions

  * Reapply "usb: handle warm-reset port requests on hub resume" (LP: #1859873)
    - usb: handle warm-reset port requests on hub resume

  * Bionic update: upstream stable patchset 2020-07-29 (LP: #1889474)
    - gpio: arizona: handle pm_runtime_get_sync failure case
    - gpio: arizona: put pm_runtime in case of failure
    - pinctrl: amd: fix npins for uart0 in kerncz_groups
    - mac80211: allow rx of mesh eapol frames with default rx key
    - scsi: scsi_transport_spi: Fix function pointer check
    - xtensa: fix __sync_fetch_and_{and,or}_4 declarations
    - xtensa: update *pos in cpuinfo_op.next
    - drivers/net/wan/lapbether: Fixed the value of hard_header_len
    - net: sky2: initialize return of gm_phy_read
    - drm/nouveau/i2c/g94-: increase NV_PMGR_DP_AUXCTL_TRANSACTREQ timeout
    - irqdomain/treewide: Keep firmware node unconditionally allocated
    - SUNRPC reverting d03727b248d0 ("NFSv4 fix CLOSE not waiting for direct IO
      compeletion")
    - spi: spi-fsl-dspi: Exit the ISR with IRQ_NONE when it's not ours
    - IB/umem: fix reference count leak in ib_umem_odp_get()
    - uprobes: Change handle_swbp() to send SIGTRAP with si_code=SI_KERNEL, to fix
      GDB regression
    - ALSA: info: Drop WARN_ON() from buffer NULL sanity check
    - ASoC: rt5670: Correct RT5670_LDO_SEL_MASK
    - btrfs: fix double free on ulist after backref resolution failure
    - btrfs: fix mount failure caused by race with umount
    - btrfs: fix page leaks after failure to lock page for delalloc
    - bnxt_en: Fix race when modifying pause settings.
    - hippi: Fix a size used in a 'pci_free_consistent()' in an error handling
      path
    - ax88172a: fix ax88172a_unbind() failures
    - net: dp83640: fix SIOCSHWTSTAMP to update the struct with actual
      configuration
    - drm: sun4i: hdmi: Fix inverted HPD result
    - net: smc91x: Fix possible memory leak in smc_drv_probe()
    - bonding: check error value of register_netdevice() immediately
    - mlxsw: destroy workqueue when trap_register in mlxsw_emad_init
    - ipvs: fix the connection sync failed in some cases
    - i2c: rcar: always clear ICSAR to avoid side effects
    - bonding: check return value of register_netdevice() in bond_newlink()
    - serial: exar: Fix GPIO configuration for Sealevel cards based on XR17V35X
    - scripts/decode_stacktrace: strip basepath from all paths
    - HID: i...

Changed in linux (Ubuntu Bionic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.