Date: Mon, 05 Feb 2018 16:42:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 225688] ppc64: Unable to read timebase Message-ID: <bug-225688-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225688 Bug ID: 225688 Summary: ppc64: Unable to read timebase Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: breno.leitao@gmail.com Created attachment 190344 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D190344&action= =3Dedit Get the timebase from the proper OF field. After revision rS328534('PPC64: use hwref instead of cpuid'), FreeBSD on powerpc64 virtual machine panics since it is unable to read the timebase, showing the following error: gcc version 4.2.1 20070831 patched [FreeBSD] WARNING: WITNESS option enabled, expect reduced performance. WARNING: Running on a broken hypervisor that does not support mandatory H_CLEAR_MOD and H_CLEAR_REF hypercalls. Performance will be suboptimal. VT: init without driver. get-property for timebase-frequency on zero phandle panic: Unable to determine timebase frequency! cpuid =3D 0 time =3D 1 KDB: stack backtrace: 0xc000000000008510: at .kdb_backtrace+0x5c 0xc000000000008640: at .vpanic+0x1a4 0xc000000000008700: at .panic+0x38 0xc000000000008790: at .chrp_timebase_freq+0x44 0xc000000000008820: at .platform_timebase_freq+0x78 0xc0000000000088b0: at .decr_init+0x54 0xc000000000008980: at .cpu_startup+0x20 0xc000000000008a10: at .mi_startup+0x11c 0xc000000000008aa0: at btext+0xb4 KDB: enter: panic With the change above, cpuref->cr_hwref does not contain the phandle anymo= re, thus, it never reads the proper CPU entry in OF. --=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-225688-8>