Kernel hang-during resume from hibernation mode (ACPI)

[bitshift]

Hello,
following problem occurs when leaving hibernation mode (suspend to disk) on my freshly purchased notebook type Lenovo IdeaPad V330:

• system goes into hibernation mode using s2disk command or writing

  Code: Select all

  echo disk > /sys/power/state

  and switches off
• upon resume, kernel boots, reads the resume image and then hangs-up while activating ACPI

following procedures / tests DO NOT work on the same machine and lead to an identical error behavior:

• writing any of the available options to /sys/power/disk, (
  [platform] shutdown reboot suspend) before entering hibernation mode as a test procedure

following procedures / tests DO work on the same machine:

• s2ram or writing echo disk > /sys/power/mem including wakeup procedure
• writing any of the available options to /sys/power/pm_test, (
  [none] core processors platform devices freezer) before entering hibernation mode as a test procedure
• writing "test_resume" to /sys/power/disk before entering hibernation mode as a test procedure
• adding acpi=off as a kernel parameter upon boot

Unfortunately, ACPI=off is not a nice solution as it will hinder some other power control features on the system.
Any help in getting hibernation mode + ACPI working on that machine is highly appreciated, also recommendations about where and how to post this problem in case it really turned out to be a specific bug.

System information:

Debian Release: 9.5
Architecture: amd64
Init: systemd

Code: Select all

 cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.9.0-8-amd64 root=UUID=056ae596-1b36-40ef-aded-fb353787d4f6 ro no_console_suspend initcall_debug ignore_loglevel resume=UUID=9cc9b263-4464-48b9-8b19-0fc0b0e6bfda

Code: Select all

uname -a
Linux zimp12 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux

Code: Select all

lsmod
Module                  Size  Used by
hid_generic            16384  0
hidp                   24576  1
pci_stub               16384  1
vboxpci                24576  0
vboxnetadp             28672  0
vboxnetflt             28672  0
vboxdrv               466944  3 vboxnetadp,vboxnetflt,vboxpci
ctr                    16384  4
ccm                    20480  2
rfcomm                 77824  14
arc4                   16384  2
cmac                   16384  1
bnep                   20480  2
joydev                 20480  0
hid_rmi                24576  0
snd_hda_codec_hdmi     49152  1
snd_hda_codec_conexant    24576  1
snd_hda_codec_generic    69632  1 snd_hda_codec_conexant
intel_rapl             20480  0
x86_pkg_temp_thermal    16384  0
intel_powerclamp       16384  0
coretemp               16384  0
binfmt_misc            20480  1
snd_soc_skl            65536  0
kvm_intel             200704  0
snd_soc_skl_ipc        45056  1 snd_soc_skl
snd_soc_sst_ipc        16384  1 snd_soc_skl_ipc
snd_soc_sst_dsp        32768  1 snd_soc_skl_ipc
snd_hda_ext_core       28672  1 snd_soc_skl
snd_soc_sst_match      16384  1 snd_soc_skl
kvm                   598016  1 kvm_intel
i2c_designware_platform    16384  0
i2c_designware_core    20480  1 i2c_designware_platform
irqbypass              16384  1 kvm
snd_soc_core          212992  1 snd_soc_skl
snd_compress           20480  1 snd_soc_core
crct10dif_pclmul       16384  0
crc32_pclmul           16384  0
i915                 1257472  26
snd_hda_intel          36864  3
ath10k_pci             45056  0
ath10k_core           253952  1 ath10k_pci
snd_hda_codec         135168  4 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_codec_generic
nls_ascii              16384  1
ath                    32768  1 ath10k_core
uvcvideo               90112  0
nls_cp437              20480  1
btusb                  45056  0
videobuf2_vmalloc      16384  1 uvcvideo
btrtl                  16384  1 btusb
btbcm                  16384  1 btusb
snd_hda_core           86016  7 snd_hda_intel,snd_hda_codec_conexant,snd_hda_codec,snd_hda_ext_core,snd_soc_skl,snd_hda_codec_hdmi,snd_hda_codec_generic
videobuf2_memops       16384  1 videobuf2_vmalloc
vfat                   20480  1
drm_kms_helper        155648  1 i915
videobuf2_v4l2         24576  1 uvcvideo
mac80211              671744  1 ath10k_core
snd_hwdep              16384  1 snd_hda_codec
btintel                16384  1 btusb
videobuf2_core         40960  2 uvcvideo,videobuf2_v4l2
snd_pcm               110592  7 snd_hda_intel,snd_hda_codec,snd_hda_ext_core,snd_hda_core,snd_soc_skl,snd_hda_codec_hdmi,snd_soc_core
efi_pstore             16384  0
snd_timer              32768  1 snd_pcm
fat                    69632  1 vfat
cfg80211              589824  3 mac80211,ath,ath10k_core
bluetooth             552960  46 btrtl,hidp,btintel,bnep,btbcm,rfcomm,btusb
videodev              176128  3 uvcvideo,videobuf2_core,videobuf2_v4l2
drm                   360448  12 i915,drm_kms_helper
ghash_clmulni_intel    16384  0
idma64                 20480  0
evdev                  24576  12
snd                    86016  16 snd_compress,snd_hda_intel,snd_hwdep,snd_hda_codec_conexant,snd_hda_codec,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_soc_core,snd_pcm
iTCO_wdt               16384  0
pcspkr                 16384  0
mei_me                 36864  0
serio_raw              16384  0
soundcore              16384  1 snd
i2c_algo_bit           16384  1 i915
efivars                20480  1 efi_pstore
media                  40960  2 uvcvideo,videodev
rfkill                 24576  9 bluetooth,cfg80211
iTCO_vendor_support    16384  1 iTCO_wdt
intel_lpss_pci         16384  0
processor_thermal_device    16384  0
intel_lpss             16384  1 intel_lpss_pci
shpchp                 36864  0
mei                   102400  1 mei_me
mfd_core               16384  1 intel_lpss
intel_soc_dts_iosf     16384  1 processor_thermal_device
intel_pch_thermal      16384  0
wmi                    16384  0
ucsi                   16384  0
int3403_thermal        16384  0
int3400_thermal        16384  0
int340x_thermal_zone    16384  2 int3403_thermal,processor_thermal_device
battery                20480  0
ac                     16384  0
video                  40960  1 i915
acpi_thermal_rel       16384  1 int3400_thermal
tpm_crb                16384  0
acpi_pad               24576  0
button                 16384  1 i915
parport_pc             28672  0
ppdev                  20480  0
lp                     20480  0
parport                49152  3 lp,parport_pc,ppdev
efivarfs               16384  1
ip_tables              24576  0
x_tables               36864  1 ip_tables
autofs4                40960  2
ext4                  585728  2
crc16                  16384  2 bluetooth,ext4
jbd2                  106496  1 ext4
crc32c_generic         16384  0
fscrypto               28672  1 ext4
ecb                    16384  0
mbcache                16384  3 ext4
xhci_pci               16384  0
xhci_hcd              188416  1 xhci_pci
crc32c_intel           24576  4
ahci                   36864  0
aesni_intel           167936  6
libahci                32768  1 ahci
libata                249856  2 ahci,libahci
aes_x86_64             20480  1 aesni_intel
i2c_i801               24576  0
glue_helper            16384  1 aesni_intel
lrw                    16384  1 aesni_intel
gf128mul               16384  1 lrw
ablk_helper            16384  1 aesni_intel
nvme                   28672  4
cryptd                 24576  3 ablk_helper,ghash_clmulni_intel,aesni_intel
r8169                  86016  0
usbcore               253952  4 uvcvideo,xhci_pci,btusb,xhci_hcd
i2c_smbus              16384  1 i2c_i801
nvme_core              40960  6 nvme
mii                    16384  1 r8169
scsi_mod              225280  1 libata
usb_common             16384  1 usbcore
i2c_hid                20480  0
fan                    16384  0
thermal                20480  0
hid                   122880  4 i2c_hid,hid_generic,hidp,hid_rmi

Kernel log on boot:
(upload of the image didn't work, so here is a link to a screenshot):
http://zimprich.info/extern/img_links/kernel_log_1.jpg

[bw123]

...
upon resume, kernel boots, reads the resume image and then hangs-up while activating ACPI
...

The pic wasn't very helpful, but since acpi=off allows resume I think it's a good guess. Do you have errors in syslog also? What do you get when searching /var/log/syslog for "ACPI: Low-level resume" or just ACPI?

I have had problems with suspend/hibernate/resume myself and it can really be frustrating. On one machine I found out that systemd and upower try to restore a kboard backlight that doesn't exist. That's a kernel issue apparently. Maybe I would try a minimal install without upower and disabling the systemd restore service with systemd.restore_state=0 kernel param.

[stevepusser]

What's the hardware? (install inxi and run "inxi -Fxz". You'll get better results by updating your hardware ID databases first as sysadmin: "update-pciids && update-usbids")

You say it's a brand-new machine, and the 4.9 kernel dates back to 2016 and can't know much, if anything, about 2018 hardware. This can remedied by upgrading to the kernel and other packages from stretch-backports, but that depends on your hardware.

[bitshift]

@bw123:

Obviously the Kernel does not make it to log something into syslog upon resume from disk.
This is what I find when observing the log from a successful suspend to ram

Code: Select all

fgrep "ACPI: Low" /var/log/syslog
Sep  5 18:24:54 zimp12 kernel: [ 3656.548995] ACPI: Low-level resume complete

But after a non-successful wakeup from suspend to disk there is no similar log entry.
These are the log entries for ACPI:

Code: Select all

fgrep "ACPI" /var/log/syslog
Sep  5 18:30:17 zimp12 kernel: [    0.156457] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Sep  5 18:30:17 zimp12 kernel: [    0.156465] ACPI: bus type PCI registered
Sep  5 18:30:17 zimp12 kernel: [    0.156471] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep  5 18:30:17 zimp12 kernel: [    0.173238] ACPI: Added _OSI(Module Device)
Sep  5 18:30:17 zimp12 kernel: [    0.173244] ACPI: Added _OSI(Processor Device)
Sep  5 18:30:17 zimp12 kernel: [    0.173249] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep  5 18:30:17 zimp12 kernel: [    0.173254] ACPI: Added _OSI(Processor Aggregator Device)
Sep  5 18:30:17 zimp12 kernel: [    0.175991] ACPI: Executed 31 blocks of module-level executable AML code
Sep  5 18:30:17 zimp12 kernel: [    0.190671] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Sep  5 18:30:17 zimp12 kernel: [    0.195666] ACPI: Dynamic OEM Table Load:
Sep  5 18:30:17 zimp12 kernel: [    0.195821] ACPI: SSDT 0xFFFF92ECA7E94000 00058B (v02 PmRef  Cpu0Ist  00003000 INTL 20160527)
Sep  5 18:30:17 zimp12 kernel: [    0.196183] ACPI: Executed 1 blocks of module-level executable AML code
Sep  5 18:30:17 zimp12 kernel: [    0.196304] ACPI: \_PR_.PR00: _OSC native thermal LVT Acked
Sep  5 18:30:17 zimp12 kernel: [    0.202338] ACPI: Dynamic OEM Table Load:
Sep  5 18:30:17 zimp12 kernel: [    0.202358] ACPI: SSDT 0xFFFF92ECA7C94C00 0003FF (v02 PmRef  Cpu0Cst  00003001 INTL 20160527)
Sep  5 18:30:17 zimp12 kernel: [    0.202682] ACPI: Executed 1 blocks of module-level executable AML code
Sep  5 18:30:17 zimp12 kernel: [    0.203406] ACPI: Dynamic OEM Table Load:
Sep  5 18:30:17 zimp12 kernel: [    0.203427] ACPI: SSDT 0xFFFF92ECA7837000 000D14 (v02 PmRef  ApIst    00003000 INTL 20160527)
Sep  5 18:30:17 zimp12 kernel: [    0.204576] ACPI: Executed 1 blocks of module-level executable AML code
Sep  5 18:30:17 zimp12 kernel: [    0.204853] ACPI: Dynamic OEM Table Load:
Sep  5 18:30:17 zimp12 kernel: [    0.204869] ACPI: SSDT 0xFFFF92ECA7838000 00030A (v02 PmRef  ApCst    00003000 INTL 20160527)
Sep  5 18:30:17 zimp12 kernel: [    0.205244] ACPI: Executed 1 blocks of module-level executable AML code
Sep  5 18:30:17 zimp12 kernel: [    0.212305] ACPI : EC: EC started
Sep  5 18:30:17 zimp12 kernel: [    0.212309] ACPI : EC: interrupt blocked
Sep  5 18:30:17 zimp12 kernel: [    0.212679] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC
Sep  5 18:30:17 zimp12 kernel: [    0.212684] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x50, EC_CMD/EC_SC=0x66, EC_DATA=0x62
Sep  5 18:30:17 zimp12 kernel: [    0.212690] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions
Sep  5 18:30:17 zimp12 kernel: [    0.212695] ACPI: Interpreter enabled
Sep  5 18:30:17 zimp12 kernel: [    0.212748] ACPI: (supports S0 S3 S4 S5)
Sep  5 18:30:17 zimp12 kernel: [    0.212753] ACPI: Using IOAPIC for interrupt routing
Sep  5 18:30:17 zimp12 kernel: [    0.212794] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep  5 18:30:17 zimp12 kernel: [    0.230818] ACPI: Power Resource [FN00] (off)
Sep  5 18:30:17 zimp12 kernel: [    0.230888] ACPI: Power Resource [FN01] (off)
Sep  5 18:30:17 zimp12 kernel: [    0.230956] ACPI: Power Resource [FN02] (off)
Sep  5 18:30:17 zimp12 kernel: [    0.231022] ACPI: Power Resource [FN03] (off)
Sep  5 18:30:17 zimp12 kernel: [    0.231088] ACPI: Power Resource [FN04] (off)
Sep  5 18:30:17 zimp12 kernel: [    0.231975] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
Sep  5 18:30:17 zimp12 kernel: [    0.236118] pci 0000:00:14.0: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.240052] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.240703] pci 0000:00:1c.5: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.241347] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.243366] pci 0000:00:1f.3: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.244405] pci 0000:01:00.0: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.257775] pci 0000:02:00.0: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.268680] pci 0000:07:00.0: System wakeup disabled by ACPI
Sep  5 18:30:17 zimp12 kernel: [    0.284761] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.284843] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.284920] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.284996] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.285072] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.285148] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.285224] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.285299] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  5 18:30:17 zimp12 kernel: [    0.286598] ACPI: Enabled 3 GPEs in block 00 to 7F
Sep  5 18:30:17 zimp12 kernel: [    0.286687] ACPI : EC: interrupt unblocked
Sep  5 18:30:17 zimp12 kernel: [    0.286707] ACPI : EC: event unblocked
Sep  5 18:30:17 zimp12 kernel: [    0.286745] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x50, EC_CMD/EC_SC=0x66, EC_DATA=0x62
Sep  5 18:30:17 zimp12 kernel: [    0.286755] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions and events
Sep  5 18:30:17 zimp12 kernel: [    0.390504] PCI: Using ACPI for IRQ routing
Sep  5 18:30:17 zimp12 kernel: [    0.426742] pnp: PnP ACPI init
Sep  5 18:30:17 zimp12 kernel: [    0.426928] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.427149] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.427273] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.427346] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.427378] system 00:04: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.427408] pnp 00:05: Plug and Play ACPI device, IDs PNP0303 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.428496] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.428822] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.429010] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  5 18:30:17 zimp12 kernel: [    0.429293] pnp: PnP ACPI: found 9 devices
Sep  5 18:30:17 zimp12 kernel: [    0.665969] DMAR: ACPI device "device:71" under DMAR at fed91000 as 00:15.0
Sep  5 18:30:17 zimp12 kernel: [    0.665973] DMAR: ACPI device "device:72" under DMAR at fed91000 as 00:15.1
Sep  5 18:30:17 zimp12 kernel: [    1.124745] ACPI: bus type USB registered
Sep  5 18:30:17 zimp12 kernel: [    7.272071] ACPI: Lid Switch [LID0]
Sep  5 18:30:17 zimp12 kernel: [    7.272496] ACPI: Power Button [PWRB]
Sep  5 18:30:17 zimp12 kernel: [    7.272543] ACPI: Power Button [PWRF]
Sep  5 18:30:17 zimp12 kernel: [    7.288171] ACPI: AC Adapter [ACAD] (on-line)
Sep  5 18:30:17 zimp12 kernel: [    7.318230] ACPI: Battery Slot [BAT1] (battery present)
Sep  5 18:30:17 zimp12 kernel: [    7.320076] ACPI: Battery Slot [BAT2] (battery absent)
Sep  5 18:30:17 zimp12 kernel: [    7.681608] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)

Setting

Code: Select all

systemd.restore_state=0 

as kernel parameter does not change anything unfortunately.

I've also tried using a backported Kernel:

Code: Select all

uname -a
Linux zimp12 4.17.0-0.bpo.3-amd64 #1 SMP Debian 4.17.17-1~bpo9+1 (2018-08-27) x86_64 GNU/Linux

same result.

To test the further recommendations will take me some more time, I hope I will be back with more results soon.

[bitshift]

And here is the system information from inxi:

Code: Select all

inxi -Fxz   
System:    Host: zimp12 Kernel: 4.9.0-8-amd64 x86_64 (64 bit gcc: 6.3.0) Console: tty 0
           Distro: Debian GNU/Linux 9 (stretch)                                             
Machine:   Device: laptop System: LENOVO product: 81B0 v: Lenovo V330-14IKB                 
           Mobo: LENOVO model: LNVNB161216 v: SDK0J40697 WIN                                
           UEFI: LENOVO v: 6UCN35WW(V2.02) date: 11/14/2017                                 
Battery    BAT1: charge: 31.4 Wh 95.1% condition: 33.0/30.0 Wh (110%)                       
           model: 53 4D 50 00 31 31 42 31 00 00 00 314250324D37314C status: N/A             
CPU:       Quad core Intel Core i5-8250U (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 14400
           clock speeds: max: 3400 MHz 1: 946 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz
           5: 799 MHz 6: 799 MHz 7: 800 MHz 8: 825 MHz
Graphics:  Card: Intel Device 5917 bus-ID: 00:02.0
           Display Server: X.org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
           tty size: 92x28 Advanced Data: N/A for root out of X
Audio:     Card Intel Device 9d71 driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.9.0-8-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 01:00.0
           IF: enp1s0 state: down mac: <filter>
           Card-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
           driver: ath10k_pci bus-ID: 02:00.0
           IF: wlp2s0 state: up mac: <filter>
           Card-3: Atheros usb-ID: 001-003
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: NA (-)
           ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
Partition: ID-1: / size: 30G used: 9.5G (35%) fs: ext4 dev: /dev/nvme0n1p7
           ID-2: /home size: 94G used: 26G (29%) fs: ext4 dev: /dev/nvme0n1p8
           ID-3: swap-1 size: 8.00GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p6
Sensors:   System Temperatures: cpu: 39.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 175 Uptime: 0 min Memory: 231.8/7727.0MB
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121) inxi: 2.3.5 

[stevepusser]

Well, you ran the inxi command as root when I didn't say anything about that, so we can't see your full graphics output, and also didn't seem to update your hardware IDs, but you have an eighth-generation Intel Coffee Lake GPU much like mine, and I know you really need that newer kernel, Mesa stack, and non-free firmware packages from stretch-backports to get your machine really working right. I'm not saying it'll fix the hibernation problems, but it will at least get your Intel graphics running better...right now, if you run "inxi -G" as a standard user, you'll see you're using gallium software rendering instead of Mesa hardware DRI for openGL.

[bitshift]

Ok, I'm back again with some further logs / results.

Running inxi from userspace gives me following using a 4.17 kernel from backports:

Code: Select all

inxi -Fxz   
System:    Host: zimp12 Kernel: 4.17.0-0.bpo.3-amd64 x86_64 (64 bit gcc: 6.3.0)
           Desktop: KDE Plasma 5.8.6 (Qt 5.7.1) Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: laptop System: LENOVO product: 81B0 v: Lenovo V330-14IKB
           Mobo: LENOVO model: LNVNB161216 v: SDK0J40697 WIN
           UEFI: LENOVO v: 6UCN35WW(V2.02) date: 11/14/2017
Battery    BAT1: charge: 32.9 Wh 100.1% condition: 32.9/30.0 Wh (110%)
           model: 53 4D 50 00 31 31 42 31 00 00 00 314250324D37314C status: Full
CPU:       Quad core Intel Core i5-8250U (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 14400
           clock speeds: max: 3400 MHz 1: 1188 MHz 2: 785 MHz 3: 1015 MHz 4: 896 MHz
           5: 861 MHz 6: 1145 MHz 7: 1116 MHz 8: 838 MHz
Graphics:  Card: Intel UHD Graphics 620 bus-ID: 00:02.0
           Display Server: X.Org 1.19.2 drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.01hz
           GLX Renderer: Mesa DRI Intel Kabylake GT1.5
           GLX Version: 3.0 Mesa 13.0.6 Direct Rendering: Yes
Audio:     Card Intel Sunrise Point-LP HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.17.0-0.bpo.3-amd64
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: 4000 bus-ID: 01:00.0
           IF: enp1s0 state: down mac: <filter>
           Card-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
           driver: ath10k_pci bus-ID: 02:00.0
           IF: wlp2s0 state: up mac: <filter>
           Card-3: Qualcomm Atheros usb-ID: 001-003
           IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:    HDD Total Size: NA (-)
           ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
Partition: ID-1: / size: 30G used: 9.6G (35%) fs: ext4 dev: /dev/nvme0n1p7
           ID-2: /home size: 94G used: 26G (29%) fs: ext4 dev: /dev/nvme0n1p8
           ID-3: swap-1 size: 8.00GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p6
Sensors:   System Temperatures: cpu: 37.5C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 232 Uptime: 1 min Memory: 723.1/7719.5MB
           Init: systemd runlevel: 5 Gcc sys: 6.3.0
           Client: Shell (bash 4.4.121) inxi: 2.3.5

I also updated the non-free firmware which is now installed in following version:

Code: Select all

dpkg -l "*firmware-linux*"
ii  firmware-linux                                                20180518-1~bpo9+1                   all                                 Binary firmware for various drivers in the Linux kernel (meta-package)                                                               
ii  firmware-linux-free                                           3.4                                 all                                 Binary firmware for various drivers in the Linux kernel                                                                              
ii  firmware-linux-nonfree                                        20180518-1~bpo9+1                   all                                 Binary firmware for various drivers in the Linux kernel (meta-package) 

... unfortunately the hibernation problem persists in just the same way.

As you see, Mesa seems to be still in place. Graphics looks totally ok with this but if this could in any way be connected to my hibernation problems, I would need further instructions about how to activate gallium.

[bitshift]

@bw123:

In the meantime I also did a clean new Installation on a separate root partition on the same machine. I just installed the minimal System with a 4.9.0 kernel image, no X server installed.
Unfortunately, also here the problem occurs in the same way.

[Wheelerof4te]

Hibernation is in general wonky in Linux. You are much better off using sleep. And I agree with stevepusser, even if backported kernel doesn't fix your issue, it will better support your newish hardware. Kernel 4.9 optionally supports chips "only" up to 6th Skylake gen.