From: "Stefan Lippers-Hollmann" <s.L-H@gmx.de>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: David Airlie <airlied@linux.ie>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: nouveau/ NV11: 3.12 freezes if X.org is started headless
Date: Wed, 27 Nov 2013 00:18:09 +0000 [thread overview]
Message-ID: <201311270018.14980.s.L-H@gmx.de> (raw)
In-Reply-To: <CAKb7UvinEmz4YFoes2w5JJp-sJ_tsDeAWj-Aa5Yw56m2=j3xHw@mail.gmail.com>
Hi
On Tuesday 26 November 2013, Ilia Mirkin wrote:
> On Tue, Nov 26, 2013 at 6:03 PM, Stefan Lippers-Hollmann <s.L-H@gmx.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
next prev parent reply other threads:[~2013-11-27 0:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 23:03 Stefan Lippers-Hollmann
2013-11-26 23:19 ` Ilia Mirkin
2013-11-27 0:18 ` Stefan Lippers-Hollmann [this message]
2013-11-27 0:49 ` Ilia Mirkin
2013-11-27 1:35 ` Stefan Lippers-Hollmann
2013-11-27 2:15 ` Ilia Mirkin
2013-11-27 2:29 ` Dave Airlie
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=201311270018.14980.s.L-H@gmx.de \
--to=s.l-h@gmx.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--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
all inboxes | Powered by JetHome®