linux-kernel - Re: nouveau/ NV11: 3.12 freezes if X.org is started headless

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: <201311270018.14980.s.L-H@gmx.de>
Date:	Wed, 27 Nov 2013 00:18:09 +0000
From:	"Stefan Lippers-Hollmann" <s.L-H@....de>
To:	Ilia Mirkin <imirkin@...m.mit.edu>
Cc:	David Airlie <airlied@...ux.ie>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>
Subject: Re: nouveau/ NV11: 3.12 freezes if X.org is started headless

Hi

On Tuesday 26 November 2013, Ilia Mirkin wrote:
> On Tue, Nov 26, 2013 at 6:03 PM, Stefan Lippers-Hollmann <s.L-H@....de> wrote:
> > v3.11 is fine, with and without monitor attached.
> > v3.12 is fine as long as X.org isn't started (but may fail to reboot
> >       cleanly). If a monitor is connected I don't observe any problems,
> >       it freezes without a monitor connected.
> > v3.13-rc1-95-gb975dc3 appears not to freeze without a monitor anymore
> >       (I didn't confirm that it's fine with a monitor attached), but I
> >       end up with the following Oops (this is before X.org is started).
[…]
> > BUG: unable to handle kernel NULL pointer dereference at   (null)
> > IP: [<e0ecaa4e>] _nouveau_clock_init+0x2a/0xaf [nouveau]
[…]
> The oops in 3.13-rc1 should be fixed by applying the equivalent of
> http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=0397aaaa009092427dc60aea8b3c21c00526d8ba

As you expected, the Oops is gone after applying the afforementioned 
patch, 3.13~ now behaves as 3.12 (it freezes, if X.org is started 
without a monitor attached).

> . Also note that libdrm had a bug when compiled with gcc-4.8 for
> pre-nv50 cards, not sure if the fixes have made it to Debian/unstable,
> but you need libdrm-2.4.48+ (or compile it with gcc-4.7/clang).

The libdrm2 version is 2.4.49-2, which -although it has been compiled 
with gcc 4.8.2-5[1]- should be unaffected by this issue. According to 
the ChangeLog the version is at 7ddc98f92f92560e2b52287ae8cf816ca4a057de
and no significant patches[2] have been applied.

> Lastly, another thing to try if you're getting random hangs is booting
> with nouveau.agpmode=0 (and if that helps, seeing if =1 or =2 still
> work ok). If that helps, it can be added to the quirks list.

Unfortunately this doesn't appear to have an effect, with 3.13~ and
the previous patch applied:

# cat /sys/module/nouveau/parameters/agpmode 
0

# init 5
[   73.708490] nouveau W[  PTIMER][0000:01:00.0] unknown input clock freq
system frozen.

Regards
	Stefan Lippers-Hollmann

[1]	https://buildd.debian.org/status/fetch.php?pkg=libdrm&arch=i386&ver=2.4.49-2&stamp=1385480211
[2]	http://anonscm.debian.org/gitweb/?p=pkg-xorg/lib/libdrm.git;a=blob;f=debian/patches/01_default_perms.diff;h=cdba93e19edf40b2b0b56d951a6416c68a0af6f0;hb=HEAD
	http://anonscm.debian.org/gitweb/?p=pkg-xorg/lib/libdrm.git;a=blob;f=debian/patches/02_kbsd_modeset.diff;h=260260925fc692c71d955d6490dabf87905abb51;hb=HEAD
--
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/