Re: [yocto] Replacing a configuration file from another recipe

2019-05-10 Thread Khem Raj
On 4/29/19 5:35 AM, Damien LEFEVRE wrote: Hi, In our base image we use nginx. I created a nginx.bbappend to add our PHP configuration in a separated layer. For a specific variant of the image I need to add an extra bit of nginx configuration. I though I could create a new recipe to

[yocto] Upcoming network outage: Fri, May 17 starting 10PM PDT (Sat, 5:00Z)

2019-05-10 Thread Michael Halstead
What: 30-minute network outage to Portland-hosted services When: Fri, May 17, between 10PM-3AM PDT (Sat, 05:00-10:00 UTC) Why : Network equipment replacement by our service provider Services Impacted: autobuilder.yoctoproject.org, downloads.yoctoproject.org, sstate.yoctoproject.org Our Portland

Re: [linux-yocto] [PATCH] kmemleak: change the lock of kmemleak_object to raw_spinlock_t

2019-05-10 Thread Bruce Ashfield
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

[yocto] [OE-core][RFC][PATCH] Remove irda-utils and the irda feature

2019-05-10 Thread Adrian Bunk
IrDA support was removed in kernel 4.17. Signed-off-by: Adrian Bunk --- documentation/ref-manual/ref-features.xml | 4 - meta-poky/conf/distro/poky-tiny.conf | 2 +- .../distro/include/default-distrovars.inc | 2 +- meta/conf/distro/include/maintainers.inc | 1 -

Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread Khem Raj
On 5/10/19 12:10 AM, AshishKumar Mishra wrote: 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

Re: [yocto] Yocto image systemd debugging

2019-05-10 Thread Lukasz Zemla
On Friday, May 10, 2019 10:09 AM, JH wrote: > > What do you mean by debug? > > In most cases 'systemctl status ', 'systemctl --failed', > > system-analyze and journalctl are efficient. Sometimes I set > > 'StandardOutput=journal+console' > > in service file to just see output during booting. >

[yocto] [meta-security][PATCH] apparmor: fetch from git

2019-05-10 Thread Alexander Kanavin
Tarballs from archive.ubuntu.com can and do disappear (similar to archive.debian.org). Signed-off-by: Alexander Kanavin --- recipes-mac/AppArmor/apparmor_2.13.2.bb | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/recipes-mac/AppArmor/apparmor_2.13.2.bb

[linux-yocto] [PATCH] kmemleak: change the lock of kmemleak_object to raw_spinlock_t

2019-05-10 Thread zhe.he
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:

Re: [yocto] Yocto image systemd debugging

2019-05-10 Thread JH
Hi Lukasz, > What do you mean by debug? > In most cases 'systemctl status ', 'systemctl --failed', > system-analyze > and journalctl are efficient. Sometimes I set > 'StandardOutput=journal+console' > in service file to just see output during booting. There is an ofono.service which failed by

Re: [Yocto-bsp] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread AshishKumar Mishra
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 --

Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread AshishKumar Mishra
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 --

Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread AshishKumar Mishra
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 --

Re: [Yocto-bsp] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread Mittal, Anuj
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

Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread Mittal, Anuj
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

Re: [linux-yocto] [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]

2019-05-10 Thread Mittal, Anuj
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

[yocto] Yocto image systemd debugging

2019-05-10 Thread Lukasz Zemla
On Friday, May 10, 2019 8:00 AM JH wrote: > How did you debug systemd running Yocto image on embedded system > when services or cron jobs failed to run? What do you mean by debug? In most cases 'systemctl status ', 'systemctl --failed', system-analyze and journalctl are efficient. Sometimes I

Re: [yocto] Yocto image systemd debugging

2019-05-10 Thread JH
Figured out crond log journalctl -u crond. Which systemd daemon for auto service launch during boot? Thank you. - jh On 5/10/19, JH wrote: > Hi, > > How did you debug systemd running Yocto image on embedded system when > services or cron jobs failed to run? > > Thank you. > > - jh > --

[yocto] Yocto image systemd debugging

2019-05-10 Thread JH
Hi, How did you debug systemd running Yocto image on embedded system when services or cron jobs failed to run? Thank you. - jh -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto