Not Suspending When Lid is Closed Causing Heat Issue

Bug #1715146 reported by Shawn Thornton
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

I installed Ubuntu Budgie 17.04 64-bit. I installed the operating system and then when booted, I apt-get update and apt-get upgrade. I went to the coffee shop and used the system for a while. When I came home I left my laptop Dell XPS 9360 in its leather case and inside my laptop bag. I left to do some errands and came back to a really hot laptop and case. The system had not gone to sleep when I closed the lid and the computer was very hot. I have attached a copy of the log files.

I then:

sudo vi /etc/systemd/logind.conf

Changed: HandleLidSwitchDocked=suspend

when I close the lid now it gives me a password to login when I open the lid, but I am not sure if it is sleeping properly. Please assist, as I do not want my laptop battery damaged by this heat again.
---
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: shawn 1786 F.... pulseaudio
DistroRelease: Ubuntu 17.04
InstallationDate: Installed on 2017-09-04 (1 days ago)
InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0c45:670c Microdia
 Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-33-generic N/A
 linux-backports-modules-4.10.0-33-generic N/A
 linux-firmware 1.164.1
Tags: zesty
Uname: Linux 4.10.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 08/02/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.1.0
dmi.board.name: 05JK94
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.1.0:bd08/02/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

Revision history for this message
Shawn Thornton (shawnthor) wrote :
Revision history for this message
fossfreedom (fossfreedom) wrote :

This looks to be a kernel issue.

My recommendation is to run apport-collect as this wiki about how to report kernel issues. https://wiki.ubuntu.com/Kernel/Bugs

A quick google reveals that other people with a similar model as you have had this issue - https://ubuntuforums.org/showthread.php?t=2358966

no longer affects: ubuntubudgie
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1715146

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Shawn Thornton (shawnthor) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected zesty
description: updated
Revision history for this message
Shawn Thornton (shawnthor) wrote : CRDA.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : IwConfig.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : JournalErrors.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : Lspci.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : ProcModules.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : RfKill.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : UdevDb.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote : WifiSyslog.txt

apport information

Revision history for this message
Shawn Thornton (shawnthor) wrote :

This is still an issue. Not suspending. Please assist.

Revision history for this message
Shawn Thornton (shawnthor) wrote :
Download full text (98.6 KiB)

Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6272] dhcp4 (wlp58s0): domain name 'umbc.edu'
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6273] dhcp4 (wlp58s0): wins '130.85.11.19'
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6273] dhcp4 (wlp58s0): wins '130.85.11.30'
Sep 8 11:37:12 budgie avahi-daemon[715]: Joining mDNS multicast group on interface wlp58s0.IPv4 with address 10.200.154.116.
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6273] dhcp4 (wlp58s0): wins '130.85.11.7'
Sep 8 11:37:12 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv4 for mDNS.
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6273] dhcp4 (wlp58s0): state changed unknown -> bound
Sep 8 11:37:12 budgie avahi-daemon[715]: Registering new address record for 10.200.154.116 on wlp58s0.IPv4.
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6344] device (wlp58s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6354] device (wlp58s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6389] device (wlp58s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6427] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 8 11:37:12 budgie dhclient[13776]: bound to 10.200.154.116 -- renewal in 1755 seconds.
Sep 8 11:37:12 budgie kernel: [ 4546.263489] wlp58s0: Limiting TX power to 17 (17 - 0) dBm as advertised by 64:a0:e7:ff:45:cf
Sep 8 11:37:12 budgie nm-dispatcher: req:295 'connectivity-change': new request (2 scripts)
Sep 8 11:37:12 budgie nm-dispatcher: req:295 'connectivity-change': start running ordered scripts...
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6510] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6513] policy: set 'UMBC Visitor' (wlp58s0) as default for IPv4 routing and DNS
Sep 8 11:37:12 budgie NetworkManager[746]: <info> [1504885032.6520] device (wlp58s0): Activation: successful, device activated.
Sep 8 11:37:12 budgie nm-dispatcher: req:296 'up' [wlp58s0]: new request (2 scripts)
Sep 8 11:37:12 budgie nm-dispatcher: req:296 'up' [wlp58s0]: start running ordered scripts...
Sep 8 11:37:12 budgie gsd-sharing[1473]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/113
Sep 8 11:37:12 budgie gsd-sharing[1473]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not loaded.
Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/113
Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/113
Sep 8 11:37:12 budgie whoopsie[1020]: [11:37:12] online
Sep ...

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

Please attach `lspci` after failed suspend. I guess 0000:39:00.0 is a TB controller.

Revision history for this message
Shawn Thornton (shawnthor) wrote :

shawn@budgie:~$ lspci
00:00.0 Host bridge: Intel Corporation Device 5904 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Device 5916 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 02)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d10 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d58 (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff)
02:00.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff)
02:01.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff)
02:02.0 PCI bridge: Intel Corporation DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015] (rev ff)
03:00.0 System peripheral: Intel Corporation DSL6340 Thunderbolt 3 NHI [Alpine Ridge 2C 2015] (rev ff)
39:00.0 USB controller: Intel Corporation DSL6340 USB 3.1 Controller [Alpine Ridge] (rev ff)
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)
3b:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01)
3c:00.0 Non-Volatile memory controller: Device 1c5c:1283
shawn@budgie:~$ ^C
shawn@budgie:~$

Revision history for this message
Shawn Thornton (shawnthor) wrote :
Download full text (34.5 KiB)

journalctl and shift g, as well.

Sep 08 13:10:14 budgie avahi-daemon[715]: New relevant interface wlp58s0.IPv6 for mDNS.
Sep 08 13:10:14 budgie avahi-daemon[715]: Registering new address record for fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
Sep 08 13:10:22 budgie systemd-logind[719]: Lid opened.
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: [0908/131022.671860:ERROR:ticl-message-validator.cc(212)] registration_digest
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: [0908/131022.671892:ERROR:ticl-message-validator.cc(319)] field registration_
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: [0908/131022.671908:ERROR:ticl-message-validator.cc(361)] field header failed
Sep 08 13:10:22 budgie budgie-plank.desktop[1747]: [0908/131022.671922:ERROR:protocol-handler.cc(145)] Received invalid message:
Sep 08 13:10:23 budgie systemd[1]: Reloading.
Sep 08 13:10:25 budgie gnome-screensaver-dialog[19008]: gkr-pam: unlocked login keyring
Sep 08 13:10:29 budgie dbus-daemon[1327]: Activating service name='com.gexperts.Terminix'
Sep 08 13:10:29 budgie dbus-daemon[1327]: Successfully activated service 'com.gexperts.Terminix'
Sep 08 13:10:29 budgie terminix[21453]: ../../../../gobject/gsignal.c:2523: signal 'notification-received' is invalid for instan
Sep 08 13:10:31 budgie kernel: pcieport 0000:02:00.0: Refused to change power state, currently in D3
Sep 08 13:10:33 budgie systemd[1]: Reloading.
Sep 08 13:10:34 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:10:34 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:28 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:29 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:34 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
Sep 08 13:11:35 budgie terminix[21453]: Allocating size to GtkScrollbar 0x55ad36983880 without calling gtk_widget_get_preferred_
lines 28081-28110/28110 (END)
Sep 08 13:10:13 budgie gsd-sharing[1473]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-serve
Sep 08 13:10:13 budgie whoopsie[1020]: [13:10:13] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/126
Sep 08 13:10:13 budgie whoopsie[1020]: [13:10:13] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/126
Sep 08 13:10:13 budgie whoopsie[1020]: [13:10:13] online
Sep 08 13:10:13 budgie sys...

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

Do you have anything plugged in the USB type-c port?

Also, please try latest mainline kernel [1].

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13/linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb

Revision history for this message
Shawn Thornton (shawnthor) wrote :

I do not have anything plugged into the USB type-c port. I will try that kernel out and report back.

Revision history for this message
Shawn Thornton (shawnthor) wrote :

shawn@budgie:~/Downloads$ sudo dpkg -i linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb
[sudo] password for shawn:
Selecting previously unselected package linux-image-4.13.0-041300-generic.
(Reading database ... 258306 files and directories currently installed.)
Preparing to unpack linux-image-4.13.0-041300-generic_4.13.0-041300.201709031731_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
Done.
Unpacking linux-image-4.13.0-041300-generic (4.13.0-041300.201709031731) ...
Setting up linux-image-4.13.0-041300-generic (4.13.0-041300.201709031731) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
update-initramfs: Generating /boot/initrd.img-4.13.0-041300-generic
W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915
W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915
W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.13.0-041300-generic /boot/vmlinuz-4.13.0-041300-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.13.0-041300-generic
Found initrd image: /boot/initrd.img-4.13.0-041300-generic
Found linux image: /boot/vmlinuz-4.10.0-33-generic
Found initrd image: /boot/initrd.img-4.10.0-33-generic
Found linux image: /boot/vmlinuz-4.10.0-19-generic
Found initrd image: /boot/initrd.img-4.10.0-19-generic
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done
shawn@budgie:~/Downloads$

Will report back..

Revision history for this message
Shawn Thornton (shawnthor) wrote :
Download full text (9.8 KiB)

I installed the kernel and clicked suspend on the taskbar at the top.

Then did "journalctl" and shift+g.

Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not
Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.servic
Sep 08 14:13:50 budgie systemd-resolved[941]: Switching to DNS server 130.85.1.23 for interface wlp58s0.
Sep 08 14:13:50 budgie dbus[729]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Sep 08 14:13:50 budgie systemd[1]: Started Network Manager Script Dispatcher Service.
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': new request (2 scripts)
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:1 'connectivity-change': start running ordered scripts...
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: new request (2 scripts)
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie nm-dispatcher[3239]: req:2 'up' [wlp58s0]: start running ordered scripts...
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/1
Sep 08 14:13:50 budgie whoopsie[1084]: [14:13:50] online
Sep 08 14:13:51 budgie dbus-daemon[1333]: Activating service name='com.gexperts.Terminix'
Sep 08 14:13:51 budgie dbus-daemon[1333]: Successfully activated service 'com.gexperts.Terminix'
Sep 08 14:13:51 budgie terminix[3275]: ../../../../gobject/gsignal.c:2523: signal 'notification-received' is invalid for instance '0x55b31b050
Sep 08 14:13:52 budgie avahi-daemon[723]: Joining mDNS multicast group on interface wlp58s0.IPv6 with address fe80::f50a:cc1e:f4f1:12cc.
Sep 08 14:13:52 budgie avahi-daemon[723]: New relevant interface wlp58s0.IPv6 for mDNS.
Sep 08 14:13:52 budgie avahi-daemon[723]: Registering new address record for fe80::f50a:cc1e:f4f1:12cc on wlp58s0.*.
~
~
~
~
~
~
lines 1974-1996/1996 (END)
Sep 08 14:13:50 budgie NetworkManager[736]: <info> [1504894430.5641] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 08 14:13:50 budgie NetworkManager[736]: <info> [1504894430.5647] policy: set 'UMBC Visitor' (wlp58s0) as default for IPv4 routing and DNS
Sep 08 14:13:50 budgie NetworkManager[736]: <info> [1504894430.5667] device (wlp58s0): Activation: successful, device activated.
Sep 08 14:13:50 budgie systemd[1]: Starting Network Manager Script Dispatcher Service...
Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not l
Sep 08 14:13:50 budgie gsd-sharing[1527]: Failed to StopUnit service: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service
Sep 08 14:13:50 budgie systemd-resolved[941]: Switching to DNS server 130.85.1.23 for interface wlp58s0.
Sep 08 14:13:50 budgie dbus[729]: [system] Successfully activated service 'org.freedesktop.n...

Revision history for this message
Shawn Thornton (shawnthor) wrote :

Also, the log file. Sorry for all the posts.

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

Did you reboot into the v4.13 kernel before suspend?

Revision history for this message
Shawn Thornton (shawnthor) wrote :

Will it not load by default?

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

It should. Can you provide full dmesg under v4.13? Don't use journalctl.

Revision history for this message
Shawn Thornton (shawnthor) wrote :
Download full text (102.1 KiB)

shawn@budgie:~$ dmesg
[ 0.000000] microcode: microcode updated early to revision 0x62, date = 2017-04-27
[ 0.000000] random: get_random_bytes called from start_kernel+0x42/0x4e1 with crng_init=0
[ 0.000000] Linux version 4.13.0-041300-generic (kernel@gloin) (gcc version 7.2.0 (Ubuntu 7.2.0-2ubuntu1)) #201709031731 SMP Sun Sep 3 21:33:09 UTC 2017
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-041300-generic root=UUID=5a8531ee-d89d-43d9-b3d9-f720bd123822 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000075807fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000075808000-0x0000000075808fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x0000000075809000-0x0000000075809fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007580a000-0x000000007a844fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007a845000-0x000000007abcffff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007abd0000-0x000000007ac10fff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000007ac11000-0x000000007aef5fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000007aef6000-0x000000007b51ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000007b520000-0x000000007b5fefff] type 20
[ 0.000000] BIOS-e820: [mem 0x000000007b5ff000-0x000000007b5fffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000007b600000-0x000000007f7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000027e7fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] efi: EFI v2.40 by American Megatrends
[ 0.000000] efi: ACPI=0x7abdd000 ACPI 2...

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

Do you have anything connects to the USB type-c or thunderbolt port?
Can you try disable thunderbolt in the BIOS and check if this still happens?

Revision history for this message
Walter (wdoekes) wrote :
Download full text (8.6 KiB)

Disabling Thunderbolt support in the BIOS (F2 during boot) worked for me.

Suspend works.

Don't know when/if I'll need the Thunderbolt. This works for now.

Thanks!

Can I provide any additional info to help you debug/fix this properly?

Cheers,
Walter

Before disabling Thunderbolt:

[ 4694.667622] wlp58s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[ 4694.679878] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 4696.418854] PM: Syncing filesystems ... done.
[ 4696.426577] PM: Preparing system for sleep (mem)
[ 4696.426825] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 4696.428577] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 4696.429797] PM: Suspending system (mem)
[ 4696.429831] Suspending console(s) (use no_console_suspend to debug)
[ 4696.645611] xhci_hcd 0000:39:00.0: WARN: xHC CMD_RUN timeout
[ 4696.645628] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110
[ 4696.645632] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
[ 4696.645636] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110
[ 4696.645642] PM: Device 0000:39:00.0 failed to suspend async: error -110
[ 4696.645836] PM: Some devices failed to suspend, or early wake event detected
[ 4696.653802] PM: resume of devices complete after 7.960 msecs
[ 4696.654412] PM: Finishing wakeup.
[ 4696.654413] Restarting tasks ... done.
[ 4696.713358] PM: Syncing filesystems ... done.
[ 4696.724043] PM: Preparing system for sleep (freeze)
[ 4696.724263] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 4696.726226] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 4696.727480] PM: Suspending system (freeze)
[ 4696.727481] Suspending console(s) (use no_console_suspend to debug)
[ 4696.727681] xhci_hcd 0000:39:00.0: WARN: xHC CMD_RUN timeout
[ 4696.727685] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110
[ 4696.727687] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110
[ 4696.727688] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110
[ 4696.727690] PM: Device 0000:39:00.0 failed to suspend async: error -110
[ 4696.727901] PM: Some devices failed to suspend, or early wake event detected
[ 4696.735295] PM: resume of devices complete after 7.392 msecs
[ 4696.735495] PM: Finishing wakeup.

After disabling Thunderbolt:

[ 467.806774] wlp58s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[ 467.819709] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[ 469.526719] PM: Syncing filesystems ... done.
[ 469.536851] PM: Preparing system for sleep (mem)
[ 469.537149] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 469.538896] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done.
[ 469.539665] PM: Suspending system (mem)
[ 469.539701] Suspending console(s) (use no_console_suspend to debug)
[ 469.759779] ACPI : EC: event blocked
[ 470.973736] PM: suspend of devices complete after 1217.757 msecs
[ 470.995596] PM: late suspend of devices complete after 21.855 msecs
[ 470.996271] ACPI : EC: interrupt blocked
[ 470.999072] xhci_hcd 0000:00:14.0: System wakeup e...

Read more...

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

I recall it a BIOS/firmware related issue.
Please upgrade your BIOS, and check if the issue is still there (with thunderbolt enabled).

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

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Shawn Thornton,

Do you still have this issue?

Revision history for this message
Walter (wdoekes) wrote :

Hi there,

I upgraded to Ubuntu Artful the other day, and today I updated the Dell BIOS (using the GUI tools).

Out of curiosity, I went back to check this: re-*enabling* Thunderbolt in the BIOS *still* *breaks* *suspend*.

Again "Some devices failed to suspend, or early wake event detected".

dmidecode:

> BIOS Information
> Vendor: Dell Inc.
> Version: 2.4.2
> Release Date: 11/21/2017
> ...
> System Information
> Manufacturer: Dell Inc.
> Product Name: XPS 13 9360

uname -a:

> Linux walter-tretton 4.13.0-21-generic #24-Ubuntu SMP
> Mon Dec 18 17:29:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Cheers,
Walter

Revision history for this message
Walter (wdoekes) wrote :

Additional info:

- if I use pm-suspend, it just refuses to suspend (after 20secs wait)

[ma dec 25 18:33:49 2017] PM: Preparing system for sleep (mem)
...
[ma dec 25 18:33:49 2017] thunderbolt 0000:03:00.0: Ignoring mailbox command error (-110) in icm_suspend
[ma dec 25 18:33:49 2017] PM: Some devices failed to suspend, or early wake event detected
[ma dec 25 18:33:49 2017] i2c i2c-7: Unbalanced pm_runtime_enable!
...
[ma dec 25 18:34:10 2017] PM: Finishing wakeup.
[ma dec 25 18:34:10 2017] OOM killer enabled.
[ma dec 25 18:34:10 2017] Restarting tasks ... done.

- if I close the lid, it does some kind of suspend with a black screen and it sometimes requires some efforts to get logged in again (ctrl-alt-del to get a login prompt again)

[ma dec 25 18:36:36 2017] PM: Preparing system for sleep (mem)
...
[ma dec 25 18:36:37 2017] PM: Some devices failed to suspend, or early wake event detected
...
[ma dec 25 18:36:57 2017] PM: Preparing system for sleep (freeze)
...
[ma dec 25 18:36:58 2017] PM: Some devices failed to suspend, or early wake event detected
...
[ma dec 25 18:37:19 2017] PM: Preparing system for sleep (mem)
...
[ma dec 25 18:37:20 2017] PM: Some devices failed to suspend, or early wake event detected
...
[ma dec 25 18:37:41 2017] PM: Preparing system for sleep (freeze)
...
[ma dec 25 18:37:42 2017] PM: Some devices failed to suspend, or early wake event detected
...

During that time, logind says:

Dec 25 18:36:35 walter-tretton systemd-logind[891]: Lid closed.
Dec 25 18:36:35 walter-tretton systemd-logind[891]: Suspending...
Dec 25 18:36:35 walter-tretton dbus[881]: [system] Rejected send message, 2 matched rules; type="error", sender=":1.5" (uid=0 pid=891 comm="/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.72" (uid=1000 pid=1466 comm="/usr/bin/gnome-shell ")
Dec 25 18:37:19 walter-tretton systemd-logind[891]: Operation 'sleep' finished.
Dec 25 18:37:19 walter-tretton systemd-logind[891]: Suspending...
Dec 25 18:38:03 walter-tretton systemd-logind[891]: Lid opened.

I'm not really satisfied that between 18:37:19 and 18:38:03 it was actually suspended.

Revision history for this message
Mario Limonciello (superm1) wrote :

Since you're on artful can you please use fwupdmgr to check the version of the Thunderbolt NVM? I wonder if your thunderbolt controller is in safe mode. If so you won't be seeing a version in fwupd. Please share your fwupdmgr devices output.

Revision history for this message
Walter (wdoekes) wrote :

(And indeed, no suspend, it was waking/sleeping during the entire 1.5h it was "suspended" just now.
$ dmesg | grep 'PM.*Preparing system for sleep' | wc -l
115)

Hi Mario, do you mean this?

$ fwupdmgr get-devices
Intel AMT (unprovisioned)
  DeviceID: /dev/mei
  Guid: 2800f812-b7b4-2d4b-aca8-46e0ff65814c
  Plugin: amt
  Flags: internal|registered
  Version: 11.8.50
  VersionBootloader: 11.8.50
  Created: 2017-12-25

Unifying Receiver
  DeviceID: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
  Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1
  Guid: cc4cbfa9-bf9d-540b-b92b-172ce31013c1
  Plugin: unifying
  Flags: updatable|supported|registered
  DeviceVendor: Logitech
  DeviceVendorId: USB:0x046D
  Version: RQR24.05_B0029
  VersionBootloader: BOT03.00_B0006
  Created: 2017-12-25

XPS13 9360 Thunderbolt Controller
  DeviceID: d2030000-0091-7508-22f9-f2e58a90981c
  Guid: dfd51125-338f-56ff-b721-fa3bea8e534e
  Plugin: thunderbolt
  Flags: internal|updatable|registered
  DeviceVendor: Dell
  DeviceVendorId: TBT:0x00D4
  Version: 18.5
  Created: 2017-12-25

XPS 13 9360 System Firmware
  DeviceID: UEFI-5ffdbc0d-f340-441c-a803-8439c8c0ae10-dev0
  Guid: 5ffdbc0d-f340-441c-a803-8439c8c0ae10
  Plugin: uefi
  Flags: internal|updatable|require-ac|supported|registered|needs-reboot
  Version: 0.2.4.2
  VersionLowest: 0.2.4.2
  Created: 2017-12-25

Integrated Webcam HD
  DeviceID: usb:00:05
  Guid: 87c78d19-a3ed-5778-9b69-8eb701529940
  Guid: ea5dc553-c861-59a3-885c-caf80c2dea78
  Plugin: usb
  Flags: registered
  DeviceVendorId: USB:0x0BDA
  Version: 99.24
  Created: 2017-12-25

USB Receiver
  DeviceID: usb:00:01
  Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1
  Guid: a00c69e9-62ec-56f5-bab4-177f3424793c
  Plugin: usb
  Flags: registered
  DeviceVendorId: USB:0x046D
  Version: 36.5
  Created: 2017-12-25

Unknown Device
  DeviceID: ro__sys_devices_pci0000_00_0000_00_02_0
  Guid: a2721130-d6d5-51aa-a710-0323525ca469
  Plugin: udev
  Flags: internal|registered
  DeviceVendor: Intel Corporation
  DeviceVendorId: PCI:0x8086
  Created: 2017-12-25

Revision history for this message
Mario Limonciello (superm1) wrote : Re: [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Download full text (3.4 KiB)

There is an updated NVM for the 9360. It's posted to LVFS testing remote.
You can manually download it from here.

https://fwupd.org/lvfs/device/dfd51125-338f-56ff-b721-fa3bea8e534e

Can you install that and see if if helps at all perhaps?

On Mon, Dec 25, 2017, 13:25 wdoekes <email address hidden> wrote:

> (And indeed, no suspend, it was waking/sleeping during the entire 1.5h it
> was "suspended" just now.
> $ dmesg | grep 'PM.*Preparing system for sleep' | wc -l
> 115)
>
>
> Hi Mario, do you mean this?
>
> $ fwupdmgr get-devices
> Intel AMT (unprovisioned)
> DeviceID: /dev/mei
> Guid: 2800f812-b7b4-2d4b-aca8-46e0ff65814c
> Plugin: amt
> Flags: internal|registered
> Version: 11.8.50
> VersionBootloader: 11.8.50
> Created: 2017-12-25
>
> Unifying Receiver
> DeviceID: /sys/devices/pci0000:00/0000:00:14.0/usb1/1-1
> Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1
> Guid: cc4cbfa9-bf9d-540b-b92b-172ce31013c1
> Plugin: unifying
> Flags: updatable|supported|registered
> DeviceVendor: Logitech
> DeviceVendorId: USB:0x046D
> Version: RQR24.05_B0029
> VersionBootloader: BOT03.00_B0006
> Created: 2017-12-25
>
> XPS13 9360 Thunderbolt Controller
> DeviceID: d2030000-0091-7508-22f9-f2e58a90981c
> Guid: dfd51125-338f-56ff-b721-fa3bea8e534e
> Plugin: thunderbolt
> Flags: internal|updatable|registered
> DeviceVendor: Dell
> DeviceVendorId: TBT:0x00D4
> Version: 18.5
> Created: 2017-12-25
>
> XPS 13 9360 System Firmware
> DeviceID: UEFI-5ffdbc0d-f340-441c-a803-8439c8c0ae10-dev0
> Guid: 5ffdbc0d-f340-441c-a803-8439c8c0ae10
> Plugin: uefi
> Flags:
> internal|updatable|require-ac|supported|registered|needs-reboot
> Version: 0.2.4.2
> VersionLowest: 0.2.4.2
> Created: 2017-12-25
>
> Integrated Webcam HD
> DeviceID: usb:00:05
> Guid: 87c78d19-a3ed-5778-9b69-8eb701529940
> Guid: ea5dc553-c861-59a3-885c-caf80c2dea78
> Plugin: usb
> Flags: registered
> DeviceVendorId: USB:0x0BDA
> Version: 99.24
> Created: 2017-12-25
>
> USB Receiver
> DeviceID: usb:00:01
> Guid: 77d843f7-682c-57e8-8e29-584f5b4f52a1
> Guid: a00c69e9-62ec-56f5-bab4-177f3424793c
> Plugin: usb
> Flags: registered
> DeviceVendorId: USB:0x046D
> Version: 36.5
> Created: 2017-12-25
>
> Unknown Device
> DeviceID: ro__sys_devices_pci0000_00_0000_00_02_0
> Guid: a2721130-d6d5-51aa-a710-0323525ca469
> Plugin: udev
> Flags: internal|registered
> DeviceVendor: Intel Corporation
> DeviceVendorId: PCI:0x8086
> Created: 2017-12-25
>
> --
> You rece...

Read more...

Revision history for this message
Mario Limonciello (superm1) wrote :

Also don't use pm-utils. It did a few over zealous actions.
It's been removed from Ubuntu installs now but you may still have it from an upgrade. You should use systemctl to invoke the suspend.

Revision history for this message
Walter (wdoekes) wrote :
Download full text (3.2 KiB)

No, because it won't install.

I tried "fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c-NN1TN_NVM21.00.cab", but I got:

  could not find thunderbolt device at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:00.0/0000:03:00.0/domain0/0-0

So I rebooted with Thunderbolt enabled.

That gave me:

  Decompressing… [- ]
  could not validate firmware: Error reading from file: Input/output error. See https://github.com/hughsie/fwupd/wiki/Thunderbolt:-Validation-failed-or-unknown-device for more information.

But a second call gave me the same error as before the reboot (i.e. as before re-enabling Thunderbolt).

Enabling test fwupd remote through lvfs-testing.conf gave me the same results after refresh+update, so I guess I typed the right commands.

Just after reboot, probably around the time of the first fwupdmgr call, I got this in the dmesg. Could be related:

[ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0
[ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID)
[ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: device [8086:9d10] error status/mask=00000001/00002000
[ma dec 25 23:04:04 2017] pcieport 0000:00:1c.0: [ 0] Receiver Error (First)
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: remove, state 1
[ma dec 25 23:04:04 2017] usb usb4: USB disconnect, device number 1
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: USB bus 4 deregistered
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: xHCI host controller not responding, assume dead
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: remove, state 1
[ma dec 25 23:04:04 2017] usb usb3: USB disconnect, device number 1
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: Host halt failed, -19
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: Host not accessible, reset failed.
[ma dec 25 23:04:04 2017] xhci_hcd 0000:39:00.0: USB bus 3 deregistered
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: stopping RX ring 0
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: disabling interrupt at register 0x38200 bit 12 (0xffffffff -> 0xffffefff)
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: stopping TX ring 0
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: disabling interrupt at register 0x38200 bit 0 (0xffffffff -> 0xfffffffe)
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: control channel stopped
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: freeing RX ring 0
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: freeing TX ring 0
[ma dec 25 23:04:04 2017] thunderbolt 0000:03:00.0: shutdown
[ma dec 25 23:04:04 2017] pci_bus 0000:03: busn_res: [bus 03] is released
[ma dec 25 23:04:04 2017] pci_bus 0000:04: busn_res: [bus 04-38] is released
[ma dec 25 23:04:04 2017] pci_bus 0000:39: busn_res: [bus 39] is released
[ma dec 25 23:04:04 2017] pci_bus 0000:02: busn_res: [bus 02-39] is released

Although the dmesg starts about 30s earlier with a bunch of other messages (mainly pci and some thunderbolt, usb and acpi). Possibly the first call took that long.

...
[ma dec 25 23:03:37 2017] thunderbolt 0000:03:00.0...

Read more...

Revision history for this message
Walter (wdoekes) wrote :

Ah..

$ gcc -I /usr/include/efivar 1.c -lsmbios_c
In file included from /usr/include/smbios_c/config/get_config.h:36:0,
                 from /usr/include/smbios_c/compat.h:27,
                 from /usr/include/smbios_c/smi.h:22,
                 from 1.c:22:
/usr/include/smbios_c/config/compiler/gcc.h:31:7: warning: #warning "Unknown compiler version - please run the configure tests and report the results" [-Wcpp]
 # warning "Unknown compiler version - please run the configure tests and report the results"
       ^~~~~~~

$ ./a.out
This application forces TBT controller to flashing mode on Dell systems

Call with an argument of '1' to force flashing mode
Call with an argument of '0' to return to normal mode

$ ./a.out 1
failed to build buffer
Failed to force device to 1 (ret -1)

$ sudo ./a.out 1
Turned device to 1

$ fwupdmgr install eac3961ba9bd466f6e34d9276c27d524395d7c3c-NN1TN_NVM21.00.cab
Decompressing… [- ]
Restarting device… [****************************************]

Okay. Let me try again.

Revision history for this message
Walter (wdoekes) wrote :

Ok, rebooted and verified that Thunderbolt was enabled. Both pm-suspend and lid-closing now works as intended.

Dec 25 23:35:41 walter-tretton kernel: [ 53.790125] Suspended for 135.895 seconds

LGTM :okay_hand:

Revision history for this message
Mario Limonciello (superm1) wrote :

Well it's good to hear the Thunderbolt update did clear things up with the initial issue. Just to probe a little more on the update process though:

When you say thunderbolt enabled in setup can you be more specific which Thunderbolt options you're referring to? That first error is confusing to me because that means the controller enumerated but disappeared.

Regarding the need for force power, that's expected with certain fwupd and kernel combinations if you have nothing plugged into the thunderbolt controller. The peculiar thing however is that the device enumerated to the extent that first error came up.

Revision history for this message
Walter (wdoekes) wrote :

BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter Configuration:

[x] Enable Thunderbolt(tm) Technology Support
[ ] Enable Thunderbolt(tm) Adapter Boot Support
[ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules

(x) Security level - User Authorization

----

I have/had no devices attached to the Thunderbolt/USB-C socket.

But like I said, I ran the command quickly after reboot. Perhaps it enumerated right after boot but went away after a while of disuse?

Revision history for this message
Mario Limonciello (superm1) wrote :

Yeah it does go to sleep after no use with those settings activated. It's
supposed to disappear from fwupd as a result too so I expected a different
error than that. But if you went really really fast I suppose that's a
possibility.

On Tue, Dec 26, 2017, 05:55 wdoekes <email address hidden> wrote:

> BIOS Setup: Settings -> System Configuration -> Thunderbolt(tm) Adapter
> Configuration:
>
> [x] Enable Thunderbolt(tm) Technology Support
> [ ] Enable Thunderbolt(tm) Adapter Boot Support
> [ ] Enable Thunderbolt(tm) Adapter Pre-boot Modules
>
> (x) Security level - User Authorization
>
> ----
>
> I have/had no devices attached to the Thunderbolt/USB-C socket.
>
> But like I said, I ran the command quickly after reboot. Perhaps it
> enumerated right after boot but went away after a while of disuse?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1715146
>
> Title:
> Not Suspending When Lid is Closed Causing Heat Issue
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715146/+subscriptions
>

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.