STATUS: FAILED BUILD: 1.8_M4.RC1: 8b3d3e7c957ad06c390886487f69aeb8e145da6a ENVIRONMENT: Lenovo AtomPC x86 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. I open this bug because the log parser found this line in dmesg and I don't know if it should be whitelisted or not. Central error: [ 0.000000] tsc: Fast TSC calibration failed *********************** [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1 [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:2304 nr_irqs:512 16 [ 0.000000] CPU 0 irqstacks, hard=f6808000 soft=f680a000 [ 0.000000] Console: colour VGA+ 80x25 [ 0.000000] console [tty0] enabled [ 0.000000] hpet clockevent registered [ 0.000000] tsc: Fast TSC calibration failed [ 0.000000] tsc: PIT calibration matches HPET. 1 loops [ 0.000000] tsc: Detected 1662.490 MHz processor [ 0.002004] Calibrating delay loop (skipped), value calculated using timer frequency.. 3324.98 BogoMIPS (lpj=1662490) [ 0.002011] pid_max: default: 32768 minimum: 301 [ 0.002029] ACPI: Core revision 20131218 [ 0.015607] ACPI: All ACPI Tables successfully acquired [ 0.016061] Security Framework initialized [ 0.016164] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.016170] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.016563] Initializing cgroup subsys debug
This error appears also on corei7-64, core-image-sato-sdk image tested with Cherrytrail hardware. @Saul: should be added to whitelist as a common error, because now it's added only for qemux86. meta-intel commit: cea00968b858b60222d68103491f076067d73876 poky: ea562de57590c966cd5a75fda8defecd397e6436 1.9_M3.rc1 build
Is this issue still reproducible?
This issue appears on 1.8.1 release, b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0 commit on NUC tested with genericx86-64, core-image-sato-sdk image. On 2.0 release it is added on whitelist. What should we do with this bug?
(In reply to comment #3) > This issue appears on 1.8.1 release, > b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0 commit on NUC tested with > genericx86-64, core-image-sato-sdk image. > > On 2.0 release it is added on whitelist. What should we do with this bug? If it was added to the white list for 2.0, then we can add it for 1.8.1 or close this as will not fix
You can backport it to 1.8 because it is added to whitelist for 2.0 release.
Setting this as resolved wontfix because the error is already whitelisted so it should be ignored.
As per last comments set it as verified.