mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Christian König" <christian.koenig@amd.com>
Cc: amd-gfx@lists.freedesktop.org,
	Alex Deucher <alexander.deucher@amd.com>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: radeon 0000:1d:00.0: GPU lockup (current fence id 0x00000000010da43f last fence id 0x00000000010da52d on ring 0)
Date: Wed, 6 Jun 2018 11:52:02 +0200	[thread overview]
Message-ID: <20180606095201.GA10840@zn.tnic> (raw)
In-Reply-To: <7921bc34-6e63-7869-0695-70baf9d480a1@amd.com>

On Wed, Jun 06, 2018 at 10:26:15AM +0200, Christian König wrote:
> Well what did you do to trigger the lockup? Looks like an application send
> something to the hardware to crash the GFX block.

So what I observed was (in that order): machine was building a kernel so
was busy, X didn't respond for a couple of seconds (which it should not
do) and I switched to tty8 to see what dmesg says (I am routing dmesg to
tty8).

At that moment it showed the lockup splat and then X restarted showing
me the login prompt again. I'm guessing the X restart was caused by the
GPU reset.

So if I had to guess, maybe pressing Ctrl+Alt+F8 caused the modeset
change and thus reset? Hmm, this is just me guessing with my
non-knowledge about graphics. :)

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

      reply	other threads:[~2018-06-06  9:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 14:44 Borislav Petkov
2018-06-06  8:11 ` Huang Rui
2018-06-06  8:26 ` Christian König
2018-06-06  9:52   ` Borislav Petkov [this message]

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=20180606095201.GA10840@zn.tnic \
    --to=bp@alien8.de \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®