4.4.0-108 fails to suspend

Bug #1742425 reported by Rainer
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

This is a Ubuntu 16.04.3 LTS, using Lubuntu's desktop (LXDE).

Note that although this is a Lenovo machine, it has a Sandy Bridge CPU (Core i5-2520M), and this is Ubuntu 16.04, so this should not be related to the recent issue with Ubuntu 17.10 and some Broadwell- and Haswell-based Lenovo machines.

Since I updated the kernel today, to 4.4.0-108, suspend fails.
Up to and including kernel 4.4.0-104, suspend always worked as expected, and still does.

Since I am now running 4.4.0-104, I refrained from using `ubuntu-bug linux`.
If need be, I can reboot to 4.4.0-108 and do that.
I have attached the result of `sudo lspci -vnvn > lspci-vnvn.log`.

It did not matter whether I used the GUI or `sudo systemctl suspend` to initiate suspend.
When I clicked "Suspend", the screen went dark, but the machine did not go to suspend,
evidenced by the fan continuing to make noise and the suspend LED staying dark.
Moving the mouse made xlock's password dialog appear immediately.

After the attempted suspend, `sudo systemctl poweroff` refused to do its work,
on the grounds that a sleep operation was already in progress.

When I used `sudo systemctl -f poweroff` to shut the machine down, it logged a kernel bug, see the following section from `/var/log/kern.log`.

----
Jan 10 10:56:49 T420 kernel: [ 29.696346] ------------[ cut here ]------------
Jan 10 10:56:49 T420 kernel: [ 29.698232] kernel BUG at /build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
Jan 10 10:56:49 T420 kernel: [ 29.699797] invalid opcode: 0000 [#1] SMP
Jan 10 10:56:49 T420 kernel: [ 29.701267] Modules linked in: tp_smapi(OE) thinkpad_ec(OE) msr acpi_call(OE) nf_log_ipv4 nf_log_ipv6 nf_log_common xt_LOG xt_limit ip6t_REJECT ipt_REJECT nf_reject_ipv6 ip6t_ah nf_reject_ipv4 nf_conntrack_ipv6 xt_tcpudp n
f_defrag_ipv6 iptable_nat xt_conntrack nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat rfcomm ip6table_filter ip6_tables iptable_filter ip_tables x_tables symap_custom_dkms_x86_64(POE) bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb btrtl btbcm btin
tel bluetooth videobuf2_v4l2 videobuf2_core v4l2_common videodev media symev_custom_dkms_x86_64(OE) binfmt_misc arc4 iwldvm intel_rapl x86_pkg_temp_thermal mac80211 intel_powerclamp coretemp snd_hda_codec_hdmi kvm snd_hda_codec_conexant snd_hda_codec_generic s
nd_hda_intel irqbypass snd_hda_codec snd_hda_core snd_hwdep iwlwifi snd_pcm input_leds joydev serio_raw cfg80211 thinkpad_acpi nvram snd_seq_midi snd_seq_midi_event snd_rawmidi lpc_ich snd_seq snd_seq_device snd_timer snd shpchp mei_me soundcore mei mac_hid nf
_conntrack_ftp nf_conntrack parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel i915 aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i2c_
algo_bit psmouse drm_kms_helper syscopyarea sysfillrect sysimgblt ahci e1000e fb_sys_fops libahci drm sdhci_pci sdhci ptp pps_core wmi fjes video
Jan 10 10:56:49 T420 kernel: [ 29.705583] CPU: 3 PID: 21 Comm: watchdog/3 Tainted: P OE 4.4.0-108-generic #131-Ubuntu
Jan 10 10:56:49 T420 kernel: [ 29.705584] Hardware name: LENOVO 4180AJ3/4180AJ3, BIOS 83ET63WW (1.33 ) 07/29/2011
Jan 10 10:56:49 T420 kernel: [ 29.705585] task: ffff880214558000 ti: ffff880214560000 task.ti: ffff880214560000
Jan 10 10:56:49 T420 kernel: [ 29.705586] RIP: 0010:[<ffffffff811f00a7>] [<ffffffff811f00a7>] kfree+0x147/0x150
Jan 10 10:56:49 T420 kernel: [ 29.705593] RSP: 0018:ffff880214563d58 EFLAGS: 00010246
Jan 10 10:56:49 T420 kernel: [ 29.705594] RAX: ffffea0008788120 RBX: ffff88021e204840 RCX: ffff88021e5f5288
Jan 10 10:56:49 T420 kernel: [ 29.705595] RDX: ffffea000852f820 RSI: ffff88021e5f5288 RDI: ffffea0008788100
Jan 10 10:56:49 T420 kernel: [ 29.705595] RBP: ffff880214563d70 R08: 0000000000000009 R09: ff80003fffffffff
Jan 10 10:56:49 T420 kernel: [ 29.705596] R10: ffffea0008788100 R11: 0000000000000001 R12: 0000000000000000
Jan 10 10:56:49 T420 kernel: [ 29.705597] R13: ffffffff810104ff R14: ffffffff81f3c840 R15: 0000000000000000
Jan 10 10:56:49 T420 kernel: [ 29.705598] FS: 0000000000000000(0000) GS:ffff88021e2c0000(0000) knlGS:0000000000000000
Jan 10 10:56:49 T420 kernel: [ 29.705599] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 10 10:56:49 T420 kernel: [ 29.705600] CR2: 000055c350f43710 CR3: 0000000212190000 CR4: 0000000000060670
Jan 10 10:56:49 T420 kernel: [ 29.705601] Stack:
Jan 10 10:56:49 T420 kernel: [ 29.705602] 0000000000000000 0000000000000000 000000000000d440 ffff880214563da0
Jan 10 10:56:49 T420 kernel: [ 29.705604] ffffffff810104ff 0000000000000004 0000000000000186 0000000000000003
Jan 10 10:56:49 T420 kernel: [ 29.705606] 0000000000000003 ffff880214563dc0 ffffffff8100608f ffff880214590000
Jan 10 10:56:49 T420 kernel: [ 29.705608] Call Trace:
Jan 10 10:56:49 T420 kernel: [ 29.705614] [<ffffffff810104ff>] release_ds_buffers+0xbf/0xd0
Jan 10 10:56:49 T420 kernel: [ 29.705617] [<ffffffff8100608f>] x86_release_hardware+0x8f/0xa0
Jan 10 10:56:49 T420 kernel: [ 29.705619] [<ffffffff810060ae>] hw_perf_event_destroy+0xe/0x20
Jan 10 10:56:49 T420 kernel: [ 29.705622] [<ffffffff81183746>] _free_event+0xb6/0x230
Jan 10 10:56:49 T420 kernel: [ 29.705623] [<ffffffff81183983>] put_event+0xc3/0x100
Jan 10 10:56:49 T420 kernel: [ 29.705625] [<ffffffff811839c9>] perf_event_release_kernel+0x9/0x10
Jan 10 10:56:49 T420 kernel: [ 29.705628] [<ffffffff8113ccae>] watchdog_nmi_disable+0x4e/0x70
Jan 10 10:56:49 T420 kernel: [ 29.705631] [<ffffffff810a4b00>] ? sort_range+0x30/0x30
Jan 10 10:56:49 T420 kernel: [ 29.705633] [<ffffffff8113cd2c>] watchdog_disable+0x5c/0x80
Jan 10 10:56:49 T420 kernel: [ 29.705635] [<ffffffff810a4be8>] smpboot_thread_fn+0xe8/0x160
Jan 10 10:56:49 T420 kernel: [ 29.705636] [<ffffffff810a1845>] kthread+0xe5/0x100
Jan 10 10:56:49 T420 kernel: [ 29.705638] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0
Jan 10 10:56:49 T420 kernel: [ 29.705642] [<ffffffff81844a0f>] ret_from_fork+0x3f/0x70
Jan 10 10:56:49 T420 kernel: [ 29.705643] [<ffffffff810a1760>] ? kthread_create_on_node+0x1e0/0x1e0
Jan 10 10:56:49 T420 kernel: [ 29.705644] Code: 4c 89 d7 e8 9c 83 fa ff eb 8c 41 b8 01 00 00 00 48 89 d9 48 89 da 4c 89 d6 e8 06 fc ff ff e9 73 ff ff ff 49 8b 42 20 a8 01 75 c7 <0f> 0b 0f 1f 80 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 57 41
Jan 10 10:56:49 T420 kernel: [ 29.705664] RIP [<ffffffff811f00a7>] kfree+0x147/0x150
Jan 10 10:56:49 T420 kernel: [ 29.705667] RSP <ffff880214563d58>
Jan 10 10:56:49 T420 kernel: [ 29.716432] ---[ end trace ad516ff87666ae06 ]---
----

Here are the installed kernels:

----
dpkg --list |grep ^ii.*linux-image
ii linux-image-4.4.0-104-generic 4.4.0-104.127 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-4.4.0-108-generic 4.4.0-108.131 amd64 Linux kernel image for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-104-generic 4.4.0-104.127 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-image-extra-4.4.0-108-generic 4.4.0-108.131 amd64 Linux kernel extra modules for version 4.4.0 on 64 bit x86 SMP
ii linux-image-generic 4.4.0.108.113 amd64 Generic Linux kernel image
----
---
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: technik 2719 F.... pulseaudio
DistroRelease: Ubuntu 16.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=6e5a1fcf-537a-4e13-bb1a-4fbca5cc02b6
InstallationDate: Installed on 2016-08-23 (504 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 4180AJ3
NonfreeKernelModules: symap_custom_dkms_x86_64
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-108-generic root=/dev/mapper/ubuntu--vg-root ro
ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
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.4.0-108-generic N/A
 linux-backports-modules-4.4.0-108-generic N/A
 linux-firmware 1.157.14
Tags: xenial
Uname: Linux 4.4.0-108-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 07/29/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET63WW (1.33 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4180AJ3
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr83ET63WW(1.33):bd07/29/2011:svnLENOVO:pn4180AJ3:pvrThinkPadT420:rvnLENOVO:rn4180AJ3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4180AJ3
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO

Revision history for this message
Rainer (rainer.blome) wrote :

Attached output of `sudo lspci -vnvn`.
Looks like adding the attachment did not work at first, so I'll try again.

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 1742425

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
tags: added: xenial
Revision history for this message
Matija Tomic (mtomic2003) wrote :

I'm experiencing the same issues and reported the separate bug report, too. Here is the link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742416

Revision history for this message
Rainer (rainer.blome) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Rainer (rainer.blome) wrote : CRDA.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : IwConfig.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : JournalErrors.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : Lspci.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : Lsusb.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : ProcEnviron.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : ProcModules.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : RfKill.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : UdevDb.txt

apport information

Revision history for this message
Rainer (rainer.blome) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Rainer (rainer.blome) wrote :

To execute the requested "apport-collect" in the context of the reproduced issue, I just tried this:

* booted 4.4.0-108
* logged in to the desktop
* used `sudo systemctl suspend`

Result was that NetworkManager turned off the network (there was a notification bubble saying "You are now disconnected" in the top right corner).
The screen stayed lit, but I did not see any further effects.

I guessed that for `apport-collect` to work, I needed connectivity, so I tried to restore it.
Tried to turn networking back on using the Network Manager GUI, but that did not work.
Connecting an Ethernet cable also had no effect. So I rebooted using `sudo systemctl -f poweroff`,
which showed the kernel bug's log output on the virtual console.

After 4.4.0-108 had rebooted, I used `apport-collect 1742425` without further attempts to reproduce the issue (had to install `sudo apt-get install python-apport` to make it work, which may be visible in logs).

Revision history for this message
Rainer (rainer.blome) wrote :

4.4.0-109 fixed the issue, thanks!

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.