Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
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 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
Yes . But this difference we expect in some minutes. But what i am observing is ( attached snapshot ) :- 1) First Compilation around ( 4:10) bitbake cleanall + bitbake core-image-minimal uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 4:30 2) Second Compilation around ( 5:00) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 5:25 2) Second Compilation around ( 5:00) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 5:25 3) Third Compilation around ( 5:45) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a: Time shown is 4:24 timestamp of files in deploy/images/: Time shown is around 6:05 So , time shown by "uname -a" is retains older value even though i had compiled the linux multiple times . Currently , only way i am able to bypass this behavior is to do bitbake -c cleanall linux-yocto before every compilation. Thanks Ashish On Fri, May 10, 2019 at 10:23 PM Khem Raj wrote: > > > 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 command or sequence here > > > > > > uname will show the time when it was built, which might be different > time then the one when it was copied over to deploy. > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Error of " fs.inotify.max_user_watches " while using bitbake [ Yocto-2.6.1 + Qemux86]
Hi Members , Can team members please let me know the solution & what is causing the below mentioned error ? ( I am having around 128GB of disk space still left , hence don't think that space is the issue here ) ~/Documents/linux-foundation-projects/yocto/poky/build (slef-bsp) : bitbake -vn virtual/kernel ERROR: No space left on device or exceeds fs.inotify.max_user_watches? ERROR: To check max_user_watches: sysctl -n fs.inotify.max_user_watches. ERROR: To modify max_user_watches: sysctl -n -w fs.inotify.max_user_watches=. ERROR: Root privilege is required to modify max_user_watches. ERROR: Command execution failed: Traceback (most recent call last): File "/home/ashish/Documents/linux-foundation-projects/yocto/poky/bitbake/lib/bb/command.py", line 113, in runAsyncCommand self.cooker.updateCache() File "/home/ashish/Documents/linux-foundation-projects/yocto/poky/bitbake/lib/bb/cooker.py", line 1541, in updateCache self.add_filewatch([[dirent]], dirs=True) File "/home/ashish/Documents/linux-foundation-projects/yocto/poky/bitbake/lib/bb/cooker.py", line 287, in add_filewatch watcher.add_watch(f, self.watchmask, quiet=False) File "/home/ashish/Documents/linux-foundation-projects/yocto/poky/bitbake/lib/pyinotify.py", line 1924, in add_watch raise WatchManagerError(err, ret_) pyinotify.WatchManagerError: add_watch: cannot watch /home/ashish/Documents/linux-foundation-projects/yocto/poky/meta/recipes-devtools/mtd WD=-1, Errno=No space left on device (ENOSPC) Summary: There were 5 ERROR messages shown, returning a non-zero exit code. ~/Documents/linux-foundation-projects/yocto/poky/build (self-bsp) : ~/Documents/linux-foundation-projects/yocto/poky/build (self-bsp) : df -h /home/ashish/ Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p3 433G 284G 127G 70% / Thanks Ashish -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [Yocto-bsp] Error of " fs.inotify.max_user_watches " while using bitbake [ Yocto-2.6.1 + Qemux86]
Yes , i checked the value & increased it 64K ( got pointer from https://hub.docker.com/r/wolverine2k/yocto-build-env/) It got the same error again today . Currently i have increased the value from 64K to 512K. But raised the query to check if i am doing any thing wrong here or missing any caution. Like if at 512K if we get the error again , not sure if increasing the value is the only value. Thanks Ashish On Mon, May 13, 2019 at 3:47 PM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Mon, 2019-05-13 at 15:38 +0530, AshishKumar Mishra wrote: > > Can team members please let me know the solution & what is causing > > the below mentioned error ? > > ( I am having around 128GB of disk space still left , hence don't > > think that space is the issue here ) > > > > ~/Documents/linux-foundation-projects/yocto/poky/build (slef-bsp) : > bitbake -vn virtual/kernel > > ERROR: No space left on device or exceeds fs.inotify.max_user_watches? > > ERROR: To check max_user_watches: sysctl -n fs.inotify.max_user_watches. > > ERROR: To modify max_user_watches: sysctl -n -w > fs.inotify.max_user_watches=. > > ERROR: Root privilege is required to modify max_user_watches. > > ERROR: Command execution failed: Traceback (most recent call last): > > Did you try what it says above and check the max_user_watches value? > > Also, did you check you had enough free inodes on the filesystem? > > Cheers, > > Richard > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Timestamp error between zImage & uname-a [ Yocto-2.6.1 + Qemux86 ]
Thanks Ralph for informative reply . Will check once again after deleting the file you suggested . Ashish On Mon, May 13, 2019, 7:05 PM Ralph Siemsen wrote: > Hi Ashish, > > On Mon, May 13, 2019 at 5:57 AM AshishKumar Mishra < > ashish.emailaddr...@gmail.com> wrote: > >> So , time shown by "uname -a" is retains older value even though >> i had compiled the linux multiple times . >> > > This is normal behaviour, even when building the kernel directly (eg. not > using Yocto). It is a bit surprising at first, but it all comes down to > dependencies in the Makefile for the kernel. > > The version string displayed by "uname -a" comes from init/version.c in > the kernel source tree. Specifically the symbol UTS_VERSION, which is > defined in include/generated/compile.h. This file is produced when you > first build, and remains thereafter, unless you do "make clean" or > equivalent. > > Currently , only way i am able to bypass this behavior is to do bitbake -c >> cleanall linux-yocto >> before every compilation. >> > > You can delete the include/generated/compile.h file in your kernel build > directory. Upon rebuild of kernel, the file will be re-created with the > current date/time. > > Regards > Ralph > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
