7806 2015-05-25 11:33:20 +0000 Parselogs: Corei7_64 LSB kernel error (Cannot find map file) 2015-09-08 07:12:11 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-intel 1.8 NUC x86_64 VERIFIED FIXED http://yocto-lava.rb.intel.com/dashboard/attachment/3401/view Medium normal 1.9 1 georgex.l.musat georgex.l.musat dvhart cristina-danielax.agurida --- Regression (Found by QA test) Don't know oldest_to_newest 51240 0 georgex.l.musat 2015-05-25 11:33:20 +0000 meta-intel : f9738ec19d3b2864c0bd71b9bb3418d16e922a12 meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 poky : fido-13.0.0 Yocto 1.8.rc1 image type core-image-sato-sdk target intel-corei7-64-lsb machine NUC STATUS: FAILED BUILD: Initial default ENVIRONMENT: corei7 on NUC STEPS TO REPRODUCE: Parse dmesg log and all log files in /var/log for keywords like: "error" , "failed" , "cannot", "can't" etc. Filter out the known and invalid errors or errors that appear in certain situations and need to be ignored. EXPECTED OUTCOME: No errors or fails should be present in logs ACTUAL OUTCOME: This error was found by the log parser: Log: /var/log//kern.log ----------------------- Central error: May 14 22:58:23 intel-corei7-64 kernel: Cannot find map file. *********************** May 14 22:58:23 intel-corei7-64 kernel: klogd 1.5.1, log source = /proc/kmsg started. May 14 22:58:23 intel-corei7-64 kernel: Cannot find map file. May 14 22:58:23 intel-corei7-64 kernel: Loaded 88871 symbols from 17 modules. May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] Initializing cgroup subsys cpuset May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] Initializing cgroup subsys cpu May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] Initializing cgroup subsys cpuacct May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] Linux version 3.19.5-yocto-standard (pokybuild@yocto-ab-master) (gcc version 4.9.2 (GCC) ) #1 SMP PREEMPT Tue May 12 03:40:14 PDT 2015 May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz root=/dev/sda2 rw console=ttyS0,115200 console=tty0 quiet May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] e820: BIOS-provided physical RAM map: May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d7ff] usable May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009d800-0x000000000009ffff] reserved May 14 22:58:23 intel-corei7-64 kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved 51268 1 sgw 2015-05-26 19:45:28 +0000 Please add this warning to the white list, it's not really a bug. Apparently klogd identifies a map file by looking for a Version symbol. But kernels later than 2.6.27 don't define this symbol if KALLSYMS=y, because in that case, the kernel includes its own symbol table and doesn't need a map file.The problem is that the kernel hackers and the people responsible for sysklogd can't agree on whose fault this is and which program should be changed, so it just doesn't get fixed. 51278 2 georgex.l.musat 2015-05-27 06:32:35 +0000 Ok, will put this into the next whitelist update. 51690 3 georgex.l.musat 2015-06-15 08:35:09 +0000 Error added to whitelist: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=7a4d72dc18ff4ce5b02684026ba1d564a2ab5c41 53816 4 cristina-danielax.agurida 2015-09-08 07:12:11 +0000 Verified.