From: Kees Bakker <spam@tasking.nl>
To: linux-kernel@vger.kernel.org
Subject: drm/nouveau E[ DRM] fail ttm_validate
Date: Fri, 04 Jan 2013 13:21:14 +0100 [thread overview]
Message-ID: <65b9.50e6c93a.b1791@altium.nl> (raw)
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
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
Some more details
/var/log/syslog:Jan 4 11:16:42 koli kernel: [ 0.000000] Linux version 3.7.0-7-generic (root@koli) (gcc version 4.7.2 (Ubuntu/Lin
/var/log/syslog:Jan 4 11:16:44 koli kernel: [ 18.081288] [drm] Initialized drm 1.1.0 20060810
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.615246] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x04b300b1
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.615251] nouveau [ DEVICE][0000:01:00.0] Chipset: G73 (NV4B)
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.615254] nouveau [ DEVICE][0000:01:00.0] Family : NV40
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.616802] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.655315] nouveau [ VBIOS][0000:01:00.0] ... appears to be valid
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.655320] nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.655505] nouveau [ VBIOS][0000:01:00.0] BIT signature found
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.655509] nouveau [ VBIOS][0000:01:00.0] version 05.73.22.67
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.660805] nouveau [ PFB][0000:01:00.0] RAM type: DDR2
/var/log/syslog:Jan 4 11:16:45 koli kernel: [ 18.660811] nouveau [ PFB][0000:01:00.0] RAM size: 256 MiB
--
Kees Bakker
next reply other threads:[~2013-01-04 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 12:21 Kees Bakker [this message]
2013-01-04 17:49 ` drm/nouveau E[ DRM] fail ttm_validate Marcin Slusarz
2013-01-04 21:25 ` Kees Bakker
2013-01-05 13:59 ` Marcin Slusarz
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=65b9.50e6c93a.b1791@altium.nl \
--to=spam@tasking.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox