linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Grodzovsky, Andrey" <Andrey.Grodzovsky@amd.com>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: "Wentland, Harry" <Harry.Wentland@amd.com>,
	"Deucher, Alexander" <Alexander.Deucher@amd.com>,
	"Koenig, Christian" <Christian.Koenig@amd.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: After Vega 56/64 GPU hang I unable reboot system
Date: Wed, 9 Jan 2019 20:35:07 +0000	[thread overview]
Message-ID: <5a53e55f-91cf-759e-b52b-f4681083d639@amd.com> (raw)
In-Reply-To: <CABXGCsPPjz57=Et-V-_iGyY0GrEwfcK2QcRJcqiujUp90zaz-g@mail.gmail.com>



On 01/09/2019 02:36 PM, Mikhail Gavrilov wrote:
> On Mon, 7 Jan 2019 at 23:47, Grodzovsky, Andrey
> <Andrey.Grodzovsky@amd.com> wrote:
>> I see 'no active waves' print meaning it's not shader hang.
>>
>> We can try and estimate around which commands the hang occurred - in
>> addition to what you already print please also dump
>>
>> sudo umr -O many,bits  -r *.*.mmGRBM_STATUS* && sudo umr -O many,bits
>> -r *.*.mmCP_EOP_* && sudo umr -O many,bits -r *.*.mmCP_PFP_HEADER_DUMP
>> && sudo umr -O many,bits  -r *.*.mmCP_ME_HEADER_DUMP
>>
>> Andrey
>>
> All new one logs attached here.
>
> Thanks.
>
> P.S. This time I had to terminate command `./umr -O verbose,follow -R
> gfx[.] > gfx.log 2>&1` cause it tried to write log infinitely.
> I also had to terminate command `./umr -O verbose,follow -R gfx[.] >
> gfx.log 2>&1` cause it stuck for a long time.
>
>
> --
> Best Regards,
> Mike Gavrilov.

I think the 'verbose' flag causes it do dump so much output, maybe try without it in ALL the commands above.
Are you are aware of any particular application during which run this happens ?

Andrey



  reply	other threads:[~2019-01-09 20:35 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 22:18 Mikhail Gavrilov
2018-12-14 19:36 ` Wentland, Harry
2018-12-15  9:42   ` Mikhail Gavrilov
2018-12-17 18:51     ` Wentland, Harry
2018-12-17 19:08       ` Grodzovsky, Andrey
2018-12-19 18:35         ` Mikhail Gavrilov
2018-12-19 20:21           ` Grodzovsky, Andrey
2018-12-19 20:51             ` StDenis, Tom
2018-12-19 20:56             ` StDenis, Tom
2018-12-19 21:14               ` Mikhail Gavrilov
2018-12-19 21:21                 ` Mikhail Gavrilov
2018-12-19 22:41                   ` StDenis, Tom
2018-12-20  3:29                     ` Mikhail Gavrilov
2018-12-20 11:17                       ` StDenis, Tom
2018-12-20 11:45                         ` Mikhail Gavrilov
2018-12-20 14:06                           ` StDenis, Tom
2018-12-20 14:08                             ` StDenis, Tom
2018-12-20 14:19                               ` StDenis, Tom
     [not found]                                 ` <96c70496-ce62-b162-187c-ff34ebb84ec2-5C7GfCeVMHo@public.gmane.org>
2018-12-20 16:07                                   ` Mikhail Gavrilov
2018-12-20 16:20                                     ` StDenis, Tom
2018-12-22 10:28                                       ` Mikhail Gavrilov
2018-12-22 10:28                                         ` Mikhail Gavrilov
2019-01-03 20:23         ` Mikhail Gavrilov
2019-01-04 17:50           ` Mikhail Gavrilov
2019-01-07 18:46             ` Grodzovsky, Andrey
2019-01-09 19:36               ` Mikhail Gavrilov
2019-01-09 20:35                 ` Grodzovsky, Andrey [this message]
2019-01-09 21:12                   ` Mikhail Gavrilov
2019-01-09 21:12                     ` Mikhail Gavrilov
2019-01-09 21:48                     ` Grodzovsky, Andrey
2019-01-10  4:04                       ` Mikhail Gavrilov
2019-01-10  8:54                     ` Michel Dänzer
2019-01-10  9:42                       ` Mikhail Gavrilov
2019-01-10  9:42                         ` Mikhail Gavrilov
2019-01-10 10:38                         ` Michel Dänzer
2019-01-10 15:22                 ` Mikhail Gavrilov
2019-01-10 15:22                   ` Mikhail Gavrilov
2019-01-10 15:31                   ` StDenis, Tom

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=5a53e55f-91cf-759e-b52b-f4681083d639@amd.com \
    --to=andrey.grodzovsky@amd.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Harry.Wentland@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=linux-mm@kvack.org \
    --cc=mikhail.v.gavrilov@gmail.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