Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Mar 2022 14:27:16 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-arm@FreeBSD.org
Subject:   [Bug 262700] pmu0: Cannot find CPU with MPIDR: 0x00000002
Message-ID:  <bug-262700-7@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262700

            Bug ID: 262700
           Summary: pmu0: Cannot find CPU with MPIDR: 0x00000002
           Product: Base System
           Version: CURRENT
          Hardware: arm64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: arm
          Assignee: freebsd-arm@FreeBSD.org
          Reporter: jfc@mit.edu

My OverDrive 1000 (4x ARM Cortex A-57) reports during boot:

Starting CPU 1 (1)
Starting CPU 2 (100)
Starting CPU 3 (101)
...
cpulist0: <Open Firmware CPU Group> on ofwbus0
cpu0: <Open Firmware CPU> on cpulist0
cpu1: <Open Firmware CPU> on cpulist0
cpu2: <Open Firmware CPU> on cpulist0
cpu3: <Open Firmware CPU> on cpulist0
pmu0: <Performance Monitoring Unit> irq 0,1,2,3 on ofwbus0
pmu0: Cannot find CPU with MPIDR: 0x00000002
pmu0: Cannot parse affinity for CPUid: 2.
device_attach: pmu0 attach returned 6
ahci0: <AHCI SATA controller> mem 0xe0300000-0xe03effff irq 9 on simplebus0

Is the (100) in the CPU list the MPIDR for CPU 2?  If so there's confusion
between sparse and dense processor numberings.

Reported against CURRENT but also present in stable/13.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262700-7>