All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Martitz <kugel-UCKwuKHb1aVAfugRpC6u6w@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [RFC PATCH v2 0/7] stabilize kepler reclocking
Date: Fri, 25 Dec 2015 00:08:05 +0100	[thread overview]
Message-ID: <567C7AD5.9050000@rockbox.org> (raw)
In-Reply-To: <1449073474-3445-1-git-send-email-nouveau-lIBOoy2+GI7scQ4cX5LuPg@public.gmane.org>

Hello,

first of all, I'm new to this list, so please beer with me. On the other 
hand, I'm a graduate computer systems engineer with experience in Linux 
kernel code, so I can hopefully provide useful input/assistance on this 
topic.

I'm replying because I tried your patches on my setup in the hope they'd 
fix my lockups. Unfortunately they didn't, so I'm offering debug 
assistance to make my system work as well.

Here's my setup:
- Arch Linux
- Lenovo Thinkpad x230 laptop with integrated intel (ivy bridge)
- External GPU (eGPU) connected via ExpressCard <-> PCIe adaptor, a 
nvidia GeForce 650 Ti (Kepler). The PCIe link is unfortunately limited 
to Gen 1 and one lane.
- PRIME with eGPU as primary (following this guide: 
https://wiki.archlinux.org/index.php/PRIME#Discrete_Card_as_Primary_GPU)
- This setup works fine under Windows 10, and the eGPU gives a lot 
better performance than the intel chip even with the limited PCIe link.
- I compiled nouveau.ko, and nothing else, from your out-of-tree fork 
(branch stable_reclocking_kepler, HEAD at bc4767c (bios/fan: hardcode 
the fan mode to linear))

With and without your patches, I get lockups when attempting to reclock 
to the highest level (echo 0f > /sys/.../pstate) and then running an 
actual game (Dota 2 in this instance). Reclock as such appears to work 
fine initially, but the whole system locks up as soon as I start Dota 2. 
glxgears runs fine. echo 0a > /sys/.../pstate works as wel, however the 
performance is poor.

I suspected that reclocking doesn't work fully in that the core voltage 
isn't ramped high enough, so that the GPU (and rest of the system) locks 
up when the load goes above some threshold (glxgears works after all). 
Unfortunately, I can't see any improvement with your patches.

FWIW, I made sure that the self-compiled nouveau.ko is used by running 
make install and then deleting the distro's shipped nouveau.ko. I 
verified this by running modprobe -nv nouveau (it also shows that 
pstate=1 is correctly passed to it). The nouveau.ko (.ko.gz actually) is 
placed under /lib/modules/4.3.3-2-ARCH/extra/nouveau.ko.gz.

Thanks for your ongoing effort to improve the situation on nvidia cards. 
I hope I can be of any help.

Best regards.

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

  parent reply	other threads:[~2015-12-24 23:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 16:24 [RFC PATCH v2 0/7] stabilize kepler reclocking Karol Herbst
     [not found] ` <1449073474-3445-1-git-send-email-nouveau-lIBOoy2+GI7scQ4cX5LuPg@public.gmane.org>
2015-12-02 16:24   ` [PATCH v2 1/7] bios/volt: handle voltage table version 0x50 with 0ed header Karol Herbst
2015-12-02 16:24   ` [PATCH v2 2/7] clk: drop cstates with too high voltage Karol Herbst
2015-12-02 16:24   ` [PATCH v2 3/7] volt: parse the boost voltage entry Karol Herbst
2015-12-02 16:24   ` [PATCH v2 4/7] clk: drop cstates with higher voltage than boost_max_voltage Karol Herbst
2015-12-02 16:24   ` [PATCH v2 5/7] nvbios: add parsing of BASE CLOCK table Karol Herbst
2015-12-02 16:24   ` [PATCH v2 6/7] subdev/clk: print the base clocks Karol Herbst
2015-12-02 16:24   ` [PATCH v2 7/7] clk: allow boosting only when NvBoost is set Karol Herbst
2015-12-24 23:08   ` Thomas Martitz [this message]
     [not found]     ` <567CEDB4.1010504@rockbox.org>
     [not found]       ` <567CEDB4.1010504-UCKwuKHb1aVAfugRpC6u6w@public.gmane.org>
2015-12-25 17:43         ` [RFC PATCH v2 0/7] stabilize kepler reclocking Pierre Moreau
     [not found]           ` <20151225174301.GA2829-WLoDKDh+7sdAfugRpC6u6w@public.gmane.org>
2015-12-25 22:37             ` Thomas Martitz
     [not found]               ` <567DC51A.1020400-UCKwuKHb1aVAfugRpC6u6w@public.gmane.org>
2015-12-26  9:33                 ` Karol Herbst
2015-12-30 22:53             ` Thomas Martitz
     [not found]               ` <5684607C.7080105-UCKwuKHb1aVAfugRpC6u6w@public.gmane.org>
2015-12-31  2:54                 ` Karol Herbst
     [not found]                   ` <1822370810.198263.1451530483711.JavaMail.open-xchange-KNm3LHm9FEhKTQ5g00o1eQ@public.gmane.org>
2015-12-31  9:56                     ` Thomas Martitz
     [not found]                       ` <6691D391-5BAB-4DB9-80CC-6A2DDD5066B0-UCKwuKHb1aVAfugRpC6u6w@public.gmane.org>
2015-12-31 10:09                         ` Karol Herbst
2016-01-06  9:53                         ` Thomas Martitz
     [not found]       ` <1617684914.182932.1451068655247.JavaMail.open-xchange@www.ud-mail.de>
     [not found]         ` <1617684914.182932.1451068655247.JavaMail.open-xchange-KNm3LHm9FEhKTQ5g00o1eQ@public.gmane.org>
2015-12-30 22:42           ` Thomas Martitz
     [not found]             ` <56845DD0.6010508-UCKwuKHb1aVAfugRpC6u6w@public.gmane.org>
2015-12-31 19:47               ` 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=567C7AD5.9050000@rockbox.org \
    --to=kugel-uckwukhb1avafugrpc6u6w@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.