AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom St Denis <tom.stdenis-5C7GfCeVMHo@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: kasan report while running piglit
Date: Tue, 30 Jan 2018 09:23:19 -0500	[thread overview]
Message-ID: <5cf98b49-a1f5-d676-d028-d5b89f860b92@amd.com> (raw)
In-Reply-To: <fa6b0a7d-614e-e1c9-a2b0-1d29f893c8bf-5C7GfCeVMHo@public.gmane.org>

On 22/01/18 01:19 PM, Tom St Denis wrote:
> On 22/01/18 09:03 AM, Tom St Denis wrote:
>> I've rolled back quite a ways from the tip of drm-next (to 
>> 196f74897ba79f6d586894519f09796447d95be5) which is ~1700 commits back 
>> from the tip and still get the attached KASAN report every time.
>>
>> I'm running piglit with DRI_PRIME=1 with the max size memory tests 
>> disabled.
>>
>> Tom
>>
> 
> Should add I don't get the KASAN if I don't use DRI_PRIME=1.  As soon as 
> I run it with DRI_PRIME=1 I get a KASAN error in a manner of seconds 
> (within the first 100 or so tests).


I've found an interesting way of recreating this.  Apparently it is 
triggered when a GL application goes full screen.  For instance,

DRI_PRIME=1 glxgears

works fine but

DRI_PRIME=1 glxgears -fullscreen

will trigger the KASAN report.

Tom
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

      parent reply	other threads:[~2018-01-30 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22 14:03 kasan report while running piglit Tom St Denis
     [not found] ` <a7611e1f-8e7e-8b9c-420a-2ace31e4bcd9-5C7GfCeVMHo@public.gmane.org>
2018-01-22 18:19   ` Tom St Denis
     [not found]     ` <fa6b0a7d-614e-e1c9-a2b0-1d29f893c8bf-5C7GfCeVMHo@public.gmane.org>
2018-01-30 14:23       ` Tom St Denis [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=5cf98b49-a1f5-d676-d028-d5b89f860b92@amd.com \
    --to=tom.stdenis-5c7gfcevmho@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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