lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130104174958.GA15275@joi.lan>
Date:	Fri, 4 Jan 2013 18:49:58 +0100
From:	Marcin Slusarz <marcin.slusarz@...il.com>
To:	Kees Bakker <spam@...king.nl>
Cc:	linux-kernel@...r.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@...onical.com>
Subject: Re: drm/nouveau E[     DRM] fail ttm_validate

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?

0.0.16 is known to behave like that - you need to upgrade to >= 1.0.

> 
> Some more details
> /var/log/syslog:Jan  4 11:16:42 koli kernel: [    0.000000] Linux version 3.7.0-7-generic (root@...i) (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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ