From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Kees Bakker <kees.bakker@xs4all.nl>
Cc: linux-kernel@vger.kernel.org,
Maarten Lankhorst <maarten.lankhorst@canonical.com>
Subject: Re: drm/nouveau E[ DRM] fail ttm_validate
Date: Sat, 5 Jan 2013 14:59:25 +0100 [thread overview]
Message-ID: <20130105135925.GA3131@joi.lan> (raw)
In-Reply-To: <50E748C7.10202@xs4all.nl>
On Fri, Jan 04, 2013 at 10:25:27PM +0100, Kees Bakker wrote:
> On 04-01-13 18:49, Marcin Slusarz wrote:
> > On Fri, Jan 04, 2013 at 01:21:14PM +0100, Kees Bakker wrote:
> >> Hi,
> >>
> >> Right after I upgraded to Ubuntu quantal I started seeing these
> >> messages:
> >> Jan 4 12:18:12 koli kernel: [ 3705.970720] nouveau E[ DRM] fail ttm_validate
> >> Jan 4 12:18:12 koli kernel: [ 3705.970726] nouveau E[ DRM] validate vram_list
> >> Jan 4 12:18:12 koli kernel: [ 3705.970760] nouveau E[ DRM] validate: -12
> > This is userspace bug. See below.
> >
> >> A few times I had corrupted graphics, and I had to stop X. Restarting didn't
> >> help and I had to reboot.
> >>
> >> I'm running my own 3.7.1 kernel, so I also installed the 3.7.0 development kernel
> >> from Ubuntu (3.7.0-7). And that kernel shows these messages too.
> >>
> >> With the Ubuntu kernel the graphics corruption is milder. I can continue to work. Sometimes
> >> I get a burst of the messages, but I have no clue how it is triggered.
> >>
> >> Now the strange thing is that I was running my 3.7.1 kernel on Ubuntu precise
> >> and I have never seen these messages before. What could be the case is that
> >> xorg is doing something new and that is causing the errors.
> >>
> >> xserver-xorg-video-nouveau
> >> precise 1:1.0.2-0ubuntu3
> >> quantal 1:0.0.16+git20111201+b5534a1-1build2
> > (Please do not use distro codenames when reporting bugs upstream)
> >
> > Quantal, being newer release than Precise, ships much older Nouveau DDX, WTF?
> > You used some PPA with Precise?
> Sorry about that. That was a typo. I meant to say:
> quantal 1:1.0.2-0ubuntu3
> precise 1:0.0.16+git20111201+b5534a1-1build2
>
> >
> > 0.0.16 is known to behave like that - you need to upgrade to >= 1.0.
>
> In other words, I have >= 1.0. But you suggest that it shouldn't
> happen with >= 1.0
> Should I report it on the nouveau list at freedesktop.org ?
Ugh, it was unexpected :/
Please follow instructions from http://nouveau.freedesktop.org/wiki/Bugs and
open new bug report. I have some patches which may help in narrowing it down,
but I would like to see all bug report data first.
Marcin
prev parent reply other threads:[~2013-01-05 13:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 12:21 drm/nouveau E[ DRM] fail ttm_validate Kees Bakker
2013-01-04 17:49 ` Marcin Slusarz
2013-01-04 21:25 ` Kees Bakker
2013-01-05 13:59 ` Marcin Slusarz [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=20130105135925.GA3131@joi.lan \
--to=marcin.slusarz@gmail.com \
--cc=kees.bakker@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
/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