AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Przemek Socha <soprwa-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Koenig,
	Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>,
	amd-gfx list
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
	"Daenzer, Michel" <Michel.Daenzer-5C7GfCeVMHo@public.gmane.org>,
	"Zhang, Jerry" <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>,
	"Huang, Ray" <Ray.Huang-5C7GfCeVMHo@public.gmane.org>
Subject: Re: amd-staging-drm-next, CIK apu, [TTM] Erroneous page count. Leaking pages. [BISECTED]
Date: Thu, 11 Apr 2019 20:41:30 +0200	[thread overview]
Message-ID: <3663873.0cdN12EykA@eclipse> (raw)
In-Reply-To: <97bc37a4-f6fc-30f8-c6ff-554fa04cb03e-5C7GfCeVMHo@public.gmane.org>


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

Dnia czwartek, 11 kwietnia 2019 19:31:27 CEST piszesz:
> Yeah, that is a known issue and already fixed in amd-staging-drm-next.
> 
> You just need to wait for the public mirror to update.
> 
> Christian.
> 
> Am 11.04.19 um 18:53 schrieb Przemek Socha:
> 
> > Hi All,
> > after today's sync with amd-staging-drm-next branch I have problems with
> > my
 Mullins APU Netbook.
> > Kernel log is flooded with "[TTM] Erroneous page count. Leaking pages."
> > message.
> >
> >
> >
> > Bisected, and it seems that "drm/ttm: fix start page for huge page check
> > in
 ttm_put_pages()" commit is causing this.
> >
> >
> >
> > git bisect log:
> > git bisect start
> > # good: [c2af9f9e84183a4dbcb53a74abbe3362dc181682] drm/amd/display: fix
> > cursor
 black issue
> > git bisect good c2af9f9e84183a4dbcb53a74abbe3362dc181682
> > # bad: [b07c394a327fc9e435ee03288584c111fa73d963] drm/amd/display: fix is
> > odm
 head pipe logic
> > git bisect bad b07c394a327fc9e435ee03288584c111fa73d963
> > # bad: [367fa96ad66fef31bf73916cf4949c475f42563f] drm/amd/display: use
> > proper
 formula to calculate bandwidth from timing
> > git bisect bad 367fa96ad66fef31bf73916cf4949c475f42563f
> > # good: [94275c6d27deebbce5055e1bb1959986051b93f2] drm/amdgpu: Add a check
> > to
 avoid panic because of unexpected irqs
> > git bisect good 94275c6d27deebbce5055e1bb1959986051b93f2
> > # bad: [8198a32b1211c6f625623bae22629cf852531097] drm/amd/display:
> > Initialize
 stream_update with memset
> > git bisect bad 8198a32b1211c6f625623bae22629cf852531097
> > # bad: [e16858a7e6e7dc00345703682d490b96f2883b99] drm/ttm: fix start page
> > for
 huge page check in ttm_put_pages()
> > git bisect bad e16858a7e6e7dc00345703682d490b96f2883b99
> > # good: [b414dfd1f975bbf4c9ee4600f9bedcf77bae84ed] drm/ttm: fix
> > out-of-bounds
 read in ttm_put_pages() v2
> > git bisect good b414dfd1f975bbf4c9ee4600f9bedcf77bae84ed
> > # first bad commit: [e16858a7e6e7dc00345703682d490b96f2883b99] drm/ttm:
> > fix
 start page for huge page check in ttm_put_pages()
> >
> >
> >
> > e16858a7e6e7dc00345703682d490b96f2883b99 is the first bad commit
> > commit e16858a7e6e7dc00345703682d490b96f2883b99
> > Author: Christian König <christian.koenig-5C7GfCeVMHo@public.gmane.org>
> > Date:   Tue Apr 2 09:29:35 2019 +0200
> >
> >
> >
> >      drm/ttm: fix start page for huge page check in ttm_put_pages()
> >      
> >      The first page entry is always the same with itself.
> >      
> >      Signed-off-by: Christian König <christian.koenig-5C7GfCeVMHo@public.gmane.org>
> >      Reviewed-by: Michel Dänzer <michel.daenzer-5C7GfCeVMHo@public.gmane.org>
> >      Reviewed-by: Junwei Zhang <Jerry.Zhang-5C7GfCeVMHo@public.gmane.org>
> >      Reviewed-by: Huang Rui <ray.huang-5C7GfCeVMHo@public.gmane.org>
> >
> >
> >
> > Any help is appreciated.
> > Thanks,
> > Przemek.
> 
> 

Thanks, and sorry about all the fuss.
Przemek.

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

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

      parent reply	other threads:[~2019-04-11 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-11 16:53 amd-staging-drm-next, CIK apu, [TTM] Erroneous page count. Leaking pages. [BISECTED] Przemek Socha
2019-04-11 17:31 ` Koenig, Christian
     [not found]   ` <97bc37a4-f6fc-30f8-c6ff-554fa04cb03e-5C7GfCeVMHo@public.gmane.org>
2019-04-11 18:41     ` Przemek Socha [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=3663873.0cdN12EykA@eclipse \
    --to=soprwa-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
    --cc=Jerry.Zhang-5C7GfCeVMHo@public.gmane.org \
    --cc=Michel.Daenzer-5C7GfCeVMHo@public.gmane.org \
    --cc=Ray.Huang-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