Suspend issue with Dell Venue 11 Pro 7140

[Tudor Holton]

Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again.

I'm attaching a suspend log.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-generic (not installed)
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tudor 1785 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 9 10:57:38 2015
HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e
InstallationDate: Installed on 2015-07-06 (2 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp.
 Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Venue 11 Pro 7140
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-22-generic N/A
 linux-backports-modules-3.19.0-22-generic N/A
 linux-firmware 1.143.1
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago)
dmi.bios.date: 06/30/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Venue 11 Pro 7140
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Tudor Holton, thank you for reporting this and helping make Ubuntu better.

Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[Tudor Holton (tudor)]

Sorry. No go.

$ uname -a
Linux kneetm 4.2.0-040200rc2-generic #201507121935 SMP Sun Jul 12 23:36:39 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
$ sudo pm-suspend

[Screen goes blank, power light goes off, but can't restart it from the power button]

[penalvch (penalvch)]

Tudor Holton, with the latest mainline kernel (4.2-rc3) could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Tudor Holton (tudor)]

I'm attaching the wakeup and resume-trace scripts. Am I reading it right that it has something to do with /home/kernel/COD/linux/drivers/base/power/main.c:1065 ?

[penalvch (penalvch)]

Tudor Holton, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (linux-pm)?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

[RussianNeuroMancer (russianneuromancer)]

In upstream report there is patches for suspend, but this patches behave erratically for me.

[penalvch (penalvch)]

Tudor Holton, could you please test the latest mainline kernel (4.6) and advise to the results?

[RussianNeuroMancer (russianneuromancer)]

Additional info for comment #9: according to reports on 4pda forum S3/S4 behave erratically with Windows too, so probably there is issues with BIOS. What works here is Windows Connected Standy and Linux Suspend Freeze. Maybe BIOS issue could be workaround somehow to make S3/S4 works too, not sure about this.

Christopher, with Linux 4.7:
S3 not working at all, same behaviour as described in original bugreport description. Patches from https://bugzilla.kernel.org/show_bug.cgi?id=102281 required to make it semi-working, at least as it works with Windows.
S4 - on wakeup system trying to start but then reboot tablet. Again, with Linux 4.4 and patches from https://bugzilla.kernel.org/show_bug.cgi?id=102281 hibernate works, but with some issues, for example WiFi and LTE not working after wakeup and reboot is required to make it work again.

So, to sum up things, I think making powerbutton working, so people will able to use at least suspend freeze mode, is goal that worth time. Is there anyone at Canonical who could review patches from https://bugzilla.kernel.org/show_bug.cgi?id=102281 to submit it to upstream?

Patch for Linux 4.4 is here: https://bugzilla.kernel.org/show_bug.cgi?id=102281#c51

[RussianNeuroMancer (russianneuromancer)]

Christopher, A09 BIOS is latest BIOS for this hardware: http://www.dell.com/support/home/us/en/04/product-support/product/dell-venue-11-pro-7000-7140/drivers

Upstream testing with Linux 4.7 has been done, issue is still reproducible.

[RussianNeuroMancer (russianneuromancer)]

Issue is also reproducible in Xenial and Yakkety.

[penalvch (penalvch)]

RussianNeuroMancer, are you noting you have personally tested this?

If so, it would be helpful to track this if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[RussianNeuroMancer (russianneuromancer)]

> are you noting you have personally tested this?
Yes, I do.

> If so, it would be helpful to track this if you filed a new report
Is there point in doing this if patch is already available?
https://bugzilla.kernel.org/show_bug.cgi?id=102281#c51

[penalvch (penalvch)]

RussianNeuroMancer, if you would like to see it applied in Ubuntu as soon as possible then yes.

[RussianNeuroMancer (russianneuromancer)]

I can't understand how duplicate report could help anyone. All information, in details, is already available in upstream report https://bugzilla.kernel.org/show_bug.cgi?id=102281 and in standard apport logs that is already attached here.

[penalvch (penalvch)]

RussianNeuroMancer, if you don't care to read the publicly available documentation provided to you on reporting bugs, that's up to you. However, it's tough to motivate folks to help you when you do the opposite of what is requested of you (and publicly documented).

Also, bugzilla 102281 is about how a power button doesn't work (not suspend). Hence, it has nothing to do with this report.

[RussianNeuroMancer (russianneuromancer)]

> Also, bugzilla 102281 is about how a power button doesn't work (not suspend).
Except if you open https://bugzilla.kernel.org/show_bug.cgi?id=102281 , press "Ctrl+F" and enter "suspend", you find it's mentioned 31 times. I said this because you obviously doesn't read this report and information about written patches, so at least please press "Ctr+F" and try to find what they talk about suspend, ok?

> Hence, it has nothing to do with this report.
Except I as owner of this hardware saying that https://bugzilla.kernel.org/show_bug.cgi?id=102281#c51 make suspend work (in freeze mode, as intended by hardware manufacturer).

Christopher, what the point? This bugreport about suspend and this patch https://bugzilla.kernel.org/show_bug.cgi?id=102281#c51 make it work. I already tested it.

[penalvch (penalvch)]

RussianNeuroMancer, the scope of the upstream report is at https://bugzilla.kernel.org/show_bug.cgi?id=102281#c0 . The scope mentions nothing about suspend.

The report here in Launchpad is scoped to a suspend issue for the original reporter and their hardware.

So, that's fine people talk about suspend elsewhere in that report, but it's not addressing its scope. That's great you found a patch that addresses your issue. However, for this report, any patch fix results, test results, etc. would need to be tested by the original reporter for it to move forward, because that is who filed it. Unfortunately, you insisting you have the same hardware, and your problem is addressed by a patch doesn't change anything for this report.

Simply put, folks who are interested in having their issue solved as quickly as possible, and help out file a report themselves.

One who wants to delay their own issue, drowns out the original reporter of another report, doesn't file a report themselves, and argues with folks in the Ubuntu community who provide advice.

[RussianNeuroMancer (russianneuromancer)]

Why you think my issue is different? Same issue with exactly same symthoms.

[RussianNeuroMancer (russianneuromancer)]

Resolved since Linux 4.17.

[penalvch (penalvch)]

Not Fix Released as defined by https://wiki.ubuntu.com/Bugs/Status .

[RussianNeuroMancer (russianneuromancer)]

Ubuntu 18.10 will be released today, so I think it should be Ok to close it now.

[Tudor Holton (tudor)]

Except that Ubuntu 18.10 ships with Linux 4.15. So unless the fix has been backported it won't be fixed released yet.

[RussianNeuroMancer (russianneuromancer)]

> Except that Ubuntu 18.10 ships with Linux 4.15.

Ubuntu 18.10 ships with Linux 4.18 according to
1. Release Notes: https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes#Linux_kernel_.2B2D3cJw-
Ubuntu 18.10 is based on the Linux release series 4.18.
2. Data about Linux package on Launchpad: https://launchpad.net/ubuntu/+source/linux
3. Data about Linux package on packages.ubuntu.com: https://packages.ubuntu.com/cosmic/linux-generic

[Kai-Heng Feng (kaihengfeng)]

We can still backport the fix if you know which commit fixes the issue.

[Tudor Holton (tudor)]

I stand corrected. Even still, it would be nice to give the OP (that being me) at least a couple of days to install the new version and test it before declaring it fixed. :-|

[Tudor Holton (tudor)]

...especially since the bug has been open for over 3 years and we have seen 6 releases in that time. Less than 2 days from release it a little unfair, don't you think?

Unless you have the same hardware and are able to verify the bug as described??

[RussianNeuroMancer (russianneuromancer)]

> Unless you have the same hardware and are able to verify the bug as described??

Yes, I have same hardware, and I did verified that it's fixed since Linux 4.17. If you are interested in proper suspend functioning of Linux 4.18 on Dell Venue 11 Pro 7140 you also could contribute this bugreport: https://bugzilla.kernel.org/show_bug.cgi?id=201469

> We can still backport the fix if you know which commit fixes the issue.

Unfortunately, I don't know. All I know is that suspend and wakeup works now since Linux 4.17.

[Tudor Holton (tudor)]

Well I just upgraded to 18.04 and I'm afraid it doesn't work for me. Suspend instead ends up in a state where the only option is to force a power reset.

This is why you should give the OP time to check.

[Tudor Holton (tudor)]

I mean I upgraded to 18.10 from 18.04.

[RussianNeuroMancer (russianneuromancer)]

> This is why you should give the OP time to check.

You see, I did verified if wakeup via power button works. I did wakeup Dell Venue 11 Pro 7140 via power button even today, few dozens times.

Try to put this config on your device https://www.freedesktop.org/software/systemd/man/systemd-sleep.conf.html#Example:%20freeze and see if at least suspend and then wakeup via keyboard works. Also verify if you running latest BIOS.

[penalvch (penalvch)]

Tudor Holton:

1) As is known, folks with the same computer manufacturer and model can have different hardware under the hood, and/or different revisions of the same underlying hardware (i.e. one person can reproduce something another cannot). Hence, it wouldn't hurt to test the latest BIOS (A17) via https://www.dell.com/support/home/us/en/19/product-support/product/dell-venue-11-pro-7000-7140/drivers , given others have noted the issue resolved for them. Once done, could you please post the results of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

2) If still reproducible, could you please test the latest mainline kernel (4.20-rc7) via https://wiki.ubuntu.com/Kernel/MainlineBuilds and advise to the results? This will allow upstream developers to further address.

[Tudor Holton (tudor)]

Ok. I've had some partial success with the addition of:

[Sleep]
SuspendState=freeze

in /etc/systemd/sleep.conf

However, I also lose the wifi in the process. The kernel reports:

[ 69.744693] ------------[ cut here ]------------
[ 69.744695] Timeout waiting for hardware access (CSR_GP_CNTRL 0xffffffff)
[ 69.744730] WARNING: CPU: 2 PID: 1323 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2008 iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi]
[ 69.744731] Modules linked in: usbhid rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac ipmi_devintf ipmi_msghandler bnep binfmt_misc nls_iso8859_1 snd_soc_sst_broadwell dell_wmi wmi_bmof snd_soc_sst_haswell_pcm snd_soc_sst_firmware snd_soc_sst_ipc snd_soc_sst_dsp intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel dell_laptop pcbc dell_smbios dell_wmi_descriptor dcdbas aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf joydev snd_hda_codec_hdmi cdc_mbim serio_raw cdc_acm btusb cdc_wdm uvcvideo btrtl arc4 cdc_ncm snd_soc_rt298 btbcm input_leds btintel videobuf2_vmalloc usbnet videobuf2_memops mii bluetooth videobuf2_v4l2 videobuf2_common snd_hda_intel videodev
[ 69.744760] ecdh_generic media snd_hda_codec iwlmvm snd_hda_core mac80211 hid_sensor_incl_3d snd_soc_rt286 snd_hwdep hid_sensor_rotation i915 snd_soc_rl6347a snd_seq_midi snd_soc_core iwlwifi snd_compress snd_seq_midi_event ac97_bus snd_rawmidi snd_pcm_dmaengine snd_pcm hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_als hid_sensor_accel_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf snd_seq drm_kms_helper hid_sensor_iio_common hid_multitouch drm cfg80211 industrialio snd_seq_device snd_timer mac_hid wmi i2c_algo_bit fb_sys_fops mei_me snd dw_dmac syscopyarea intel_vbtn sysfillrect sysimgblt dw_dmac_core snd_soc_sst_acpi processor_thermal_device snd_soc_acpi soc_button_array int3400_thermal soundcore video int3403_thermal mei snd_soc_acpi_intel_match sparse_keymap acpi_thermal_rel
[ 69.744786] int340x_thermal_zone intel_soc_dts_iosf acpi_pad sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 mmc_block hid_sensor_custom hid_sensor_hub hid_generic sdhci_pci cqhci sdhci ahci i2c_i801 libahci lpc_ich i2c_hid hid [last unloaded: usbhid]
[ 69.744801] CPU: 2 PID: 1323 Comm: NetworkManager Tainted: G OE 4.18.0-13-generic #14-Ubuntu
[ 69.744801] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A17 09/10/2018
[ 69.744807] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi]
[ 69.744807] Code: 2f f9 49 8d 56 08 bf 00 20 00 00 e8 d2 15 d2 f7 e9 31 ff ff ff 89 c6 48 c7 c7 50 b4 5a c0 c6 05 6f 6c 02 00 01 e8 ca 3c d0 f7 <0f> 0b e9 ec fe ff ff 48 8b 7b 30 48 c7 c1 b8 b4 5a c0 31 d2 31 f6
[ 69.744830] RSP: 0018:ffffba2501ecb190 EFLAGS: 00010086
[ 69.744831] RAX: 0000000000000000 RBX: ffff965a4f7f0018 RCX: 0000000000000006
[ 69.744832] RDX: 0000000000000007 RSI: 0000000000000086 RDI: ffff965a5e5164b0
[ 69.744833] RBP: ffffba2501ecb1b0 R08: 0000000000000001 R09: 00000000000003a9
[ 69.744834] R10: 0000000000000004 R...

[Tudor Holton (tudor)]

For @penalvch:

1) $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A17
09/10/2018

2) I tried with kernel 4.20.3 and got a similar result to above (with the "Not Tainted" Network Manager), however after suspending and resuming, the machine consistently locks up as soon as the disk is written to, meaning that I couldn't even get a copy of the report!

In 5.0.0-rc2, there is no complaint from the kernel, however, the WiFi adapter still doesn't work and the machine also locks up consistently after the resume so I couldn't get a report from that either! :-(

(I can probably grab a photo with my phone if you really need it.)

If it had just been a case of the WiFi adapter not working, I'd say this was fixed, but I think the locking up in mainline kernels may indicate a deeper problem from the suspend.

[penalvch (penalvch)]

Tudor Holton, to confirm a WORKAROUND, in both kernel Ubuntu 4.20 and mainline 5.0-rc2:

1) If you remove the module iwlwifi prior to suspend, after resuming and before enabling the module, do you still have crashes, or an issue successfully resuming?

2) If 1) was successful, if you then enable the module, is there any issue?

[Tudor Holton (tudor)]

Hi Christopher,

1) I tried removing iwlwifi and iwlmvm and then suspending. In both kernel 4.20.3 and 5.0.0-rc2 the result was the same.

I tried just leaving the system to run *without suspending*, and I found that the system would lock up after a few minutes anyway. The memory steadily increased (but nowhere near full) and the system load hit 5 (out of 4 CPUs). In both cases jbd2 was consuming 100% CPU at the time it locked up. I would normally think this was a disk issue in this case but I can't replicate it on Ubuntu kernel 4.18 (and I use this machine all day every day) so I don't think the issue is faulty hardware.

2) On a short suspend/resume cycle (before the system locked up) I resumed and reenabled the module. This time Network Manager appeared to connect, however the system locked up very shortly after that.

I think there is a deeper issue here. Perhaps with jbd2 or kworker.

[RussianNeuroMancer (russianneuromancer)]

WiFi issue was linked in Comment #30

Workaround patch from https://bugzilla.kernel.org/show_bug.cgi?id=201469#c22 (with typo fix from next comment) works for me on Linux 4.18.1 in suspend freeze mode (WiFi is still alive after resume from suspend). Deep sleep is never supposed to work on this hardware, therefore Linux is not default to suspend freeze mode on this tablet, since Linux 4.19 ( https://github.com/torvalds/linux/commit/6f9db69ad93cd6ab77d5571cf748ff7cdcfb0285 ).

[RussianNeuroMancer (russianneuromancer)]

typo

*Linux is now default to

[penalvch (penalvch)]

Tudor Holton:

Given you've tested the latest mainline kernel, latest BIOS, and assuming all the previous test results are the same when not using any non-default kernel parameters as noted in your Bug Description:
i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013"

it appears one is to wait while upstream attends to the issues noted in KBZ#201469. However, it wouldn't hurt to gather the information upstream requested using the latest mainline kernel (and continue to do so when a new mainline kernel is released), as this helps to keep developer attention.