Re: [Nouveau] [PATCH] drm/nouveau/iccsense: fix memory leak on default sensor->type case

Hi Colin, thanks for pointing this out, but I am quite sure this continue statement won't ever be hit, ever. check the nvkm_iccsense_create_sensor function. A sensor object will only be created for one of those three types and others don't exist. I've just added that default statement to shut

PROBLEM: mmiotracing issue with nvidia kernel module

included). Many Thanks Karol Herbst kernel version: Linux version 4.4.1-gentoo (root@) (gcc version 5.3.0 (Gentoo 5.3.0 p1.0, pie-0.6.5) ) #11 SMP PREEMPT Mon Feb 8 08:42:46 CET 2016 cpuinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 60 model name

Re: [PATCH 2/2] net/forcedeth: add wol p support

one note though: I am not _really_ sure it is the right flag. I've contacted somebody at nvidia and asked for documentation regarding this mmio reg. I still get some random wakeups and I don't know where they are comming from. > Karol Herbst <g...@karolherbst.de> hat am 10. März 2016

[PATCH 2/2] net/forcedeth: add wol p support

REd on my mac mini. No idea if that also works on other ethernet cards supported by forcedeth, but I doubt anybody cares at all, otherwise somebody else would have REd it already. Signed-off-by: Karol Herbst <nouv...@karolherbst.de> --- drivers/net/ethernet/nvidia/forcedeth.c | 9 ++

[PATCH 1/2] net/forcedeth: refactor wol support to make it easier to add more wol modes

Signed-off-by: Karol Herbst <g...@karolherbst.de> --- drivers/net/ethernet/nvidia/forcedeth.c | 28 +++- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/drivers/net/ethernet/nvidia/forcedeth.c b/drivers/net/ethernet/nvidia/forcedeth.c index 7

[PATCH 0/2] drivers/net/forcedeth: add support for WAKE_PHY

From: Karol Herbst <nouv...@karolherbst.de> I want to use my mac mini as a local server, but put it to sleep automatically therefore wol p, and because wol g is a mess if you want to wakeup the target machine automagically :) Karol Herbst (2): net/forcedeth: refactor wol support t

Re: [PATCH] drm/nouveau/nvbios/iccsense: fix semicolon.cocci warnings

e unneeded semicolon. > > > > Generated by: scripts/coccinelle/misc/semicolon.cocci > > > > CC: Martin Peres <martin.pe...@free.fr> > > Signed-off-by: Fengguang Wu <fengguang...@intel.com> > Signed-off-by: Martin Peres <martin.pe...@free.fr> Signed-off-by: Karol Herbst <nouv...@karolherbst.de>

Re: [PATCH] drm/nouveau/iccsense: fix ifnullfree.cocci warnings

arning > > "kfree(NULL) is safe this check is probably not required" > > and kfreeaddr.cocci by Julia Lawall. > > > > Generated by: scripts/coccinelle/free/ifnullfree.cocci > > > > CC: Karol Herbst <nouv...@karolherbst.de> > > Signed-off-b

RFC: [PATCH] x86/kmmio: fix mmiotrace for hugepages

fault within the same page twice anymore. I don't know if I got this right though, so please read this change with great care v2: use page_level macros Signed-off-by: Karol Herbst <nouv...@karolherbst.de> --- arch/x86/mm/kmmio.c | 89 -

Re: ftrace use of pci_resource_to_user()

2016-05-06 12:16 GMT+02:00 Pekka Paalanen : > On Wed, 4 May 2016 14:17:13 -0500 > Bjorn Helgaas wrote: > >> 138295373ccf ("ftrace: mmiotrace update, #2") added this use of >> pci_resource_to_user(): >> >> +static int mmio_print_pcidev(struct trace_seq

Re: mmiotracer hangs the system

hi all, mhhh exactly this commit fixed mmiotrace for me and a few other nouveau devs on x86_64. Also the error log doesn't really show a problem inside the tracer? Maybe it would be helpful to provide full dmesg in the case of error, just to rule silly things out. I will try to figure out how

Re: mmiotracer hangs the system

2016-08-19 17:35 GMT+02:00 Andy Shevchenko <andy.shevche...@gmail.com>: > On Fri, Aug 19, 2016 at 6:08 PM, karol herbst <karolher...@gmail.com> wrote: >> 2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevche...@gmail.com>: >>> On Fri, Aug 19, 2016 at 1:35 PM,

Re: mmiotracer hangs the system

Hi everybody, is there any update on that issue I missed somehow? I really don't want to leave the mmiotracer in a state, where it breaks something while fixing other issues. But for now, without being able to even reproduce the issue, I can't really do much, because the code in the current

Re: mmiotracer hangs the system

2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevche...@gmail.com>: > On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolher...@gmail.com> wrote: >> is there any update on that issue I missed somehow? I really don't >> want to leave the mmiotracer in a state

Re: mmiotracer hangs the system

t 6:08 PM, karol herbst <karolher...@gmail.com> wrote: >> 2016-08-19 15:02 GMT+02:00 Andy Shevchenko <andy.shevche...@gmail.com>: >>> On Fri, Aug 19, 2016 at 1:35 PM, karol herbst <karolher...@gmail.com> wrote: >>>> is there any update on that iss

Re: [Nouveau] [PATCH] drm/nouveau: fix LEDS_CLASS=m configuration

2016-11-08 16:46 GMT+01:00 Ilia Mirkin : > On Tue, Nov 8, 2016 at 8:56 AM, Arnd Bergmann wrote: >> The newly introduced LED handling for nouveau fails to link when the >> driver is built-in but the LED subsystem is a loadable module: >> >>

Re: [Nouveau] [PATCH] drm/nouveau: fix LEDS_CLASS=m configuration

2016-11-08 17:12 GMT+01:00 Arnd Bergmann : > On Tuesday, November 8, 2016 5:07:01 PM CET Lukas Wunner wrote: >> On Tue, Nov 08, 2016 at 04:52:49PM +0100, Arnd Bergmann wrote: >> > The underlying problem is that we already have a number of other >> > symbols that either have "depends

Re: [Nouveau] [PATCH 01/17] drm/nouveau/core: add missing header dependencies

I think it would be better to squash those commits: 1. for the includes 2. for static declerations 2016-10-22 11:41 GMT+02:00 Baoyou Xie : > We get 2 warnings when building kernel with W=1: > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:34:1: warning: no previous >

Re: [Nouveau] noveau: emergency shutdown handling is overcomplex and broken

Thanks for the pointer. But I don't like this patch. If you find a bug, make a bug report or just fix it if you know the fix already. Or write something in IRC. Or write on the Mailing list as a general question or something else But I really don't agree on doing it this way. You would have

Re: [Nouveau] [PATCH 01/17] drm/nouveau/core: add missing header dependencies

2016-10-24 9:13 GMT+02:00 Baoyou Xie <baoyou@linaro.org>: > > > On 23 October 2016 at 01:32, Karol Herbst <karolher...@gmail.com> wrote: >> >> I think it would be better to squash those commits: >> 1. for the includes >> 2. for static declerations

Re: [Nouveau] [PATCH] nouveau: hide gcc-4.9 -Wmaybe-uninitialized

uhh, that function looks so odd, ... yeah. Change looks fine. Reviewed-By: Karol Herbst <karolher...@gmail.com> 2016-10-24 17:30 GMT+02:00 Arnd Bergmann <a...@arndb.de>: > gcc-4.9 notices that the validate_init() function returns unintialized > data when called with a zero 'nr

Re: mmiotracer hangs the system

sorry for that, but I forgot the patch 2016-11-19 11:56 GMT+01:00 Karol Herbst <karolher...@gmail.com>: > this is odd, I found a bug related to nouveau (modprobe/bind doesn't > return), but that isn't related to your issue at all or maybe it is > exactly this, cause the bindin

Re: mmiotracer hangs the system

;: > On Fri, Oct 14, 2016 at 12:12 AM, Karol Herbst <karolher...@gmail.com> wrote: >> sorry for the delay fixing that bug. I got occupied with other things >> and didn't really got to the issue again, it is on my todo list as the >> next item though and I hope I will be ab

Re: mmiotracer hangs the system

for the delay. Karol 2016-08-19 22:46 GMT+02:00 Karol Herbst <karolher...@gmail.com>: > Hi again, > > I was able to get a crash/freeze/something while unbinding/binding my > nvidia gpu from nouveau. > > Guess that means something is odd. I will investigate this more over

Re: [Nouveau] [PATCH] drm/nouveau: fix unknown chipset for GTX 1060

we already have that included in 4.10 2016-12-12 12:26 GMT+01:00 Chris Chiu : > Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it > only gives VGA resolution on screen. Use the same chipset as nv134 > then it shows FullHD. This commit copies fields from

Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335

Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE usage we could convert to WARN_ONCE? Reviewed-By: Karol Herbst <karolher...@gmail.com> On Fri, Jul 14, 2017 at 5:05 PM, Tobias Klausmann <tobias.johannes.klausm...@mni.thm.de> wrote: > On 7/14/17 3:41 PM, Mike

Re: [PATCH] drm/nouveau: Add support for clockgating on Fermi+

Hi Lyude, thanks for the great work. Just a view comments inline. 2017-04-25 20:38 GMT+02:00 Lyude : > This adds support for enabling automatic clockgating on nvidia GPUs for > Fermi and later generations. This saves a little bit of power, bringing > my fermi GPU's power

Re: [Nouveau] [PATCH] [RESEND] drm/nouveau/clk: fix gcc-7 -Wint-in-bool-context warning

On Wed, Sep 6, 2017 at 3:56 PM, Arnd Bergmann wrote: > gcc thinks that interpreting a multiplication result as a bool > is confusing: > > drivers/gpu/drm/nouveau/nvkm/subdev/clk/gt215.c: In function 'read_pll': > drivers/gpu/drm/nouveau/nvkm/subdev/clk/gt215.c:133:8: error: '*' in

Re: [Nouveau] [PATCH] [RESEND] drm/nouveau/clk: fix gcc-7 -Wint-in-bool-context warning

On Wed, Sep 6, 2017 at 10:11 PM, Arnd Bergmann <a...@arndb.de> wrote: > On Wed, Sep 6, 2017 at 4:20 PM, Karol Herbst <karolher...@gmail.com> wrote: >>> In this instance, I think using multiplication is more intuitive >>> than '&&', so I'm addin

Re: [Nouveau] [PATCH] drm/nouveau/mmu: fix odd_ptr_err.cocci warnings (fwd)

Hi julia, I think it would be better to extract the assignment out of the if clause. Then you'll get something like this: memory = ...; if (IS_ERR(memory)) { } so, to answer your question: no, it isn't necessary. On Tue, Nov 28, 2017 at 1:56 PM, Julia Lawall wrote:

[PATCH] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses

<ly...@redhat.com> Signed-off-by: Karol Herbst <kher...@redhat.com> --- arch/x86/mm/ioremap.c | 4 ++-- arch/x86/mm/kmmio.c | 12 +++- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/arch/x86/mm/ioremap.c b/arch/x86/mm/ioremap.c index 34f0e1847dd6..5d4c358778dd 100644

Re: [Nouveau] [PATCH] drm/nouveau/mmu: fix odd_ptr_err.cocci warnings

Reviewed-by: Karol Herbst <kher...@redhat.com> On Thu, Nov 30, 2017 at 8:53 PM, Christoph Böhmwalder <christ...@boehmwalder.at> wrote: > The kbuild test bot complained about a new coccinelle warning nearby, > which sparked a discussion about the assignment to 'memory' inside of

Re: [tip:x86/urgent] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses

gt; >> On Tue, Dec 12, 2017 at 02:55:30AM -0800, tip-bot for Karol Herbst wrote: >> > Commit-ID: 6d60ce384d1d5ca32b595244db4077a419acc687 >> > Gitweb: >> > https://git.kernel.org/tip/6d60ce384d1d5ca32b595244db4077a419acc687 >> > Author: Karol Herbst

Re: [Nouveau] [PATCH] drm/nouveau/mmu: Fix trailing semicolon

Reviewed-by: Karol Herbst <kher...@redhat.com> On Wed, Jan 17, 2018 at 7:53 PM, Luis de Bethencourt <lui...@kernel.org> wrote: > The trailing semicolon is an empty statement that does no operation. > Removing it since it doesn't do anything. > > Signed-off-by:

Re: [Nouveau] [RFC v2 1/4] drm/nouveau: Add support for basic clockgating on Kepler1

On Fri, Jan 26, 2018 at 4:35 AM, Lyude Paul wrote: > This adds support for enabling automatic clockgating on nvidia GPUs for > Kepler1. While this is not technically a clockgating level, it does > enable clockgating using the clockgating values initially set by the > vbios

Re: [PATCH 1/5] drm/nouveau: Check backlight IDs are >= 0, not > 0

Patches 1-5 are Reviewed-by: Karol Herbst I think it might be worth to test those patches on a system without any backlight devices just to verify we don't break things, but the code looked good already, so maybe we don't really need to test. On Thu, Aug 23, 2018 at 3:21 AM, Lyude Paul wrote

Re: [Nouveau] [PATCH] drm/nouveau/mmu: fix odd_ptr_err.cocci warnings (fwd)

Hi julia, I think it would be better to extract the assignment out of the if clause. Then you'll get something like this: memory = ...; if (IS_ERR(memory)) { } so, to answer your question: no, it isn't necessary. On Tue, Nov 28, 2017 at 1:56 PM, Julia Lawall wrote: > This is a false

Re: [Nouveau] [PATCH] drm/nouveau/mmu: fix odd_ptr_err.cocci warnings

Reviewed-by: Karol Herbst On Thu, Nov 30, 2017 at 8:53 PM, Christoph Böhmwalder wrote: > The kbuild test bot complained about a new coccinelle warning nearby, > which sparked a discussion about the assignment to 'memory' inside of > the conditional expression. See Link below for the

Re: [Nouveau] [PATCH] [RESEND] drm/nouveau/clk: fix gcc-7 -Wint-in-bool-context warning

On Wed, Sep 6, 2017 at 3:56 PM, Arnd Bergmann wrote: > gcc thinks that interpreting a multiplication result as a bool > is confusing: > > drivers/gpu/drm/nouveau/nvkm/subdev/clk/gt215.c: In function 'read_pll': > drivers/gpu/drm/nouveau/nvkm/subdev/clk/gt215.c:133:8: error: '*' in boolean >

Re: [Nouveau] [PATCH] [RESEND] drm/nouveau/clk: fix gcc-7 -Wint-in-bool-context warning

On Wed, Sep 6, 2017 at 10:11 PM, Arnd Bergmann wrote: > On Wed, Sep 6, 2017 at 4:20 PM, Karol Herbst wrote: >>> In this instance, I think using multiplication is more intuitive >>> than '&&', so I'm adding a comparison to zero instead to shut up >>> the warn

Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335

Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE usage we could convert to WARN_ONCE? Reviewed-By: Karol Herbst On Fri, Jul 14, 2017 at 5:05 PM, Tobias Klausmann wrote: > On 7/14/17 3:41 PM, Mike Galbraith wrote: >> >> On Fri, 2017-07-14 at 15:36 +0200, Mike

[PATCH] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses

Rostedt Cc: Ingo Molnar Cc: Thomas Gleixner Cc: Pekka Paalanen Cc: nouv...@lists.freedesktop.org Cc: x...@kernel.org Acked-by: Pekka Paalanen Tested-by: Lyude Signed-off-by: Karol Herbst --- arch/x86/mm/ioremap.c | 4 ++-- arch/x86/mm/kmmio.c | 12 +++- 2 files changed, 9 insertions

Re: [tip:x86/urgent] x86/mm/kmmio: Fix mmiotrace for page unaligned addresses

p-bot for Karol Herbst wrote: >> > Commit-ID: 6d60ce384d1d5ca32b595244db4077a419acc687 >> > Gitweb: >> > https://git.kernel.org/tip/6d60ce384d1d5ca32b595244db4077a419acc687 >> > Author: Karol Herbst >> > AuthorDate: Mon, 27 Nov 2017 08:51:39

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

fyi, there is a patch which solves a maybe related issue on your GPU, mind giving it a try before we dig further? https://gitlab.freedesktop.org/drm/nouveau/-/issues/14#note_767791 On Thu, Jan 21, 2021 at 3:33 AM Jamie Heilman wrote: > > Karol Herbst wrote: > > On Wed, Jan 6, 202

[PATCH] drm/nouveau/svm: fail NOUVEAU_SVM_INIT ioctl on unsupported devices

Fixes a crash when trying to create a channel on e.g. Turing GPUs when NOUVEAU_SVM_INIT was called before. Fixes: eeaf06ac1a558 ("drm/nouveau/svm: initial support for shared virtual memory") Signed-off-by: Karol Herbst --- drivers/gpu/drm/nouveau/nouveau_svm.c | 4 1 file

[PATCH] drm/nouveau/svm: fail NOUVEAU_SVM_INIT ioctl on unsupported devices

Fixes a crash when trying to create a channel on e.g. Turing GPUs when NOUVEAU_SVM_INIT was called before. Fixes: eeaf06ac1a558 ("drm/nouveau/svm: initial support for shared virtual memory") Signed-off-by: Karol Herbst --- drivers/gpu/drm/nouveau/nouveau_svm.c | 4 1 file

Re: [Nouveau] [PATCH] tracing: remove definition of DEBUG

Reviewed-by: Karol Herbst On Fri, Jan 15, 2021 at 11:51 PM wrote: > > From: Tom Rix > > Defining DEBUG should only be done in development. > So remove DEBUG. > > Signed-off-by: Tom Rix > --- > kernel/trace/trace_mmiotrace.c | 2 -- > 1 file changed, 2 deleti

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

On Wed, Jan 6, 2021 at 4:25 AM Jamie Heilman wrote: > > Jamie Heilman wrote: > > Jamie Heilman wrote: > > > Karol Herbst wrote: > > > > do you think you'd be able to do a kernel bisect in order to pinpoint > > > > the actual commit causing it? Thanks &

[PATCH 1/2] drm/nouveau/device: return error for unknown chipsets

Previously the code relied on device->pri to be NULL and to fail probing later. We really should just return an error inside nvkm_device_ctor for unsupported GPUs. Fixes: 24d5ff40a732 ("drm/nouveau/device: rework mmio mapping code to get rid of second map") Signed-off-by: Karol Her

[PATCH 2/2] drm/nouveau/mem: guard against NULL pointer access in mem_del

other drivers seems to do something similar Signed-off-by: Karol Herbst Cc: dri-devel Cc: Dave Airlie Cc: sta...@vger.kernel.org --- drivers/gpu/drm/nouveau/nouveau_mem.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nouveau_mem.c b/drivers/gpu/drm/nouveau

Re: [Nouveau] [PATCH RFC] drm/nouveau: fix memory leak in nvkm_iccsense_oneinit

Ben, I think this is like the 5th patch tackling this issue, I think we should merge one of those. On Thu, Oct 15, 2020 at 6:23 AM Keita Suzuki wrote: > > struct pw_rail_t is allocated as an array in function nvios_iccsense_parse, > and stored to a struct member of local variable. However, the

Re: [Nouveau] [PATCH RFC] drm/nouveau: fix memory leak in nvkm_iccsense_oneinit

On Thu, Oct 15, 2020 at 6:32 PM Karol Herbst wrote: > > Ben, I think this is like the 5th patch tackling this issue, I think > we should merge one of those. > maybe I just confused that with reports, but it seems to turn up quite a bit and maybe I should have pushed more of it as wel

Re: [Nouveau] nouveau broken on Riva TNT2 in 5.9.0-rc8: GPU not supported on big-endian

On Fri, Oct 9, 2020 at 11:35 PM Ondrej Zary wrote: > > Hello, > I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped working: > [0.00] Linux version 5.9.0-rc8+ (zary@gsql) (gcc (Debian 8.3.0-6) > 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #326 SMP Fri Oct 9 22:31:40 > CEST 2020 >

Re: [Nouveau] nouveau broken on Riva TNT2 in 5.9.0-rc8: GPU not supported on big-endian

On Sat, Oct 10, 2020 at 12:23 AM Ilia Mirkin wrote: > > On Fri, Oct 9, 2020 at 5:54 PM Karol Herbst wrote: > > > > On Fri, Oct 9, 2020 at 11:35 PM Ondrej Zary wrote: > > > > > > Hello, > > > I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped work

Re: [PATCH v2 1/2] drm/nouveau: return temperatures in temp_get() via parameter

On Wed, Sep 16, 2020 at 9:47 PM Jeremy Cline wrote: > > The temp_get() function currently returns negative error numbers or a > temperature. However, the thermal sensors can (in theory) measure > negative temperatures. Some implementations of temp_get() correctly > clamp negative temperature

Re: [PATCH v2 1/2] drm/nouveau: return temperatures in temp_get() via parameter

On Wed, Sep 16, 2020 at 10:01 PM Karol Herbst wrote: > > On Wed, Sep 16, 2020 at 9:47 PM Jeremy Cline wrote: > > > > The temp_get() function currently returns negative error numbers or a > > temperature. However, the thermal sensors can (in theory) measure > &g

Re: [PATCH v2 1/2] drm/nouveau: return temperatures in temp_get() via parameter

On Thu, Sep 17, 2020 at 4:11 PM Jeremy Cline wrote: > > On Wed, Sep 16, 2020 at 10:03:22PM +0200, Karol Herbst wrote: > > On Wed, Sep 16, 2020 at 10:01 PM Karol Herbst wrote: > > > > > > On Wed, Sep 16, 2020 at 9:47 PM Jeremy Cline wrote: > > > >

Re: [PATCH] drm/nouveau: Add fine-grain temperature reporting

Reviewed-by: Karol Herbst On Wed, Aug 12, 2020 at 10:50 PM Jeremy Cline wrote: > > Commit d32656373857 ("drm/nouveau/therm/gp100: initial implementation of > new gp1xx temperature sensor") added support for reading finer-grain > temperatures, but continued to report te

Re: [Nouveau] [PATCH] drm/nouveau: Add fine-grain temperature reporting

On Wed, Sep 9, 2020 at 6:06 AM Ben Skeggs wrote: > > On Thu, 13 Aug 2020 at 06:50, Jeremy Cline wrote: > > > > Commit d32656373857 ("drm/nouveau/therm/gp100: initial implementation of > > new gp1xx temperature sensor") added support for reading finer-grain > > temperatures, but continued to

Re: [Nouveau] [PATCH] drm/nouveau/acr: fix a coding style in nvkm_acr_lsfw_load_bl_inst_data_sig()

Reviewed-by: Karol Herbst On Mon, Aug 3, 2020 at 5:46 AM Jing Xiangfeng wrote: > > This patch performs the following changes: > 1. remove a redundant parentheses around the nvkm_acr_lsfw_add() calls > 2. do assignment before this if condition, it is more readable > > S

Re: [Nouveau] [PATCH v2] ALSA: hda: Continue to probe when codec probe fails

On Tue, Dec 22, 2020 at 3:50 AM Kai-Heng Feng wrote: > > On Tue, Dec 22, 2020 at 1:56 AM Ilia Mirkin wrote: > > > > On Mon, Dec 21, 2020 at 11:33 AM Kai-Heng Feng > > wrote: > > > > > > [+Cc nouveau] > > > > > > On Fri, Dec 18, 2020 at 4:06 PM Takashi Iwai wrote: > > > [snip] > > > > > Quite

Re: [Nouveau] nouveau regression post v5.8, still present in v5.10

do you think you'd be able to do a kernel bisect in order to pinpoint the actual commit causing it? Thanks On Sun, Dec 27, 2020 at 8:16 PM Jamie Heilman wrote: > > Something between v5.8 and v5.9 has resulted in periodically losing video. > Unfortunately, I can't reliably reproduce it, it seems

Re: [PATCH 000/141] Fix fall-through warnings for Clang

On Thu, Nov 26, 2020 at 4:28 PM Geert Uytterhoeven wrote: > > Hi Miguel, > > On Thu, Nov 26, 2020 at 3:54 PM Miguel Ojeda > wrote: > > On Wed, Nov 25, 2020 at 11:44 PM Edward Cree wrote: > > > To make the intent clear, you have to first be certain that you > > > understand the intent;

Re: [Nouveau] [PATCH 2/3] drm/nouveau: manage nouveau_drm lifetime with devres

On Fri, Nov 6, 2020 at 3:17 AM Jeremy Cline wrote: > > Make use of the devm_drm_dev_alloc() API to bind the lifetime of > nouveau_drm structure to the drm_device. This is important because a > reference to nouveau_drm is accessible from drm_device, which is > provided to a number of DRM layer

Re: [Nouveau] [PATCH 1/7] Revert "ACPI / OSI: Add OEM _OSI string to enable dGPU direct output"

On Thu, Aug 15, 2019 at 4:30 PM wrote: > > > On Thu, Aug 15, 2019 at 10:15 AM Karol Herbst wrote: > > > > > > On Thu, Aug 15, 2019 at 4:13 PM Alex Deucher > > wrote: > > > > > > > > On Thu, Aug 15, 2019 at 10:04 AM Karol Herbst > &

Re: [Nouveau] pcieport 0000:00:01.0: PME: Spurious native interrupt (nvidia with nouveau and thunderbolt on thinkpad P73)

On Sun, Sep 6, 2020 at 8:52 PM Marc MERLIN wrote: > > Ok, I have an update to this problem. I added the nouveau list because > I can't quite tell if the issue is: > - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below > > - a new issue with thunderbold on thinkpad P73, that

Re: [Nouveau] pcieport 0000:00:01.0: PME: Spurious native interrupt (nvidia with nouveau and thunderbolt on thinkpad P73)

On Mon, Sep 7, 2020 at 10:58 PM Marc MERLIN wrote: > > On Mon, Sep 07, 2020 at 09:14:03PM +0200, Karol Herbst wrote: > > > - changes in the nouveau driver. Mika told me the PCIe regression > > > "pcieport :00:01.0: PME: Spurious native interrupt!" is s

Re: [Nouveau] nouveau broken on Riva TNT2 in 5.9.0-rc8: GPU not supported on big-endian

I sent a patch to the mailing list and wanted to have some review on that from at least Ben, but no idea if Ben already picked it and if it's good enough for sending it to stable yet.

Re: [Nouveau] [PATCH] drm/nouveau/mmu: Fix trailing semicolon

Reviewed-by: Karol Herbst On Wed, Jan 17, 2018 at 7:53 PM, Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > Removing it since it doesn't do anything. > > Signed-off-by: Luis de Bethencourt > --- > > Hi, > >

Re: [Nouveau] [RFC v2 1/4] drm/nouveau: Add support for basic clockgating on Kepler1

On Fri, Jan 26, 2018 at 4:35 AM, Lyude Paul wrote: > This adds support for enabling automatic clockgating on nvidia GPUs for > Kepler1. While this is not technically a clockgating level, it does > enable clockgating using the clockgating values initially set by the > vbios (which should be safe

Re: [RFC PATCH] pci: prevent putting pcie devices into lower device states on certain intel bridges

On Tue, Oct 1, 2019 at 10:47 AM Mika Westerberg wrote: > > On Mon, Sep 30, 2019 at 06:36:12PM +0200, Karol Herbst wrote: > > On Mon, Sep 30, 2019 at 6:30 PM Mika Westerberg > > wrote: > > > > > > On Mon, Sep 30, 2019 at 06:05:14PM +0200, Karol Herbst wrote: &

Re: [RFC PATCH] pci: prevent putting pcie devices into lower device states on certain intel bridges

On Tue, Oct 1, 2019 at 11:11 AM Mika Westerberg wrote: > > On Tue, Oct 01, 2019 at 10:56:39AM +0200, Karol Herbst wrote: > > On Tue, Oct 1, 2019 at 10:47 AM Mika Westerberg > > wrote: > > > > > > On Mon, Sep 30, 2019 at 06:36:12PM +0200, Karol Herbst wrote:

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

On Wed, Oct 16, 2019 at 11:37 PM Bjorn Helgaas wrote: > > [+cc linux-acpi] > > On Wed, Oct 16, 2019 at 09:18:32PM +0200, Karol Herbst wrote: > > but setting the PCI_DEV_FLAGS_NO_D3 flag does prevent using the > > platform means of putting the device into D3cold, right?

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

On Tue, Oct 22, 2019 at 2:45 PM Mika Westerberg wrote: > > On Tue, Oct 22, 2019 at 11:16:14AM +0200, Karol Herbst wrote: > > I think there is something I totally forgot about: > > > > When there was never a driver bound to the GPU, and if runtime power > > manageme

[PATCH] RFC: ACPI / OSI: remove workarounds for hybrid graphics laptops

can look into it and come up with a proper fix (and keep this patch out until we resolve all of those). Signed-off-by: Karol Herbst CC: Alex Hung CC: "Rafael J. Wysocki" CC: Len Brown CC: Lyude Paul CC: linux-kernel@vger.kernel.org CC: dri-de...@lists.freedesktop.or

Re: [PATCH] RFC: ACPI / OSI: remove workarounds for hybrid graphics laptops

On Fri, Jul 17, 2020 at 9:52 PM Alex Hung wrote: > > On 2020-07-17 1:05 p.m., Karol Herbst wrote: > > It's hard to figure out what systems are actually affected and right now I > > don't see a good way of removing those... > > > > But I'd like to see thos getting rem

Re: [PATCH] RFC: ACPI / OSI: remove workarounds for hybrid graphics laptops

On Mon, Jul 20, 2020 at 3:19 AM Alex Hung wrote: > > On 2020-07-19 1:50 p.m., Karol Herbst wrote: > > On Fri, Jul 17, 2020 at 9:52 PM Alex Hung wrote: > >> > >> On 2020-07-17 1:05 p.m., Karol Herbst wrote: > >>> It's hard to figure out what sys

Re: nouveau regression with 5.7 caused by "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"

On Wed, Jul 22, 2020 at 11:25 AM Mika Westerberg wrote: > > On Tue, Jul 21, 2020 at 01:37:12PM -0500, Patrick Volkerding wrote: > > On 7/21/20 10:27 AM, Mika Westerberg wrote: > > > On Tue, Jul 21, 2020 at 11:01:55AM -0400, Lyude Paul wrote: > > >> Sure thing. Also, feel free to let me know if

Re: nouveau regression with 5.7 caused by "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"

On Fri, Jul 17, 2020 at 1:54 AM Bjorn Helgaas wrote: > > [+cc Sasha -- stable kernel regression] > [+cc Patrick, Kai-Heng, LKML] > > On Fri, Jul 17, 2020 at 12:10:39AM +0200, Karol Herbst wrote: > > On Tue, Jul 7, 2020 at 9:30 PM Karol Herbst wrote: >

Re: nouveau regression with 5.7 caused by "PCI/PM: Assume ports without DLL Link Active train links in 100 ms"

Filed at https://bugzilla.kernel.org/show_bug.cgi?id=208597 oddly enough I wasn't able to reproduce it on my XPS 9560, will ping once something breaks. On Fri, Jul 17, 2020 at 2:43 AM Karol Herbst wrote: > > On Fri, Jul 17, 2020 at 1:54 AM Bjorn Helgaas wrote: > > > > [+

Re: [PATCH v3] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

On Mon, Oct 21, 2019 at 4:09 PM Mika Westerberg wrote: > > On Mon, Oct 21, 2019 at 03:54:09PM +0200, Karol Herbst wrote: > > > I really would like to provide you more information about such > > > workaround but I'm not aware of any ;-) I have not seen any issues lik

Re: [git pull] drm for 5.8-rc1

On Wed, Jul 1, 2020 at 6:45 AM James Jones wrote: > > This implies something is trying to use one of the old > DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK format modifiers with DRM-KMS without > first checking whether it is supported by the kernel. I had tried to > force an Xorg+Mesa stack without my

Re: [git pull] drm for 5.8-rc1

On Wed, Jul 1, 2020 at 6:01 PM Daniel Vetter wrote: > > On Wed, Jul 1, 2020 at 5:51 PM James Jones wrote: > > > > On 7/1/20 4:24 AM, Karol Herbst wrote: > > > On Wed, Jul 1, 2020 at 6:45 AM James Jones wrote: > > >> > > >> Thi

Re: [git pull] drm for 5.8-rc1

On Wed, Jul 1, 2020 at 7:37 PM James Jones wrote: > > On 7/1/20 10:04 AM, Karol Herbst wrote: > > On Wed, Jul 1, 2020 at 6:01 PM Daniel Vetter wrote: > >> > >> On Wed, Jul 1, 2020 at 5:51 PM James Jones wrote: > >>> > >>> On 7/1/20 4:24 AM,

Re: [PATCH 1/5] drm/nouveau: Check backlight IDs are >= 0, not > 0

Patches 1-5 are Reviewed-by: Karol Herbst I think it might be worth to test those patches on a system without any backlight devices just to verify we don't break things, but the code looked good already, so maybe we don't really need to test. On Thu, Aug 23, 2018 at 3:21 AM, Lyude Paul wrote

Re: mmiotracer hangs the system

sorry for that, but I forgot the patch 2016-11-19 11:56 GMT+01:00 Karol Herbst : > this is odd, I found a bug related to nouveau (modprobe/bind doesn't > return), but that isn't related to your issue at all or maybe it is > exactly this, cause the binding of the device doesn

Re: [Nouveau] [PATCH 01/17] drm/nouveau/core: add missing header dependencies

2016-10-24 9:13 GMT+02:00 Baoyou Xie : > > > On 23 October 2016 at 01:32, Karol Herbst wrote: >> >> I think it would be better to squash those commits: >> 1. for the includes >> 2. for static declerations >> > OK, I have resent new patch that squash tho

Re: [Nouveau] [PATCH] nouveau: hide gcc-4.9 -Wmaybe-uninitialized

uhh, that function looks so odd, ... yeah. Change looks fine. Reviewed-By: Karol Herbst 2016-10-24 17:30 GMT+02:00 Arnd Bergmann : > gcc-4.9 notices that the validate_init() function returns unintialized > data when called with a zero 'nr_buffers' argument, when called with the >

Re: [Nouveau] noveau: emergency shutdown handling is overcomplex and broken

Thanks for the pointer. But I don't like this patch. If you find a bug, make a bug report or just fix it if you know the fix already. Or write something in IRC. Or write on the Mailing list as a general question or something else But I really don't agree on doing it this way. You would have

Re: [Nouveau] [PATCH] drm/nouveau: fix unknown chipset for GTX 1060

we already have that included in 4.10 2016-12-12 12:26 GMT+01:00 Chris Chiu : > Nouveau driver shows unknown chipset (136000a1) for GTX 1060, so it > only gives VGA resolution on screen. Use the same chipset as nv134 > then it shows FullHD. This commit copies fields from nv134_chipset > to

Re: mmiotracer hangs the system

for the delay. Karol 2016-08-19 22:46 GMT+02:00 Karol Herbst : > Hi again, > > I was able to get a crash/freeze/something while unbinding/binding my > nvidia gpu from nouveau. > > Guess that means something is odd. I will investigate this more over > the weekend. > >

Re: [Nouveau] [PATCH] drm/nouveau: fix LEDS_CLASS=m configuration

2016-11-08 16:46 GMT+01:00 Ilia Mirkin : > On Tue, Nov 8, 2016 at 8:56 AM, Arnd Bergmann wrote: >> The newly introduced LED handling for nouveau fails to link when the >> driver is built-in but the LED subsystem is a loadable module: >> >> drivers/gpu/drm/nouveau/nouveau.o: In function

Re: [Nouveau] [PATCH] drm/nouveau: fix LEDS_CLASS=m configuration

2016-11-08 17:12 GMT+01:00 Arnd Bergmann : > On Tuesday, November 8, 2016 5:07:01 PM CET Lukas Wunner wrote: >> On Tue, Nov 08, 2016 at 04:52:49PM +0100, Arnd Bergmann wrote: >> > The underlying problem is that we already have a number of other >> > symbols that either have "depends on LEDS_CLASS"

Re: mmiotracer hangs the system

ight know where the issue is, but didn't confirm >> it yet. > > Thanks.I'm still using revert. Feel free to Cc me when you will have > some material to test. > >> >> Again, sorry for the delay. >> >> Karol >> >> 2016-08-19 22:46 GMT+02:00 Karol Herbst

Re: [Nouveau] [PATCH 01/17] drm/nouveau/core: add missing header dependencies

I think it would be better to squash those commits: 1. for the includes 2. for static declerations 2016-10-22 11:41 GMT+02:00 Baoyou Xie : > We get 2 warnings when building kernel with W=1: > drivers/gpu/drm/nouveau/nvkm/core/firmware.c:34:1: warning: no previous > prototype for

Re: mmiotracer hangs the system

Hi everybody, is there any update on that issue I missed somehow? I really don't want to leave the mmiotracer in a state, where it breaks something while fixing other issues. But for now, without being able to even reproduce the issue, I can't really do much, because the code in the current

Re: mmiotracer hangs the system

2016-08-19 15:02 GMT+02:00 Andy Shevchenko : > On Fri, Aug 19, 2016 at 1:35 PM, karol herbst wrote: >> is there any update on that issue I missed somehow? I really don't >> want to leave the mmiotracer in a state, where it breaks something >> while fixing other issues. >

Re: mmiotracer hangs the system

2016-08-19 17:35 GMT+02:00 Andy Shevchenko : > On Fri, Aug 19, 2016 at 6:08 PM, karol herbst wrote: >> 2016-08-19 15:02 GMT+02:00 Andy Shevchenko : >>> On Fri, Aug 19, 2016 at 1:35 PM, karol herbst wrote: >>>> is there any update on that issue I missed somehow? I r

Re: mmiotracer hangs the system

Hi again, I was able to get a crash/freeze/something while unbinding/binding my nvidia gpu from nouveau. Guess that means something is odd. I will investigate this more over the weekend. 2016-08-19 17:35 GMT+02:00 Andy Shevchenko : > On Fri, Aug 19, 2016 at 6:08 PM, karol herbst wrote: >

Re: [PATCH] drm/nouveau: Add support for clockgating on Fermi+

Hi Lyude, thanks for the great work. Just a view comments inline. 2017-04-25 20:38 GMT+02:00 Lyude : > This adds support for enabling automatic clockgating on nvidia GPUs for > Fermi and later generations. This saves a little bit of power, bringing > my fermi GPU's power consumption from ~28.3W

  1   2   >