• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

[Gelöst] Grafik-Initialisierung von i915 scheitert nach Suspend-To-RAM

gehrke

Administrator
Teammitglied
Moin *,

Schwiegervattern brauchte ein neues Notebook, der Job blieb an mir hängen. Die Wahl fiel auf ein Fujitsu Lifebook A555 i5-6200U mit CentOS 7 (KDE-Spin).

Die Installation verlief problemlos, soweit ich erkennen kann funktioniert alles mit einer Ausnahme: Susppend-To-RAM (STR). Bei STR funktioniert das eigentliche Schlafenlegen, aber beim Resume wird die Grafik nicht richtig initialisiert - der Monitor bleibt dunkel, egal mit welcher Tastenkombination man eine andere Session ansteuern möchte. Per SSH sehe ich, dass das System wieder problemlos läuft, nur halt mit milchig-dunklem Monitor.
Interessanterweise tritt das Problem bei einem Hibernate (Suspend-To-Disk) nicht auf.

Hardware:
Code:
[root@h2 ~]# lspci
00:00.0 Host bridge: Intel Corporation Sky Lake Host Bridge/DRAM Registers (rev 08)
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated Graphics (rev 07)
00:14.0 USB controller: Intel Corporation Device 9d2f (rev 21)
00:14.2 Signal processing controller: Intel Corporation Device 9d31 (rev 21)
00:16.0 Communication controller: Intel Corporation Device 9d3a (rev 21)
00:17.0 SATA controller: Intel Corporation Device 9d03 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Device 9d14 (rev f1)
00:1c.5 PCI bridge: Intel Corporation Device 9d15 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Device 9d18 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d48 (rev 21)
00:1f.2 Memory controller: Intel Corporation Device 9d21 (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d70 (rev 21)
00:1f.4 SMBus: Intel Corporation Device 9d23 (rev 21)
01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 524a (rev 01)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Code:
[root@h2 ~]# cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 78
model name      : Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
stepping        : 3
microcode       : 0x8a
cpu MHz         : 504.656
cache size      : 3072 KB
physical id     : 0
siblings        : 4
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 22
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb pln pts dtherm hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt xsaveopt xsavec xgetbv1 xsaves
bogomips        : 4797.90
clflush size    : 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:
[...]
Die Logs vom Suspend:
Code:
Nov 06 10:04:59 h2 systemd-logind[1047]: Lid closed.
Nov 06 10:04:59 h2 kernel: ACPI: \_SB_.PCI0.GFX0: ACPI_NOTIFY_BUS_CHECK event
Nov 06 10:04:59 h2 kernel: ACPI: \_SB_.PCI0.GFX0: Bus check in hotplug_event()
Nov 06 10:04:59 h2 kernel: i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
Nov 06 10:05:00 h2 NetworkManager[1149]: <info>  sleep requested (sleeping: no  enabled: yes)
Nov 06 10:05:00 h2 NetworkManager[1149]: <info>  sleeping...
Nov 06 10:05:00 h2 NetworkManager[1149]: <info>  (wlp1s0): device state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Nov 06 10:05:00 h2 NetworkManager[1149]: <info>  (wlp1s0): canceled DHCP transaction, DHCP client pid 1588
Nov 06 10:05:00 h2 NetworkManager[1149]: <info>  (wlp1s0): DHCPv4 state changed bound -> done
Nov 06 10:05:00 h2 kernel: wlp1s0: deauthenticating from <xxx> by local choice (Reason: 3=DEAUTH_LEAVING)
Nov 06 10:05:00 h2 NetworkManager[1149]: <info>  NetworkManager state is now ASLEEP
Nov 06 10:05:00 h2 kernel: IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
Nov 06 10:05:00 h2 dbus-daemon[1029]: dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 06 10:05:00 h2 dbus[1029]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Nov 06 10:05:00 h2 NetworkManager[1149]: <warn>  Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect.
Nov 06 10:05:00 h2 systemd[1]: Reached target Sleep.
Nov 06 10:05:00 h2 systemd[1]: Starting Sleep.
Nov 06 10:05:00 h2 systemd[1]: Starting Suspend...
Nov 06 10:05:00 h2 systemd[1]: Starting Network Manager Script Dispatcher Service...
Nov 06 10:05:00 h2 systemd-sleep[4171]: Suspending system...
Nov 06 10:05:00 h2 kernel: PM: Syncing filesystems ... done.

Die Logs vom Resume:
Code:
Nov 06 10:05:53 h2 kernel: Freezing user space processes ... (elapsed 0.016 seconds) done.
Nov 06 10:05:53 h2 kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Nov 06 10:05:53 h2 kernel: Suspending console(s) (use no_console_suspend to debug)
Nov 06 10:05:53 h2 kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Nov 06 10:05:53 h2 kernel: sd 0:0:0:0: [sda] Stopping disk
Nov 06 10:05:53 h2 kernel: PM: suspend of devices complete after 285.537 msecs
Nov 06 10:05:53 h2 kernel: PM: late suspend of devices complete after 10.962 msecs
Nov 06 10:05:53 h2 kernel: r8169 0000:08:00.0: System wakeup enabled by ACPI
Nov 06 10:05:53 h2 kernel: xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
Nov 06 10:05:53 h2 kernel: PM: noirq suspend of devices complete after 49.856 msecs
Nov 06 10:05:53 h2 kernel: ACPI: Preparing to enter system sleep state S3
Nov 06 10:05:53 h2 kernel: PM: Saving platform NVS memory
Nov 06 10:05:53 h2 kernel: Disabling non-boot CPUs ...
Nov 06 10:05:53 h2 kernel: intel_pstate CPU 1 exiting
Nov 06 10:05:53 h2 kernel: Broke affinity for irq 127
Nov 06 10:05:53 h2 kernel: smpboot: CPU 1 is now offline
Nov 06 10:05:53 h2 kernel: intel_pstate CPU 2 exiting
Nov 06 10:05:53 h2 kernel: Broke affinity for irq 125
Nov 06 10:05:53 h2 kernel: smpboot: CPU 2 is now offline
Nov 06 10:05:53 h2 kernel: intel_pstate CPU 3 exiting
Nov 06 10:05:53 h2 kernel: Broke affinity for irq 128
Nov 06 10:05:53 h2 kernel: smpboot: CPU 3 is now offline
Nov 06 10:05:53 h2 kernel: ACPI: Low-level resume complete
Nov 06 10:05:53 h2 kernel: PM: Restoring platform NVS memory
Nov 06 10:05:53 h2 kernel: Enabling non-boot CPUs ...
Nov 06 10:05:53 h2 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Nov 06 10:05:53 h2 kernel: CPU1 is up
Nov 06 10:05:53 h2 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x1
Nov 06 10:05:53 h2 kernel: CPU2 is up
Nov 06 10:05:53 h2 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Nov 06 10:05:53 h2 kernel: CPU3 is up
Nov 06 10:05:53 h2 kernel: ACPI: Waking up from system sleep state S3
Nov 06 10:05:53 h2 kernel: ACPI: \_SB_.PCI0.RP05: ACPI_NOTIFY_BUS_CHECK event
Nov 06 10:05:53 h2 kernel: ACPI: \_SB_.PCI0.RP06: ACPI_NOTIFY_BUS_CHECK event
Nov 06 10:05:53 h2 kernel: ACPI: \_SB_.PCI0.RP09: ACPI_NOTIFY_BUS_CHECK event
Nov 06 10:05:53 h2 kernel: ACPI: \_SB_.PWRB: ACPI_NOTIFY_DEVICE_WAKE event
Nov 06 10:05:53 h2 kernel: xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
Nov 06 10:05:53 h2 kernel: PM: noirq resume of devices complete after 79.908 msecs
Nov 06 10:05:53 h2 kernel: PM: early resume of devices complete after 12.877 msecs
Nov 06 10:05:53 h2 kernel: r8169 0000:08:00.0: System wakeup disabled by ACPI
Nov 06 10:05:53 h2 kernel: sd 0:0:0:0: [sda] Starting disk
Nov 06 10:05:53 h2 kernel: r8169 0000:08:00.0 enp8s0: link down
Nov 06 10:05:53 h2 kernel: pciehp 0000:00:1c.5:pcie04: Device 0000:02:00.0 already exists at 0000:02:00, cannot hot-add
Nov 06 10:05:53 h2 kernel: pciehp 0000:00:1c.5:pcie04: Cannot add device at 0000:02:00
Nov 06 10:05:53 h2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Nov 06 10:05:53 h2 kernel: ata1.00: configured for UDMA/133
Nov 06 10:05:53 h2 kernel: ata2.00: configured for UDMA/133
Nov 06 10:05:53 h2 kernel: ahci 0000:00:17.0: port does not support device sleep
Nov 06 10:05:53 h2 kernel: usb 1-5: reset high-speed USB device number 3 using xhci_hcd
Nov 06 10:05:53 h2 kernel: atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
Nov 06 10:05:53 h2 kernel: atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
Nov 06 10:05:53 h2 kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Nov 06 10:05:53 h2 kernel: [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to start channel equalization
Nov 06 10:05:53 h2 kernel: ACPI: \_SB_.PCI0.GFX0: ACPI_NOTIFY_BUS_CHECK event
Nov 06 10:05:53 h2 kernel: usb 1-7: reset full-speed USB device number 4 using xhci_hcd
Nov 06 10:05:53 h2 kernel: atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
Nov 06 10:05:53 h2 kernel: atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
Nov 06 10:05:53 h2 kernel: PM: resume of devices complete after 840.844 msecs
Nov 06 10:05:53 h2 kernel: atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
Nov 06 10:05:53 h2 kernel: atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
Nov 06 10:05:53 h2 kernel: ACPI: \_SB_.PCI0.RP05: Bus check in hotplug_event()
Nov 06 10:05:53 h2 kernel: atkbd serio0: Unknown key released (translated set 2, code 0x7c on isa0060/serio0).
Nov 06 10:05:53 h2 kernel: atkbd serio0: Use 'setkeycodes 7c <keycode>' to make it known.
Nov 06 10:05:53 h2 kernel: Restarting tasks ... done.
Nov 06 10:05:53 h2 systemd[1]: Time has been changed
Nov 06 10:05:53 h2 systemd-logind[1047]: Lid opened.
Nov 06 10:05:53 h2 systemd[1]: Started Network Manager Script Dispatcher Service.
[...]
Augenfällig scheinen mir diese Hinweise zu sein:
Code:
Nov 06 10:05:53 h2 kernel: [drm:intel_dp_start_link_train [i915]] *ERROR* failed to enable link training
Nov 06 10:05:53 h2 kernel: [drm:intel_dp_complete_link_train [i915]] *ERROR* failed to start channel equalization
Ursächlich scheint mir diese Meldung zu sein:
Code:
[root@h2 ~]# dmesg | grep 'preliminary'
[    1.163647] [drm] This hardware requires preliminary hardware support.
See CONFIG_DRM_I915_PRELIMINARY_HW_SUPPORT, and/or modparam preliminary_hw_support
Eine Recherche zeigt viele Treffer hierzu, beispielsweise hier: http://www.phoronix.com/scan.php?page=news_item&px=intel-skl-prelim-support
Möglicherweise ist die Kombination von Enterprise-Linux (CentOS) mit abgehangenem Kernel einerseits und sehr frischer Hardware andererseits hier keine gute Wahl gewesen.

Ich habe schon einige Zeit verbraten, um hierfür eine Lösung zu finden. Zum einen habe ich erfolglos die Kernelparameter (wie im obigen Artikel skizziert) zum Start in der grub.cfg übergeben:
Code:
linuxefi /vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/system-os ro crashkernel=auto rd.luks.uuid=luks-cd681b1a-213d-45f9-97a8-f883a832be30 rd.lvm.lv=system/os rd.lvm.lv=system/swap rhgb quiet i915.preliminary_hw_support=1 i915.disable_power_well=0
Zum anderen habe ich Quirks beim Suspend probiert: https://www.linuxliteos.com/forums/video-cards/%28solved%29-black-screen-after-sleep-asus-eee1025/msg16885/?PHPSESSID=bf44ae022ca7dbaf8e85e51be77ddb15#msg16885
Letzteres hatte tatsächlich einen gewissen Effekt bei manchen Kombinationen: Der Monitor blieb nicht milchig-schwarz, sondern wurde wild mit bunden Blöcken gefüllt...

Bin etwas unter Zeitdruck, weil der Eigentümer schon mit den Hufen scharrt. Wenn ich das Teil nun abgebe, habe ich aufgrund der geographischen Entfernung nur noch erschwerten Zugriff darauf. Und ohne funktionierenden Suspend ist ein Notebook irgendwie uncool.
Hat jemand einen Hinweis?
TNX


cu, gehrke
 

Sauerland

Ultimate Guru
Skylake funktioniert erst richtig mit Kernel 4.3...
https://wiki.archlinux.org/index.php/intel_graphics#Skylake_support
 
OP
gehrke

gehrke

Administrator
Teammitglied
Code:
[root@h2 ~]# dmesg | egrep -i "err|warn|fail|fault|crit|acpi"
[    0.000000] BIOS-e820: [mem 0x000000006e50d000-0x000000006e50dfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000006e5e9000-0x000000006eee8fff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000085f7e000-0x0000000087f7dfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x0000000087f7e000-0x0000000087ffdfff] ACPI data
[    0.000000] reserve setup_data: [mem 0x000000006e50d000-0x000000006e50dfff] ACPI NVS
[    0.000000] reserve setup_data: [mem 0x000000006e5e9000-0x000000006eee8fff] ACPI NVS
[    0.000000] reserve setup_data: [mem 0x0000000085f7e000-0x0000000087f7dfff] ACPI NVS
[    0.000000] reserve setup_data: [mem 0x0000000087f7e000-0x0000000087ffdfff] ACPI data
[    0.000000] efi:  SMBIOS=0x855fb000  ACPI 2.0=0x87ffd014 
[    0.000000] MTRR default type: uncachable
[    0.000000] ACPI: RSDP 0000000087ffd014 00024 (v02 FUJ   )
[    0.000000] ACPI: XSDT 0000000087fc4188 00104 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: FACP 0000000087fe9000 000F4 (v05 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI Error: Gpe0Block - 32-bit FADT register is too long (32 bytes, 256 bits) to convert to GAS struct - 255 bits max, truncating (20130517/tbfadt-202)
[    0.000000] ACPI: DSDT 0000000087fc6000 1D490 (v02 FUJ    FJNBB46  01100000 FUJ  00000001)
[    0.000000] ACPI: FACS 0000000087f6b000 00040
[    0.000000] ACPI: TCPA 0000000087ffc000 00032 (v02 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: UEFI 0000000087ffb000 00236 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: UEFI 0000000087ffa000 00042 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: SSDT 0000000087ff9000 004B7 (v02 Intel_ Tpm2Tabl 00001000 INTL 20130117)
[    0.000000] ACPI: SSDT 0000000087ff8000 0004B (v02 MeSsdt  MeSsdt  00003000 INTL 20130117)
[    0.000000] ACPI: TPM2 0000000087ff7000 00034 (v03 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: FOAT 0000000087ff6000 00055 (v03 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: SSDT 0000000087ff0000 0532F (v02 SaSsdt  SaSsdt  00003000 INTL 20130117)
[    0.000000] ACPI: DBGP 0000000087fef000 00034 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: DBG2 0000000087fee000 00061 (v00 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: ASF! 0000000087fed000 000A5 (v32 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: ASPT 0000000087fec000 00034 (v07 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: BOOT 0000000087feb000 00028 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: DBGP 0000000087fea000 00034 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: HPET 0000000087fe8000 00038 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: LPIT 0000000087fe7000 00094 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: APIC 0000000087fe6000 000BC (v03 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: MCFG 0000000087fe5000 0003C (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: SSDT 0000000087fc5000 00D7C (v02 INSYDE H2O BIOS 00001000 ACPI 00040000)
[    0.000000] ACPI: SSDT 0000000087fc3000 002D4 (v01 INSYDE H2O BIOS 00000000 ACPI 00040000)
[    0.000000] ACPI: SSDT 0000000087fc2000 0019A (v02 INSYDE H2O BIOS 00001000 ACPI 00040000)
[    0.000000] ACPI: SSDT 0000000087fc1000 006DC (v02 INSYDE H2O BIOS 00001000 ACPI 00040000)
[    0.000000] ACPI: SSDT 0000000087fc0000 00B49 (v02 INSYDE H2O BIOS 00001000 ACPI 00040000)
[    0.000000] ACPI: SSDT 0000000087fbf000 00212 (v02 INSYDE H2O BIOS 00001000 ACPI 00040000)
[    0.000000] ACPI: SSDT 0000000087fbe000 00E58 (v02 CpuRef  CpuSsdt 00003000 INTL 20130117)
[    0.000000] ACPI: FPDT 0000000087fbd000 00044 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: BGRT 0000000087fe4000 00038 (v01 FUJ    PC       01100000 FUJ  00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: PM-Timer IO Port: 0x1808
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0xff] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0xff] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x07] lapic_id[0xff] disabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0xff] disabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[    0.000000] tsc: Fast TSC calibration failed
[    0.000017] pid_max: default: 32768 minimum: 301
[    0.007591] ACPI: Core revision 20130517
[    0.033856] ACPI: All ACPI Tables successfully acquired
[    0.118913] PM: Registering ACPI NVS region [mem 0x6e50d000-0x6e50dfff] (4096 bytes)
[    0.118915] PM: Registering ACPI NVS region [mem 0x6e5e9000-0x6eee8fff] (9437184 bytes)
[    0.119028] PM: Registering ACPI NVS region [mem 0x85f7e000-0x87f7dfff] (33554432 bytes)
[    0.120406] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.120408] ACPI: bus type PCI registered
[    0.120409] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.121725] ACPI: Added _OSI(Module Device)
[    0.121727] ACPI: Added _OSI(Processor Device)
[    0.121728] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.121730] ACPI: Added _OSI(Processor Aggregator Device)
[    0.124999] ACPI: EC: Look up EC in DSDT
[    0.133301] ACPI: Executed 18 blocks of module-level executable AML code
[    0.145742] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[    0.151887] ACPI: SSDT 0000000085e70c18 0037F (v02  PmRef  Cpu0Cst 00003001 INTL 20130117)
[    0.152689] ACPI: Dynamic OEM Table Load:
[    0.152691] ACPI: SSDT           (null) 0037F (v02  PmRef  Cpu0Cst 00003001 INTL 20130117)
[    0.152815] ACPI: SSDT 0000000085e73698 0061E (v02  PmRef  Cpu0Ist 00003000 INTL 20130117)
[    0.153645] ACPI: Dynamic OEM Table Load:
[    0.153646] ACPI: SSDT           (null) 0061E (v02  PmRef  Cpu0Ist 00003000 INTL 20130117)
[    0.158326] ACPI: SSDT 0000000085e70618 005AA (v02  PmRef    ApIst 00003000 INTL 20130117)
[    0.159195] ACPI: Dynamic OEM Table Load:
[    0.159196] ACPI: SSDT           (null) 005AA (v02  PmRef    ApIst 00003000 INTL 20130117)
[    0.160914] ACPI: SSDT 0000000085e71c18 00119 (v02  PmRef    ApCst 00003000 INTL 20130117)
[    0.161711] ACPI: Dynamic OEM Table Load:
[    0.161713] ACPI: SSDT           (null) 00119 (v02  PmRef    ApCst 00003000 INTL 20130117)
[    0.165815] ACPI: Interpreter enabled
[    0.165824] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20130517/hwxface-571)
[    0.165832] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20130517/hwxface-571)
[    0.165855] ACPI: (supports S0 S3 S4 S5)
[    0.165856] ACPI: Using IOAPIC for interrupt routing
[    0.165886] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.166327] ACPI: Power Resource [PG00] (on)
[    0.166606] ACPI: Power Resource [PG01] (on)
[    0.166874] ACPI: Power Resource [PG02] (on)
[    0.179151] ACPI: Power Resource [FN00] (off)
[    0.179206] ACPI: Power Resource [FN01] (off)
[    0.179259] ACPI: Power Resource [FN02] (off)
[    0.179311] ACPI: Power Resource [FN03] (off)
[    0.179362] ACPI: Power Resource [FN04] (off)
[    0.180188] ACPI: \_PR_.CPU4: failed to get CPU physical ID.
[    0.180192] ACPI: \_PR_.CPU5: failed to get CPU physical ID.
[    0.180195] ACPI: \_PR_.CPU6: failed to get CPU physical ID.
[    0.180198] ACPI: \_PR_.CPU7: failed to get CPU physical ID.
[    0.180480] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe])
[    0.180485] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.182713] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[    0.186120] pci 0000:00:14.0: System wakeup disabled by ACPI
[    0.188627] pci 0000:00:1c.0: System wakeup disabled by ACPI
[    0.189235] pci 0000:00:1c.5: System wakeup disabled by ACPI
[    0.189842] pci 0000:00:1d.0: System wakeup disabled by ACPI
[    0.191669] pci 0000:00:1f.3: System wakeup disabled by ACPI
[    0.192807] pci 0000:01:00.0: System wakeup disabled by ACPI
[    0.195204] pci 0000:02:00.0: System wakeup disabled by ACPI
[    0.197234] pci 0000:08:00.0: System wakeup disabled by ACPI
[    0.198982] acpi PNP0A08:00: Disabling ASPM (FADT indicates it is unsupported)
[    0.199704] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.199752] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.199797] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.199843] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.199889] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.199933] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.199977] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.200022] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.200280] ACPI: Enabled 7 GPEs in block 00 to 7F
[    0.200355] ACPI: EC: GPE = 0x51, I/O: command/status = 0x66, data = 0x62
[    0.200519] ACPI: bus type USB registered
[    0.200656] PCI: Using ACPI for IRQ routing
[    0.228233] NetLabel:  unlabeled traffic allowed by default
[    0.234344] pnp: PnP ACPI init
[    0.234351] ACPI: bus type PNP registered
[    0.234505] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.234730] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.234781] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
[    0.234845] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
[    0.234944] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.235025] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.235054] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.235079] pnp 00:07: Plug and Play ACPI device, IDs FUJ0300 PNP0303 (active)
[    0.235102] pnp 00:08: Plug and Play ACPI device, IDs ALP040b PNP0f13 (active)
[    0.236071] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.236450] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.236619] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.236892] pnp: PnP ACPI: found 12 devices
[    0.236893] ACPI: bus type PNP unregistered
[    0.247364] PCI: CLS 64 bytes, default 64
[    0.749635] io scheduler deadline registered (default)
[    0.750280] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[    0.750282] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    0.750297] pcieport 0000:00:1c.5: Signaling PME through PCIe PME interrupt
[    0.750298] pci 0000:02:00.0: Signaling PME through PCIe PME interrupt
[    0.750314] pcieport 0000:00:1d.0: Signaling PME through PCIe PME interrupt
[    0.750315] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
[    0.754947] ACPI: AC Adapter [ADP1] (on-line)
[    0.758872] ACPI: Lid Switch [LID0]
[    0.758898] ACPI: Power Button [PWRB]
[    0.758921] ACPI: Power Button [PWRF]
[    0.758973] ACPI: Requesting acpi_cpufreq
[    0.760292] ACPI: Thermal Zone [TZ00] (28 C)
[    0.760389] ACPI: Thermal Zone [TZ01] (30 C)
[    0.761259] ACPI: Battery Slot [BAT1] (battery present)
[    0.772088] usb: failed to peer usb2-port5 and usb1-port6 by location (usb2-port5:none) (usb1-port6:usb2-port4)
[    0.772090] usb usb2-port5: failed to peer to usb1-port6 (-16)
[    0.772576] usb: failed to peer usb2-port6 and usb1-port6 by location (usb2-port6:none) (usb1-port6:usb2-port4)
[    0.772577] usb usb2-port6: failed to peer to usb1-port6 (-16)
[   28.982202] tpm_crb MSFT0101:00: ioremap of the command buffer failed
[   28.982211] tpm_crb: probe of MSFT0101:00 failed with error -12
[   28.985304] fujitsu_laptop: ACPI: Fujitsu FUJ02E3 [FEXT] (on)
[   29.021156] ACPI Warning: SystemIO range 0x0000000000005040-0x000000000000505f conflicts with OpRegion 0x0000000000005040-0x000000000000504f (\_SB_.PCI0.SBUS.SMBI) (20130517/utaddress-254)
[   29.021163] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   29.132033] snd_hda_intel 0000:00:1f.3: failed to add i915 component master (-19)
[ 2959.324019] r8169 0000:08:00.0: System wakeup enabled by ACPI
[ 2959.357176] xhci_hcd 0000:00:14.0: System wakeup enabled by ACPI
[ 2959.374709] ACPI: Preparing to enter system sleep state S3
[ 2959.454613] ACPI: Low-level resume complete
[ 2959.516826] ACPI: Waking up from system sleep state S3
[ 2959.519913] ACPI: \_SB_.PCI0.RP05: ACPI_NOTIFY_BUS_CHECK event
[ 2959.519928] ACPI: \_SB_.PCI0.RP06: ACPI_NOTIFY_BUS_CHECK event
[ 2959.519974] ACPI: \_SB_.PCI0.RP09: ACPI_NOTIFY_BUS_CHECK event
[ 2959.520183] ACPI: \_SB_.PWRB: ACPI_NOTIFY_DEVICE_WAKE event
[ 2959.538243] xhci_hcd 0000:00:14.0: System wakeup disabled by ACPI
[ 2959.593806] r8169 0000:08:00.0: System wakeup disabled by ACPI
[ 2961.330492] ACPI: \_SB_.PCI0.RP05: Bus check in hotplug_event()
[ 2961.330625] ACPI: \_SB_.PCI0.RP06: Bus check in hotplug_event()
[ 2961.330733] ACPI: \_SB_.PCI0.RP09: Bus check in hotplug_event()
 
OP
gehrke

gehrke

Administrator
Teammitglied
Sauerland schrieb:
Skylake funktioniert erst richtig mit Kernel 4.3...
Dank für den Link - so etwas hatte ich befürchtet. Damit habe ich nun möglicherweise einen problematischen Konflikt: Einerseits habe ich mir bewusst ein CentOS mit älterem Kernel ausgesucht (und möchte das auch nicht ändern), andererseits die vorhandene Hardware, woran ich auch nichts ändern möchte.
Argghhh...
 

Sauerland

Ultimate Guru
Du kannst es noch damit versuchen:
i915.preliminary_hw_support=1 must be added to your boot parameters for the driver to work on the new Intel Skylake

Wobei es bei meinem i5 mit Leap 42.2 ohne Probleme funktioniert............
 
OP
gehrke

gehrke

Administrator
Teammitglied
Sauerland schrieb:
Du kannst es noch damit versuchen:
i915.preliminary_hw_support=1 must be added to your boot parameters for the driver to work on the new Intel Skylake
Das hatte ich schon ausprobiert:
gehrke schrieb:
Zum einen habe ich erfolglos die Kernelparameter (wie im obigen Artikel skizziert) zum Start in der grub.cfg übergeben:
Code:
linuxefi /vmlinuz-3.10.0-327.el7.x86_64 root=/dev/mapper/system-os ro crashkernel=auto rd.luks.uuid=luks-cd681b1a-213d-45f9-97a8-f883a832be30 rd.lvm.lv=system/os rd.lvm.lv=system/swap rhgb quiet i915.preliminary_hw_support=1 i915.disable_power_well=0
Oder meintest Du ohne das i915.disable_power_well=0?

Sauerland schrieb:
Wobei es bei meinem i5 mit Leap 42.2 ohne Probleme funktioniert............
Hat AFAIK ja auch Kernel 4.4. Aber das hilft mir wenig, ich will weder SUSE noch eine Beta für diesen Job. Notfalls würde ich eher zu Fedora greifen, aber das ist nicht mein Ziel, ich will langfristigen Support.
 
OP
gehrke

gehrke

Administrator
Teammitglied
Sauerland schrieb:
https://wiki.archlinux.org/index.php/intel_graphics#Skylake_support
Habe den Hinweis von archwiki ausprobiert:
Code:
[root@h2 ~]# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.10.0-327.36.3.el7.x86_64 root=/dev/mapper/system-os ro crashkernel=auto rd.luks.uuid=luks-cd681b1a-213d-45f9-97a8-f883a832be30 rd.lvm.lv=system/os rd.lvm.lv=system/swap rhgb quiet i915.preliminary_hw_support=1
Code:
[root@h2 ~]# cat /etc/X11/xorg.conf.d/20-intel.conf
Section "Device"
        Identifier  "Intel Graphics"
        Driver      "intel"
        Option      "DRI"       "false"
EndSection
An dem beschriebenen Verhalten ändert sich dadurch leider nichts.
TNX
 

spoensche

Moderator
Teammitglied
Versuch mal folgendes:

1. Die Datei /etc/modprobe.d/blacklist-lpc_ich.conf mit folgendem Inhalt anlegen:
Code:
blacklist lpc_ich

Du kannst auch nen 4.4er Kernel aus dem EPEL Repo installieren.

https://www.centos.org/forums/viewtopic.php?t=57168
 
OP
gehrke

gehrke

Administrator
Teammitglied
spoensche schrieb:
1. Die Datei /etc/modprobe.d/blacklist-lpc_ich.conf mit folgendem Inhalt anlegen:
Hhhmm, damit bekomme ich ganz komische Effekte mit verschwindendem Desktop bei vertikalen Mausbewegungen. Nicht gut...
TNX
 
OP
gehrke

gehrke

Administrator
Teammitglied
spoensche schrieb:
Du kannst auch nen 4.4er Kernel aus dem EPEL Repo installieren.
Das klingt auf den ersten Blick durchaus interessant. Aber wenn ich dann das folgende lese, zweifel ich, ob das für mein Szenario geeignet ist:
http://elrepo.org/tiki/kernel-ml:
Notes
These packages are provided 'As-Is' with no implied warranty or support. Using the kernel-ml may expose your system to security, performance and/or data corruption issues. Since timely updates may not be available from the ELRepo Project, the end user has the ultimate responsibility for deciding whether to continue using the kernel-ml packages in regular service. These packages are not signed for SecureBoot.
Gedacht ist das Notebook nicht für mich, sondern für einen Senioren ohne tiefere Kenntnisse und Ambitionen. Das sollte rund und stabil laufen, inkl. automatischer Updates. Und da will/kann ich nicht ständig Support vor Ort leisten bei einer Anfahrtszeit von 1 1/2 Stunden.

Wenn es für mich selbst wäre, würde ich durchaus mal drüber nachdenken.
TNX
 
OP
gehrke

gehrke

Administrator
Teammitglied
Weil mir hierzu nicht mehr viel eingefallen ist und nicht absehbar war, wie lange sich eine funktionierende Lösung noch hinziehen wird, habe ich nun CentOS7 durch Fedora24 ersetzt. Damit funktioniert Suspend-To-RAM ohne Probleme. Für so frische Hardware war CentOS die falsche Wahl.

Bemerkenswert:
*Suspend-To-Disk musste erst manuell ermöglicht werden. Es fehlte ein entsprechender resume-Eintrag in der grub.cfg.
*Die Tools 'pm-suspend' und 'pm-hibernate' existieren nicht mehr. Beides läuft jetzt via systemd.

Vielen Dank an alle Beteiligten...
 
A

Anonymous

Gast
Hi,
wie zufrieden bist du denn mit Fedora 24 und den Administrations-Tools?
Ich meine jetzt auch, wie gut der Umfang von Fedora RPM Fusion im Vergleich zu openSUSE Packman ist. Wahrscheinlich hat dein Schwiegervater aber nicht so hohe Ansprüche. [OT]
 
OP
gehrke

gehrke

Administrator
Teammitglied
LUH 3417 schrieb:
wie zufrieden bist du denn mit Fedora 24 und den Administrations-Tools?
Ich meine jetzt auch, wie gut der Umfang von Fedora RPM Fusion im Vergleich zu openSUSE Packman ist.
Ich nutzte Fedora nur in Ausnahmefällen (wenn CentOS aus Gründen wie hier nicht geht), kann da aber überhaupt nicht klagen - weder was Stabilität noch Softwareauswahl angeht. So etwas wie YaST gibt es dort AFAIK nicht (brauche ich aber auch nicht mehr).
LUH 3417 schrieb:
Wahrscheinlich hat dein Schwiegervater aber nicht so hohe Ansprüche. [OT]
Die Anforderungen sind mit Thunderbird und Firefox zu 100% erfüllt...
 
Oben