From: Dave Jones <davej@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: David Airlie <airlied@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ben Skeggs <bskeggs@redhat.com>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [3.10rc6] /proc/dri/0/vma broken on nouveau.
Date: Wed, 28 Aug 2013 16:39:18 -0400 [thread overview]
Message-ID: <20130828203918.GB22866@redhat.com> (raw)
In-Reply-To: <CAPM=9twByvO7Ok6TaPa0g3ptHoC_19QU37_jBk1BRQsipOFJ=A@mail.gmail.com>
On Thu, Aug 29, 2013 at 06:35:22AM +1000, Dave Airlie wrote:
> On Thu, Aug 29, 2013 at 6:30 AM, Dave Jones <davej@redhat.com> wrote:
> > On Mon, Aug 05, 2013 at 09:40:33AM +0200, Daniel Vetter wrote:
> > > On Mon, Jul 29, 2013 at 08:53:35PM -0400, Dave Jones wrote:
> > > > On Mon, Jun 17, 2013 at 09:49:27PM -0400, David Airlie wrote:
> > > > >
> > > > > > Reading /proc/dri/0/vma causes bad things to happen on a box with nouveau
> > > > > > loaded.
> > > > > > (Note, no X running on that box)
> > > > > >
> > > > > > Trace below shows trinity, but I can reproduce it with just cat
> > > > > > /proc/dri/0/vma
> > > > >
> > > > > How about this, lets just rip it all out.
> > > >
> > > > No-one objected, and this is still around in 3.11-rc3 in the same
> > > > easily oopsable state.. I vote we kill it with fire.
> > >
> > > Can we make it burn brighter while at it?
> > >
> > > http://cgit.freedesktop.org/~danvet/drm/commit/?h=for-dvdhrm&id=151591c2828e18fde1eb8447874704f3422168b0
> >
> > This went kinda quiet, what's the plan here ?
>
> We nuked it from orbit in drm-next.
Awesome. Looks like that missed a Cc: -stable tag btw.
Dave
prev parent reply other threads:[~2013-08-28 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 1:36 [3.10rc6] /proc/dri/0/vma broken on nouveau Dave Jones
2013-06-18 1:49 ` David Airlie
2013-06-18 1:58 ` Dave Jones
2013-07-30 0:53 ` Dave Jones
2013-08-05 7:40 ` Daniel Vetter
2013-08-28 20:30 ` Dave Jones
2013-08-28 20:35 ` Dave Airlie
2013-08-28 20:39 ` Dave Jones [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=20130828203918.GB22866@redhat.com \
--to=davej@redhat.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.