On Wed, Jan 24, 2024 at 7:19 AM Erico Nunes wrote:
>
> On Fri, Jan 19, 2024 at 2:50 AM Qiang Yu wrote:
> >
> > On Thu, Jan 18, 2024 at 7:14 PM Erico Nunes wrote:
> > >
> > > On Thu, Jan 18, 2024 at 2:36 AM Qiang Yu wrote:
> > > >
> > > > So this is caused by same job trigger both done and timeo
On Fri, Jan 19, 2024 at 2:50 AM Qiang Yu wrote:
>
> On Thu, Jan 18, 2024 at 7:14 PM Erico Nunes wrote:
> >
> > On Thu, Jan 18, 2024 at 2:36 AM Qiang Yu wrote:
> > >
> > > So this is caused by same job trigger both done and timeout handling?
> > > I think a better way to solve this is to make sur
On Thu, Jan 18, 2024 at 7:14 PM Erico Nunes wrote:
>
> On Thu, Jan 18, 2024 at 2:36 AM Qiang Yu wrote:
> >
> > So this is caused by same job trigger both done and timeout handling?
> > I think a better way to solve this is to make sure only one handler
> > (done or timeout) process the job instea
On Thu, Jan 18, 2024 at 2:36 AM Qiang Yu wrote:
>
> So this is caused by same job trigger both done and timeout handling?
> I think a better way to solve this is to make sure only one handler
> (done or timeout) process the job instead of just making lima_pm_idle()
> unique.
It's not very clear t
So this is caused by same job trigger both done and timeout handling?
I think a better way to solve this is to make sure only one handler
(done or timeout) process the job instead of just making lima_pm_idle()
unique.
Regards,
Qiang
On Wed, Jan 17, 2024 at 11:12 AM Erico Nunes wrote:
>
> In case
On Tue, Jan 16, 2024 at 7:12 PM Erico Nunes wrote:
>
> In case a task manages to complete but it took just long enough to also
> trigger the timeout handler, the current code results in a refcount
> imbalance on lima_pm_idle.
>
> While this can be a rare occurrence, when it happens it may fill use
In case a task manages to complete but it took just long enough to also
trigger the timeout handler, the current code results in a refcount
imbalance on lima_pm_idle.
While this can be a rare occurrence, when it happens it may fill user
logs with stack traces such as:
[10136.669170] WARNING: CPU:
