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 58615] [NV43] hangs with direct rendering since 3.7 rework
Date: Mon, 19 Jan 2015 20:26:09 +0000	[thread overview]
Message-ID: <bug-58615-8800-SpSpxV2jQu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-58615-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #13 from Andrew Randrianasulu <randrik-JGs/UdohzUI@public.gmane.org> ---
I seems I  can avoid (workaround) this bug by simply changing in my .config
CONFIG_PREEMPT_NONE=y to CONFIG_PREEMPT_VOLUNTARY=y . I made  this  discovery 
while  trying  official Slackware kernel from Slackware-current. May be this
bug has something in  common with bug described  in
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.3 as "mm, vmscan:
prevent kswapd livelock due to pfmemalloc-throttled process being killed' . 
Bug seems to hit  only nv40 (and less?) codepath, because my nv50 works fine
without preemption.

Should I  leave  this  bugreport open, or resolve it as WORKSFORME? (currently
I'm  compiling additional test kernel based on nouveau/linux-2.6 linux-3.19
branch , just  to test my workaround one more time.)

Reclocking still seems to work only partially (lost  display  and  another 
kind  of  hang  after  just  few seconds of glxgears  on highest perf level,
lost  display after I switch clocks back to lower frequencies), but this is 
another  issue

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

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

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

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

  parent reply	other threads:[~2015-01-19 20:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 12:18 [Bug 58615] New: nv43 hangs with direct rendering since 3.7 rework bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-58615-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-12-21 12:20   ` [Bug 58615] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-21 12:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-21 12:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-21 12:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-21 13:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-21 13:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-15  5:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-15  5:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-02  8:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-02  5:46   ` [Bug 58615] [NV43] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-04  1:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-15 18:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-19 20:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-01-29  7:12   ` 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-58615-8800-SpSpxV2jQu@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.