dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Alex Deucher <alexdeucher@gmail.com>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Hardware 3D acceleration doesn't work anymore with the latest git kernel
Date: Tue, 21 Nov 2017 12:32:15 +0100	[thread overview]
Message-ID: <ca5f1eec-e6e3-739d-277c-4c7c1401077f@xenosoft.de> (raw)
In-Reply-To: <CADnq5_PES3KQRqX6y+=FQsA_Sadqf3C=bNekMj3c+6mpvwpnRw@mail.gmail.com>

Alex,

Thanks for your fast reply. I have looked in the first bad commit 
e60e1ee60630cafef5e430c2ae364877e061d980 (Merge tag 'drm-for-v4.15') [1].
I have found a lot of kzalloc changes. I am sorry, I don't have any 
experiences with this code. I only know that my Radeon HD6870 doesn't 
have hardware 3D acceleration anymore.

Maybe I could revert the drm_gem_object_init and ttm_bo_init changes but 
the kzalloc changes are too much. I think I need help to solve this issue.

Thanks,
Christian


[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e60e1ee60630cafef5e430c2ae364877e061d980


On 21 November 2017 at 05:38AM, Alex Deucher wrote:
>
> If you look at the code, radeon_bo_create() is failing with -ENOMEM in
> radeon_wb_init().  If you look at radeon_bo_create(), it can fail for
> the following reasons:
> 1. kzalloc fails
> 2. drm_gem_object_init fails
> 3. ttm_bo_init fails
>
> I'd start by looking into what's changed in those areas.
>
> Alex
>
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel


_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-11-21 11:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 18:08 Hardware 3D acceleration doesn't work anymore with the latest git kernel Christian Zigotzky
2017-11-21  4:38 ` Alex Deucher
2017-11-21 11:32   ` Christian Zigotzky [this message]
2017-11-22 13:20   ` Christian Zigotzky
2017-11-22 13:27     ` Ilia Mirkin
2017-11-22 13:40       ` Christian Zigotzky
2017-11-22 13:45         ` Ilia Mirkin
2017-11-22 14:53           ` Christian Zigotzky
2017-11-24 14:29           ` Christian Zigotzky
2017-11-24 16:09             ` Michel Dänzer
2017-11-24 19:08               ` Christian Zigotzky
2017-11-24 19:13                 ` Christian Zigotzky
2017-11-24 19:14                 ` Ilia Mirkin
2017-11-24 20:58                   ` Christian Zigotzky
2017-11-27 11:02               ` Michel Dänzer
2017-11-27 11:50                 ` Christian König
2017-11-27 12:02                   ` Michel Dänzer
2017-11-27 12:17                     ` Tom St Denis
2017-11-27 14:53                       ` Michel Dänzer
2017-11-28  5:43                         ` Christian Zigotzky
2017-11-28  9:40                           ` Michel Dänzer
2017-11-28 23:48                             ` Christian Zigotzky
2017-11-27 12:20                     ` Christian König
2017-11-29  8:50                       ` Michel Dänzer

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=ca5f1eec-e6e3-739d-277c-4c7c1401077f@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=alexdeucher@gmail.com \
    --cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).