linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	jani.nikula@linux.intel.com, rodrigo.vivi@intel.com,
	intel-gfx@lists.freedesktop.org, chris@chris-wilson.co.uk
Subject: v4.20-rc5+ on x220: Resetting chip for hang on rcs0
Date: Sun, 9 Dec 2018 12:18:56 +0100	[thread overview]
Message-ID: <20181209111856.GA20366@amd> (raw)
In-Reply-To: <20181208112447.GA9663@amd>


[-- Attachment #1.1: Type: text/plain, Size: 1286 bytes --]


Hi!

Another day, another problem... but this one is different from the
previous hang, as machine survives.

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
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #1.2: delme.gz --]
[-- Type: application/gzip, Size: 22379 bytes --]

[-- Attachment #1.3: delme2.gz --]
[-- Type: application/gzip, Size: 2546 bytes --]

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2018-12-09 11:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 17:58 v4.20-rc1: list_del corruption on thinkpad x220 Pavel Machek
2018-11-21 11:19 ` Joonas Lahtinen
2018-11-21 11:54   ` Pavel Machek
2018-11-23  8:17     ` Joonas Lahtinen
2018-11-24 15:23       ` Pavel Machek
2018-12-08 11:13         ` v4.20-rc1: list_del corruption on thinkpad x220, graphics related? Pavel Machek
2018-12-08 11:24           ` Pavel Machek
2018-12-09 11:18             ` Pavel Machek [this message]
2018-12-10  8:30               ` v4.20-rc5+ on x220: Resetting chip for hang on rcs0 Joonas Lahtinen
2018-12-10  8:28             ` v4.20-rc1: list_del corruption on thinkpad x220, graphics related? Joonas Lahtinen
2018-12-12 18:29               ` 4.20.0-rc6-next-20181210, " Pavel Machek
2018-12-13  8:29                 ` Joonas Lahtinen
2018-12-27  8:34                   ` [regression from v4.19] " Pavel Machek
2019-01-02  9:34                     ` Joonas Lahtinen
2019-01-02 21:02                       ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181209111856.GA20366@amd \
    --to=pavel@ucw.cz \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).