You are not logged in.

#1 2020-01-22 17:25:47

ashic
Member
Registered: 2020-01-22
Posts: 14

Trying to trace intermittent freezes

Hi,
I have a Dell Precision 5510, and when connected to a Dell 4K monitor via USB C, the machine intermittently freezes for a few seconds. This seems more prominent when running Chrome, and things like jupyter notebooks seem to trigger it more. Outlook.com with overlays (i.e. pdf previews) sees this quite often, but not always. When chrome is locked up, the whole machine is unresponsive for a few seconds; I use i3wm, but I can't switch desktops when this happens.

On i3wm, I have my cpu percentage on the bottom bar, and during these lock ups, it shoots to 99% or so. If I'm not plugged in to the monitor, the freezes are far less common, though they do happen but last a fraction of a second. On rare occasions, the machine locks up, and I have to hold the power button to hard boot it.

I'm trying to figure out what I can do to trace this down. It's a fairly old machine (4.5 years of usage, with battery replaced 2.5 years ago). I mostly run on integrated graphics.

Any pointers will be appreciated.

Offline

#2 2020-01-22 17:28:16

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

To add, it seems if I have a USB charger plugged in, it freezes as well (so not just a monitor).

Offline

#3 2020-01-22 17:28:36

loqs
Member
Registered: 2014-03-06
Posts: 9,773

Re: Trying to trace intermittent freezes

Welcome to the arch linux forums ashic.  Have you looked in the journal if there is any output when there is a freeze?

Offline

#4 2020-01-22 17:29:42

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,668

Re: Trying to trace intermittent freezes

Remove xf86-video-intel (and custom configuration if present) if you have it installed, reboot/restart xorg, look at your dmesg logs to check whether you are not running into https://bbs.archlinux.org/viewtopic.php?id=250765

Offline

#5 2020-01-22 17:38:55

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

Thanks guys. I'll try capturing the journal / dmesg during a freeze.

I could very well be running into that bug, @V1del. The timeframe of when I started noticing issues seems to align.

Offline

#6 2020-01-22 18:12:36

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

@V1del

I do see

Jan 22 18:03:11 HeartyX kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=77508 end=77509) time 127 us, min 2146, max 2159, scanline start 2145, end 2162
Jan 22 18:05:31 HeartyX kernel: hrtimer: interrupt took 594937 ns
Jan 22 18:07:00 HeartyX kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=71692 end=71693) time 172 us, min 2146, max 2159, scanline start 2133, end 2161

and similar. This seems related to the bug you linked to, right?

Offline

#7 2020-01-22 18:21:25

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,668

Re: Trying to trace intermittent freezes

No that's yet another bug, and one I've only seen on xf86-video-intel, so definitely try without.

Offline

#8 2020-01-23 00:45:17

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

@V1del I tried removing xf86-video-intel, rebooted, and it wouldn't go into graphics login. Used alt+F2 to drop to shell and reinstalled. Is there an alternative package that I can use?

Offline

#9 2020-01-23 00:55:10

loqs
Member
Registered: 2014-03-06
Posts: 9,773

Re: Trying to trace intermittent freezes

What was the contents of Xorg.log with xf86-video-intel removed?  Does the system use a config that specifies the intel driver?

Last edited by loqs (2020-01-23 00:55:38)

Offline

#10 2020-01-23 00:57:58

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 17,042

Re: Trying to trace intermittent freezes

Did you create an xorg configuration file that directed the use of the intel driver? did you remove it?
Hint:  Look in /etc/X11/xorg.conf.d/


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#11 2020-01-23 13:53:24

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

I found a file /etc/X11/xorg.conf , and renamed it to /etc/X11/xorg.conf.bak. Removing xf86-video-intel now does boot up, however the microfreezes continue, and I'm still getting stuff like:

[  339.754703] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=20072 end=20073) time 123 us, min 2146, max 2159, scanline start 2145, end 2157

in dmesg.

Offline

#12 2020-01-23 20:24:14

loqs
Member
Registered: 2014-03-06
Posts: 9,773

Re: Trying to trace intermittent freezes

Are the issues also present under linux-lts?

Offline

#13 2020-01-24 11:05:48

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

Upgraded to linux 5.4.14.arch1-1 this morning. Seems worse.
Also switched to lts: linux-lts 4.19.98-1

Still seeing freezes. 100% CPU, etc.

Offline

#14 2020-01-24 11:28:28

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

I'm seeing the following from dstat:


1  17  12   0   0|   0     0 | 170k  305B|4.0   0  30|2004M 28.2G  156M 1806M|   0     0 |   0    15G|                      |avahi-daemon 9.6
 70  21   9   0   0|   0  1664k| 124k    0 |7.0   0  15|1999M 28.2G  156M 1802M|   0     0 |   0    15G|chrome        0   764k|avahi-daemon  18
 76  23   1   0   0|   0     0 | 159k  688B| 20   0  24|1997M 28.2G  156M 1799M|   0     0 |   0    15G|                      |avahi-daemon  22
 78  22   0   0   0|   0     0 | 134k  737B| 11   0  25|2033M 28.2G  156M 1835M|   0     0 |   0    15G|                      |avahi-daemon  14 missed 2 ticks
 78  12  10   0   0|   0     0 |  20k    0 |4.0   0 5.0|2034M 28.2G  156M 1836M|   0     0 |   0    15G|                      |avahi-daemon 5.6
 69  13  18   0   0|   0   112k|  80k  328B|4.0   0  30|2032M 28.2G  156M 1831M|   0     0 |   0    15G|chrome        0    80k|avahi-daemon  14
 54  11  35   0   0|   0  1264k|  94k  305B|2.0   0  15|2028M 28.2G  156M 1831M|   0     0 |   0    15G|chrome        0    40k|avahi-daemon 9.0
 61  21  18   0   0|  72k 4008k| 104k 2398B|4.0   0  41|1496M 28.7G  156M 1725M|   0     0 |   0    15G|chrome       16M    0 |chrome        18
 51  11  37   1   0| 128k 4272k| 109k 2936B|1.0   0  34|1138M 29.0G  156M 1527M|   0     0 |   0    15G|                      |avahi-daemon  11
 41  10  49   0   0|   0     0 |  89k    0 |1.0   0  34|1244M 28.9G  156M 1631M|   0     0 |   0    15G|                      |avahi-daemon  12
 32   5  63   0   0|   0     0 | 154k    0 |1.0   0  31|1212M 29.0G  156M 1599M|   0     0 |   0    15G|                      |avahi-daemon  10
 30   4  67   0   0| 160k    0 |  90k    0 |1.0   0  39|1167M 29.0G  156M 1554M|   0     0 |   0    15G|rofi         60k    0 |avahi-daemon  11
 21   2  76   0   0|   0  8192B| 116k    0 |  0   0  38|1167M 29.0G  156M 1554M|   0     0 |   0    15G|                      |avahi-daemon 4.0
 15   1  85   0   0|   0     0 |  61k    0 |  0   0  31|1167M 29.0G  156M 1555M|   0     0 |   0    15G|                      |avahi-daemon 0.9
 17   1  82   0   0|   0   176k|  89k    0 |  0   0  41|1169M 29.0G  156M 1555M|   0     0 |   0    15G|                      |avahi-daemon 1.4
 15   1  84   0   0|   0     0 | 102k    0 |  0   0  31|1167M 29.0G  156M 1554M|   0     0 |   0    15G|                      |avahi-daemon 0.9
 18   1  81   0   0|   0     0 | 102k    0 |  0   0  31|1167M 29.0G  156M 1554M|   0     0 |   0    15G|                      |avahi-daemon 4.9
 18   2  79   2   0| 155M 8192B|  67k    0 |1.0   0  36|1135M 29.0G  156M 1592M|   0     0 |   0    15G|chromium     78M    0 |avahi-daemon 2.1
 35   7  56   2   0|  73M    0 |  99k    0 |2.0   0  79|1186M 28.9G  156M 1629M|   0     0 |   0    15G|chromium     23M   92k|chromium      10
 43  10  45   2   0|  54M  648k| 199k   11k|6.0   0 119|1333M 28.7G  156M 1761M|   0     0 |   0    15G|chromium     22M    0 |chromium      16
 74  24   2   0   0| 144k    0 | 112k 2879B| 17   0  26|1335M 28.7G  156M 1757M|   0     0 |   0    15G|chromium    128k 8192B|avahi-daemon  25
 79  21   0   0   0| 416k   96k| 221k 2710B| 13   0  34|1331M 28.7G  156M 1752M|   0     0 |   0    15G|chromium   1004k    0 |avahi-daemon  43 missed 2 ticks
 81  19   0   0   0|2008k 1896k| 381k 3885B| 11   0  75|1335M 28.7G  156M 1753M|   0     0 |   0    15G|chromium    280k    0 |avahi-daemon 9.6 missed 3 ticks

when running:

 dstat -cdnpmgs --top-bio --top-cpu

It seems to miss ticks during freezes.

Offline

#15 2020-01-24 12:03:33

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,668

Re: Trying to trace intermittent freezes

Can you repro the freezes without the monitor? Could be an issue with the cable.

Offline

#16 2020-01-24 12:09:53

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

@V1del Don't think that's the issue either, as a USB C charger plugged in to the same port (different cable) seems to have the same effect. Without the monitor, the freezes do happen, but last a lot less, so things are "usable".

Offline

#17 2020-01-24 12:30:05

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

Could it be heat related? It's 4.5 years old, so wondering if the thermal paste is needed. How would I go about pinpointing whether it is that or not?

Offline

#18 2020-01-30 10:53:00

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

Any ideas? The issue persists with i915.enable_psr=0. And it only seems to be a notable issue when plugged in. Some more dmesg output:

[ 1521.723725] audit: type=1110 audit(1580379773.444:129): pid=51802 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_tally2,pam_shells,pam_unix,pam_permit,pam_gnome_keyring acct="ashic" exe="/usr/bin/lightdm" hostname=? addr=? terminal=:1 res=success'
[ 1622.766972] audit: type=1131 audit(1580379874.492:130): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@620 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1622.777100] audit: type=1131 audit(1580379874.502:131): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@620 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1820.373930] audit: type=1130 audit(1580380072.107:132): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 1830.614655] audit: type=1131 audit(1580380082.348:133): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[ 2391.931958] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=114179 end=114180) time 131 us, min 2146, max 2159, scanline start 2145, end 2163
[ 2564.041831] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=124505 end=124506) time 91 us, min 2146, max 2159, scanline start 2144, end 2160
[ 2595.678200] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=126403 end=126404) time 129 us, min 2146, max 2159, scanline start 2138, end 2160
[ 2908.202761] perf: interrupt took too long (2925 > 2500), lowering kernel.perf_event_max_sample_rate to 68100
[ 2915.552376] xhci_hcd 0000:3e:00.0: Refused to change power state, currently in D3
[ 2915.628191] xhci_hcd 0000:3e:00.0: Refused to change power state, currently in D3
[ 2915.628246] xhci_hcd 0000:3e:00.0: Controller not ready at resume -19
[ 2915.628252] xhci_hcd 0000:3e:00.0: PCI post-resume error -19!
[ 2915.628269] xhci_hcd 0000:3e:00.0: HC died; cleaning up
[ 2915.628321] xhci_hcd 0000:3e:00.0: remove, state 4
[ 2915.628331] usb usb4: USB disconnect, device number 1
[ 2915.629033] usb 3-1: USB disconnect, device number 2
[ 2915.630267] xhci_hcd 0000:3e:00.0: USB bus 4 deregistered
[ 2915.630282] xhci_hcd 0000:3e:00.0: remove, state 4
[ 2915.630303] usb usb3: USB disconnect, device number 1
[ 2915.631072] xhci_hcd 0000:3e:00.0: Host halt failed, -19
[ 2915.631078] xhci_hcd 0000:3e:00.0: Host not accessible, reset failed.
[ 2915.631540] xhci_hcd 0000:3e:00.0: USB bus 3 deregistered
[ 2915.649881] pci_bus 0000:07: Allocating resources
[ 2915.649928] pcieport 0000:07:02.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 3e] add_size 200000 add_align 100000
[ 2915.649967] pcieport 0000:07:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
[ 2915.649973] pcieport 0000:07:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[ 2915.649987] pcieport 0000:07:02.0: BAR 15: no space for [mem size 0x00200000 64bit pref]
[ 2915.650005] pcieport 0000:07:02.0: BAR 15: failed to assign [mem size 0x00200000 64bit pref]
[ 2915.849112] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPCB.HEC.CHRG], AE_NOT_FOUND (20190816/psargs-330)
[ 2915.849156] ACPI Error: Aborting method \PNOT due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 2915.849580] ACPI Error: Aborting method \_SB.AC._PSR due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
[ 2915.850652] ACPI Error: AE_NOT_FOUND, Error reading AC Adapter state (20190816/ac-115)
[ 2920.600050] pcieport 0000:07:00.0: Refused to change power state, currently in D3
[ 2920.602444] pci_bus 0000:08: busn_res: [bus 08] is released
[ 2920.602573] pci_bus 0000:09: busn_res: [bus 09-3d] is released
[ 2920.602686] pci_bus 0000:3e: busn_res: [bus 3e] is released
[ 2920.604240] pci_bus 0000:07: busn_res: [bus 07-3e] is released

(Note, I'd unplugged the USB C monitor).

Offline

#19 2020-01-30 11:02:33

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

Also, I booted into Windows yesterday... No issues whatsoever.

Offline

#20 2020-01-30 12:57:26

CarbonChauvinist
Member
Registered: 2012-06-16
Posts: 208

Re: Trying to trace intermittent freezes

You've still yet to post a full journal which makes it difficult to help as everything is speculation.

I also have a 5510 - they have Skylake chips and are affected by the recent i915 issue that V1del linked in post #4. Run a 5.5 kernel to avoid those hangs.

You also haven't been clear about how you're disabling the nvidia card.

ashic wrote:

I mostly run on integrated graphics.

Lastly, please edit your posts to add data if no one else has posted in the meantime instead of double/triple-posting.


"the wind-blown way, wanna win? don't play"

Offline

#21 2020-01-30 15:59:10

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

Apologies for not being clear.

1. Here's a jounalctl -b. Since the boot, I unplugged the usb-c charger, and plugged in the usb-c external monitor. A few freezes happened in the meantime. At eachtime, CPU went to 92-100%, and things resumed a few seconds later. Running slack in chrome seems to make it worse, though that could be orthogonal. https://gist.github.com/ashic/6ec4c1960 … f6f581ffbd

2. I'm currently on 5.4.15-arch1-1 . Is there an easy way to try out 5.5?

3. I run on integrated graphics, and have optirun / primusrun kick off required processes on the nvidia. Bumblebee makes it happen, and it's worked fine till a few months ago. (Primusrun still works, the microfreezes are likely orthogonal).

Offline

#22 2020-01-30 17:13:24

loqs
Member
Registered: 2014-03-06
Posts: 9,773

Re: Trying to trace intermittent freezes

To test 5.5 enable the testing repositories.

Offline

#23 2020-02-03 12:09:59

ashic
Member
Registered: 2020-01-22
Posts: 14

Re: Trying to trace intermittent freezes

I'm trying 5.5. The USB-C charger seems to have no problems now. However, the external monitor still gives microfreezes. I'll test with a monitor at home and see if there's any improvement.

Offline

Board footer

Powered by FluxBB