Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm on a /slightly/ old tablet. Intel graphics drivers installed. Linux Mint. 4.4.0-45-generic #66-Ubuntu SMP but is has been like this for at least 4 kernel upgrades.
I'm getting random freezing. By that I mean I can't even switch to a terminal with ctrl+alt+f2. My keyboard doesn't seem to have a sysrq key either (pff!) so I can't use that... so I have to kill the power.
The freeze is most consistent when I visit Google Drive. It also happens on other complex / prefetching webpages. It sounds like hardware acceleration right? If so, how do I disable that in xorg? Having said this, it does also feel a bit like it's bogging down due to lack of memory - once the Google Drive page is opened a terminal is slower to open. Yet... memory usage isn't particularly maxed out.
Firefox has similar problems but is slightly more reliable...
Because the freeze is total I have a feeling that no particular error will be logged.. so how do I pull out the point in the logs which was were it froze?
Does it make sense to focus on the GPU modules? I thought they should be stable now.
$ tail /var/log/kern.log.2
Oct 24 16:03:05 j-3310-9756 kernel: [ 50.529804] Bluetooth: RFCOMM socket layer initialized
Oct 24 16:03:05 j-3310-9756 kernel: [ 50.529817] Bluetooth: RFCOMM ver 1.11
Oct 24 16:03:13 j-3310-9756 kernel: [ 58.975508] wlp1s0: authenticate with 4c:5e:0c:72:05:4f
Oct 24 16:03:13 j-3310-9756 kernel: [ 58.978322] wlp1s0: send auth to 4c:5e:0c:72:05:4f (try 1/3)
Oct 24 16:03:13 j-3310-9756 kernel: [ 58.980307] wlp1s0: authenticated
Oct 24 16:03:13 j-3310-9756 kernel: [ 58.983363] wlp1s0: associate with 4c:5e:0c:72:05:4f (try 1/3)
Oct 24 16:03:13 j-3310-9756 kernel: [ 58.994129] wlp1s0: RX AssocResp from 4c:5e:0c:72:05:4f (capab=0x421 status=0 aid=4)
Oct 24 16:03:13 j-3310-9756 kernel: [ 59.002657] wlp1s0: associated
Oct 24 16:03:13 j-3310-9756 kernel: [ 59.002755] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Oct 24 16:30:24 j-3310-9756 kernel: [ 1693.334463] perf interrupt took too long (2530 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
~ $ tail /var/log/kern.log.1
Nov 2 12:44:12 j-3310-9756 NetworkManager[986]: <info> [1478043852.9990] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 2 12:44:13 j-3310-9756 NetworkManager[986]: <info> [1478043853.0201] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 2 12:44:13 j-3310-9756 NetworkManager[986]: <info> [1478043853.0220] policy: set 'YHA Public Access' (wlp1s0) as default for IPv4 routing and DNS
Nov 2 12:44:13 j-3310-9756 NetworkManager[986]: <info> [1478043853.0251] dns-plugin[0x15413a0]: starting dnsmasq...
Nov 2 12:44:13 j-3310-9756 NetworkManager[986]: <info> [1478043853.0367] dns-mgr: Writing DNS information to /sbin/resolvconf
Nov 2 12:44:13 j-3310-9756 NetworkManager[986]: <info> [1478043853.3385] device (wlp1s0): Activation: successful, device activated.
Nov 2 12:44:13 j-3310-9756 NetworkManager[986]: <info> [1478043853.3495] dnsmasq[0x15413a0]: dnsmasq appeared as :1.20
Nov 2 12:44:19 j-3310-9756 kernel: [ 321.018207] Bluetooth: RFCOMM TTY layer initialized
Nov 2 12:44:19 j-3310-9756 kernel: [ 321.018224] Bluetooth: RFCOMM socket layer initialized
Nov 2 12:44:19 j-3310-9756 kernel: [ 321.018238] Bluetooth: RFCOMM ver 1.11
Cups seems to be a coinsidence:
Code:
$ tail syslog.1
Nov 3 13:27:31 j-3310-9756 anacron[928]: Job `cron.daily' started
Nov 3 13:27:31 j-3310-9756 anacron[2908]: Updated timestamp for job `cron.daily' to 2016-11-03
Nov 3 13:27:32 j-3310-9756 cracklib: no dictionary update necessary.
Nov 3 13:27:33 j-3310-9756 systemd[1]: Stopping Make remote CUPS printers available locally...
Nov 3 13:27:33 j-3310-9756 systemd[1]: Stopped Make remote CUPS printers available locally.
Nov 3 13:27:33 j-3310-9756 systemd[1]: Stopping CUPS Scheduler...
Nov 3 13:27:33 j-3310-9756 systemd[1]: Stopped CUPS Scheduler.
Nov 3 13:27:34 j-3310-9756 systemd[1]: Started CUPS Scheduler.
Nov 3 13:27:34 j-3310-9756 systemd[1]: Started Make remote CUPS printers available locally.
Nov 3 13:27:34 j-3310-9756 rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="937" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
$ tail syslog.2
Nov 2 12:44:23 j-3310-9756 org.gtk.vfs.AfcVolumeMonitor[1951]: Volume monitor alive
Nov 2 12:44:27 j-3310-9756 anacron[913]: Job `cron.daily' started
Nov 2 12:44:27 j-3310-9756 anacron[2425]: Updated timestamp for job `cron.daily' to 2016-11-02
Nov 2 12:44:28 j-3310-9756 cracklib: no dictionary update necessary.
Nov 2 12:44:29 j-3310-9756 systemd[1]: Stopping Make remote CUPS printers available locally...
Nov 2 12:44:29 j-3310-9756 systemd[1]: Stopped Make remote CUPS printers available locally.
Nov 2 12:44:29 j-3310-9756 systemd[1]: Stopping CUPS Scheduler...
Nov 2 12:44:29 j-3310-9756 systemd[1]: Stopped CUPS Scheduler.
Nov 2 12:44:29 j-3310-9756 systemd[1]: Started CUPS Scheduler.
Nov 2 12:44:29 j-3310-9756 systemd[1]: Started Make remote CUPS printers available locally.
xorg gives no error:
Code:
$ tail Xorg.0.log
[ 38.263] (**) AT Translated Set 2 keyboard: always reports core events
[ 38.263] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event4"
[ 38.263] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 38.263] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 38.263] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 38.264] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
[ 38.264] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 19)
[ 38.264] (**) Option "xkb_rules" "evdev"
[ 38.264] (**) Option "xkb_model" "pc105"
[ 38.264] (**) Option "xkb_layout" "us"
You might want to elaborate a bit more on that. One of my older touchscreen netbooks is single core atom n270 with 2 gig of ram with a intel graphics chip
and handles google drive OK. Hard drive is a ide pata zif 60 gig. No speed demon
for sure.
I run AntiX on it with Icewm window manager with Firefox ESR 45.4 when I access my google drive using my browser.
Edit: Forgot to mention. Being a small 9 incher unit. I don't bother running CUPS on it.
I've done some more testing and I find that while firefox is slow... it's actually Chromium-browser causing the lockups. Further, chromium doesn't actually quit when exited and generates new thread, sometimes quietly starting and stoppin the threads before I notice them in top. Eventually this can cause a crash. So far I haven't had a crash now using only firefox and killing chrome processes.
It's a latest version of chrome (53.0.2785.14 amd64).
But really.... linux should watchdog Chrome and prevent it from taking everything down. It will crash every time now in trying to open google drive with Chrome.
By kernels, my thought is that it's NOT the kernel since I have upgraded the kernel multiple time and the problem persists.
At least I've narrowed it down to Chrome a bit. Although if the system can't handle Chrome then the problem is open to affect other programs that misbehave this way.
I believe there is a way to limit such process spawning but I forget how...
hmm.... something else is slowing it down from time to time... appears firefox related... but firefox is at 20%CPT & 50mb RAM in top at max.... so what can be slowing the system down to the point of the mouse barely responding....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.