Dear Takashi, gentle reader, http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7039/openSU... did not work, i.e. the error persisted. No problem for me, because I can work again completely untroubled and productive, which was not the case with any version of drm-kmp-default installed. Yours sincerely Christoph-Erdmann Pfeiler Am 07.08.2017 um 20:21 schrieb Takashi Iwai:

...

Gentle reader,

please look - if You are interested - onto the appended file containing the lspci output.

The drm-kmp-default version is 4.9.33_k4.4.76_1-3.2

The graphic is a 4 Series Chipset Integrated Graphics Controller.

The graphic display and the keyboard froze, while the system was still available over the net, a xrdp server was not affected and remained fully operable (therefore I do have a thin client on my desk ;-)))

Please tell, whether I should file a bug report (or not :-/) Possibly a bug that was already fixed in the upcoming update, or

On Mon, 07 Aug 2017 20:10:04 +0200, Christoph-Erdmann Pfeiler wrote: possibly a still remaining issue.

Please check drm-kmp update at http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7039/openSU...

You'd need to uninstall drm-kmp-default at first, then install it again. It's a known problem of the conflicts with the same version.

thanks,

Takashi

...

Yours sincerely

Christoph-Erdmann Pfeiler

00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) (prog-if 00 Subsystem: Acer Incorporated [ALI] Device 023c Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 27 Region 0: Memory at fe400000 (64-bit, non-prefetchable) [size=4M] Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at dc00 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0300c Data: 4192 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915

00:02.1 Display controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03) Subsystem: Acer Incorporated [ALI] Device 023c Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Region 0: Memory at fe900000 (64-bit, non-prefetchable) [size=1M] Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Gentle reader, I did - as a matter of course - reboot my machine before and after each installation respective deinstallation of drm-kmp-default. The malfunction is clearly an effect of a race condition. I am using fvwm2/xdm, very well established, definitely non-"cool" pieces of software consuming a very little amount of system resources. The main "fat" application is a Mozilla Firefox, which runs several JavaScript based system monitoring tools (Icinga, code produced by High Energy Physicists) and consumes a lot of memory. The login prompt of xdm was garbled (blank) after the initial system startup reliably, after a "systemctl restart display-manager" after the completion of the boot process, from a text console or via xrdp it showed not defects. The system went into trashing - I was able to monitor this by a thin client on xrdp - during movement of windows, e.g. xterm, implying directly handled memory transfer under drm. The locally connected keyboard and mouse were disabled, too. Killing the local X server (from the xrdp session) helped several times, while the xrdp server did not cause problems. Yours sincerely Christoph-Erdmann Pfeiler Am 08.08.2017 um 09:05 schrieb opensuse.lietuviu.kalba:

2017.08.07 21:21, Takashi Iwai rašė:

...

Possibly a bug that was already fixed in the upcoming update, or possibly a still remaining issue.

Please check drm-kmp update at

http://download.opensuse.org/repositories/openSUSE:/Maintenance:/7039/openSU...

You'd need to uninstall drm-kmp-default at first, then install it again. It's a known problem of the conflicts with the same version.

I also had similar problem in DELL laptop with integrated Intel i5-4300M GPU (4th Generation, Haswell). This update for me fixed issues related with i915: desktop no longer hang, KDE Plasma no longer notifies about graphics reset, no longer so often opens DrKonqi for Plasma crash or various other components, desktop no longer restarts at high usage of computer. Note, I needed to restart computer to make effect of updated drm-kmp-default (just update in running system did not changed situation). Thanks!

What was associated bug number for this update?

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, 09 Aug 2017 12:43:17 +0200, Christoph-Erdmann Pfeiler wrote:

Gentle reader,

the GPU malfunction caused by drm-kmp-default persists even with the most recent kernel:

The Leap kernel version doesn't matter much regarding this problem since the GPU driver function is provided by drm-kmp, not by the kernel. On Leap, kABI is kept compatible, thus the KMP is keep linked to the newer kernel. So the question is whether the newer updated drm-kmp works better or not. But, from the given bug reports so far, 4.9.x kernel doesn't seem working better than 4.4.x for older Intel chips, unfortunately. You can keep drm-kmp uninstalled on such platforms by simply adding zypper lock. That's the very advantage of upgrading the stuff via KMP, after all. You can easily roll back to the previous stable state as of SP2. Takashi -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org