[Dell Vostro 5490] proposed linux-oem-osp1 suspend resume fails

Bug #1860642 reported by Taihsiang Ho
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-oem-osp1 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hardware: Dell Vostro 5490 (CID 201906-27089)
Image: Pre-loaded OEM image
Kernel: 5.0.0-1036-oem-osp1

Reproducing rate: 5 out of 5

[Steps to Reproduce]
1. Boot into the desktop
2. Suspend over the suspend applet GUI

[Expected Result]
Press power button will wake up the machine

[Actual Result]
Black screen. The ethernet connection is always not available.

[More Information]
- 5.0.0-1034-oem-osp1 could also reproduce this issue
- 5.0.0-1033-oem-osp1 could NOT reproduce this issue.

- Another Dell Vostro 5490 (201906-27090) could reproduce this issue

Monitor /var/log/syslog on suspending with 5.0.0-1036-oem-osp1

Jan 23 17:13:04 201806-27089 systemd[1]: Startup finished in 5.827s (firmware) + 3.590s (loader) + 3.801s (kernel) + 22.428s (userspace) = 35.647s.
Jan 23 17:13:05 201806-27089 ntpdate[2056]: adjust time server 91.189.91.157 offset 0.430561 sec
Jan 23 17:13:11 201806-27089 boltd[1656]: power: setting force_power to OFF
Jan 23 17:13:14 201806-27089 systemd-timesyncd[881]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com).
Jan 23 17:13:49 201806-27089 gnome-shell[1530]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.71/org/ayatana/NotificationItem/software_update_available
Jan 23 17:13:49 201806-27089 gnome-shell[1530]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.71/org/ayatana/NotificationItem/livepatch
Jan 23 17:13:49 201806-27089 systemd[1]: Starting Stop ureadahead data collection...
Jan 23 17:13:49 201806-27089 systemd[1]: Started Stop ureadahead data collection.
Jan 23 17:15:02 201806-27089 CRON[2401]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Jan 23 17:16:13 201806-27089 systemd[1]: Started Session 9 of user ubuntu.
Jan 23 17:16:36 201806-27089 gnome-shell[1530]: JS WARNING: [resource:///org/gnome/shell/ui/search.js 506]: reference to undefined property "_searchCancelTimeoutId"
Jan 23 17:16:36 201806-27089 gnome-shell[1530]: JS WARNING: [resource:///org/gnome/shell/ui/search.js 599]: reference to undefined property "_searchCancelTimeoutId"
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.24' (uid=1001 pid=1530 comm="/usr/bin/gnome-shell " label="unconfined")
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Activating service name='org.gnome.Nautilus' requested by ':1.24' (uid=1001 pid=1530 comm="/usr/bin/gnome-shell " label="unconfined")
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Activating service name='org.gnome.Calendar' requested by ':1.24' (uid=1001 pid=1530 comm="/usr/bin/gnome-shell " label="unconfined")
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Activating service name='org.gnome.seahorse.Application' requested by ':1.24' (uid=1001 pid=1530 comm="/usr/bin/gnome-shell " label="unconfined")
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.24' (uid=1001 pid=1530 comm="/usr/bin/gnome-shell " label="unconfined")
Jan 23 17:16:36 201806-27089 systemd[1245]: Starting GNOME Terminal Server...
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Successfully activated service 'org.gnome.ControlCenter.SearchProvider'
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Successfully activated service 'org.gnome.Nautilus'
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Successfully activated service 'org.gnome.Calendar'
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Successfully activated service 'org.gnome.Terminal'
Jan 23 17:16:36 201806-27089 systemd[1245]: Started GNOME Terminal Server.
Jan 23 17:16:36 201806-27089 dbus-daemon[1384]: [session uid=1001 pid=1384] Successfully activated service 'org.gnome.seahorse.Application'
Jan 23 17:16:36 201806-27089 nautilus[2510]: g_key_file_load_from_file: assertion 'file != NULL' failed
Jan 23 17:16:36 201806-27089 nautilus[2510]: Could not establish a connection to Tracker: Failed to load SPARQL backend: Key file does not have group “DomainOntology”
Jan 23 17:16:36 201806-27089 nautilus[2510]: g_queue_pop_head: assertion 'queue != NULL' failed
Jan 23 17:16:36 201806-27089 nautilus[2510]: g_queue_foreach: assertion 'queue != NULL' failed
Jan 23 17:16:36 201806-27089 nautilus[2510]: g_queue_free: assertion 'queue != NULL' failed
Jan 23 17:16:36 201806-27089 nautilus[2510]: g_queue_pop_head: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_foreach: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_free: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_pop_head: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_foreach: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_free: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_pop_head: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_foreach: assertion 'queue != NULL' failed
Jan 23 17:16:37 201806-27089 nautilus[2510]: g_queue_free: assertion 'queue != NULL' failed
Jan 23 17:16:38 201806-27089 NetworkManager[1032]: <info> [1579770998.2784] manager: sleep: sleep requested (sleeping: no enabled: yes)
Jan 23 17:16:38 201806-27089 NetworkManager[1032]: <info> [1579770998.2787] device (wlp0s20f3): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 17:16:38 201806-27089 NetworkManager[1032]: <info> [1579770998.3019] manager: NetworkManager state is now ASLEEP
Jan 23 17:16:38 201806-27089 NetworkManager[1032]: <info> [1579770998.3038] device (enp2s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 17:16:38 201806-27089 whoopsie[1943]: [17:16:38] offline
Jan 23 17:16:38 201806-27089 dbus-daemon[980]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=1032 comm="/usr/sbin/NetworkManager --no-daemon " label=
"unconfined")
Jan 23 17:16:38 201806-27089 NetworkManager[1032]: <info> [1579770998.3079] device (enp2s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 23 17:16:38 201806-27089 avahi-daemon[1037]: Withdrawing address record for fe80::3240:68e0:a953:e9f7 on enp2s0.
Jan 23 17:16:38 201806-27089 avahi-daemon[1037]: Leaving mDNS multicast group on interface enp2s0.IPv6 with address fe80::3240:68e0:a953:e9f7.
Jan 23 17:16:38 201806-27089 avahi-daemon[1037]: Interface enp2s0.IPv6 no longer relevant for mDNS.
Jan 23 17:16:38 201806-27089 systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 23 17:16:38 201806-27089 dbus-daemon[980]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 23 17:16:38 201806-27089 systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 23 17:16:38 201806-27089 nm-dispatcher: req:1 'connectivity-change': new request (2 scripts)
Jan 23 17:16:38 201806-27089 nm-dispatcher: req:1 'connectivity-change': start running ordered scripts...
Jan 23 17:16:38 201806-27089 wpa_supplicant[1067]: nl80211: deinit ifname=wlp0s20f3 disabled_11b_rates=0
Jan 23 17:16:38 201806-27089 NetworkManager[1032]: <info> [1579770998.3427] dhcp4 (enp2s0): canceled DHCP transaction, DHCP client pid 1928

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

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-oem-osp1 5.0.0.1036.40
ProcVersionSignature: Ubuntu 5.0.0-1033.38-oem-osp1 5.0.21
Uname: Linux 5.0.0-1033-oem-osp1 x86_64
ApportVersion: 2.20.9-0ubuntu7.10
Architecture: amd64
Date: Thu Jan 23 17:43:27 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-worm+X06
InstallationDate: Installed on 2019-10-08 (107 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10
SourcePackage: linux-meta-oem-osp1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Taihsiang Ho (tai271828) wrote :
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

if -1033 isn't buggy and -1034 is, this is caused by the ASoC patches for bug 1857409

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

which means the eoan master kernel should be affected as well, since they were added there too

Taihsiang Ho (tai271828)
description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

the patches on eoan are only on master-next, not on any tagged release

no longer affects: linux-meta-oem-osp1 (Ubuntu)
Revision history for this message
Hui Wang (hui.wang) wrote :

Taihsiang,

could you please help check if the firmware and ucm is updated or not?

ls -la /lib/firmware/intel/sof
ls -la /usr/share/alsa/ucm/sof-skl_hda_card

thx.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-osp1 - 5.0.0-1037.42

---------------
linux-oem-osp1 (5.0.0-1037.42) bionic; urgency=medium

  * bionic/linux-oem-osp1: 5.0.0-1037.42 -proposed tracker (LP: #1860784)

  * [Dell Vostro 5490] proposed linux-oem-osp1 suspend resume fails
    (LP: #1860642)
    - Revert "ASoC: SOF: Intel: Fix CFL and CML FW nocodec binary names."
    - Revert "ASoC: Intel: acpi-match: split CNL tables in three"
    - Revert "ASoC: SOF: Intel: hda: use fallback for firmware name"

 -- Timo Aaltonen <email address hidden> Fri, 24 Jan 2020 15:02:03 +0200

Changed in linux-oem-osp1 (Ubuntu):
status: New → Fix Released
Revision history for this message
Chih-Hsyuan Ho (chih) wrote :

Both Dell Vostro systems (CID 201906-27089 and CID 201906-27090) are equipped with Intel CML QS CPUs. If possible, please use the CID 201910-27452, which comes with a MP CPU for a re-test, since all the newer SOF firmware we received from Intel was verified against the MP CPU.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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