On 2018-08-31 14:42:25 [-0500], Grygorii Strashko wrote:
>
>
> On 08/31/2018 02:30 PM, Sebastian Andrzej Siewior wrote:
> > On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
> >>
> >> I've tried this and do not see warnings. I'm sending 4.14-rt patches i
> >> have as
> >> I could miss
On 2018-08-31 14:42:25 [-0500], Grygorii Strashko wrote:
>
>
> On 08/31/2018 02:30 PM, Sebastian Andrzej Siewior wrote:
> > On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
> >>
> >> I've tried this and do not see warnings. I'm sending 4.14-rt patches i
> >> have as
> >> I could miss
On 08/31/2018 02:30 PM, Sebastian Andrzej Siewior wrote:
> On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
>>
>> I've tried this and do not see warnings. I'm sending 4.14-rt patches i have
>> as
>> I could miss smth while cherry-picking.
>
> perfect. Thanks for the confirmation.
> I
On 08/31/2018 02:30 PM, Sebastian Andrzej Siewior wrote:
> On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
>>
>> I've tried this and do not see warnings. I'm sending 4.14-rt patches i have
>> as
>> I could miss smth while cherry-picking.
>
> perfect. Thanks for the confirmation.
> I
On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
>
> I've tried this and do not see warnings. I'm sending 4.14-rt patches i have as
> I could miss smth while cherry-picking.
perfect. Thanks for the confirmation.
I saw your three patches. Could you please instead just backport the two
On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
>
> I've tried this and do not see warnings. I'm sending 4.14-rt patches i have as
> I could miss smth while cherry-picking.
perfect. Thanks for the confirmation.
I saw your three patches. Could you please instead just backport the two
On 08/30/2018 04:14 AM, Sebastian Andrzej Siewior wrote:
> On 2018-08-29 16:28:50 [-0500], Grygorii Strashko wrote:
>>
>> Thank you. Are there any plans to back port them for 4.14-rt?
>> Patch [1] need to be reworked a bit, [2] - I was able to cherry-pick from
>> 4.18-rt.
>
> Grygorii, could
On 08/30/2018 04:14 AM, Sebastian Andrzej Siewior wrote:
> On 2018-08-29 16:28:50 [-0500], Grygorii Strashko wrote:
>>
>> Thank you. Are there any plans to back port them for 4.14-rt?
>> Patch [1] need to be reworked a bit, [2] - I was able to cherry-pick from
>> 4.18-rt.
>
> Grygorii, could
On 2018-08-29 16:28:50 [-0500], Grygorii Strashko wrote:
>
> Thank you. Are there any plans to back port them for 4.14-rt?
> Patch [1] need to be reworked a bit, [2] - I was able to cherry-pick from
> 4.18-rt.
Grygorii, could you please replace the second patch with
On 2018-08-29 16:28:50 [-0500], Grygorii Strashko wrote:
>
> Thank you. Are there any plans to back port them for 4.14-rt?
> Patch [1] need to be reworked a bit, [2] - I was able to cherry-pick from
> 4.18-rt.
Grygorii, could you please replace the second patch with
On Wed, 29 Aug 2018 16:28:50 -0500
Grygorii Strashko wrote:
> On 08/29/2018 09:08 AM, Sebastian Andrzej Siewior wrote:
> > On 2018-08-28 18:28:42 [-0500], Grygorii Strashko wrote:
>
> [...]
>
> >> [0.912275] [] alloc_pages_current+0xcc/0xe0
> >> [0.912287] []
On Wed, 29 Aug 2018 16:28:50 -0500
Grygorii Strashko wrote:
> On 08/29/2018 09:08 AM, Sebastian Andrzej Siewior wrote:
> > On 2018-08-28 18:28:42 [-0500], Grygorii Strashko wrote:
>
> [...]
>
> >> [0.912275] [] alloc_pages_current+0xcc/0xe0
> >> [0.912287] []
On 08/29/2018 09:08 AM, Sebastian Andrzej Siewior wrote:
> On 2018-08-28 18:28:42 [-0500], Grygorii Strashko wrote:
[...]
>> [0.912275] [] alloc_pages_current+0xcc/0xe0
>> [0.912287] [] its_allocate_pending_table+0x60/0xa0
>> [0.912295] [] its_cpu_init+0x2a0/0x380
>> [
On 08/29/2018 09:08 AM, Sebastian Andrzej Siewior wrote:
> On 2018-08-28 18:28:42 [-0500], Grygorii Strashko wrote:
[...]
>> [0.912275] [] alloc_pages_current+0xcc/0xe0
>> [0.912287] [] its_allocate_pending_table+0x60/0xa0
>> [0.912295] [] its_cpu_init+0x2a0/0x380
>> [
On 2018-08-28 18:28:42 [-0500], Grygorii Strashko wrote:
> Hi
Hi,
…
> = Log 1 =
…
> [0.625149] GICv3: CPU1: found redistributor 1 region 0:0x018a
> [0.625176] BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:974
> [0.625182]
On 2018-08-28 18:28:42 [-0500], Grygorii Strashko wrote:
> Hi
Hi,
…
> = Log 1 =
…
> [0.625149] GICv3: CPU1: found redistributor 1 region 0:0x018a
> [0.625176] BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:974
> [0.625182]
Hi
I can see below back traces during secondary CPUs initialization (boot) on TI's
AM6 SoC (ARM64 4 CPUs)
with debug options enabled it happens without CONFIG_NUMA=n (log 1) and with
CONFIG_NUMA=y.
This is TI branch, there are no RT specific changes.
I've also found the similar issue was
Hi
I can see below back traces during secondary CPUs initialization (boot) on TI's
AM6 SoC (ARM64 4 CPUs)
with debug options enabled it happens without CONFIG_NUMA=n (log 1) and with
CONFIG_NUMA=y.
This is TI branch, there are no RT specific changes.
I've also found the similar issue was
18 matches
Mail list logo