From: Alexandre Courbot <acourbot@nvidia•com>
To: Matthew Wilcox <willy@linux•intel.com>,
Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Andrew Morton <akpm@linux-foundation•org>,
linux-next@vger•kernel.org,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"dri-devel@lists•freedesktop.org"
<dri-devel@lists•freedesktop.org>
Subject: Re: Issue with DRM and "reimplement IDR and IDA using the radix tree"
Date: Wed, 14 Dec 2016 23:08:20 +0900 [thread overview]
Message-ID: <ca40ae10-2352-9cec-94db-94bca3c14616@nvidia.com> (raw)
In-Reply-To: <fd3db206-8b3e-150f-a060-e88cc2f49606@nvidia.com>
Forgot to add the most relevant list for this issue (linux-next).
Stephen, maybe you will want to temporarily revert this patch until this
is cleared? This probably affects other users than DRM.
On 12/13/2016 04:14 PM, Alexandre Courbot wrote:
> Hi Matthew,
>
> Trying the latest -next on the Jetson TK1 board (with two different DRM
> devices and display and render), I noticed that the GPU device probe
> always failed with error -ENOSPC. After investigating I figured out that
> this was due to the minor device allocation failing when a second DRM
> device is added.
>
> More precisely, when drm_minor_alloc() is called with DRM_MINOR_PRIMARY
> (0) as argument for a second time, the call to idr_alloc() (which has a
> requested range of 0..64) fails instead of returning 1 as expected. Note
> that the first call is successful.
>
> Reverting "reimplement IDR and IDA using the radix tree" on 20161213's
> next fixes the issue for me, suggesting a bug may have slipped in there.
>
> Not sure how this could be fixed, so reporting the issue for now in case
> it is not known yet.
>
> Cheers,
> 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
next parent reply other threads:[~2016-12-14 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd3db206-8b3e-150f-a060-e88cc2f49606@nvidia.com>
2016-12-14 14:08 ` Alexandre Courbot [this message]
2016-12-16 16:16 ` Issue with DRM and "reimplement IDR and IDA using the radix tree" Thierry Reding
2016-12-17 6:47 ` Alexandre Courbot
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=ca40ae10-2352-9cec-94db-94bca3c14616@nvidia.com \
--to=acourbot@nvidia$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=willy@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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