From: Hans de Goede <hdegoede@redhat.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: "mesa-dev@lists.freedesktop.org" <mesa-dev@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>
Subject: Re: [PATCH mesa 3/3] nv30: Disable msaa for now because it causes lockups
Date: Tue, 8 Sep 2015 10:00:38 +0200 [thread overview]
Message-ID: <55EE95A6.5040307@redhat.com> (raw)
In-Reply-To: <CAKb7UvghqjAb9MhJRo+LPX5-sE2x=Wj0kZMLeBGMJQgKMdHyTA@mail.gmail.com>
Hi,
On 07-09-15 22:00, Ilia Mirkin wrote:
> On Mon, Sep 7, 2015 at 3:50 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> msaa use on nv30 may trigger a (mesa?) bug where dmesg says:
>> [ 1197.850642] nouveau E[soffice.bin[3785]] fail ttm_validate
>> [ 1197.850648] nouveau E[soffice.bin[3785]] validating bo list
>> [ 1197.850654] nouveau E[soffice.bin[3785]] validate: -12
>> [ 1201.766955] nouveau E[soffice.bin[3785]] fail ttm_validate
>> [ 1201.766961] nouveau E[soffice.bin[3785]] validating bo list
>> [ 1201.766968] nouveau E[soffice.bin[3785]] validate: -12
>>
>> After which the program using the msaa visual freezes, and eventually
>> the entire system freezes. Disable msaa until this is fixed.
>>
>> This happens on both nv3x and nv4x cards.
>
> Ugh. This is aka "you ran out of vram, goodbye".
Ah right 12 == ENOMEM. This also explains why I can reproduce this much
easier on a 64 MB nv34 card then on my nv46 card which has more RAM.
> We don't really
> handle that case extremely well. I feel really bad doing this :( The
> issue is anachronistic applications like soffice that don't keep with
> the limitations of GPUs of the days of yore. So we end up penalizing
> people who do use applications of the day.
>
> But the practical issue is that people do upgrade, and people do run
> these applications, and so it makes sense to keep it off by default.
> Could I convince you to use debug_get_int_option (or something along
> those lines, forget the function name) to still allow an env var
> override? Like NV30_MAX_MSAA or something (and clamp it to 4 so people
> don't get ideas).
Using debug_get_int_option and defaulting it to 0 sounds like a good
idea, I'll do a v2 using this, and I'll update the comment / commit
message to reflect that this is caused by the applications causing
us to go oom.
Regards,
Hans
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
next prev parent reply other threads:[~2015-09-08 8:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 19:50 [PATCH mesa 1/3] nv30: Fix max width / height checks in nv30 sifm code Hans de Goede
2015-09-07 19:50 ` [PATCH mesa 2/3] nv30: Fix color resolving for nv3x cards Hans de Goede
[not found] ` <1441655450-9336-2-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-07 19:55 ` Ilia Mirkin
[not found] ` <CAKb7Uvhk56knb4ovaSrMDrOXKQq4ODJm3n1xhwQ+q=2jiNGbvA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-08 7:53 ` Hans de Goede
[not found] ` <55EE93EC.1090100-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-09 13:42 ` Hans de Goede
2015-09-07 19:50 ` [PATCH mesa 3/3] nv30: Disable msaa for now because it causes lockups Hans de Goede
2015-09-07 20:00 ` Ilia Mirkin
2015-09-08 8:00 ` Hans de Goede [this message]
[not found] ` <55EE95A6.5040307-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-08 8:48 ` Ben Skeggs
[not found] ` <1441655450-9336-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-07 19:52 ` [PATCH mesa 1/3] nv30: Fix max width / height checks in nv30 sifm code Ilia Mirkin
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=55EE95A6.5040307@redhat.com \
--to=hdegoede@redhat.com \
--cc=imirkin@alum.mit.edu \
--cc=mesa-dev@lists.freedesktop.org \
--cc=nouveau@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.