Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-18 Thread Karol Herbst
On Thu, Aug 18, 2022 at 10:39 PM Lyude Paul wrote: > > So then - if we can get this patch re-submitted with the /* TODO */ added, > I'll be happy to push this > yeah, I'll send something out tomorrow then. > On Fri, 2022-08-12 at 01:07 +0200, Karol Herbst wrote: > > On Thu, Aug 11, 2022 at

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-18 Thread Lyude Paul
So then - if we can get this patch re-submitted with the /* TODO */ added, I'll be happy to push this On Fri, 2022-08-12 at 01:07 +0200, Karol Herbst wrote: > On Thu, Aug 11, 2022 at 11:20 PM Lyude Paul wrote: > > > > On Thu, 2022-08-11 at 00:08 +0200, Karol Herbst wrote: > > > the thing is,

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-11 Thread Karol Herbst
On Thu, Aug 11, 2022 at 11:20 PM Lyude Paul wrote: > > On Thu, 2022-08-11 at 00:08 +0200, Karol Herbst wrote: > > the thing is, without this patch, the "hw path" fails with a timeout > > of... 30 seconds?, the code falls back to sw and it takes up to 2-3 > > minutes to finish up. So even if this

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-11 Thread Lyude Paul
On Thu, 2022-08-11 at 00:08 +0200, Karol Herbst wrote: > the thing is, without this patch, the "hw path" fails with a timeout > of... 30 seconds?, the code falls back to sw and it takes up to 2-3 > minutes to finish up. So even if this solution is overkill, it fixes a > real issue. I suspect

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-10 Thread Karol Herbst
On Wed, Aug 10, 2022 at 11:35 PM Lyude Paul wrote: > > On Wed, 2022-08-10 at 13:59 +0200, Karol Herbst wrote: > > On Wed, Aug 10, 2022 at 12:42 PM Computer Enthusiastic > > wrote: > > > > > > Hello, > > > > > > The "supend to ram" issue (system freeze when resuming after suspend > > > to ram or

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-10 Thread Lyude Paul
On Wed, 2022-08-10 at 13:59 +0200, Karol Herbst wrote: > On Wed, Aug 10, 2022 at 12:42 PM Computer Enthusiastic > wrote: > > > > Hello, > > > > The "supend to ram" issue (system freeze when resuming after suspend > > to ram or disk hibernation) is still affecting the nouveau kernel > > module

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-10 Thread Karol Herbst
On Wed, Aug 10, 2022 at 12:42 PM Computer Enthusiastic wrote: > > Hello, > > The "supend to ram" issue (system freeze when resuming after suspend > to ram or disk hibernation) is still affecting the nouveau kernel > module from linux version 5 and above with nvidia GeForce 9600M GT and > other

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-08-10 Thread Computer Enthusiastic
Hello, The "supend to ram" issue (system freeze when resuming after suspend to ram or disk hibernation) is still affecting the nouveau kernel module from linux version 5 and above with nvidia GeForce 9600M GT and other nvidia graphic card with the same chipset [1][2][3]. I've been successfully

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2022-01-24 Thread computer enthusiastic
Hello, On Thu, Oct 14, 2021 at 02:07:33PM -0400, Ilia Mirkin wrote: > On Thu, Oct 14, 2021 at 12:51 PM Computer Enthusiastic > wrote: > > [..] > > > > The patch is "mm: security: introduce init_on_alloc=1 and init_on_free=1 > > boot options" (commit 6471384af2a6530696fc0203bafe4de41a23c9ef) [1].

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2021-10-14 Thread Ilia Mirkin
On Thu, Oct 14, 2021 at 12:51 PM Computer Enthusiastic wrote: > > Hello, > > Thanks for the answer. > > On Wed, Oct 13, 2021 at 01:43:56PM -0400, Ilia Mirkin wrote: > > The most straightforward thing, if you can reproduce at will, would be > > to do a bisect to figure out which change this

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2021-10-14 Thread Computer Enthusiastic
Hello, Thanks for the answer. On Wed, Oct 13, 2021 at 01:43:56PM -0400, Ilia Mirkin wrote: > The most straightforward thing, if you can reproduce at will, would be > to do a bisect to figure out which change this happened with. Once we > know which change caused the problem, it will hopefully

Re: [Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2021-10-13 Thread Ilia Mirkin
The most straightforward thing, if you can reproduce at will, would be to do a bisect to figure out which change this happened with. Once we know which change caused the problem, it will hopefully provide with more ability to sort out where we're going wrong. You can also play with things like

[Nouveau] Advice about debugging nouveau driver suspend issue (init_on_alloc=1 and init_on_free=1)

2021-10-13 Thread Computer Enthusiastic
Hello, Greeting to all list members. I hope this mailing list is the right place to ask about it, otherwise I apologize in advance and, please, direct me to the right mailing list. I would like to receive advice on how to debug (or help to debug) the noveau kernel module suspend issue reported