ubuntu_boot:log_check: intel_pmu_init warnings on spitfire

Bug #1953138 reported by Stefan Bader
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned

Bug Description

The log check on spitfire(amd64) while doing boot tests reports the following:

[ 0.239511] WARNING: CPU: 0 PID: 1 at /build/linux-3Zqs18/linux-4.4.0/arch/x86/events/intel/core.c:3656 intel_pmu_init+0xc48/0xe03()
[ 0.238545] WARNING: CPU: 0 PID: 1 at /build/linux-Bc7FjL/linux-4.4.0/arch/x86/events/intel/core.c:3656 intel_pmu_init+0xc48/0xe03()
[ 0.239193] WARNING: CPU: 0 PID: 1 at /build/linux-Bc7FjL/linux-4.4.0/arch/x86/events/intel/core.c:3656 intel_pmu_init+0xc48/0xe03()

I don't think this is a regression since we only changed hugetlbfs and the warning is reporting that the HW supports less perf events than set up.

@3654:
        if (x86_pmu.num_counters_fixed > INTEL_PMC_MAX_FIXED) {
                WARN(1, KERN_ERR "hw perf events fixed %d > max(%d), clipping!",
                     x86_pmu.num_counters_fixed, INTEL_PMC_MAX_FIXED);
                x86_pmu.num_counters_fixed = INTEL_PMC_MAX_FIXED;
        }

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.