Attachment 101823 Details for Bug 80568 – dmesg tail after GPU crash

dmesg tail after GPU crash

dmesgtail (text/plain), 2.31 KB, created by haineb on 2014-06-26 18:50:19 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: haineb

Created: 2014-06-26 18:50:19 UTC

Size: 2.31 KB

patch

obsolete

>[   14.772247] Bluetooth: SCO socket layer initialized
>[   14.775546] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>[   14.775549] Bluetooth: BNEP filters: protocol multicast
>[   14.775555] Bluetooth: BNEP socket layer initialized
>[   14.777163] Bluetooth: RFCOMM TTY layer initialized
>[   14.777168] Bluetooth: RFCOMM socket layer initialized
>[   14.777173] Bluetooth: RFCOMM ver 1.11
>[   15.250836] init: cups main process (812) killed by HUP signal
>[   15.250849] init: cups main process ended, respawning
>[   17.034308] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
>[   17.040682] init: samba-ad-dc main process (853) terminated with status 1
>[   17.140074] e1000e 0000:00:19.0: irq 48 for MSI/MSI-X
>[   17.140183] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>[   17.140472] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
>[   18.476363] init: plymouth-upstart-bridge main process ended, respawning
>[   18.481296] init: plymouth-upstart-bridge main process (1296) terminated with status 1
>[   18.481307] init: plymouth-upstart-bridge main process ended, respawning
>[   18.736883] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
>[   18.736991] e1000e 0000:00:19.0 eth0: 10/100 speed: disabling TSO
>[   18.737020] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>[ 1471.805010] perf samples too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
>[13018.934783] [drm] GPU crash dump saved to /sys/class/drm/card0/error
>[13018.934788] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
>[13018.934789] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
>[13018.934790] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
>[13018.934791] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
>[93914.820026] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... render ring idle
>[93927.368042] Watchdog[10549]: segfault at 0 ip 00007f8cfed32b4e sp 00007f8cee758670 error 6 in chrome[7f8cfad41000+4f39000]
>[93951.462185] Watchdog[10761]: segfault at 0 ip 00007fac560d0b4e sp 00007fac45af6670 error 6 in chrome[7fac520df000+4f39000]
>[93961.505812] Watchdog[10810]: segfault at 0 ip 00007f8075c05b4e sp 00007f806562b670 error 6 in chrome[7f8071c14000+4f39000]

Actions: View

Attachments on bug 80568: 101821 | 101823 | 109501 | 109502 | 109507 | 109509 | 109510 | 109667 | 109788 | 112888 | 112956

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.