All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100567] Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Date: Mon, 06 May 2019 17:36:09 +0000	[thread overview]
Message-ID: <bug-100567-8800-Tdzx2Rmr37@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100567-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1820 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100567

--- Comment #31 from Marc Burkhardt <libreoffice.org-5+OZ0iQkl5WoYr4blSSd5g@public.gmane.org> ---
Hi Ilia,

by offering a $100 for this the intention was to just get this thing sorted out
from the nouveau guys _prior_ to any "my game X still doesn't work with
nouveau" bug. I don't want to lean out toooo far out of the window, but I think
this actually is a gregression, too. Not just a bug. Nevertheless, I know
developers earn much more than that, I'm a developer myself.

I cannot share your expression "The best way to get a good experience is to
avoid doing things which break nouveau". What experience is this if you use a
product that you know has a bug and you try to avoid it? Someday you change the
product. But I do not want this. I want the bug to be sorted out, offering my
spare time, some bucks for you to have a night out and nothing more.

I use enlightenment desktop on top of modesetting driver with
"nouveau.noaccel=0 nouveau.nofbaccel=1 nouveau.modeset=1 nouveau.runpm=0
nouveau.debug=disp=trace,i2c=trace,bios=trace nouveau.config=NvPmShowAll=true"
applied. I see no reason to just _not_ use the features the driver offers. And
when they do not work: either fix them or get rid of them.

I'm also absolutely not into heavy 3D, hevay OpenGL or whatever-usage. I just
use a modern and advanced desktop environment (Enlightenment, git) on recent
"stable" hardware (ThinkPad P50). Not trying to _force_ nouveau to go down.

If your answer really is to "not stress" the driver with a usual workload,
avoid stuff "with the letters G and K" or whatever... oh dear. Cannot imagine
how I start to argue over this for _my_ work with _my_ boss...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2666 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-05-06 17:36 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 20:09 [Bug 100567] New: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-100567-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-04-05 16:18   ` [Bug 100567] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-06 15:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 23:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-13 18:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-20 14:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26  9:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26  9:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-26  9:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-06-30  7:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-14 11:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-30 20:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-12-29 17:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-30 13:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-01 17:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-30 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-05 10:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-22 11:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-05 21:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-06 14:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-06 18:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-08 11:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-04 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-07  0:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-02-11 21:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-05 15:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-05 18:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-06 16:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-06 17:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-06 17:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-05-06 20:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 19:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-08 14:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-26 19:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-21 15:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-21 15:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-05 14:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-23 21:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-10-08  7:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=bug-100567-8800-Tdzx2Rmr37@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.