Op vrijdag 22 juni 2018 16:44:01 CEST schreef Axel Braun:
Am Freitag, 22. Juni 2018, 14:25:52 CEST schrieb Patrick Shanahan:
* Axel Braun <docb@opensuse.org> [06-22-18 07:53]:
Hi again,
I still face an issue on the Desktop I have converted from Leap 42.3 to 15. Desktop (KDE) is partly unresponsive for 2 Minutes, full load on both CPU cores, most likely due to disk-activities (baloo....). Not even CRTL-ESC is working during this time.
Is there any tweak to make it more responsive? - Different kind of Kernel or Kernel scheduler? Currently running the default kernel. - any idea to reduce the priority of baloo in order to reduce the disk activities?
Dual Core Intel G4400@3.3 GHz, 8G RAM, MSI H110M PRO-D Motherboard Any additional information needed?
have you tried top or htop to see what process(s) is stalling your system rather than "most likely" as you leave us shooting in the dark.
you are right, top gives a better overview than KDE process monitor
At the top of the list, esp, when there is no response from the desktop, is plasmashell and kwin_X11.
Graphics is an Intel i915 - is this maybe related? southpole: # lspci -s 00:02.0 -v 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 510 (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7996 Flags: bus master, fast devsel, latency 0, IRQ 122 Memory at de000000 (64-bit, non-prefetchable) [size=16M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Kernel driver in use: i915 Kernel modules: i915
Best, Axel What would actually be interesting to see is the top output whilst the desktop being frozen. I do suscpect baloo, and suggest you have it rebuild it's database. I've seen this a couple of times in the forums, where the conclusion was that the baloo database was corrupted, since after it rebuilt it's database the issue of freezing was gone. So, move it ( and all baloo's settings ) whilst being logged out, log back in and see what happens.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org