Le 24/09/2017 à 18:05, Guenter Roeck a écrit :
On 09/21/2017 11:44 AM, Christophe LEROY wrote:
Le 20/09/2017 à 05:45, Guenter Roeck a écrit :
On 09/19/2017 08:05 PM, Michael Ellerman wrote:
Guenter Roeck writes:
Hi,
I see a the following traceback when running an
On 09/21/2017 11:44 AM, Christophe LEROY wrote:
Le 20/09/2017 à 05:45, Guenter Roeck a écrit :
On 09/19/2017 08:05 PM, Michael Ellerman wrote:
Guenter Roeck writes:
Hi,
I see a the following traceback when running an SMP image based on
85xx/mpc85xx_cds_defconfig in
Le 20/09/2017 à 05:45, Guenter Roeck a écrit :
On 09/19/2017 08:05 PM, Michael Ellerman wrote:
Guenter Roeck writes:
Hi,
I see a the following traceback when running an SMP image based on
85xx/mpc85xx_cds_defconfig in qemu.
[ cut here ]
On 09/19/2017 08:05 PM, Michael Ellerman wrote:
Guenter Roeck writes:
Hi,
I see a the following traceback when running an SMP image based on
85xx/mpc85xx_cds_defconfig in qemu.
[ cut here ]
WARNING: CPU: 0 PID: 1 at kernel/smp.c:416
Guenter Roeck writes:
> Hi,
>
> I see a the following traceback when running an SMP image based on
> 85xx/mpc85xx_cds_defconfig in qemu.
>
> [ cut here ]
> WARNING: CPU: 0 PID: 1 at kernel/smp.c:416 smp_call_function_many+0xcc/0x2fc
> CPU: 0 PID: 1
Hi,
I see a the following traceback when running an SMP image based on
85xx/mpc85xx_cds_defconfig in qemu.
[ cut here ]
WARNING: CPU: 0 PID: 1 at kernel/smp.c:416 smp_call_function_many+0xcc/0x2fc
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0-rc1-9-g0666f56 #1