[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <76ccd79ddff183113a4cc972e6a8cc1c8bb29a05.camel@linux.intel.com>
Date: Mon, 10 Dec 2018 10:30:08 +0200
From: Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>
To: Pavel Machek <pavel@....cz>
Cc: kernel list <linux-kernel@...r.kernel.org>,
jani.nikula@...ux.intel.com, rodrigo.vivi@...el.com,
intel-gfx@...ts.freedesktop.org, chris@...is-wilson.co.uk
Subject: Re: v4.20-rc5+ on x220: Resetting chip for hang on rcs0
On Sun, 2018-12-09 at 12:18 +0100, Pavel Machek wrote:
> Hi!
>
> Another day, another problem... but this one is different from the
> previous hang, as machine survives.
Please, file a bug. It says so even in the splat...
Regards, Joonas
>
> Chromium was running with youtube video playing.
>
> [31850.666274] [drm] GPU hangs can indicate a bug anywhere in the
> entire gfx stack, including userspace.
> [31850.666277] [drm] Please file a _new_ bug report on
> bugs.freedesktop.org against DRI -> DRM/Intel
> [31850.666279] [drm] drm/i915 developers can then reassign to the
> right component if it's not a kernel issue.
> [31850.666282] [drm] The gpu crash dump is required to analyze gpu
> hangs, so please always attach it.
> [31850.666285] [drm] GPU crash dump saved to
> /sys/class/drm/card0/error
> [31850.666394] i915 0000:00:02.0: Resetting chip for hang on rcs0
> [31850.668474] WARNING: CPU: 0 PID: 13675 at
> /data/fast/l/k/include/linux/dma-fence.h:503
> i915_request_skip+0x71/0x80
> [31850.668478] Modules linked in:
> [31850.668484] CPU: 0 PID: 13675 Comm: kworker/0:3 Not tainted
> 4.20.0-rc5+ #5
> [31850.668487] Hardware name: LENOVO 42872WU/42872WU, BIOS 8DET74WW
> (1.44 ) 03/13/2018
>
> Dmesg and /sys/class/drm/card0/error are attached.
>
> Best regards,
> Pavel
--
Joonas Lahtinen
Open Source Graphics Center
Intel Corporation
Powered by blists - more mailing lists