On Fri, May 10, 2019 at 4:32 AM wrote:
> From: Liu Haitao
>
> The following call trace would be triggered as kmemleak is running.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:974
> in_atomic(): 1, irqs_disabled(): 1, pid: 2401, name: kmemleak
> Preemption
From: Liu Haitao
The following call trace would be triggered as kmemleak is running.
BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:974
in_atomic(): 1, irqs_disabled(): 1, pid: 2401, name: kmemleak
Preemption disabled at:
[] scan_block+0x31/0x120
CPU: 12 PID:
HI Anuj ,
I was building minimal image using $ bitbake core-image-minimal haven't
tried full-cmdline.
Not able to track why kernel "uname" has older timestamp rather than the
one from build/deploy/image
as seen by "ls -al
Am i missing any command or sequence here
--
It's picking up the minimal image instead of full-cmdline? Can you try:
runqemu tmp/deploy/images/qemux86/
or
runqemu qemux86 core-image-full-cmdline
Thanks,
Anuj
On Fri, 2019-05-10 at 06:46 +, AshishKumar Mishra wrote:
> HI Members ,
> Good Afternoon.
>
> I am trying to recompile the
