Skip to contentSkip to conversation

5.8-rc2: X hangs due to drm problem (on thinkpad x220)

DISCUSSION Pavel Machek 1 participant 1 message Jun 30, 2020

lore
Share & tools
lore
#0 lore raw

Hi!

[221198.058766] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),task=chromium,pid=3612,uid=1000
[221198.058804] Out of memory: Killed process 3612 (chromium) total-vm:2677236kB, anon-rss:95868kB, file-rss:0kB, shmem-rss:1390212kB, UID:1000 pgtables:4104kB oom_score_adj:200
[221198.123441] oom_reaper: reaped process 3612 (chromium), now anon-rss:16kB, file-rss:0kB, shmem-rss:1380368kB
[223149.407523] perf: interrupt took too long (10405 > 10375), lowering kernel.perf_event_max_sample_rate to 19000
[223351.853087] perf: interrupt took too long (13074 > 13006), lowering kernel.perf_event_max_sample_rate to 15250
[223652.320162] perf: interrupt took too long (16350 > 16342), lowering kernel.perf_event_max_sample_rate to 12000
[223998.558829] perf: interrupt took too long (20625 > 20437), lowering kernel.perf_event_max_sample_rate to 9500
[224119.659585] Adding 1681428k swap on /dev/sda1.  Priority:-2 extents:1 across:1681428k 
[224452.285193] perf: interrupt took too long (25999 > 25781), lowering kernel.perf_event_max_sample_rate to 7500
[225248.349100] i915 0000:00:02.0: [drm] Resetting chip for stopped heartbeat on rcs0
[225248.452665] i915 0000:00:02.0: [drm] chromium[719] context reset due to GPU hang

Ok, so... cat drm/card0/error, they said? Well... no. It says "can not allocate memory". Swap is unused and there are 3.5G free AFAICT.

pavel@duo:~$ sudo cat /sys/devices/pci0000:00/0000:00:02.0/drm/card0/error
cat: '/sys/devices/pci0000:00/0000:00:02.0/drm/card0/error': Cannot allocate memory
pavel@duo:~$ free
              total        used        free      shared  buff/cache   available
Mem:        5973704     1802036      987008      430904     3184660     3654380
Swap:       1681428           8     1681420

(And yes, this is same machine from [Intel-gfx] v5.8-rc1 on thinkpad x220, intel graphics: interface frozen, can still switch to text console thread, and hang looks very similar).

Any ideas?

Is it possible that there's some kind of memory leak in graphics subsystem? I suspected leak in chromium, but this time I restarted chromium, and did swapoff / swapon, and machine was ... still pretty unusable, culminating with hang of graphics. Text console still works.

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html