Arch Linux

ktfh

Member

Registered: 2014-01-03

Posts: 7

frequent segfaults caused by gpu

Everything seems stable on start up but as programs run longer they become more likely to segfault. Tabs in chromium begin to segfault constantly and Firefox crashes almost as soon as its opened and all other programs crash but more sporadically. I am not sure how to resolve this or even determine if its hardware failing or a driver problem. I also cant think of any specific update this behavior coincided with.

journalctl

Mar 30 20:27:09 localhost kernel: [drm] stuck on render ring
Mar 30 20:27:09 localhost kernel: [drm] stuck on blitter ring
Mar 30 20:27:09 localhost kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mar 30 20:27:09 localhost kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 30 20:27:09 localhost kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 30 20:27:09 localhost kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 30 20:27:09 localhost kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
Mar 30 20:35:50 localhost kernel: [drm] stuck on render ring
Mar 30 21:03:09 localhost kernel: perf samples too long (5013 > 4990), lowering kernel.perf_event_max_sample_rate to 25200
Mar 30 21:33:19 localhost kernel: [drm] stuck on render ring
Mar 30 21:33:19 localhost kernel: [drm] stuck on blitter ring
Mar 30 21:54:33 localhost kernel: chromium[3277]: segfault at 382694104228 ip 00007fb789250850 sp 00007fffeff00968 error 4 in chromium[7fb787a9f000+535e000]
Mar 30 21:55:31 localhost kernel: chromium[3288]: segfault at 372b5c504120 ip 00007fb7893ab5ec sp 00007fffeff001b0 error 4 in chromium[7fb787a9f000+535e000]
Mar 30 21:55:35 localhost kernel: chromium[3202]: segfault at 3387e7ded2a8 ip 00007fb78bab8481 sp 00007fffeff01210 error 4 in chromium[7fb787a9f000+535e000]
Mar 30 21:57:10 localhost kernel: chromium[3311]: segfault at 3a8e6e00018 ip 00007fb789326320 sp 00007fffeff00af0 error 4 in chromium[7fb787a9f000+535e000]
Mar 30 22:06:25 localhost systemd-coredump[3377]: Core too large, core will not be stored.
Mar 30 22:06:25 localhost systemd-coredump[3377]: Process 512 (firefox) dumped core.
Mar 30 22:14:40 localhost kernel: chromium[3069]: segfault at 3279a2c0422b ip 00007fb78929ec12 sp 00007fffeff00cf0 error 4 in chromium[7fb787a9f000+535e000]
Mar 30 23:25:20 localhost kernel: chromium[3817]: segfault at bf4c2b088c3 ip 00007fb7892b5ddd sp 00007fffefeff450 error 4 in chromium[7fb787a9f000+535e000]
Mar 30 23:44:09 localhost kernel: [drm] stuck on render ring
Mar 30 23:44:09 localhost kernel: [drm] stuck on blitter ring
Mar 30 23:47:02 localhost kernel: chromium[4453]: segfault at 17a1bc681a20 ip 00003795c7384b5f sp 00007ffffff5ae20 error 4
Mar 30 23:47:54 localhost org.gtk.Private.UDisks2VolumeMonitor[406]: ### debug: Name owner ':1.0' vanished
Mar 30 23:56:07 localhost kernel: [drm] stuck on render ring
Mar 30 23:56:07 localhost kernel: [drm] stuck on blitter ring
Mar 30 23:57:56 localhost kernel: [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
Mar 30 23:59:12 localhost kernel: OptimizingCompi[4442]: segfault at 22b26f3581e8 ip 00007f74e550ffd6 sp 00007f74cf35f820 error 4 in chromium[7f74e3c63000+535e

Mar 31 11:30:00 localhost kernel: sd_festival[2074]: segfault at 2d0 ip 00007f39797181a1 sp 00007fffa4a23620 error 4 in libpthread-2.19.so[7f397970b000+18000]
Mar 31 11:30:00 localhost systemd-coredump[2075]: Process 2074 (sd_festival) dumped core.
Mar 31 11:42:19 localhost kernel: hda-intel 0000:00:1b.0: Unstable LPIB (130816 >= 8192); disabling LPIB delay counting

Mar 31 12:39:25 localhost kernel: chromium[3933]: segfault at 7 ip 00007f3c68d85850 sp 00007fff2eb122e8 error 4 in chromium[7f3c675d4000+535e000]
Mar 31 12:39:29 localhost kernel: traps: chromium[3944] trap int3 ip:7f3c69039db1 sp:7fff2eb10090 error:0
Mar 31 12:39:33 localhost kernel: chromium[3954]: segfault at 336f41100019 ip 00007f3c68ea4f44 sp 00007fff2eb120d0 error 4 in chromium[7f3c675d4000+535e000]
Mar 31 12:39:36 localhost kernel: chromium[3964]: segfault at 3cbf7ade94c8 ip 00007f3c68eb892d sp 00007fff2eb0f9b0 error 4 in chromium[7f3c675d4000+535e000]
Mar 31 12:39:39 localhost kernel: chromium[3974]: segfault at 21386a114618 ip 00007f3c68b5994e sp 00007fff2eb10990 error 4 in chromium[7f3c675d4000+535e000]
Mar 31 12:41:39 localhost systemd-coredump[4014]: Core too large, core will not be stored.
Mar 31 12:41:39 localhost systemd-coredump[4014]: Process 2445 (firefox) dumped core.

dmesg

[ 2613.072555] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[ 2708.304598] fuse init (API version 7.22)
[ 9735.567941] sd_festival[2074]: segfault at 2d0 ip 00007f39797181a1 sp 00007fffa4a23620 error 4 in libpthread-2.19.so[7f397970b000+18000]
[10475.945708] hda-intel 0000:00:1b.0: Unstable LPIB (130816 >= 8192); disabling LPIB delay counting
[11723.649327] perf samples too long (2504 > 2500), lowering kernel.perf_event_max_sample_rate to 50100
[13905.253065] chromium[3933]: segfault at 7 ip 00007f3c68d85850 sp 00007fff2eb122e8 error 4 in chromium[7f3c675d4000+535e000]
[13909.634254] traps: chromium[3944] trap int3 ip:7f3c69039db1 sp:7fff2eb10090 error:0
[13913.730004] chromium[3954]: segfault at 336f41100019 ip 00007f3c68ea4f44 sp 00007fff2eb120d0 error 4 in chromium[7f3c675d4000+535e000]
[13915.862660] chromium[3964]: segfault at 3cbf7ade94c8 ip 00007f3c68eb892d sp 00007fff2eb0f9b0 error 4 in chromium[7f3c675d4000+535e000]
[13919.066996] chromium[3974]: segfault at 21386a114618 ip 00007f3c68b5994e sp 00007fff2eb10990 error 4 in chromium[7f3c675d4000+535e000]
[14215.534298] chromium[977]: segfault at 2000000000 ip 0000002000000000 sp 00007fff692bfa08 error 14
[14217.307167] systemd-journald[111]: Failed to write entry (26 items, 386401146 bytes) despite vacuuming, ignoring: Argument list too long
[14509.223324] chromium[4025]: segfault at da8c6900018 ip 00007f3c68e5b320 sp 00007fff2eb12e50 error 4 in chromium[7f3c675d4000+535e000]
[14519.290360] chromium[4121]: segfault at 18 ip 00007f3c68e5b320 sp 00007fff2eb12390 error 4 in chromium[7f3c675d4000+535e000]
[14604.753564] chromium[4151]: segfault at 2cbeb1c39c98 ip 00007f3c68d8f048 sp 00007fff2eb12710 error 4 in chromium[7f3c675d4000+535e000]
[16026.958004] chromium[4099]: segfault at 35a580a2dd38 ip 00007fc7d938f0f0 sp 00007fff1da1bcb8 error 4 in libdrm_intel.so.1.0.0[7fc7d9387000+1f000]
[16027.994823] systemd-journald[111]: Deleted empty journal /var/log/journal/234c2db5e4bf46a8bb2f0fb78faa84fa/user-1000@30f2b243e195478281feadb923f17493-0000000000000000-0000000000000000.journal (8392704 bytes).
[16028.263903] systemd-journald[111]: Failed to write entry (26 items, 297673596 bytes) despite vacuuming, ignoring: Argument list too long
[16043.277605] chromium[4274]: segfault at 1e3883f586c0 ip 000029973f143167 sp 00007fff2eb11f18 error 4

lshw -c video

  *-display               
       description: VGA compatible controller
       product: 2nd Generation Core Processor Family Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:48 memory:f5000000-f53fffff memory:e0000000-efffffff ioport:e000(size=64)

vainfo

libva info: VA-API version 0.35.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.35 (libva 1.3.0)
vainfo: Driver version: Intel i965 driver - 1.3.0
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            : VAEntrypointVLD
      VAProfileMPEG2Main              : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main               : VAEntrypointVLD
      VAProfileH264Main               : VAEntrypointEncSlice
      VAProfileH264High               : VAEntrypointVLD
      VAProfileH264High               : VAEntrypointEncSlice
      VAProfileVC1Simple              : VAEntrypointVLD
      VAProfileVC1Main                : VAEntrypointVLD
      VAProfileVC1Advanced            : VAEntrypointVLD
      VAProfileNone                   : VAEntrypointVideoProc

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,196

Re: frequent segfaults caused by gpu

Mar 30 20:27:09 localhost kernel: [drm] stuck on render ring
Mar 30 20:27:09 localhost kernel: [drm] stuck on blitter ring
Mar 30 20:27:09 localhost kernel: [drm] GPU crash dump saved to /sys/class/drm/card0/error
Mar 30 20:27:09 localhost kernel: [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
Mar 30 20:27:09 localhost kernel: [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
Mar 30 20:27:09 localhost kernel: [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
Mar 30 20:27:09 localhost kernel: [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

Looks like a driver / software problem to me, i suggest you follow the advice above and register a bugreport.

Check you pacman log for recent updates for the kernel , mesa and xf86-video-intel .
Either of them could be the cause.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

ktfh

Member

Registered: 2014-01-03

Posts: 7

Re: frequent segfaults caused by gpu

Seems my ram was bad, since replacing it the segfaults stopped happening.