seduction
 Language:
Welcome, Guest. Please login or register.
Did you miss your activation email?
2019/05/26, 09:30:22


Help

Author [EN] [PL] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: Nach Update: Bildschirm friert nach einiger Zeit ein, nur Maus beweglich  (Read 698 times)

0 Members and 1 Guest are viewing this topic.

Offline tomsiduction

  • User
  • Posts: 100
Hallo

Momentan friert bei meinem - heute aktualisierten - System immer wieder der Bildschirm ein, die Maus bleibt beweglich aber sonst reagiert auf der Oberfläche nichts.

Auf einer anderen Konsole komme ich auf das System und sehe (htop):
- es ist jede Menge Speicher vorhanden
- kwin lässt sich nicht beenden bzw taucht sofort wieder auf

ich habe den Eindruck dass der Xserver Probleme macht.

journalctl zeigt für den Tag eines "Einfrierens" gar nichts an sondern endet am Ende des Vortages.

Wie grenze ich das Problem ein?

Vielen Dank im Voraus

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.630
  • we are the priests ... of the temples of syrinx
Can you post the output of

Code: [Select]
journalctl -k
Code: [Select]
journalctl -xb
Code: [Select]
systemd-analyze blame
Code: [Select]
inxi -Fr
"We're all grown up and don't freak out when a piece of text contains the word 'fuck'. I still don't understand why people think that the word 'fuck' is what would keep certain groups from contributing to the Linux kernel. In all seriousness, it doesn't."

John Paul Adrian Glaubitz

Offline tomsiduction

  • User
  • Posts: 100
Hallo und vielen Dank / Thank you very much

journalctl -k

Code: [Select]
-- Logs begin at Tue 2018-12-04 18:21:02 CET, end at Tue 2018-12-04 23:48:46 CET. --
Dez 04 23:48:14 siduction kernel: microcode: microcode updated early to revision 0x2e, date = 2018-04-10

systemd-analyze blame

Code: [Select]
          6.940s NetworkManager-wait-online.service
          1.429s systemd-cryptsetup@swap.service
           501ms udisks2.service
           496ms upower.service
           488ms systemd-logind.service
           472ms dev-mapper-VGsys\x2dLVroot.device
           338ms accounts-daemon.service
           313ms loadcpufreq.service
           282ms ModemManager.service
           248ms winbind.service
           199ms systemd-timesyncd.service
           184ms avahi-daemon.service
           184ms bluetooth.service
           166ms dnsmasq.service
           165ms gpm.service
           157ms systemd-modules-load.service
           147ms NetworkManager.service
           142ms tlp.service
           130ms user@1000.service
           129ms systemd-journald.service
           115ms keyboard-setup.service
           115ms lm-sensors.service
           110ms wpa_supplicant.service
           101ms preload.service
            99ms systemd-udev-trigger.service
            98ms virtualbox.service
            97ms qemu-guest-agent.service
            95ms alsa-restore.service
Dez 04 23:48:14 siduction kernel: Linux version 4.17.6-towo.1-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (De
Dez 04 23:48:14 siduction kernel: Command line: BOOT_IMAGE=/vmlinuz-4.17.6-towo.1-siduction-amd64 root=/dev/mapper/VGsys-
Dez 04 23:48:14 siduction kernel: Disabled fast string operations
Dez 04 23:48:14 siduction kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dez 04 23:48:14 siduction kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dez 04 23:48:14 siduction kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dez 04 23:48:14 siduction kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Dez 04 23:48:14 siduction kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' forma
Dez 04 23:48:14 siduction kernel: e820: BIOS-provided physical RAM map:
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000ca98efff] usable
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000ca98f000-0x00000000cae9efff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000cae9f000-0x00000000caf9efff] ACPI NVS
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000caf9f000-0x00000000caffefff] ACPI data
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000cafff000-0x00000000caffffff] usable
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000cb000000-0x00000000cf9fffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000ffd90000-0x00000000ffffffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022fdfffff] usable
Dez 04 23:48:14 siduction kernel: NX (Execute Disable) protection: active

journalctl -xb
Code: [Select]
-- Logs begin at Tue 2018-12-04 18:21:02 CET, end at Tue 2018-12-04 23:48:46 CET. --
Dez 04 23:48:14 siduction kernel: microcode: microcode updated early to revision 0x2e, date = 2018-04-10
Dez 04 23:48:14 siduction kernel: Linux version 4.17.6-towo.1-siduction-amd64 (towo@siduction.org) (gcc version 7.3.0 (De
Dez 04 23:48:14 siduction kernel: Command line: BOOT_IMAGE=/vmlinuz-4.17.6-towo.1-siduction-amd64 root=/dev/mapper/VGsys-
Dez 04 23:48:14 siduction kernel: Disabled fast string operations
Dez 04 23:48:14 siduction kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Dez 04 23:48:14 siduction kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Dez 04 23:48:14 siduction kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Dez 04 23:48:14 siduction kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Dez 04 23:48:14 siduction kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' forma
Dez 04 23:48:14 siduction kernel: e820: BIOS-provided physical RAM map:
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000ca98efff] usable
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000ca98f000-0x00000000cae9efff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000cae9f000-0x00000000caf9efff] ACPI NVS
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000caf9f000-0x00000000caffefff] ACPI data
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000cafff000-0x00000000caffffff] usable
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000cb000000-0x00000000cf9fffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x00000000ffd90000-0x00000000ffffffff] reserved
Dez 04 23:48:14 siduction kernel: BIOS-e820: [mem 0x0000000100000000-0x000000022fdfffff] usable
Dez 04 23:48:14 siduction kernel: NX (Execute Disable) protection: active

inxi -Fr
Code: [Select]
System:    Host: siduction Kernel: 4.17.6-towo.1-siduction-amd64 x86_64 bits: 64 Desktop: KDE Plasma 5.14.3
           Distro: siduction 17.1.0 Patience - kde - (201703051755)
Machine:   Type: Laptop System: FUJITSU product: LIFEBOOK E751 v: 10601186096 serial: DSCD077197
           Mobo: FUJITSU model: FJNB223 v: A1 serial: F1 KU4G UEFI [Legacy]: FUJITSU // Phoenix v: Version 1.16
           date: 12/09/2011
Battery:   ID-1: CMB1 charge: 62.6 Wh condition: 62.6/62.6 Wh (100%)
CPU:       Topology: Dual Core model: Intel Core i5-2520M bits: 64 type: MT MCP L2 cache: 3072 KiB
           Speed: 798 MHz min/max: 800/3200 MHz Core speeds (MHz): 1: 798 2: 798 3: 798 4: 798
Graphics:  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel
           Display: x11 server: X.Org 1.20.3 driver: intel resolution: 1600x900~60Hz
           OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.2.6
Audio:     Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel
           Sound Server: ALSA v: k4.17.6-towo.1-siduction-amd64
Network:   Device-1: Intel 82579V Gigabit Network driver: e1000e
           IF: enp0s25 state: down mac: b0:99:28:d8:2a:a6
           Device-2: Qualcomm Atheros AR9287 Wireless Network Adapter driver: ath9k
           IF: wlp10s0 state: up mac: e0:ca:94:c2:4d:d1
           Device-3: Sierra Wireless type: USB driver: qcserial,qmi_wwan
           IF: wwp0s29u1u6 state: down mac: 2e:fd:39:db:25:82
Drives:    Local Storage: total: 238.47 GiB used: 202.58 GiB (84.9%)
           ID-1: /dev/sda vendor: Samsung model: SSD 850 PRO 256GB size: 238.47 GiB
Partition: ID-1: / size: 11.75 GiB used: 10.20 GiB (86.8%) fs: ext4 dev: /dev/dm-1
           ID-2: /boot size: 476.2 MiB used: 90.7 MiB (19.0%) fs: ext3 dev: /dev/sda1
           ID-3: /home size: 19.56 GiB used: 13.41 GiB (68.5%) fs: ext4 dev: /dev/dm-2
           ID-4: swap-1 size: 5.59 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-4
Sensors:   System Temperatures: cpu: 64.0 C mobo: N/A
           Fan Speeds (RPM): N/A
Repos:     No active apt repos in: /etc/apt/sources.list
           Active apt repos in: /etc/apt/sources.list.d/debian.list
           1: deb http://deb.debian.org/debian/ unstable non-free contrib main
           Active apt repos in: /etc/apt/sources.list.d/extra.list
           1: deb https://packages.siduction.org/extra/ unstable main
           Active apt repos in: /etc/apt/sources.list.d/fixes.list
           1: deb https://packages.siduction.org/fixes/ unstable non-free contrib main
           Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
           1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
         Info:      Processes: 215 Uptime: 10h 33m Memory: 7.71 GiB used: 1.65 GiB (21.4%) Shell: bash inxi: 3.0.28



Besten Dank nochmals / Regards
« Last Edit: 2018/12/05, 10:55:59 by tomsiduction »

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.630
  • we are the priests ... of the temples of syrinx
First thing I would do is a full-upgrade, your using kernel 4.17.6-towo.1-siduction-amd64 x86_64, the latest is 4.19.6-towo.3-siduction-amd64
"We're all grown up and don't freak out when a piece of text contains the word 'fuck'. I still don't understand why people think that the word 'fuck' is what would keep certain groups from contributing to the Linux kernel. In all seriousness, it doesn't."

John Paul Adrian Glaubitz

Offline tomsiduction

  • User
  • Posts: 100
Thank you

I did as suggested.
I will report what will happen.

Regards

Offline tomsiduction

  • User
  • Posts: 100
Hello
Unfortunately still the same

Thank you

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.630
  • we are the priests ... of the temples of syrinx
Code: [Select]
6.940s NetworkManager-wait-online.service
          1.429s s6.940s NetworkManager-wait-online.service
          1.429s systemd-cryptsetup@swap.service

I can't help with the cryptsetup@swap, I don't use encryption on any box and have no need for it.

My swap is

Code: [Select]
232ms dev-disk-by\x2duuid-bee4c35a\x2db180\x2d4d4b\x2da672\x2dba8f2d33dd4b.swap
For the NetworkManager-wait-online.service you can try and edit as root

Code: [Select]
/lib/systemd/system/NetworkManager-wait-online.service

Edit these lines:

Code: [Select]
[Service]
Type=oneshot
ExecStart=/usr/bin/nm-online -s -q --timeout=30

Change the 30 to like 10 (experiment with maybe higher than 30 or lower than 10)


Instead of the above you can also try disabling the service with

Code: [Select]
systemctl disable NetworkManager-wait-online.service
I don't have a intel video card, so no experience with them, you may want to check

https://hobo.house/2018/05/18/fix-for-intel-i915-gpu-freeze-on-recent-linux-kernels/

https://wiki.archlinux.org/index.php/intel_graphics

"We're all grown up and don't freak out when a piece of text contains the word 'fuck'. I still don't understand why people think that the word 'fuck' is what would keep certain groups from contributing to the Linux kernel. In all seriousness, it doesn't."

John Paul Adrian Glaubitz

Offline melmarker

  • Global Moderator
  • User
  • *****
  • Posts: 2.630
    • g-com.eu
damn, i hate to repeat myself often - disable wait online, done - wait-online make sense if one runs (act as servver) big local databases or (maybe) use nfs served from the local machine - otherwise it don't make much sense for a desktop machine.
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline tomsiduction

  • User
  • Posts: 100
Hello an thank you very much

I just did as suggested.
Code: [Select]
systemctl disable NetworkManager-wait-online.service



I will report what will happen.

Regards


Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.630
  • we are the priests ... of the temples of syrinx
Melmrker

+ 1 and I agree 100% , but, not everyone wants to do that for some reason, I do it myself, why I gave an option  :P
"We're all grown up and don't freak out when a piece of text contains the word 'fuck'. I still don't understand why people think that the word 'fuck' is what would keep certain groups from contributing to the Linux kernel. In all seriousness, it doesn't."

John Paul Adrian Glaubitz

Offline melmarker

  • Global Moderator
  • User
  • *****
  • Posts: 2.630
    • g-com.eu
ok - wait-online for every manager make sense if ${HOME} is on a network-device - i forget, sorry 8)
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)

Offline tomsiduction

  • User
  • Posts: 100
Hello an thank you

The screen-freeze still appears.

The following things I see:

May be this has to do with the problem or not

1. service ntp status
    ends up with:
 
Code: [Select]
kernel reports TIME_ERROR: 0x2041: Clock
 ntpd[30502]: bind(24) AF_INET6 fe80::e2ca:94ff:fec2:4dd1%3#123 flags 0x11 failed: Cannot assign
 ntpd[30502]: unable to create socket on wlp10s0 (6) for fe80::e2ca:94ff:fec2:4dd1%3#123
2. Even after
Code: [Select]
    systemctl disable NetworkManager-wait-online.service
     I get a 
     
     systemd-analyze blame
   
Code: [Select]
     6.932s NetworkManager-wait-online.service
   
   

     Q: How can i permanent disable that service?

3.  The time the screen freezes (or just has freezed) I get the following message

Code: [Select]
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Output:  66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Property:  Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         State (newValue, Deleted):  0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Output:  66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Property:  Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         State (newValue, Deleted):  0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Output:  66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Property:  Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         State (newValue, Deleted):  0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Output:  66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Property:  Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         State (newValue, Deleted):  0
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper: RRNotify_OutputProperty (ignored)
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Output:  66
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         Property:  Backlight
Dez 21 13:39:06 siduction org.kde.KScreen[2769]: kscreen.xcb.helper:         State (newValue, Deleted):  0

Thank you in advance
« Last Edit: 2018/12/21, 17:14:12 by tomsiduction »

Offline piper

  • Global Moderator
  • User
  • *****
  • Posts: 1.630
  • we are the priests ... of the temples of syrinx
I seen a bug posted at redhat

Code: [Select]
NetworkManager.service starts on boot, regardless of disabling the systemd unit.

disabled does not mean that a service cannot start. If another service requires NM.service, it will still be started. If you don't want it to ever start, you need to mask it.

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=28b97f02f64ecf94e22c8929dfd0ba64151bd9d3

Some people got around this by doing

Code: [Select]
systemctl disable NetworkManager.service
systemctl disable NetworkManager-wait-online.service

This was back in 2017-11-15, so not sure if it still matters
"We're all grown up and don't freak out when a piece of text contains the word 'fuck'. I still don't understand why people think that the word 'fuck' is what would keep certain groups from contributing to the Linux kernel. In all seriousness, it doesn't."

John Paul Adrian Glaubitz

Offline tomsiduction

  • User
  • Posts: 100
Thank you

Just a question:
Code: [Select]
systemctl disable NetworkManager.service
systemctl disable NetworkManager-wait-online.service

will not disable the Networkmanager permanently?

Regards

Offline melmarker

  • Global Moderator
  • User
  • *****
  • Posts: 2.630
    • g-com.eu
@tomsiduction - i would suggest only to disable the wait-online service - it might be that n-m is your main networking service, so disabling that would be funny but not cool. :)
Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. (Benjamin Franklin, November 11, 1755)
Never attribute to malice that which can be adequately explained by stupidity. (Hanlons razor)