From owner-freebsd-ppc@freebsd.org Sun May 13 08:14:07 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69193FCD72D for ; Sun, 13 May 2018 08:14:07 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic306-20.consmr.mail.ne1.yahoo.com (sonic306-20.consmr.mail.ne1.yahoo.com [66.163.189.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBE746B365 for ; Sun, 13 May 2018 08:14:06 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: Pw0_wp4VM1lkGxGurXv0.uOWGljyz8XyYnm2ayR5DqEhFYwzBORcGhH2AZ7sGZF 743LbM6T.jJeoVFEL.y5DahLoQ1dZ1adub3sU_29wYfb1_aZk9OFbzwSwOx6YWF5r7zZTDftjpZi SKmSqG5E_0V_vXsp4JWxt4Yl6j5AeYjM88NlDK9xYa289ssIRLxVQaNlumcsM2yjeR0E4grCau.O lNSjZLSeDBYjzbQSheTl0wNN2gERHGwannajrgFKV9YBEwO2HgBCiWXwYUQgY_hLlegE.KaTfqrG tWlvv_BwZ5ePTrO6TRe7hyJVutjHAS306j8vgFJYqXRkNp0vu5tzx4asJiZ5andE_OSbM2QDWxE9 IcSJdqmGHyBrbwvOExQtNqK5aXDoi3VY4O6l1jFEATkOngxHGV_HVcn7xLmLTSKFN5WES.5640q2 _rUTi02yhvJMGNYE6Nx6aER2X1PoI9tASFIVXi9xMO2JjT3Chv3wbvEnILDDGZs6KzY89C9CFtIE Elqws63GTA3.MiYfdGFD9OuSYVvIcKCku6izj3WobWvsYxLAx9ntoJcq24yV3DrSrmxvLwRlcVzf csIlve2XZFdP__zq5TNZkPMPVh9kL2O82ukNaAqeRU3S4vw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ne1.yahoo.com with HTTP; Sun, 13 May 2018 08:13:59 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp417.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 5c19a5b6b7aca08a23836d59d003e95a; Sun, 13 May 2018 08:13:56 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Still true at -r333575 : head -r320458 (e.g.) amd64 -> powerpc64 cross build's install32 during installworld: /usr/src/share/mk/bsd.linker.mk tried to use "head" when PATH provided no access (head is missing) From: Mark Millard In-Reply-To: <8EB87EA5-0ED6-4F46-80FC-1A0DB29CF7D6@dsl-only.net> Date: Sun, 13 May 2018 01:13:55 -0700 Cc: FreeBSD Toolchain , FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <84A73CB0-CBCB-4EE4-A4B7-B8B2F25EECB5@yahoo.com> References: <0E42D991-D350-4DC1-A683-CEA506167520@dsl-only.net> <8F22B659-90DE-42E5-B4C6-75C9B9626462@dsl-only.net> <8EB87EA5-0ED6-4F46-80FC-1A0DB29CF7D6@dsl-only.net> To: Bryan Drewery X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2018 08:14:07 -0000 Retrying the amd64 -> powerpc64 cross build via a powerpc64-gcc this time, combined with WITH_LIB32=3D , got: "sh: head: not found" and = its later consequences, like before for installworld (to a directory on the amd64 host context). This is from the /usr/src/share/mk/bsd.linker.mk = line that results in: (/usr/local/powerpc64-freebsd/bin/ld --version || echo none) | head -n 1 but head is not available by default at the time (lib32 context). (I = make head be available via using LOCAL_ITOOLS=3Dhead in order to work around = the issue.) An example of the messages (without having LOCAL_ITOOLS=3Dhead) is: --- _installlinks --- install -l s ../../libexec/ld-elf32.so.1 = /usr/obj/DESTDIRs/xtcgcc-powerpc64-installworld/usr/libexec/ld-elf32.so.1 cd /usr/src/usr.bin/ldd; PROG=3Dldd32 . . . . . . . . . MAKEOBJDIRPREFIX=3D MK_MAN=3Dno MK_HTML=3Dno MK_TOOLCHAIN=3Dno = -DLIBRARIES_ONLY install sh: head: not found make[4]: "/usr/src/share/mk/bsd.linker.mk" line 47: warning: = "(/usr/local/powerpc64-unknown-freebsd12.0/bin/ld --version || echo = none) | head -n 1" returned non-zero status make[4]: "/usr/src/share/mk/bsd.linker.mk" line 58: warning: Unknown = linker from XLD=3D/usr/local/powerpc64-unknown-freebsd12.0/bin/ld: , = defaulting to bfd The two "make[4]" lines are consequences of the prior "sh: head: not = found" issue that leaded to a "non-zero status" independent of the prior = "--version" and "echo none" material. It then leads to assuming bfd. Using LOCAL_ITOOLS=3Dhead makes head available and so then the status = value check works. On 2017-Nov-25, at 4:54 PM, Mark Millard wrote: . . . On 2017-Jul-26, at 3:06 AM, Mark Millard wrote: . . . =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Sun May 13 23:13:07 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80A29FD9540 for ; Sun, 13 May 2018 23:13:07 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic305-21.consmr.mail.gq1.yahoo.com (sonic305-21.consmr.mail.gq1.yahoo.com [98.137.64.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E949D836A8 for ; Sun, 13 May 2018 23:13:06 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: fkgWJ1sVM1m2TR9a.e2phHQFjC9vr1LLAS.3K_rnPQlnUC388i5fsDQF6q5eq7r DGPX9nRoB4OPkt1ZSE8Yg3lYlYCvDlcsMwO7y729GjIaMIxmpuc11gr5e5DDoO1imb3e_VaSU1vv 8txPV0Y3u23G6GpDU4FK.K8LlVfPv63dem9LWIohzIHn56Du_gm5GqzO5BU03h6cKUO6gMfLQZMp v8XUPcxoqpGQPhVfPS6PcTv3JzlZqZyQ3CZIl1dHDsIRmH0wCPcPlbMln.2lx5UeQl0EhDzn2tA4 nfVS1yQbwcRT6P42k85rI19RIyLefzibJT40w0EoUxIiBWEu4arw8KF.HgCgpocvkpuYXly6jvS4 1mcmdN.rbyhWPZG1gdGlMFdkSxG7LRTpL5XWvY1XGUzU0Vlq3C5nZZH_3MaROb6saIu_bmFgk.5_ DQV0TLdHc3Fx7WTsTixWSj82isPruDHToEepspsG9rBo3WgzSbvjj_5lGtvkmMqASQOFKf87xu_8 RC4ZH3xPULww8XGvieTTzXLbbjupCn6L8pCb3_JtVSCntOiHzEe8Rec9euOWxMxnFqAwvZPWR3In 4wcYlwyMnwwxM1dmhgBa_Cf3m68Y98lB6yt4loCGYLFugh3BihA-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.gq1.yahoo.com with HTTP; Sun, 13 May 2018 23:13:00 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp423.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 8fcb695bce434c34c10f6f97d63dc061 for ; Sun, 13 May 2018 23:12:59 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: head -r333575's kernel: fails to boot old PowerMac G5 so-called "Quad Core", failing very early Message-Id: <94E173AD-74C0-43ED-9D0D-86D9A56C2A74@yahoo.com> Date: Sun, 13 May 2018 16:12:58 -0700 To: FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 May 2018 23:13:07 -0000 I'd had to revert to the old kernel from the last time I'd updated the old PowerMac G5 "Quad Core" for powerpc64 style use [back in early Jan.]: # uname -apKU FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r327364M powerpc = powerpc64 1200054 1200063 because buildkernel instalkernel for -r333575 results for all the following fail in the same way: A) devel/powerpc64-xtoolchain-gcc based build (from /usr/ports/ -r469767 so before the upgrade to 6.4) B) gcc 4.2.1 based build C) system clang6 based build These were all amd64 -> powerpc64 cross builds. Each is a non-debug build --but with symbols. The following 3 lines are displayed and nothing more visible happens after that in the boot sequence, the lines are the ones that start with: GDB: no debug ports present KDB: debugger backends: KDB: current backend: It does not display any Copyright notice line or even clear the screen. The old -r327364 kernel boots the old PowerMac G5 "Quad Core" just fine (with the -r333575 world at this point). So far, this much suggests the issue is not toolchain related, although in all 3 cases devel/powerpc64-binutils is in use so it can not be eliminated as easily. [A problem is I'm very restricted on the amount of time I can be involved in bisecting this and 333575-327364=3D=3D6211 for the version span. Another problem is that, at the failure stage, getting information about failure details is problematical on the old PowerMac, even if I could apply the time for such.] For powerpc64 context I have: # more /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG # # GENERIC -- Custom configuration for the powerpc/powerpc64 # include "GENERIC64" ident GENERIC64vtsc-NODBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols nooptions PS3 # Sony Playstation 3 = HACK!!! to allow sc options KDB # Enable kernel debugger support options ALT_BREAK_TO_DEBUGGER options BREAK_TO_DEBUGGER # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger options GDB # HACK!!! ... # Extra stuff: #options VERBOSE_SYSINIT # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE #options KTR #options KTR_MASK=3DKTR_TRAP ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable any extra checking for. . . nooptions DEADLKRES # Enable the deadlock resolver nooptions INVARIANTS # Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DIAGNOSTIC nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones device filemon device geom_label # svnlite diff = /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp Index: /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp = (revision 333575) +++ /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp = (working copy) @@ -1176,7 +1176,7 @@ // For SVR4, don't emit a move for the CR spill slot if we = haven't // spilled CRs. if (isSVR4ABI && (PPC::CR2 <=3D Reg && Reg <=3D PPC::CR4) - && !MustSaveCR) + && (!MustSaveCR && isPPC64)) continue; // For 64-bit SVR4 when we have spilled CRs, the spill location Note: The following file does not intend a powerpc64 functional change but a powerpc (32-bit) change: # svnlite diff /usr/src/sys/powerpc/ofw/ofw_machdep.c Index: /usr/src/sys/powerpc/ofw/ofw_machdep.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/sys/powerpc/ofw/ofw_machdep.c (revision 333575) +++ /usr/src/sys/powerpc/ofw/ofw_machdep.c (working copy) @@ -116,26 +116,27 @@ * Assume that interrupt are disabled at this point, or * SPRG1-3 could be trashed */ -#ifdef __powerpc64__ - __asm __volatile("mtsprg1 %0\n\t" - "mtsprg2 %1\n\t" - "mtsprg3 %2\n\t" - : - : "r"(ofmsr[2]), - "r"(ofmsr[3]), - "r"(ofmsr[4])); -#else - __asm __volatile("mfsprg0 %0\n\t" - "mtsprg0 %1\n\t" - "mtsprg1 %2\n\t" - "mtsprg2 %3\n\t" - "mtsprg3 %4\n\t" - : "=3D&r"(ofw_sprg0_save) - : "r"(ofmsr[1]), - "r"(ofmsr[2]), - "r"(ofmsr[3]), - "r"(ofmsr[4])); +#ifndef __powerpc64__ + if (!(cpu_features & PPC_FEATURE_64)) + __asm __volatile("mfsprg0 %0\n\t" + "mtsprg0 %1\n\t" + "mtsprg1 %2\n\t" + "mtsprg2 %3\n\t" + "mtsprg3 %4\n\t" + : "=3D&r"(ofw_sprg0_save) + : "r"(ofmsr[1]), + "r"(ofmsr[2]), + "r"(ofmsr[3]), + "r"(ofmsr[4])); + else #endif + __asm __volatile("mtsprg1 %0\n\t" + "mtsprg2 %1\n\t" + "mtsprg3 %2\n\t" + : + : "r"(ofmsr[2]), + "r"(ofmsr[3]), + "r"(ofmsr[4])); } static __inline void @@ -152,7 +153,8 @@ * PCPU data cannot be used until this routine is called ! */ #ifndef __powerpc64__ - __asm __volatile("mtsprg0 %0" :: "r"(ofw_sprg0_save)); + if (!(cpu_features & PPC_FEATURE_64)) + __asm __volatile("mtsprg0 %0" :: "r"(ofw_sprg0_save)); #endif } #endif Note: The following file's change is actually for !defined(__powerpc64__) added code . . . # svnlite diff /usr/src/sys/powerpc/aim/mmu_oea64.c Index: /usr/src/sys/powerpc/aim/mmu_oea64.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/src/sys/powerpc/aim/mmu_oea64.c (revision 333575) +++ /usr/src/sys/powerpc/aim/mmu_oea64.c (working copy) @@ -1820,6 +1820,18 @@ PV_PAGE_UNLOCK(m); } +#if defined(AIM) && !defined(__powerpc64__) +// +// Part of PowerMac G5 HACK FOR PROBLEM FINDING. . . +// (G5 used via 32-bit FreeBSD.) +// + +extern char _GOT_START_[]; // beginning of .got/.got.plt +extern char _GOT_END_[]; // ending of .got/.got.plt + +extern vm_offset_t __startkernel, __endkernel; +#endif + /* * Map a wired page into kernel virtual address space. */ @@ -1830,6 +1842,52 @@ struct pvo_entry *pvo, *oldpvo; pvo =3D alloc_pvo_entry(0); +#if defined(AIM) && !defined(__powerpc64__) + // + // PowerMac G5 HACK FOR PROBLEM FINDING. . . + // (G5 used via 32-bit FreeBSD.) + // + // As a problem-finding-aid try to catch some examples of + // jumping to non-code in the kernel before it tries to + // execute that that code. Hopefully this will show where + // the bad jump into the likes of the .hash section is + // happening. (dbb bt and vmcore.*'s have not lead to + // that information so far.) + // + if (cpu_features & PPC_FEATURE_64) + { + // First deal with pages that should have the original + // VM_PROT_EXECUTE status for something on the page + // (most pages in the kernel area). So pages with some + // byte(s) from .text, .got, or .got.plt, along with + // any requested from before where __startkernel + // indicates. Also any va requested from a page + // containing where __endkernel indicates or later + // gets VM_PROT_EXECUTE if such a va is requested. + // + // So: have just the rest of the kernel area not have + // VM_PROT_EXECUTE status in hopes that it will report + // where the code is that is making bad jumps to + // non-code, such as jumping into the .hash section + // instead of reporting on illegal instructions + // from the incorrect traget area. + // + if ( va < ((vm_offset_t)(etext+(PAGE_SIZE-1)) & = ~PAGE_MASK) ) + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE | VM_PROT_EXECUTE; + + else if ( ((vm_offset_t)_GOT_START_ & ~PAGE_MASK) <=3D = va + && va < ((vm_offset_t)(_GOT_END_+(PAGE_SIZE-1)) = & ~PAGE_MASK) + ) + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE | VM_PROT_EXECUTE; + + else if ( va < (__endkernel & ~PAGE_MASK) ) + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE; + + else // Otherwise do as before the HACK: + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE | VM_PROT_EXECUTE; + } + else +#endif pvo->pvo_pte.prot =3D VM_PROT_READ | VM_PROT_WRITE | = VM_PROT_EXECUTE; pvo->pvo_pte.pa =3D (pa & ~ADDR_POFF) | moea64_calc_wimg(pa, = ma); pvo->pvo_vaddr |=3D PVO_WIRED; Note: The following should not matter because it is only for devel/powerpc64-gcc but gcc 4.2.1 and system clang6 got the same result: # svnlite diff /usr/ports/devel/powerpc64-gcc/Makefile Index: /usr/ports/devel/powerpc64-gcc/Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/ports/devel/powerpc64-gcc/Makefile (revision 469767) +++ /usr/ports/devel/powerpc64-gcc/Makefile (working copy) @@ -2,7 +2,7 @@ PORTNAME=3D gcc PORTVERSION=3D 6.3.0 -PORTREVISION=3D 5 +PORTREVISION=3D 6 CATEGORIES=3D devel MASTER_SITES=3D GCC/releases/gcc-${DISTVERSION} PKGNAMEPREFIX?=3D powerpc64- @@ -42,6 +42,7 @@ GNU_CONFIGURE=3D yes CONFIGURE_OUTSOURCE=3D yes CONFIGURE_ARGS+=3D--target=3D${GCC_TARGET} --disable-nls = --enable-languages=3Dc,c++ \ + --enable-gnu-indirect-function \ --without-headers \ --with-gmp=3D${LOCALBASE} \ --with-pkgversion=3D"FreeBSD Ports Collection for = ${PKGNAMEPREFIX:C/-//g}" \ @@ -104,6 +105,6 @@ # This port and all its slave ports fail on aarch64 -- but not all # the same way. Provide this definition for the master. -BROKEN_aarch64?=3D fails to package +#BROKEN_aarch64?=3D fails to package .include =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Mon May 14 00:45:58 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4E6FFDDDF6 for ; Mon, 14 May 2018 00:45:58 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 480147A095 for ; Mon, 14 May 2018 00:45:58 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (cpe-75-82-218-62.socal.res.rr.com [75.82.218.62]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w4E0Z2oE013127 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sun, 13 May 2018 17:35:03 -0700 Subject: Re: head -r333575's kernel: fails to boot old PowerMac G5 so-called "Quad Core", failing very early To: freebsd-ppc@freebsd.org References: <94E173AD-74C0-43ED-9D0D-86D9A56C2A74@yahoo.com> From: Nathan Whitehorn Message-ID: <1c62913a-0caa-aa6e-b0b6-97c338aa50c7@freebsd.org> Date: Sun, 13 May 2018 17:35:01 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <94E173AD-74C0-43ED-9D0D-86D9A56C2A74@yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVasEoHZHdFOgQ6ARrBL1xsJZqvQa9MO+CUHIiQHjSfi7SbisogL4WcpIT3g+kndvdm96qmWilmwaaE3tTAGF4KljEoSdVTp3OU= X-Sonic-ID: C;BkDBow5X6BGj5WqHilMZWw== M;BKZNpA5X6BGj5WqHilMZWw== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 00:45:58 -0000 This should be fixed if you update past r333594. -Nathan On 05/13/18 16:12, Mark Millard via freebsd-ppc wrote: > I'd had to revert to the old kernel from the last time I'd > updated the old PowerMac G5 "Quad Core" for powerpc64 style > use [back in early Jan.]: > > # uname -apKU > FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r327364M powerpc powerpc64 1200054 1200063 > > because buildkernel instalkernel for -r333575 results for > all the following fail in the same way: > > A) devel/powerpc64-xtoolchain-gcc based build > (from /usr/ports/ -r469767 so before the upgrade to 6.4) > B) gcc 4.2.1 based build > C) system clang6 based build > > These were all amd64 -> powerpc64 cross builds. Each is a > non-debug build --but with symbols. > > The following 3 lines are displayed and nothing more > visible happens after that in the boot sequence, the > lines are the ones that start with: > > GDB: no debug ports present > KDB: debugger backends: > KDB: current backend: > > It does not display any Copyright notice line or even > clear the screen. > > The old -r327364 kernel boots the old PowerMac G5 "Quad Core" > just fine (with the -r333575 world at this point). > > So far, this much suggests the issue is not toolchain related, > although in all 3 cases devel/powerpc64-binutils is in use > so it can not be eliminated as easily. > > [A problem is I'm very restricted on the amount of time > I can be involved in bisecting this and 333575-327364==6211 > for the version span. Another problem is that, at the failure > stage, getting information about failure details is > problematical on the old PowerMac, even if I could apply > the time for such.] > > > For powerpc64 context I have: > > # more /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG > # > # GENERIC -- Custom configuration for the powerpc/powerpc64 > # > > include "GENERIC64" > > ident GENERIC64vtsc-NODBG > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > > nooptions PS3 # Sony Playstation 3 HACK!!! to allow sc > > options KDB # Enable kernel debugger support > > options ALT_BREAK_TO_DEBUGGER > options BREAK_TO_DEBUGGER > > # For minimum debugger support (stable branch) use: > options KDB_TRACE # Print a stack trace for a panic > options DDB # Enable the kernel debugger > options GDB # HACK!!! ... > > # Extra stuff: > #options VERBOSE_SYSINIT # Enable verbose sysinit messages > #options BOOTVERBOSE=1 > #options BOOTHOWTO=RB_VERBOSE > #options KTR > #options KTR_MASK=KTR_TRAP > ##options KTR_CPUMASK=0xF > #options KTR_VERBOSE > > # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt historically mishandled during booting > device sc > #device kbdmux # HACK: already listed by vt > options SC_OFWFB # OFW frame buffer > options SC_DFLT_FONT # compile font in > makeoptions SC_DFLT_FONT=cp437 > > > # Disable any extra checking for. . . > nooptions DEADLKRES # Enable the deadlock resolver > nooptions INVARIANTS # Enable calls of extra sanity checking > nooptions INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS > nooptions WITNESS # Enable checks to detect deadlocks and cycles > nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > nooptions DIAGNOSTIC > nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones > > device filemon > device geom_label > > > > # svnlite diff /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp > Index: /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp > =================================================================== > --- /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp (revision 333575) > +++ /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp (working copy) > @@ -1176,7 +1176,7 @@ > // For SVR4, don't emit a move for the CR spill slot if we haven't > // spilled CRs. > if (isSVR4ABI && (PPC::CR2 <= Reg && Reg <= PPC::CR4) > - && !MustSaveCR) > + && (!MustSaveCR && isPPC64)) > continue; > > // For 64-bit SVR4 when we have spilled CRs, the spill location > > > > Note: The following file does not intend a powerpc64 functional change > but a powerpc (32-bit) change: > > # svnlite diff /usr/src/sys/powerpc/ofw/ofw_machdep.c > Index: /usr/src/sys/powerpc/ofw/ofw_machdep.c > =================================================================== > --- /usr/src/sys/powerpc/ofw/ofw_machdep.c (revision 333575) > +++ /usr/src/sys/powerpc/ofw/ofw_machdep.c (working copy) > @@ -116,26 +116,27 @@ > * Assume that interrupt are disabled at this point, or > * SPRG1-3 could be trashed > */ > -#ifdef __powerpc64__ > - __asm __volatile("mtsprg1 %0\n\t" > - "mtsprg2 %1\n\t" > - "mtsprg3 %2\n\t" > - : > - : "r"(ofmsr[2]), > - "r"(ofmsr[3]), > - "r"(ofmsr[4])); > -#else > - __asm __volatile("mfsprg0 %0\n\t" > - "mtsprg0 %1\n\t" > - "mtsprg1 %2\n\t" > - "mtsprg2 %3\n\t" > - "mtsprg3 %4\n\t" > - : "=&r"(ofw_sprg0_save) > - : "r"(ofmsr[1]), > - "r"(ofmsr[2]), > - "r"(ofmsr[3]), > - "r"(ofmsr[4])); > +#ifndef __powerpc64__ > + if (!(cpu_features & PPC_FEATURE_64)) > + __asm __volatile("mfsprg0 %0\n\t" > + "mtsprg0 %1\n\t" > + "mtsprg1 %2\n\t" > + "mtsprg2 %3\n\t" > + "mtsprg3 %4\n\t" > + : "=&r"(ofw_sprg0_save) > + : "r"(ofmsr[1]), > + "r"(ofmsr[2]), > + "r"(ofmsr[3]), > + "r"(ofmsr[4])); > + else > #endif > + __asm __volatile("mtsprg1 %0\n\t" > + "mtsprg2 %1\n\t" > + "mtsprg3 %2\n\t" > + : > + : "r"(ofmsr[2]), > + "r"(ofmsr[3]), > + "r"(ofmsr[4])); > } > > static __inline void > @@ -152,7 +153,8 @@ > * PCPU data cannot be used until this routine is called ! > */ > #ifndef __powerpc64__ > - __asm __volatile("mtsprg0 %0" :: "r"(ofw_sprg0_save)); > + if (!(cpu_features & PPC_FEATURE_64)) > + __asm __volatile("mtsprg0 %0" :: "r"(ofw_sprg0_save)); > #endif > } > #endif > > > > Note: The following file's change is actually for > !defined(__powerpc64__) added code . . . > > # svnlite diff /usr/src/sys/powerpc/aim/mmu_oea64.c > Index: /usr/src/sys/powerpc/aim/mmu_oea64.c > =================================================================== > --- /usr/src/sys/powerpc/aim/mmu_oea64.c (revision 333575) > +++ /usr/src/sys/powerpc/aim/mmu_oea64.c (working copy) > @@ -1820,6 +1820,18 @@ > PV_PAGE_UNLOCK(m); > } > > +#if defined(AIM) && !defined(__powerpc64__) > +// > +// Part of PowerMac G5 HACK FOR PROBLEM FINDING. . . > +// (G5 used via 32-bit FreeBSD.) > +// > + > +extern char _GOT_START_[]; // beginning of .got/.got.plt > +extern char _GOT_END_[]; // ending of .got/.got.plt > + > +extern vm_offset_t __startkernel, __endkernel; > +#endif > + > /* > * Map a wired page into kernel virtual address space. > */ > @@ -1830,6 +1842,52 @@ > struct pvo_entry *pvo, *oldpvo; > > pvo = alloc_pvo_entry(0); > +#if defined(AIM) && !defined(__powerpc64__) > + // > + // PowerMac G5 HACK FOR PROBLEM FINDING. . . > + // (G5 used via 32-bit FreeBSD.) > + // > + // As a problem-finding-aid try to catch some examples of > + // jumping to non-code in the kernel before it tries to > + // execute that that code. Hopefully this will show where > + // the bad jump into the likes of the .hash section is > + // happening. (dbb bt and vmcore.*'s have not lead to > + // that information so far.) > + // > + if (cpu_features & PPC_FEATURE_64) > + { > + // First deal with pages that should have the original > + // VM_PROT_EXECUTE status for something on the page > + // (most pages in the kernel area). So pages with some > + // byte(s) from .text, .got, or .got.plt, along with > + // any requested from before where __startkernel > + // indicates. Also any va requested from a page > + // containing where __endkernel indicates or later > + // gets VM_PROT_EXECUTE if such a va is requested. > + // > + // So: have just the rest of the kernel area not have > + // VM_PROT_EXECUTE status in hopes that it will report > + // where the code is that is making bad jumps to > + // non-code, such as jumping into the .hash section > + // instead of reporting on illegal instructions > + // from the incorrect traget area. > + // > + if ( va < ((vm_offset_t)(etext+(PAGE_SIZE-1)) & ~PAGE_MASK) ) > + pvo->pvo_pte.prot = VM_PROT_READ | VM_PROT_WRITE | VM_PROT_EXECUTE; > + > + else if ( ((vm_offset_t)_GOT_START_ & ~PAGE_MASK) <= va > + && va < ((vm_offset_t)(_GOT_END_+(PAGE_SIZE-1)) & ~PAGE_MASK) > + ) > + pvo->pvo_pte.prot = VM_PROT_READ | VM_PROT_WRITE | VM_PROT_EXECUTE; > + > + else if ( va < (__endkernel & ~PAGE_MASK) ) > + pvo->pvo_pte.prot = VM_PROT_READ | VM_PROT_WRITE; > + > + else // Otherwise do as before the HACK: > + pvo->pvo_pte.prot = VM_PROT_READ | VM_PROT_WRITE | VM_PROT_EXECUTE; > + } > + else > +#endif > pvo->pvo_pte.prot = VM_PROT_READ | VM_PROT_WRITE | VM_PROT_EXECUTE; > pvo->pvo_pte.pa = (pa & ~ADDR_POFF) | moea64_calc_wimg(pa, ma); > pvo->pvo_vaddr |= PVO_WIRED; > > > > Note: The following should not matter because it is only for > devel/powerpc64-gcc but gcc 4.2.1 and system clang6 got the > same result: > > # svnlite diff /usr/ports/devel/powerpc64-gcc/Makefile > Index: /usr/ports/devel/powerpc64-gcc/Makefile > =================================================================== > --- /usr/ports/devel/powerpc64-gcc/Makefile (revision 469767) > +++ /usr/ports/devel/powerpc64-gcc/Makefile (working copy) > @@ -2,7 +2,7 @@ > > PORTNAME= gcc > PORTVERSION= 6.3.0 > -PORTREVISION= 5 > +PORTREVISION= 6 > CATEGORIES= devel > MASTER_SITES= GCC/releases/gcc-${DISTVERSION} > PKGNAMEPREFIX?= powerpc64- > @@ -42,6 +42,7 @@ > GNU_CONFIGURE= yes > CONFIGURE_OUTSOURCE= yes > CONFIGURE_ARGS+=--target=${GCC_TARGET} --disable-nls --enable-languages=c,c++ \ > + --enable-gnu-indirect-function \ > --without-headers \ > --with-gmp=${LOCALBASE} \ > --with-pkgversion="FreeBSD Ports Collection for ${PKGNAMEPREFIX:C/-//g}" \ > @@ -104,6 +105,6 @@ > > # This port and all its slave ports fail on aarch64 -- but not all > # the same way. Provide this definition for the master. > -BROKEN_aarch64?= fails to package > +#BROKEN_aarch64?= fails to package > > .include > > > === > Mark Millard > marklmi26-fbsd at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > > > > > > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@freebsd.org Mon May 14 01:04:57 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98201FDEB8A for ; Mon, 14 May 2018 01:04:57 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic317-28.consmr.mail.bf2.yahoo.com (sonic317-28.consmr.mail.bf2.yahoo.com [74.6.129.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20C107F81D for ; Mon, 14 May 2018 01:04:56 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: lFjojrQVM1mGf8Rr0deM4YoxhdD3swD78nOkZEy8OBqj1Ffw4lfllGf.qq3AhMc ZgYVxR43KONuBKX9__dm086qCgH0kcJDYO_x7aSaNBsXnyyl0tt5uGT1Wd64mbxgt.s5u1U0C6jd KlSKvWRvHWZt0JtqvcWR4iilyaGdUHL4tFvBwZA9EoVdteKLMY4Nktj2lUDwdMtzF_QMzCfoMGug 2YW9s4CI2PZUXbVVrPHl3Zq5zlP2aw72tuqrvmRFrJqpx3YRyyOVqUbkKcNmPrf1.tqdtFUpHAo5 s9iSedGCyD0CG2T7dSb3_cpYuJfqeEmLymfOqy3HFtRIFLeMw6j0J7m1lTeyf9uOsoZcDtLJkV_d o84CgK.pU4if.iE1dda4WZtdW6MJpczym.sILFlccuVrOrBYayHH5M9xpWa3Su.GV_JxSgbdFuNB bKqu5sH2ZGIroKHN4aZ6KvSCfQFUUHRMB2DUh9Gb.C4pfpgrYsm5TgH4RXCHGVN1P4s0aeJ_lhMq .tha4U7kE2FGyIUkQAgkk2aHwyYXsUi67D3G2KspR4nDUWUjuStDgmw33yS4b672ibz3nosz2XsN boQ70IeAMLzT8MEx.nshTkoS5jaB9qqWsTajbSs1gFLu7hORLPw-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.bf2.yahoo.com with HTTP; Mon, 14 May 2018 01:04:50 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp422.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 6e87548ab73ab669016d221ecb98dcd3; Mon, 14 May 2018 01:04:47 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: head -r333575's kernel: fails to boot old PowerMac G5 so-called "Quad Core", failing very early From: Mark Millard In-Reply-To: <1c62913a-0caa-aa6e-b0b6-97c338aa50c7@freebsd.org> Date: Sun, 13 May 2018 18:04:45 -0700 Cc: freebsd-ppc@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <94E173AD-74C0-43ED-9D0D-86D9A56C2A74@yahoo.com> <1c62913a-0caa-aa6e-b0b6-97c338aa50c7@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 May 2018 01:04:57 -0000 On 2018-May-13, at 5:35 PM, Nathan Whitehorn = wrote: > This should be fixed if you update past r333594. > -Nathan Confirmed: my -r333594 buildkernel booted normally. Thanks! > On 05/13/18 16:12, Mark Millard via freebsd-ppc wrote: >> I'd had to revert to the old kernel from the last time I'd >> updated the old PowerMac G5 "Quad Core" for powerpc64 style >> use [back in early Jan.]: >>=20 >> # uname -apKU >> FreeBSD FBSDG5L 12.0-CURRENT FreeBSD 12.0-CURRENT r327364M powerpc = powerpc64 1200054 1200063 >>=20 >> because buildkernel instalkernel for -r333575 results for >> all the following fail in the same way: >>=20 >> A) devel/powerpc64-xtoolchain-gcc based build >> (from /usr/ports/ -r469767 so before the upgrade to 6.4) >> B) gcc 4.2.1 based build >> C) system clang6 based build >>=20 >> These were all amd64 -> powerpc64 cross builds. Each is a >> non-debug build --but with symbols. >>=20 >> The following 3 lines are displayed and nothing more >> visible happens after that in the boot sequence, the >> lines are the ones that start with: >>=20 >> GDB: no debug ports present >> KDB: debugger backends: >> KDB: current backend: >>=20 >> It does not display any Copyright notice line or even >> clear the screen. >>=20 >> The old -r327364 kernel boots the old PowerMac G5 "Quad Core" >> just fine (with the -r333575 world at this point). >>=20 >> So far, this much suggests the issue is not toolchain related, >> although in all 3 cases devel/powerpc64-binutils is in use >> so it can not be eliminated as easily. >>=20 >> [A problem is I'm very restricted on the amount of time >> I can be involved in bisecting this and 333575-327364=3D=3D6211 >> for the version span. Another problem is that, at the failure >> stage, getting information about failure details is >> problematical on the old PowerMac, even if I could apply >> the time for such.] >>=20 >>=20 >> For powerpc64 context I have: >>=20 >> # more /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG >> # >> # GENERIC -- Custom configuration for the powerpc/powerpc64 >> # >>=20 >> include "GENERIC64" >>=20 >> ident GENERIC64vtsc-NODBG >>=20 >> makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols >>=20 >> nooptions PS3 # Sony Playstation 3 = HACK!!! to allow sc >>=20 >> options KDB # Enable kernel debugger = support >>=20 >> options ALT_BREAK_TO_DEBUGGER >> options BREAK_TO_DEBUGGER >>=20 >> # For minimum debugger support (stable branch) use: >> options KDB_TRACE # Print a stack trace for a = panic >> options DDB # Enable the kernel debugger >> options GDB # HACK!!! ... >>=20 >> # Extra stuff: >> #options VERBOSE_SYSINIT # Enable verbose sysinit = messages >> #options BOOTVERBOSE=3D1 >> #options BOOTHOWTO=3DRB_VERBOSE >> #options KTR >> #options KTR_MASK=3DKTR_TRAP >> ##options KTR_CPUMASK=3D0xF >> #options KTR_VERBOSE >>=20 >> # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting >> device sc >> #device kbdmux # HACK: already listed by vt >> options SC_OFWFB # OFW frame buffer >> options SC_DFLT_FONT # compile font in >> makeoptions SC_DFLT_FONT=3Dcp437 >>=20 >>=20 >> # Disable any extra checking for. . . >> nooptions DEADLKRES # Enable the deadlock = resolver >> nooptions INVARIANTS # Enable calls of extra = sanity checking >> nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS >> nooptions WITNESS # Enable checks to detect = deadlocks and cycles >> nooptions WITNESS_SKIPSPIN # Don't run witness on = spinlocks for speed >> nooptions DIAGNOSTIC >> nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones >>=20 >> device filemon >> device geom_label >>=20 >>=20 >>=20 >> # svnlite diff = /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp >> Index: /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp = (revision 333575) >> +++ /usr/src/contrib/llvm/lib/Target/PowerPC/PPCFrameLowering.cpp = (working copy) >> @@ -1176,7 +1176,7 @@ >> // For SVR4, don't emit a move for the CR spill slot if we = haven't >> // spilled CRs. >> if (isSVR4ABI && (PPC::CR2 <=3D Reg && Reg <=3D PPC::CR4) >> - && !MustSaveCR) >> + && (!MustSaveCR && isPPC64)) >> continue; >>=20 >> // For 64-bit SVR4 when we have spilled CRs, the spill = location >>=20 >>=20 >>=20 >> Note: The following file does not intend a powerpc64 functional = change >> but a powerpc (32-bit) change: >>=20 >> # svnlite diff /usr/src/sys/powerpc/ofw/ofw_machdep.c >> Index: /usr/src/sys/powerpc/ofw/ofw_machdep.c >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- /usr/src/sys/powerpc/ofw/ofw_machdep.c (revision 333575) >> +++ /usr/src/sys/powerpc/ofw/ofw_machdep.c (working copy) >> @@ -116,26 +116,27 @@ >> * Assume that interrupt are disabled at this point, or >> * SPRG1-3 could be trashed >> */ >> -#ifdef __powerpc64__ >> - __asm __volatile("mtsprg1 %0\n\t" >> - "mtsprg2 %1\n\t" >> - "mtsprg3 %2\n\t" >> - : >> - : "r"(ofmsr[2]), >> - "r"(ofmsr[3]), >> - "r"(ofmsr[4])); >> -#else >> - __asm __volatile("mfsprg0 %0\n\t" >> - "mtsprg0 %1\n\t" >> - "mtsprg1 %2\n\t" >> - "mtsprg2 %3\n\t" >> - "mtsprg3 %4\n\t" >> - : "=3D&r"(ofw_sprg0_save) >> - : "r"(ofmsr[1]), >> - "r"(ofmsr[2]), >> - "r"(ofmsr[3]), >> - "r"(ofmsr[4])); >> +#ifndef __powerpc64__ >> + if (!(cpu_features & PPC_FEATURE_64)) >> + __asm __volatile("mfsprg0 %0\n\t" >> + "mtsprg0 %1\n\t" >> + "mtsprg1 %2\n\t" >> + "mtsprg2 %3\n\t" >> + "mtsprg3 %4\n\t" >> + : "=3D&r"(ofw_sprg0_save) >> + : "r"(ofmsr[1]), >> + "r"(ofmsr[2]), >> + "r"(ofmsr[3]), >> + "r"(ofmsr[4])); >> + else >> #endif >> + __asm __volatile("mtsprg1 %0\n\t" >> + "mtsprg2 %1\n\t" >> + "mtsprg3 %2\n\t" >> + : >> + : "r"(ofmsr[2]), >> + "r"(ofmsr[3]), >> + "r"(ofmsr[4])); >> } >>=20 >> static __inline void >> @@ -152,7 +153,8 @@ >> * PCPU data cannot be used until this routine is called ! >> */ >> #ifndef __powerpc64__ >> - __asm __volatile("mtsprg0 %0" :: "r"(ofw_sprg0_save)); >> + if (!(cpu_features & PPC_FEATURE_64)) >> + __asm __volatile("mtsprg0 %0" :: = "r"(ofw_sprg0_save)); >> #endif >> } >> #endif >>=20 >>=20 >>=20 >> Note: The following file's change is actually for >> !defined(__powerpc64__) added code . . . >>=20 >> # svnlite diff /usr/src/sys/powerpc/aim/mmu_oea64.c >> Index: /usr/src/sys/powerpc/aim/mmu_oea64.c >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- /usr/src/sys/powerpc/aim/mmu_oea64.c (revision 333575) >> +++ /usr/src/sys/powerpc/aim/mmu_oea64.c (working copy) >> @@ -1820,6 +1820,18 @@ >> PV_PAGE_UNLOCK(m); >> } >>=20 >> +#if defined(AIM) && !defined(__powerpc64__) >> +// >> +// Part of PowerMac G5 HACK FOR PROBLEM FINDING. . . >> +// (G5 used via 32-bit FreeBSD.) >> +// >> + >> +extern char _GOT_START_[]; // beginning of .got/.got.plt >> +extern char _GOT_END_[]; // ending of .got/.got.plt >> + >> +extern vm_offset_t __startkernel, __endkernel; >> +#endif >> + >> /* >> * Map a wired page into kernel virtual address space. >> */ >> @@ -1830,6 +1842,52 @@ >> struct pvo_entry *pvo, *oldpvo; >>=20 >> pvo =3D alloc_pvo_entry(0); >> +#if defined(AIM) && !defined(__powerpc64__) >> + // >> + // PowerMac G5 HACK FOR PROBLEM FINDING. . . >> + // (G5 used via 32-bit FreeBSD.) >> + // >> + // As a problem-finding-aid try to catch some examples of >> + // jumping to non-code in the kernel before it tries to >> + // execute that that code. Hopefully this will show where >> + // the bad jump into the likes of the .hash section is >> + // happening. (dbb bt and vmcore.*'s have not lead to >> + // that information so far.) >> + // >> + if (cpu_features & PPC_FEATURE_64) >> + { >> + // First deal with pages that should have the = original >> + // VM_PROT_EXECUTE status for something on the page >> + // (most pages in the kernel area). So pages with = some >> + // byte(s) from .text, .got, or .got.plt, along with >> + // any requested from before where __startkernel >> + // indicates. Also any va requested from a page >> + // containing where __endkernel indicates or later >> + // gets VM_PROT_EXECUTE if such a va is requested. >> + // >> + // So: have just the rest of the kernel area not have >> + // VM_PROT_EXECUTE status in hopes that it will = report >> + // where the code is that is making bad jumps to >> + // non-code, such as jumping into the .hash section >> + // instead of reporting on illegal instructions >> + // from the incorrect traget area. >> + // >> + if ( va < ((vm_offset_t)(etext+(PAGE_SIZE-1)) & = ~PAGE_MASK) ) >> + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE | VM_PROT_EXECUTE; >> + >> + else if ( ((vm_offset_t)_GOT_START_ & ~PAGE_MASK) <=3D= va >> + && va < = ((vm_offset_t)(_GOT_END_+(PAGE_SIZE-1)) & ~PAGE_MASK) >> + ) >> + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE | VM_PROT_EXECUTE; >> + >> + else if ( va < (__endkernel & ~PAGE_MASK) ) >> + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE; >> + >> + else // Otherwise do as before the HACK: >> + pvo->pvo_pte.prot =3D VM_PROT_READ | = VM_PROT_WRITE | VM_PROT_EXECUTE; >> + } >> + else >> +#endif >> pvo->pvo_pte.prot =3D VM_PROT_READ | VM_PROT_WRITE | = VM_PROT_EXECUTE; >> pvo->pvo_pte.pa =3D (pa & ~ADDR_POFF) | moea64_calc_wimg(pa, = ma); >> pvo->pvo_vaddr |=3D PVO_WIRED; >>=20 >>=20 >>=20 >> Note: The following should not matter because it is only for >> devel/powerpc64-gcc but gcc 4.2.1 and system clang6 got the >> same result: >>=20 >> # svnlite diff /usr/ports/devel/powerpc64-gcc/Makefile >> Index: /usr/ports/devel/powerpc64-gcc/Makefile >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- /usr/ports/devel/powerpc64-gcc/Makefile (revision 469767) >> +++ /usr/ports/devel/powerpc64-gcc/Makefile (working copy) >> @@ -2,7 +2,7 @@ >>=20 >> PORTNAME=3D gcc >> PORTVERSION=3D 6.3.0 >> -PORTREVISION=3D 5 >> +PORTREVISION=3D 6 >> CATEGORIES=3D devel >> MASTER_SITES=3D GCC/releases/gcc-${DISTVERSION} >> PKGNAMEPREFIX?=3D powerpc64- >> @@ -42,6 +42,7 @@ >> GNU_CONFIGURE=3D yes >> CONFIGURE_OUTSOURCE=3D yes >> CONFIGURE_ARGS+=3D--target=3D${GCC_TARGET} --disable-nls = --enable-languages=3Dc,c++ \ >> + --enable-gnu-indirect-function \ >> --without-headers \ >> --with-gmp=3D${LOCALBASE} \ >> --with-pkgversion=3D"FreeBSD Ports Collection for = ${PKGNAMEPREFIX:C/-//g}" \ >> @@ -104,6 +105,6 @@ >>=20 >> # This port and all its slave ports fail on aarch64 -- but not all >> # the same way. Provide this definition for the master. >> -BROKEN_aarch64?=3D fails to package >> +#BROKEN_aarch64?=3D fails to package >>=20 >> .include >>=20 >=20 =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Tue May 15 00:05:04 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 46207EA94A2; Tue, 15 May 2018 00:05:04 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF3A67882D; Tue, 15 May 2018 00:05:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 7A6FABF1; Tue, 15 May 2018 00:05:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 5DC0A5B0C; Tue, 15 May 2018 00:05:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id A7DfIo8VZORh; Tue, 15 May 2018 00:04:59 +0000 (UTC) To: Mark Millard DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 0E9605B04 Cc: FreeBSD Toolchain , FreeBSD PowerPC ML References: <0E42D991-D350-4DC1-A683-CEA506167520@dsl-only.net> <8F22B659-90DE-42E5-B4C6-75C9B9626462@dsl-only.net> <8EB87EA5-0ED6-4F46-80FC-1A0DB29CF7D6@dsl-only.net> <84A73CB0-CBCB-4EE4-A4B7-B8B2F25EECB5@yahoo.com> From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8CGwwF AlrozigFCQpgez0ACgkQNddxu25Gl8+m5Af/R3VEdxNMAcDIes9ADhQyofj20SPV3eCJ3HYR OebTSuNdOudGt4AAyA8Ks94u9hiIp5IGsc6RDsT9W7O2vgXhd6eV3eiY5Oif5xLIYrIDVu1Y 1GyRxRrPEn/QOqDN6uFZCPwK1aOapGcYCrO9lB0gMuTVfgHanU61rgC9tMX0OoAOyRd+V3/M 8lDNhjJdF/IpO3SdYzKfkwduy4qamw4Gphcx/RfYQvYLq/eDkP8d50PphWdboqWBwNRHayro W/07OGzfxM5fJ5mBsXPQcO2QcRjkyHf6xCM6Hi1qQL4OnXMNE/ZTX0lnOj1/pH93TlzSHZMP TaiiA/MBD3vGsXBmBg== Organization: FreeBSD Subject: Re: Still true at -r333575 : head -r320458 (e.g.) amd64 -> powerpc64 cross build's install32 during installworld: /usr/src/share/mk/bsd.linker.mk tried to use "head" when PATH provided no access (head is missing) Message-ID: <9086ff35-009b-c965-4970-3f8ad4fe6e6b@FreeBSD.org> Date: Mon, 14 May 2018 17:04:54 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <84A73CB0-CBCB-4EE4-A4B7-B8B2F25EECB5@yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xUnsQmDdAaQK1ZcNG661OOtPY8XP2g7nN" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 00:05:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xUnsQmDdAaQK1ZcNG661OOtPY8XP2g7nN Content-Type: multipart/mixed; boundary="1ETGVcUMnAsaAkxy3gD8mKaG2yODbb5zi"; protected-headers="v1" From: Bryan Drewery To: Mark Millard Cc: FreeBSD Toolchain , FreeBSD PowerPC ML Message-ID: <9086ff35-009b-c965-4970-3f8ad4fe6e6b@FreeBSD.org> Subject: Re: Still true at -r333575 : head -r320458 (e.g.) amd64 -> powerpc64 cross build's install32 during installworld: /usr/src/share/mk/bsd.linker.mk tried to use "head" when PATH provided no access (head is missing) References: <0E42D991-D350-4DC1-A683-CEA506167520@dsl-only.net> <8F22B659-90DE-42E5-B4C6-75C9B9626462@dsl-only.net> <8EB87EA5-0ED6-4F46-80FC-1A0DB29CF7D6@dsl-only.net> <84A73CB0-CBCB-4EE4-A4B7-B8B2F25EECB5@yahoo.com> In-Reply-To: <84A73CB0-CBCB-4EE4-A4B7-B8B2F25EECB5@yahoo.com> --1ETGVcUMnAsaAkxy3gD8mKaG2yODbb5zi Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 5/13/2018 1:13 AM, Mark Millard wrote: > Retrying the amd64 -> powerpc64 cross build via a powerpc64-gcc > this time, combined with WITH_LIB32=3D , got: "sh: head: not found" and= its > later consequences, like before for installworld (to a directory on the= > amd64 host context). This is from the /usr/src/share/mk/bsd.linker.mk l= ine > that results in: >=20 > (/usr/local/powerpc64-freebsd/bin/ld --version || echo none) | head -n = 1 >=20 > but head is not available by default at the time (lib32 context). (I ma= ke > head be available via using LOCAL_ITOOLS=3Dhead in order to work around= the > issue.) >=20 > An example of the messages (without having LOCAL_ITOOLS=3Dhead) is: >=20 > --- _installlinks --- > install -l s ../../libexec/ld-elf32.so.1 /usr/obj/DESTDIRs/xtcgcc-powe= rpc64-installworld/usr/libexec/ld-elf32.so.1 > cd /usr/src/usr.bin/ldd; PROG=3Dldd32 . . . > . . . > . . . MAKEOBJDIRPREFIX=3D MK_MAN=3Dno MK_HTML=3Dno MK_TOOLCHAIN=3Dno = -DLIBRARIES_ONLY install > sh: head: not found > make[4]: "/usr/src/share/mk/bsd.linker.mk" line 47: warning: "(/usr/loc= al/powerpc64-unknown-freebsd12.0/bin/ld --version || echo none) | head -n= 1" returned non-zero status > make[4]: "/usr/src/share/mk/bsd.linker.mk" line 58: warning: Unknown li= nker from XLD=3D/usr/local/powerpc64-unknown-freebsd12.0/bin/ld: , defaul= ting to bfd >=20 >=20 > The two "make[4]" lines are consequences of the prior "sh: head: not fo= und" > issue that leaded to a "non-zero status" independent of the prior "--ve= rsion" > and "echo none" material. It then leads to assuming bfd. >=20 > Using LOCAL_ITOOLS=3Dhead makes head available and so then the status v= alue > check works. >=20 Sure but this command being executed never should be executing during install; Adding 'head' as a tool isn't the right fix. I have never been able to recreate the problem here. I have an idea I'll test. >=20 >=20 > On 2017-Nov-25, at 4:54 PM, Mark Millard wrote:= >=20 > . . . >=20 > On 2017-Jul-26, at 3:06 AM, Mark Millard wrote:= >=20 > . . . >=20 > =3D=3D=3D > Mark Millard > marklmi26-fbsd at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) >=20 >=20 >=20 >=20 >=20 >=20 --=20 Regards, Bryan Drewery --1ETGVcUMnAsaAkxy3gD8mKaG2yODbb5zi-- --xUnsQmDdAaQK1ZcNG661OOtPY8XP2g7nN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJa+iQqAAoJEDXXcbtuRpfPFDAH/334+Sv8BYDx1h4oqNyzvlYV qJ2WHfrIPj7kOUD+GP2JnInTcZwJaz3cTGqjw0Ao5zf0hJR942c5nksixcIf6wgn l8hHV6z1g1lENR80WYRE96K0mj8bRlEeZtpvZqLQyZPioG1U5p51rELj/UTIZdtt sColEQBk+xrvh890d5HYtYs4cmKCHfoqg1+XeDsBynDW2DvVJ4Q8tsiy39dl3YBA FR0zqkrUc/3xiHGu6F5rVYtWlrgmkM+A/dbA39G/htPjqoOFSGTTK4uMdkNbN4km 7KGTMYWGM7YWDqVS2Q/W5vq7zPwbF3Gi1ZQd3zATWZJ/ZjRXKqbyKyeLmuPHPOI= =yLqe -----END PGP SIGNATURE----- --xUnsQmDdAaQK1ZcNG661OOtPY8XP2g7nN-- From owner-freebsd-ppc@freebsd.org Tue May 15 13:12:49 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43072ED8E49 for ; Tue, 15 May 2018 13:12:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D16BE8541A for ; Tue, 15 May 2018 13:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8B2A2ED8E3D; Tue, 15 May 2018 13:12:48 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 771F0ED8E3C for ; Tue, 15 May 2018 13:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 101F285416 for ; Tue, 15 May 2018 13:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3BCD1189B1 for ; Tue, 15 May 2018 13:12:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4FDClXd063734 for ; Tue, 15 May 2018 13:12:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4FDCl2b063729 for ppc@FreeBSD.org; Tue, 15 May 2018 13:12:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 225629] powerpc64 (POWER9) segfaults randomly (e.g., building lang/gcc5) Date: Tue, 15 May 2018 13:12:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 13:12:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225629 --- Comment #16 from Mark Millard --- Just for reference: I my build of head -r333594 ( WITHOUT_LIB32=3D ) used on a PowerMac G5 so-called "Quad Core" has been building ports just fine, including the likes of lang/llvm60 and devel/powerpc64-gcc so far. (Builds still going.) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Tue May 15 13:12:48 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 67DD1ED8E37 for ; Tue, 15 May 2018 13:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F2A585414 for ; Tue, 15 May 2018 13:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 05749170F5; Tue, 15 May 2018 13:12:48 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 012F3170F4 for ; Tue, 15 May 2018 13:12:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C352D85412 for ; Tue, 15 May 2018 13:12:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C6F20189AE for ; Tue, 15 May 2018 13:12:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4FDCkrh063705 for ; Tue, 15 May 2018 13:12:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4FDCkar063704 for powerpc@FreeBSD.org; Tue, 15 May 2018 13:12:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 225629] powerpc64 (POWER9) segfaults randomly (e.g., building lang/gcc5) Date: Tue, 15 May 2018 13:12:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 13:12:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225629 --- Comment #16 from Mark Millard --- Just for reference: I my build of head -r333594 ( WITHOUT_LIB32=3D ) used on a PowerMac G5 so-called "Quad Core" has been building ports just fine, including the likes of lang/llvm60 and devel/powerpc64-gcc so far. (Builds still going.) --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Tue May 15 14:42:48 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13CD6EDE82C for ; Tue, 15 May 2018 14:42:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BCE27AE4F for ; Tue, 15 May 2018 14:42:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 7679A130FC; Tue, 15 May 2018 14:42:47 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 72106130FB for ; Tue, 15 May 2018 14:42:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 465D47AE4B for ; Tue, 15 May 2018 14:42:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 52F0E19654 for ; Tue, 15 May 2018 14:42:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4FEgkkC022651 for ; Tue, 15 May 2018 14:42:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4FEgku2022650 for powerpc@FreeBSD.org; Tue, 15 May 2018 14:42:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 228055] lang/gcl fails to compile on powerpc64 Date: Tue, 15 May 2018 14:42:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hamiltcl@verizon.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 May 2018 14:42:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228055 Curtis Hamilton changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Overcome By Events --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Fri May 18 03:58:27 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A67AEE87D0 for ; Fri, 18 May 2018 03:58:27 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic305-22.consmr.mail.ne1.yahoo.com (sonic305-22.consmr.mail.ne1.yahoo.com [66.163.185.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04E9A83FC1 for ; Fri, 18 May 2018 03:58:26 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: _LZG4qcVM1nviEqB.XDTu5sJdFKfFPxAcGLr3CrdB3IWRikW9jhCjUk_rf8LnAk LnqpS5GnTp0Cd4_9L97Ur6dw7duKzD5We.oHxtYwaTMeoUY7xWFqBdmuv94ggK_p9DKrIxOjmaoD fAh64iEaAMuZyvZW.bwHFLRWDcrGXSawp2nsR9Q.bKSwGCaAnQ1WpBHir_9dSP8ISZvmHvLDSZiQ sm4WAosRBl4Lnw2bCQkCedbprLt7PU5fBIQjRpoj9pIL1wKiuJgdiViMKif5rp_9d5tjP0TRyiYx yYdjd6HPp06SaZqBlsgQnaSxkO9IFl4EPI6t27CYR_oW1Z9SIfXgaC6h6rQdcQB_Nf_xADx8hYKj .o9Ul94bc5T5q_LJx4L3swCnm44svCdNRWltRF_nzi9jY4RtE4CPIUQH.nQOhf2nVnV3ns._zpk6 soA_eukawwGoCNYnNSrbj9gvMF0_ZZMYqd3aqJz47OSzzAKK415YLYRenoBxkucHz6OUtrXNg4Wa ymsuVvFbUaevC8g.86LLB6hXEe.3i4tT3qwHYUPrPZ6dRUp9uhJVVlVh7gwkbi0fzX7r7WPgBabE hZMF0WJSyeZTwCWSseldNG_vK_GiJCwF3tWGY78ntZEBOEebYAuIultmCPMCSOGzFlpjA5LHlgqq 3r2piH05L Received: from sonic.gate.mail.ne1.yahoo.com by sonic305.consmr.mail.ne1.yahoo.com with HTTP; Fri, 18 May 2018 03:58:20 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp403.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4f9c57344d3faaa3226565dc801e2d2c; Fri, 18 May 2018 03:58:18 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC Message-Id: Date: Thu, 17 May 2018 20:58:16 -0700 To: Mark Johnston , freebsd-arch@freebsd.org, FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 03:58:27 -0000 Mark Johnston markj at FreeBSD.org wrote on Thu May 17 17:24:19 UTC 2018 : > Over the past couple of years, a number of kernel dump features have > been added: encryption, compression and dumping to a remote host > (netdump). These features are currently all omitted from GENERIC. >=20 > . . . > Therefore, I'd like to propose enabling these features by default > on i386, amd64, arm64, powerpc(64) and sparc64 so that they're = available > out of the box in 12.0. > . . . Bugzilla 214598 (from late 2016) was about dump for TARGET_ARCH=3Dpowerpc64 builds getting failures like: KDB: enter: manual escape to debugger [ thread pid 12 tid 10018 ] Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 db> dump Dumping 9 MB (3 chunks) chunk 0: 10MB (2510 pages) ... ok chunk 1: 1MB (24 pages) ... ok chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: = c000000000022000 (A 32-bit powerpc build on the same machine worked fine for dumping.) I just tried it with head -r333594 and I got something similar. (Old and new mention routines with _bus_dma_map_ in the names near the trap in the call stack. I've not done a detailed comparison.) So, at least for the old PowerMac G5 so-called "Quad Core" powerpc64 context that was in use, there may be problems putting the changes to use --or in any use of dump. As for config for the kernel configuration involved: # more /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODBG # # GENERIC -- Custom configuration for the powerpc/powerpc64 # include "GENERIC64" ident GENERIC64vtsc-NODBG makeoptions DEBUG=3D-g # Build kernel with gdb(1) = debug symbols nooptions PS3 # Sony Playstation 3 = HACK!!! to allow sc options KDB # Enable kernel debugger support options ALT_BREAK_TO_DEBUGGER options BREAK_TO_DEBUGGER # For minimum debugger support (stable branch) use: options KDB_TRACE # Print a stack trace for a = panic options DDB # Enable the kernel debugger options GDB # HACK!!! ... # Extra stuff: #options VERBOSE_SYSINIT # Enable verbose sysinit = messages #options BOOTVERBOSE=3D1 #options BOOTHOWTO=3DRB_VERBOSE #options KTR #options KTR_MASK=3DKTR_TRAP ##options KTR_CPUMASK=3D0xF #options KTR_VERBOSE # HACK!!! to allow sc for 2560x1440 display on Radeon X1950 that vt = historically mishandled during booting device sc #device kbdmux # HACK: already listed by vt options SC_OFWFB # OFW frame buffer options SC_DFLT_FONT # compile font in makeoptions SC_DFLT_FONT=3Dcp437 # Disable any extra checking for. . . nooptions DEADLKRES # Enable the deadlock resolver nooptions INVARIANTS # Enable calls of extra sanity = checking nooptions INVARIANT_SUPPORT # Extra sanity checks of = internal structures, required by INVARIANTS nooptions WITNESS # Enable checks to detect = deadlocks and cycles nooptions WITNESS_SKIPSPIN # Don't run witness on spinlocks = for speed nooptions DIAGNOSTIC nooptions MALLOC_DEBUG_MAXZONES # Separate malloc(9) zones device filemon device geom_label =3D=3D=3D Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Fri May 18 06:17:44 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F6FAEEBA29; Fri, 18 May 2018 06:17:44 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9D0068B12; Fri, 18 May 2018 06:17:43 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x244.google.com with SMTP id x9-v6so3252306pfm.2; Thu, 17 May 2018 23:17:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=cZFzvAHCZ9ZyqGrlvJc7qbfcstDWs/5KBZPvVr4aeJ4=; b=iDIWSJEq69TJocFJbkxpPr7ihhHFyv0iwecZr0HUCASHSoRDFr8nCxNsj6+EdYEEqn o4D42ZBzIb7y9ryEFhKBYg7LMe8OxsUpDtL/2nsQfFvChxsLcK5RyZxqPJrGVe78IEp1 /uBvb1q2ktVkSyDvehxh2ZbfqD2Pgh19Y0fs+PoO/LLMHY9FP0rmbDBOGEfW0c/8XBw8 xp3k9lZJ2L+3a42S0xoBo/hgo9eY1HcOpqi3oOuM2py0m6+H5kRkzKw4T3vqO8pfyVLu 0/v7wCUnlkvN9OS5zq+k0kvqBWfpVFfWjfiu0qeesBP0ZxSVEwCNGQyWSHRf56MC8yyp NAbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=cZFzvAHCZ9ZyqGrlvJc7qbfcstDWs/5KBZPvVr4aeJ4=; b=YzzlI6hPCJeFN6o0a0T0R5B3UwEX7zUC1R3ov+ABfvxwYbkSBPTG7s103hO5E6Lwjc ri10HWMxonguTRkH/A7LOog2np6qu4jMZaBNeXOXdM2IDUg9R2M2BE2Iag6jSY0Tnvnc NxiarOCiJ6YJ687DOODBXqy5YbAYKdEAOz37GqbiqQ4tNMl/3fu948wYT+MPJnNQ/ZrT oSsUWe7gj6Ta2U/zXVl0y95r7DmuX0UieYlgnwUEXXFtRklinWNTp4RimYEpXozE2nFs +ApmOaQbEC8of7df4I0MxX2hgYXcS8jsSMTUsiBLgIOycdtpbF3FHdVSW7a6gcoHInUb Mc5Q== X-Gm-Message-State: ALKqPwe0cRaMHdpNRV/9hP7/cIETlYFZMRao4SihpW4+fILPgX/KNSkS OE1xi3uIvSX+m/pppYtIwfc= X-Google-Smtp-Source: AB8JxZo1xk4EFCa/yNo+mhjaqiAoNWrci9l+Wh5GwHvcjveTv2UPVyiSjFzE2s9NzibUZSsrHqGxeA== X-Received: by 2002:a62:a391:: with SMTP id q17-v6mr8124835pfl.87.1526624262727; Thu, 17 May 2018 23:17:42 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id g207-v6sm12556422pfb.18.2018.05.17.23.17.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 23:17:41 -0700 (PDT) Sender: Mark Johnston Date: Fri, 18 May 2018 02:17:39 -0400 From: Mark Johnston To: Mark Millard Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Subject: Re: enabling kernel dump options in GENERIC Message-ID: <20180518061739.GC5515@raichu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 06:17:44 -0000 On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: > Mark Johnston markj at FreeBSD.org wrote on > Thu May 17 17:24:19 UTC 2018 : > > > Over the past couple of years, a number of kernel dump features have > > been added: encryption, compression and dumping to a remote host > > (netdump). These features are currently all omitted from GENERIC. > > > > . . . > > Therefore, I'd like to propose enabling these features by default > > on i386, amd64, arm64, powerpc(64) and sparc64 so that they're available > > out of the box in 12.0. > > . . . > > Bugzilla 214598 (from late 2016) was about > dump for TARGET_ARCH=powerpc64 builds getting > failures like: > > KDB: enter: manual escape to debugger > [ thread pid 12 tid 10018 ] > Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 > db> dump > Dumping 9 MB (3 chunks) > chunk 0: 10MB (2510 pages) ... ok > chunk 1: 1MB (24 pages) ... ok > chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: c000000000022000 > > (A 32-bit powerpc build on the same machine worked > fine for dumping.) > > I just tried it with head -r333594 and I got something > similar. (Old and new mention routines with _bus_dma_map_ > in the names near the trap in the call stack. I've not > done a detailed comparison.) What is the call stack? From owner-freebsd-ppc@freebsd.org Fri May 18 13:14:58 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06593EF4C3A for ; Fri, 18 May 2018 13:14:58 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-21.consmr.mail.gq1.yahoo.com (sonic311-21.consmr.mail.gq1.yahoo.com [98.137.65.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6A8AF7536F for ; Fri, 18 May 2018 13:14:56 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: IZDxD5MVM1kEqN7oRScH8dHlbWym4Or4dg6eRlIMX98ui6r35nefzBlwv4b4XoV OdDij4y7ZQBV5emzFLimWb1aqRl9h4LM.5GfEqUbqGwIOFIkEG8M5wW3l0CKRqGf3KLwFqUbZGRE jJpA68IJl1gkceWp.MjhN5fMNCFYNI1mZFebaO.lxDgY7W9O0GbXmAETHVBCO5y.hlaUOKQsKbSt 9BGthI_vg5TBpaQE.G2MfBAOuaPlVYqyUHEG5rKN12wyhkjwTU74XOm6FYNDC_hk5Nfu2nAqvfY2 9NOs8QSLE1v6_LDKKzocVXCEj9jtwizCBL5zhpjfG77cx1iWuHX.xZ6AhQgcvt8RyYoHjFT_aN6K vXzU301rwNjRz0BZM5Oh0n8bXJl_svaQvG9rLcinCqplJUfx2xCZdwA6a8w0ag2UXPhd7cKoV1Hz 19H0XK1_Bo5zbbPz_FfrL3hqnCvqNPZNhHBX2w8PYpsuataBHGb70IKNtJTWqZhoLPv4jSWWMq5J cSOx8lcoE9hZxzXz7iANxyOGlXgqpXkQflJ5ixheV7Va2UR4ZQOv_Pht.n6I1nBYSioAkwamifpi XK1o4XUHo1SKIwZ24HC5R.X.r_.TESWOXGvZnZtVCWBeLwn2kcvdls5CC9cxMHp4DYM7SJevy4vX 0kWtlrC89 Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.gq1.yahoo.com with HTTP; Fri, 18 May 2018 13:14:55 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp422.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 3842a887bad1402a8d7eac6d60f0749f; Fri, 18 May 2018 13:14:51 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC From: Mark Millard In-Reply-To: <20180518061739.GC5515@raichu> Date: Fri, 18 May 2018 06:14:50 -0700 Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180518061739.GC5515@raichu> To: Mark Johnston X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 13:14:58 -0000 On 2018-May-17, at 11:17 PM, Mark Johnston wrote: > On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: >> Mark Johnston markj at FreeBSD.org wrote on >> Thu May 17 17:24:19 UTC 2018 : >>=20 >>> Over the past couple of years, a number of kernel dump features have >>> been added: encryption, compression and dumping to a remote host >>> (netdump). These features are currently all omitted from GENERIC. >>>=20 >>> . . . >>> Therefore, I'd like to propose enabling these features by default >>> on i386, amd64, arm64, powerpc(64) and sparc64 so that they're = available >>> out of the box in 12.0. >>> . . . >>=20 >> Bugzilla 214598 (from late 2016) was about >> dump for TARGET_ARCH=3Dpowerpc64 builds getting >> failures like: >>=20 >> KDB: enter: manual escape to debugger >> [ thread pid 12 tid 10018 ] >> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 >> db> dump >> Dumping 9 MB (3 chunks) >> chunk 0: 10MB (2510 pages) ... ok >> chunk 1: 1MB (24 pages) ... ok >> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: = c000000000022000 >>=20 >> (A 32-bit powerpc build on the same machine worked >> fine for dumping.) >>=20 >> I just tried it with head -r333594 and I got something >> similar. (Old and new mention routines with _bus_dma_map_ >> in the names near the trap in the call stack. I've not >> done a detailed comparison.) >=20 > What is the call stack? I'll have to induce the failure, take a picture of the screen that results, and hand type in the material for the fairly modern backtrace (-r333594). I will not be able to do this until later today. The bugzilla report has the old backtrace. I did not quote all the material from that report in the above. So there is something to compare against once I supply a modern one. Also: in about a week I'll lose access to the PowerMacs for an unknown period of time (weeks? months?). =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Fri May 18 13:27:32 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61DA8EA80D2 for ; Fri, 18 May 2018 13:27:31 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA75975B7C for ; Fri, 18 May 2018 13:27:28 +0000 (UTC) (envelope-from andy.silva@snscommunication.com) X-MSFBL: 6ZrrICsrnrPOha6qNMDDCeEUfBl/PiNQJJs35UjLxu8=|eyJiIjoiU25zdGVsZWN vbV9kZWRpY2F0ZWRfcG9vbF83NF85MV84NV8yMzgiLCJyIjoiZnJlZWJzZC1wcGN AZnJlZWJzZC5vcmciLCJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCJ9 Received: from [10.137.129.33] ([10.137.129.33:59466] helo=mtl-mtsp-c02-1.int.smtp) by mtl-mtsp-mta05-out1.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id 79/A7-23421-900DEFA5; Fri, 18 May 2018 13:07:21 +0000 Received: from 10.137.11.90 by Caffeine (mtl-mtsp-c02-1) with SMTP id 5f93f322-b676-4566-8c7b-e05d1b9ddd76 for freebsd-ppc@freebsd.org; Fri, 18 May 2018 13:07:19 +0000 (UTC) Received: from [65.49.242.4] ([65.49.242.4:58066] helo=gull-dhcp-65-49-242-4.bloombb.net) by mtl-mtsp-mta04-in2 (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id A1/4F-05140-600DEFA5; Fri, 18 May 2018 13:07:19 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snscommunication.com To: freebsd-ppc@freebsd.org Subject: Private LTE & 5G Network Ecosystem: 2018 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Fri, 18 May 2018 09:07:17 -0400 Message-ID: <968024123118469926092@Ankur> Feedback-ID: 6008902:SMTPCOM X-SMTPCOM-Sender-ID: 6008902 X-SMTPCOM-Tracking-Number: 5f93f322-b676-4566-8c7b-e05d1b9ddd76 X-SMTPCOM-Message-ID: 35630248-aa2a-42d3-a7c9-dfce6867b0d6 X-SMTPCOM-Payload: =?utf-8?q?CJBX8hMag7-=5FTJQE9mmeVDXHRoZjtWpWS=5FrTCFjA?= =?utf-8?q?LmxajP2fvsjrRLlzikcxkxf8Qc9o4GXPuRyFvgUZ-UHo7EZjAvj2ZGYa17=5FOL?= =?utf-8?q?ZM=5F8DtCaQrs9x9GTXk9sBCBpIn=5FUmJJPDN36olGBkQxpKEdBg=3D=3D?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smtpserver.email; i=@smtpserver.email; q=dns/txt; s=smtpcustomer; t=1526648840; h=MIME-Version : From : Reply-To : To : Subject : Content-Type : Date : Message-ID : List-Unsubscribe : From : Subject : Date; bh=u77tRajDCwVERMbYEz7u0hsSmRPObKcz2nonqcpVUk4=; b=qc5Ri3vr8Q0D2KVAcViih/c/M5FEryDlWhCEEGxS4ojCD4ryDSKNYzX7GMaUgS6nBj4s2W VGDm7BuVNN2iR0iu54fAbEA9pRc3OuxB57JdZlGi7C/v/VoGnQAqM/nQWMRi1GpJMrjEM49G G+nB6XRHGyv8VqparAoveWx7rjAo1ABKPkVYdUt7r9CIhNIGxPhg1T7lNUGwRTrLgWz+MkEi JRL/47O/mjn82uMc0Y/muGKrNWqe75LtqjsXJy7eN5Bf77Mq0rkT6zBGPL1pnBfeDO+Zr4nb HiFZhC2FWqUY2Pc6v4rHbOF+X1f5FkeZ6XZ0OMNyA9tUzgl/ONTLE6Mg== X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 13:27:32 -0000 Private LTE & 5G Network Ecosystem: 2018 =96 2030 =96 Opportunities, Challe= nges, Strategies, Industry Verticals & Forecasts (Report) Let me offer you the latest SNS Research report to you and your team, "Priv= ate LTE & 5G Network Ecosystem: 2018 =96 2030 =96 Opportunities, Challenges= , Strategies, Industry Verticals & Forecasts" Below is the report highligh= t and if you like I can send you sample pages for your details inside.=20 By providing authority over wireless coverage and capacity, private LTE and= 5G networks can ensure guaranteed connectivity, while supporting a wide ra= nge of applications and usage scenarios. Small-scale private LTE and 5G-rea= dy networks are also beginning to be deployed in industrial IoT (Internet o= f Things) settings =96 where LTE and 5G can fulfill the stringent reliabili= ty, availability and low latency requirements for connectivity in industria= l control and automation systems, besides supporting mobility for robotics = and machines. In addition, with the emergence of capabilities such as multi-operator smal= l cells and shared/unlicensed spectrum access schemes, the use of private = LTE and 5G networks =96 in enterprise buildings, campuses and public venues= , for localized connectivity =96 is expected to grow significantly over the= coming years. Expected to surpass $2.5 Billion in annual spending by the end of 2018, pri= vate LTE and 5G networks are increasingly becoming the preferred approach t= o deliver wireless connectivity for critical communications, industrial IoT= , enterprise & campus environments, and public venues. SNS Telecom & IT es= timates that the market will further grow at a CAGR of approximately 30% be= tween 2018 and 2021, eventually accounting for more than $5 Billion by the = end of 2021. Report Information: Release date: February 2018 Number of Pages: 904 Number of Tables and Figures: 259 Key Questions Answered: How big is the private LTE & 5G network opportunity=3F What trends, challenges and barriers are influencing its growth=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2021 and at what rate will it grow=3F Which vertical markets will see the highest percentage of growth=3F How will unlicensed and shared spectrum schemes =96 such as CBRS in the Uni= ted States =96 accelerate the adoption of private LTE & 5G networks for enterprises, public venues and neutral hosts=3F How does standardization impact the adoption of LTE & 5G networks for criti= cal communications and industrial IoT=3F When will MCPTT and other 3GPP-compliant mission-critical capabilities beco= me commercially mature for implementation=3F What opportunities exist for commercial mobile operators in the private LTE= & 5G network ecosystem=3F Will private LTE & 5G networks replace GSM-R and other legacy technologies = for railway communications=3F What are the prospects of deployable LTE & 5G systems=3F Who are the key market players and what are their strategies=3F What strategies should LTE/5G infrastructure OEMs, system integrators and m= obile operators adopt to remain competitive=3F Key Findings: The report has the following key findings: Expected to surpass $2.5 Billion in annual spending by the end of 2018, pri= vate LTE and 5G networks are increasingly becoming the preferred approach t= o deliver wireless connectivity for critical communications, industrial IoT= , enterprise & campus environments, and public venues.=20 SNS Telecom & IT estimates that the market will further grow at a CAGR of a= pproximately 30% between 2018 and 2021, eventually accounting for more than= $5 Billion in annual spending by the end of 2021. The critical communications and industrial IoT segment will continue to dom= inate the market in the coming years, primarily driven by the wide-area and= ubiquitous coverage requirements of ongoing nationwide public safety LTE n= etwork rollouts such as FirstNet and South Korea's Safe-Net, and supported = by considerable investments in the military, energy, utilities, mining and = transportation sectors. In the coming years, we also expect to see significant activity in the 3.5 = GHz CBRS and 5 GHz unlicensed bands, to support private LTE and 5G network = deployments across a range of environments, particularly enterprise buildin= gs, public venues, factories and warehouses. To avoid the high costs associated with large-scale dedicated LTE networks,= governments in a number of countries =96 predominantly in Europe =96 are e= ncouraging the adoption of secure MVNO (Mobile Virtual Network Operator) ar= rangements that pair private mobile core platforms with commercial LTE netw= orks to deliver broadband capabilities for critical communications users. Mobile operators are becoming ever more creative in their strategies to gai= n a foothold in the private LTE and 5G network ecosystem =96 ranging from = operated-branded critical communications LTE platforms to the BYON (Build Y= our Own Network) business model where mobile operators provide access to th= eir licensed spectrum so organizations can establish their own private LTE = networks in their active footprint. Vertical-domain specialists are leveraging partnerships with established wi= reless network infrastructure OEMs =96 such as Ericsson, Nokia, Huawei and= Samsung =96 to offer end-to-end private LTE and 5G-ready network solutions. The report covers the following topics: Private LTE & 5G network ecosystem Market drivers and barriers Architectural components and operational models for private LTE & 5G networ= ks Analysis of vertical markets and applications =96 ranging from mobile broad= band and mission-critical voice to domain-specific applications such as the= delay- sensitive control of railway infrastructure Key enabling technologies and concepts including MCPTT, deployable LTE/5G s= ystems, eMTC, NB-IoT, unlicensed/shared spectrum, neutral-host small cells = and network slicing Review of private LTE & 5G network engagements worldwide, including case st= udies of 30 live networks Spectrum availability, allocation and usage for private LTE & 5G networks Standardization, regulatory and collaborative initiatives Industry roadmap and value chain Profiles and strategies of over 440 ecosystem players including LTE/5G netw= ork infrastructure OEMs and vertical-domain specialists Strategic recommendations for end users, LTE/5G network infrastructure OEMs= , system integrators and commercial/private mobile operators Market analysis and forecasts from 2018 till 2030 Report Pricing: =20 Single User License: USD 2,500 Company Wide License: USD 3,500 =20 Ordering Process: =20 Please provide the following information: Report Title - Report License - (Single User/Company Wide) Name - Email - Job Title - Company - Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents and List of figures mentioned in report are given below for= more inside. I look forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom =20 _________________________________________________________________________ Table of Contents: =20 1.1 Executive Summary 1.2 Topics Covered 1.3 Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 2 Chapter 2: An Overview of Private LTE & 5G Networks 2.1 Private Wireless Networks 2.1.1 Addressing the Needs of the Critical Communications Industry 2.1.2 The Limitations of LMR (Land Mobile Radio) Networks 2.1.3 Moving Towards Commercial Mobile Broadband Technologies 2.1.4 Connectivity Requirements for the Industrial IoT (Internet of Things) 2.1.5 Localized Mobile Networks for Buildings, Campuses & Public Venues 2.2 LTE & 5G for Private Networking 2.2.1 Why LTE=3F 2.2.2 Performance Metrics 2.2.3 Coexistence, Interoperability and Spectrum Flexibility 2.2.4 A Thriving Ecosystem 2.2.5 Economic Feasibility 2.2.6 Moving Towards LTE-Advanced & LTE-Advanced Pro Networks 2.2.7 5G Capabilities & Usage Scenarios 2.3 Architectural Components of Private LTE & 5G Networks 2.3.1 UE (User Equipment) 2.3.2 E-UTRAN =96 The LTE RAN (Radio Access Network) 2.3.2.1 eNB Base Stations 2.3.2.2 TDD vs. FDD 2.3.3 Transport Network 2.3.4 EPC (Evolved Packet Core) =96 The LTE Mobile Core 2.3.4.1 SGW (Serving Gateway) 2.3.4.2 PGW (Packet Data Network Gateway) 2.3.4.3 MME (Mobility Management Entity) 2.3.4.4 HSS (Home Subscriber Server) 2.3.4.5 PCRF (Policy Charging and Rules Function) 2.3.5 IMS (IP-Multimedia Subsystem), Application & Service Elements 2.3.5.1 IMS Core & VoLTE 2.3.5.2 eMBMS (Enhanced Multimedia Broadcast Multicast Service) 2.3.5.3 ProSe (Proximity Services) 2.3.5.4 Group Communication & Mission-Critical Services 2.3.6 Gateways for LTE-External Network Interworking 2.3.7 Proposed 5G Architectural Elements 2.3.7.1 5G NR (New Radio) 2.3.7.2 NextGen Core Network 2.4 Key Enabling Technologies & Concepts 2.4.1 Critical Communications 2.4.1.1 MCPTT (Mission-Critical PTT) Voice & Group Communications 2.4.1.2 Mission-Critical Video & Data 2.4.1.3 ProSe (Proximity Services) for D2D Connectivity & Communications 2.4.1.4 IOPS (Isolated E-UTRAN Operation for Public Safety) 2.4.1.5 Deployable LTE & 5G Systems 2.4.1.6 UE Enhancements 2.4.2 eMTC & NB-IoT: Wide Area & High Density IoT Applications 2.4.3 QPP (QoS, Priority & Preemption) 2.4.4 End-to-End Security 2.4.5 Licensed Spectrum Sharing & Aggregation 2.4.6 Unlicensed & Shared Spectrum Usage 2.4.6.1 LSA (Licensed Shared Access): Two-Tiered Sharing 2.4.6.2 CBRS (Citizens Broadband Radio Service): Three-Tiered Sharing 2.4.6.3 LAA (License Assisted Access) & LTE-U: Licensed & Unlicensed Spectr= um Aggregation 2.4.6.4 MulteFire 2.4.7 Network Sharing & Slicing 2.4.7.1 MOCN (Multi-Operator Core Network) 2.4.7.2 DECOR (Dedicated Core) 2.4.7.3 Network Slicing 2.4.8 Software-Centric Networking 2.4.8.1 NFV (Network Functions Virtualization) 2.4.8.2 SDN (Software Defined Networking) 2.4.9 C-RAN (Centralized RAN) 2.4.10 MEC (Multi-Access Edge Computing) 2.5 Private LTE & 5G Network Operational Models 2.5.1 Independent Private Network 2.5.2 Managed Private Network 2.5.3 MVNO: Commercial Network with a Private Mobile Core 2.5.4 Other Approaches 2.6 Key Applications of Private LTE & 5G Networks 2.6.1 Secure & Seamless Mobile Broadband Access 2.6.2 Bandwidth-Intensive & Latency-Sensitive Field Applications 2.6.3 Bulk Multimedia & Data Transfers 2.6.4 In-Building Coverage & Capacity 2.6.5 Seamless Roaming & Mobile VPN Access 2.6.6 Mission-Critical HD Voice & Group Communications 2.6.7 Video & High-Resolution Imagery 2.6.8 Messaging & Presence Services 2.6.9 Location Services & Mapping 2.6.10 Command & Control Systems 2.6.11 Smart Grid Operations 2.6.12 Industrial Automation 2.6.13 High-Speed Railway Connectivity 2.6.14 PIS (Passenger Information System) 2.6.15 Delay-Sensitive Control of Railway Infrastructure 2.6.16 In-Flight Connectivity for Passengers & Airline Operators 2.6.17 Maritime Connectivity for Ships & Offshore Facilities 2.6.18 Telemetry, Control & Remote Diagnostics 2.6.19 Emerging 5G Applications 2.7 Market Growth Drivers 2.7.1 Recognition of LTE as the De-Facto Mobile Broadband Standard 2.7.2 Spectral Efficiency, Flexible Bandwidth, Regional Interoperability & = Cost Efficiency 2.7.3 Endorsement from the Critical Communications Industry 2.7.4 Emergence of Unlicensed & Shared Spectrum Technologies 2.7.5 Growing Demands for High-Speed Data Applications 2.7.6 Limited Coverage in Indoor, Industrial & Remote Environments 2.7.7 Control over QoS (Quality of Service) 2.8 Market Barriers 2.8.1 Lack of Licensed Spectrum 2.8.2 Funding Challenges for Large-Scale Networks 2.8.3 Smaller Coverage Footprint than Legacy LMR Systems 2.8.4 Delayed Standardization =20 3 Chapter 3: Vertical Markets, Case Studies & Private LTE/5G Engagements 3.1 Vertical Markets 3.1.1 Critical Communications & Industrial IoT 3.1.1.1 Public Safety 3.1.1.2 Military 3.1.1.3 Energy 3.1.1.4 Utilities 3.1.1.5 Mining 3.1.1.6 Transportation 3.1.1.7 Factories & Warehouses 3.1.1.8 Others 3.1.2 Enterprise & Campus Environments 3.1.3 Public Venues & Other Neutral Hosts 3.2 Private LTE & 5G Network Case Studies 3.2.1 Air France 3.2.2 ASTRID 3.2.3 Beach Energy 3.2.4 Busan Transportation Corporation 3.2.5 China Southern Power Grid 3.2.6 EAN (European Aviation Network) 3.2.7 FirstNet (First Responder Network) Authority 3.2.8 French Army 3.2.9 German Armed Forces (Bundeswehr) 3.2.10 Gold Fields 3.2.11 Halton Regional Police Service 3.2.12 INET (Infrastructure Networks) 3.2.13 Kenyan Police Service 3.2.14 KRNA (Korea Rail Network Authority) 3.2.15 LG Chem 3.2.16 Nedaa 3.2.17 Ocado 3.2.18 PSCA (Punjab Safe Cities Authority) 3.2.19 Qatar MOI (Ministry of Interior) 3.2.20 RESCAN (Canary Islands Network for Emergency and Security) 3.2.21 Rio Tinto Group 3.2.22 Rivas Vaciamadrid City Council 3.2.23 Shanghai Police Department 3.2.24 South Korea=92s Safe-Net (National Disaster Safety Communications Ne= twork) 3.2.25 Southern Linc 3.2.26 Tampnet 3.2.27 U.S. Navy 3.2.28 Ukkoverkot 3.2.29 United Kingdom=92s ESN (Emergency Services Network) 3.2.30 Zhengzhou Metro 3.3 Review of Other Private LTE & 5G Network Engagements 3.3.1 Asia Pacific 3.3.1.1 Australia 3.3.1.2 China 3.3.1.3 Hong Kong 3.3.1.4 India 3.3.1.5 Indonesia 3.3.1.6 Japan 3.3.1.7 Laos 3.3.1.8 Malaysia 3.3.1.9 New Zealand 3.3.1.10 Pakistan 3.3.1.11 Philippines 3.3.1.12 Singapore 3.3.1.13 South Korea 3.3.1.14 Thailand 3.3.2 Europe 3.3.2.1 Austria 3.3.2.2 Belgium 3.3.2.3 Denmark 3.3.2.4 Finland 3.3.2.5 France 3.3.2.6 Germany 3.3.2.7 Italy 3.3.2.8 Netherlands 3.3.2.9 Norway 3.3.2.10 Poland 3.3.2.11 Russia 3.3.2.12 Spain 3.3.2.13 Sweden 3.3.2.14 Switzerland 3.3.2.15 Turkey 3.3.2.16 United Kingdom 3.3.2.17 Other Countries 3.3.3 Latin & Central America 3.3.3.1 Brazil 3.3.3.2 Mexico 3.3.3.3 Other Countries 3.3.4 Middle East & Africa 3.3.4.1 GCC (Gulf Corporation Council) Countries 3.3.4.2 Ghana 3.3.4.3 Israel 3.3.4.4 Kenya 3.3.4.5 South Africa 3.3.4.6 Other Countries 3.3.5 North America 3.3.5.1 Canada 3.3.5.2 United States =20 4 Chapter 4: Spectrum Availability, Allocation & Usage 4.1 Frequency Bands for Private LTE & 5G Networks 4.1.1 Licensed Spectrum 4.1.1.1 400/450 MHz 4.1.1.2 700 MHz 4.1.1.3 800 MHz 4.1.1.4 900 MHz 4.1.1.5 1.4 GHz 4.1.1.6 1.8 GHz 4.1.1.7 2 GHz 4.1.1.8 2.6 GHz 4.1.1.9 3.5 GHz & Higher Frequencies 4.1.2 Unlicensed & Shared Spectrum 4.1.2.1 3.5 GHz CBRS 4.1.2.2 5 GHz Unlicensed 4.1.2.3 Other Frequencies 4.2 Spectrum Regulation, Sharing & Management 4.2.1 ITU-R (International Telecommunication Union Radiocommunication Secto= r) 4.2.2 450 MHz Alliance 4.2.3 CBRS Alliance 4.2.4 DSA (Dynamic Spectrum Alliance) 4.2.5 MulteFire Alliance 4.2.6 WinnForum (Wireless Innovation Forum) =20 5 Chapter 5: Standardization, Regulatory & Collaborative Initiatives 5.1 3GPP (Third Generation Partnership Project) 5.1.1 Public Safety & Critical Communications Enhancements in Releases 11-14 5.1.2 Industrial IoT Enhancements in Releases 13 & 14: eMTC & NB-IoT 5.1.3 Release 15 & Beyond: Mission-Critical Service Requirements for Railwa= ys & Transportation 5.2 AGURRE (Association of Major Users of Operational Radio Networks, Franc= e) 5.2.1 Advocacy Efforts for Private LTE Networks in the Transportation & Ene= rgy Sectors 5.3 ATIS (Alliance for Telecommunications Industry Solutions) 5.3.1 Standardization Efforts Relevant to Private & Critical Communications= LTE 5.4 China Association of Metros 5.4.1 Adoption of LTE as the Communications Standard for Urban Rail Systems 5.5 CRC (Communications Research Centre Canada) 5.5.1 Interoperability Research and Evaluation of Public Safety LTE Networks 5.6 DRDC (Defence Research and Development Canada) 5.6.1 R&D Efforts in Public Safety & Military LTE Networks 5.7 ETSI (European Telecommunications Standards Institute) 5.7.1 TCCE (TETRA and Critical Communications Evolution) Technical Committee 5.8 EUAR (European Union Agency for Railways) 5.8.1 Coordinating Efforts for FRMCS (Future Railway Mobile Communication S= ystem) 5.9 Home Office, United Kingdom 5.9.1 Public Safety LTE Standardization Efforts 5.10 KRRI (Korea Railroad Research Institute) 5.10.1 LTE-Based KRTCS (Korean Radio-Based Train Control System) 5.11 PSCE (Public Safety Communications Europe) 5.11.1 Standardization & Readiness Efforts for Mission-Critical Mobile Broa= dband 5.12 PSCR (Public Safety Communications Research) Program 5.12.1 Technology Development & Standardization Efforts for Public Safety L= TE 5.13 Public Safety Canada 5.13.1 Participation in the Federal PSBN (Public Safety Broadband Network) = Task Team 5.14 Safe-Net Forum 5.14.1 Guidance & Ecosystem Development for Public Safety LTE Networks 5.15 SCF (Small Cell Forum) 5.15.1 Specifications for Enterprise & Unlicensed Small Cells 5.16 TCCA (TETRA and Critical Communications Association) 5.16.1 CCBG (Critical Communications Broadband Group) 5.16.2 BIG (Broadband Industry Group) 5.17 TIA (Telecommunications Industry Association) 5.17.1 TR-8.8: Subcommittee on Broadband Data Systems 5.18 TTA (Telecommunications Technology Association of Korea) 5.18.1 Functional Requirements for Public Safety LTE 5.18.2 LTE-R (LTE Based Railway Communication System) 5.18.3 LTE-M (LTE-Maritime) 5.19 U.S. NIST (National Institute of Standards and Technology) 5.19.1 CTL (Communications Technology Laboratory): R&D Leadership for First= Net 5.20 U.S. NPSTC (National Public Safety Telecommunications Council) 5.20.1 Early Leadership in Public Safety LTE 5.21 U.S. NTIA (National Telecommunications and Information Administration) 5.21.1 FirstNet Governance & Funding 5.22 UIC (International Union of Railways) 5.22.1 Replacing GSM-R with LTE 5.22.2 FRMCS (Future Railway Mobile Communication System) Initiative 5.23 UTC (Utilities Telecom Council) & EUTC (European UTC) 5.23.1 Advocacy Efforts for Critical Infrastructure Private LTE Networks 5.24 Vendor-Led Alliances 5.24.1 Huawei's eLTE Industry Alliance 5.24.2 Nokia's Mission Critical Communications Alliance 5.25 Others =20 6 Chapter 6: Industry Roadmap & Value Chain 6.1 Industry Roadmap 6.1.1 Pre-2020: Large-Scale Investments in Critical Communications LTE Netw= orks 6.1.2 2020 =96 2025: Commercial Maturity of Unlicensed & Shared Spectrum 6.1.3 2025 =96 2030: Continued Investments in Private 5G Networks 6.2 Value Chain 6.2.1 Enabling Technology Providers 6.2.2 RAN, Mobile Core & Transport Infrastructure OEMs 6.2.3 Device OEMs 6.2.4 System Integrators 6.2.5 Application Developers 6.2.6 Test, Measurement & Performance Specialists 6.2.7 Mobile Operators 6.2.8 MVNOs 6.2.9 Vertical Market End Users =20 7 Chapter 7: Key Ecosystem Players 7.1 Alliander (450connect/Utility Connect) 7.2 4K Solutions 7.3 AAS (Amphenol Antenna Solutions) 7.4 Accelleran 7.5 Ace Technologies Corporation 7.6 AceAxis 7.7 Adax 7.8 ADLINK Technology 7.9 ADRF (Advanced RF Technologies) 7.10 ADTRAN 7.11 ADVA Optical Networking 7.12 Advantech 7.13 Advantech Wireless 7.14 Affarii Technologies 7.15 Affirmed Networks 7.16 Airbus Defence and Space 7.17 Air-Lynx 7.18 Airspan Networks 7.19 Alea 7.20 Alepo 7.21 Allied Telesis 7.22 Alpha Networks 7.23 Alpha Technologies 7.24 Alstom 7.25 Altaeros Energies 7.26 Altair Semiconductor 7.27 Altiostar Networks 7.28 Alvarion Technologies 7.29 AM Telecom 7.30 Ambra Solutions/Ecotel 7.31 Amarisoft 7.32 Amdocs 7.33 American Tower Corporation 7.34 Anritsu Corporation 7.35 Ansaldo STS 7.36 Arcadyan Technology Corporation 7.37 Arete M 7.38 Argela/Netsia 7.39 ArgoNET 7.40 Aricent 7.41 ARM Holdings 7.42 Arqiva 7.43 Artemis Networks 7.44 Artesyn Embedded Technologies 7.45 Artiza Networks 7.46 ASELAN 7.47 ASOCS 7.48 Assured Wireless Corporation 7.49 ASTRI (Hong Kong Applied Science and Technology Research Institute) 7.50 AT&T 7.51 Atel Antennas 7.52 Athonet 7.53 Atos 7.54 AttoCore 7.55 Avanti Communications Group 7.56 Aviat Networks 7.57 Azcom Technology 7.58 Azetti Networks 7.59 BAE Systems 7.60 Baicells Technologies 7.61 Barrett Communications 7.62 BATS (Broadband Antenna Tracking Systems) 7.63 BCE (Bell Canada) 7.64 Benetel 7.65 BFDX (BelFone) 7.66 Bird Technologies 7.67 Bittium Corporation 7.68 Black & Veatch 7.69 Black Box Corporation 7.70 Blackned 7.71 Bombardier Transportation 7.72 BridgeWave Communications 7.73 Broadcom 7.74 BTI Wireless 7.75 C Spire 7.76 CACI International 7.77 CalAmp Corporation 7.78 Cambium Networks 7.79 Cambridge Consultants 7.80 Casa Systems 7.81 CCI (Communication Components Inc.) 7.82 CCI Systems 7.83 CCN (Cirrus Core Networks) 7.84 cellXica 7.85 Ceragon Networks 7.86 Challenge Networks 7.87 Chemring Technology Solutions 7.88 Cielo Networks 7.89 Ciena Corporation 7.90 Cirpack 7.91 Cisco Systems 7.92 Cloudstreet 7.93 CND (Core Network Dynamics) 7.94 Cobham Wireless 7.95 Codan Radio Communications 7.96 Coherent Logix 7.97 Collinear Networks 7.98 Comba Telecom 7.99 COMLAB 7.100 CommAgility 7.101 CommScope 7.102 Comrod Communication Group 7.103 Comtech Telecommunications Corporation 7.104 CONET Technologies 7.105 Connect Tech 7.106 Contela 7.107 Coriant 7.108 Cornet Technology 7.109 Corning/Spider Cloud Wireless 7.110 Cradlepoint 7.111 Crown Castle International Corporation 7.112 CS Corporation 7.113 CybertelBridge 7.114 CyPhy Works 7.115 Dali Wireless 7.116 DAMM Cellular Systems 7.117 Datang Mobile 7.118 Dell Technologies 7.119 Delta Electronics 7.120 Dialogic 7.121 DragonWave-X 7.122 Druid Software 7.123 DT (Deutsche Telekom) 7.124 Duons 7.125 EchoStar Corporation 7.126 EE 7.127 EION Wireless 7.128 Elbit Systems 7.129 ELUON Corporation 7.130 Embraer Defense & Security 7.131 ENENSYS Technologies 7.132 Ericsson 7.133 ETELM 7.134 Etherstack 7.135 Ethertronics 7.136 ETRI (Electronics & Telecommunications Research Institute, South Kore= a) 7.137 Exalt Wireless 7.138 Excelerate Technology 7.139 EXFO 7.140 Expeto Wireless 7.141 Expway 7.142 ExteNet Systems 7.143 Eyecom Telecommunications Group 7.144 Facebook 7.145 Fairwaves 7.146 FastBack Networks 7.147 Federated Wireless 7.148 Fenix Group 7.149 Flash Private Mobile Networks 7.150 Foxcom 7.151 Fraunhofer FOKUS (Institute for Open Communication Systems) 7.152 Fraunhofer HHI (Heinrich Hertz Institute) 7.153 FreeWave Technologies 7.154 Ice Group 7.155 MVM Net 7.156 FRTek 7.157 Fujian Sunnada Network Technology 7.158 Fujitsu 7.159 Funkwerk 7.160 Future Technologies 7.161 Galtronics Corporation 7.162 GCT Semiconductor 7.163 GE (General Electric) 7.164 Gemtek Technology 7.165 Genaker 7.166 General Dynamics Mission Systems 7.167 GenXComm 7.168 GIKO GROUP 7.169 Gilat Satellite Networks 7.170 Globalstar 7.171 Goodman Networks 7.172 Goodmill Systems 7.173 Google/Alphabet 7.174 GRENTECH 7.175 GSI (GS Instech) 7.176 Guangzhou Iplook Technologies 7.177 GWT (Global Wireless Technologies) 7.178 Harris Corporation 7.179 HCL Technologies 7.180 HISPASAT Group 7.181 Hitachi 7.182 Hoimyung ICT 7.183 Honeywell International 7.184 Horsebridge Defence & Security 7.185 HPE (Hewlett Packard Enterprise) 7.186 Huawei 7.187 Hughes Network Systems 7.188 Hunter Technology 7.189 Hytera Communications 7.190 IAI (Israel Aerospace Industries) 7.191 Icom 7.192 IDY Corporation 7.193 Indra 7.194 InfoVista 7.195 Inmarsat 7.196 InnoWireless 7.197 Intel Corporation 7.198 InterDigital 7.199 Intracom Telecom 7.200 ip.access 7.201 IPITEK 7.202 Iridium Communications 7.203 ISCO International 7.204 IS-Wireless 7.205 Italtel 7.206 ITRI (Industrial Technology Research Institute, Taiwan) 7.207 JMA Wireless 7.208 JRC (Japan Radio Company) 7.209 Juni Global 7.210 Juniper Networks 7.211 JVCKENWOOD Corporation 7.212 Kapsch CarrierCom 7.213 Kathrein-Werke KG 7.214 KBR 7.215 Keysight Technologies 7.216 Kisan Telecom 7.217 Klas Telecom 7.218 Kleos 7.219 KMW 7.220 Koning & Hartman 7.221 Kontron S&T 7.222 KPN 7.223 KRTnet Corporation 7.224 KT Corporation 7.225 Kudelski Group 7.226 Kumu Networks 7.227 Kyocera Corporation 7.228 L3 Technologies 7.229 LCR Embedded Systems 7.230 Lemko Corporation 7.231 Leonardo 7.232 LG Electronics 7.233 LG Uplus 7.234 LGS Innovations 7.235 Ligado Networks 7.236 Lime Microsystems 7.237 LOCIVA 7.238 Lockheed Martin Corporation 7.239 LS telcom 7.240 Luminate Wireless 7.241 M87 7.242 Macquarie Group 7.243 Marlink 7.244 Martin UAV 7.245 Marvell Technology Group/Cavium 7.246 Mavenir Systems 7.247 MediaTek 7.248 Mellanox Technologies 7.249 MER Group 7.250 Metaswitch Networks 7.251 Microlab 7.252 Microwave Networks 7.253 MitraStar Technology Corporation 7.254 Mitsubishi Electric Corporation 7.255 Mobilicom 7.256 MoMe 7.257 Moseley Associates 7.258 Motorola Solutions 7.259 MP Antenna 7.260 MRV Communications 7.261 MTI (Microelectronics Technology, Inc.) 7.262 Mutualink 7.263 N.A.T. 7.264 Nash Technologies 7.265 NEC Corporation 7.266 Nemergent Solutions 7.267 Netas 7.268 NetMotion 7.269 NETSCOUT Systems 7.270 New Postcom Equipment 7.271 Nextivity 7.272 NI (National Instruments) 7.273 Node-H 7.274 Nokia Networks 7.275 Northrop Grumman Corporation 7.276 NuRAN Wireless 7.277 NVIS Communications 7.278 NXP Semiconductors 7.279 Oceus Networks 7.280 Octasic 7.281 ODN (Orbital Data Network) 7.282 Omnitele 7.283 Omoco 7.284 One2many 7.285 Oracle Communications 7.286 Orange 7.287 PacStar (Pacific Star Communications) 7.288 Panasonic Corporation 7.289 Panda Electronics Group 7.290 Panorama Antennas 7.291 Parallel Wireless 7.292 Parsons Corporation 7.293 PCTEL 7.294 pdvWireless 7.295 Pepro 7.296 Persistent Telecom 7.297 Phluido 7.298 Plover Bay Technologies 7.299 PMN (Private Mobile Networks) 7.300 Polaris Networks 7.301 Potevio 7.302 PRISMA Telecom Testing 7.303 Pulse Electronics 7.304 Qinetiq 7.305 Qualcomm 7.306 Quanta Computer 7.307 Qucell 7.308 Quintel 7.309 Quortus 7.310 RACOM Corporation 7.311 RAD Data Communications 7.312 Radio IP Software 7.313 Radisys Corporation 7.314 RADWIN 7.315 Rafael Advanced Defense Systems 7.316 Rajant Corporation 7.317 Range Networks 7.318 Raycap 7.319 Raytheon Company 7.320 Red Hat 7.321 RED Technologies 7.322 REDCOM Laboratories 7.323 Redline Communications 7.324 Rescue 42 7.325 RF Window 7.326 RFS (Radio Frequency Systems) 7.327 Ribbon Communications 7.328 RIVA Networks 7.329 Rivada Networks 7.330 Rockwell Collins 7.331 Rogers Communications 7.332 Rohde & Schwarz 7.333 Rohill 7.334 ROK Mobile 7.335 Rosenberger 7.336 Ruckus Wireless/ARRIS International 7.337 Saab 7.338 SAI Technology 7.339 SAIC (Science Applications International Corporation) 7.340 Samji Electronics 7.341 Samsung Electronics 7.342 Sapient Consulting 7.343 Sepura 7.344 Sequans Communications 7.345 SerComm Corporation 7.346 SES 7.347 Sevis Systems 7.348 SFR 7.349 Shentel (Shenandoah Telecommunications Company) 7.350 SIAE Microelettronica 7.351 Siemens 7.352 Sierra Wireless 7.353 Signal Information & Communication Corporation 7.354 Siklu Communication 7.355 Silicom 7.356 Simoco Wireless Solutions 7.357 Singtel/Optus 7.358 SiRRAN 7.359 Sistelbanda 7.360 SITRONICS 7.361 Siyata Mobile 7.362 SK Telecom 7.363 SK Telesys 7.364 SLA Corporation 7.365 SmartSky Networks 7.366 Smith Micro Software 7.367 Softil 7.368 SOLiD 7.369 Soliton Systems 7.370 Sonim Technologies 7.371 Sooktha 7.372 Southern Linc 7.373 Space Data Corporation 7.374 Spectra Group 7.375 Spirent Communications 7.376 Spreadtrum Communications 7.377 Sprint Corporation 7.378 SRS (Software Radio Systems) 7.379 Star Solutions 7.380 STMicroelectronics 7.381 sTraffic 7.382 StreamWIDE 7.383 Sumitomo Electric Industries 7.384 Swisscom 7.385 TacSat Networks 7.386 Tait Communications 7.387 Tampa Microwave 7.388 Tampnet 7.389 TASSTA 7.390 Tata Elxsi 7.391 TCL Communication 7.392 TCOM 7.393 Tech Mahindra 7.394 Tecom 7.395 Tecore Networks 7.396 TEKTELIC Communications 7.397 Telco Systems 7.398 Telef=F3nica Group 7.399 Telenor Group 7.400 Tellabs 7.401 Telrad Networks 7.402 Telstra 7.403 Teltronic 7.404 Telum 7.405 Telus Corporation 7.406 TESSCO Technologies 7.407 Thales 7.408 TI (Texas Instruments) 7.409 TIM (Telecom Italia Mobile) 7.410 TLC Solutions 7.411 T-Mobile USA 7.412 Tr=F3pico 7.413 U.S. Cellular 7.415 UK Broadband 7.416 Ukkoverkot 7.417 URSYS 7.418 Utility Associates 7.419 Vanu 7.420 Vencore Labs 7.421 Verizon Communications 7.422 ViaSat 7.423 Viavi Solutions 7.424 VMware 7.425 VNC (Virtual Network Communications) 7.426 VNL (Vihaan Networks Limited) 7.427 Vodafone Group 7.428 VTT Technical Research Centre of Finland 7.429 Westell Technologies 7.430 WiPro 7.431 Wireless Telecom Group 7.432 WNC (Wistron NeWeb Corporation) 7.433 WTL (World Telecom Labs) 7.434 Wytec International 7.435 xG Technology 7.436 Xilinx 7.437 Z-Com 7.438 Zetel Solutions 7.439 Zinwave 7.440 ZMTel (Shanghai Zhongmi Communication Technology) 7.441 ZTE =20 8 Chapter 8: Market Sizing & Forecasts 8.1 Global Outlook for Private LTE & 5G Network Investments 8.2 Segmentation by Technology 8.2.1 LTE 8.2.2 5G 8.3 Segmentation by Submarket 8.3.1 RAN 8.3.2 Mobile Core 8.3.3 Backhaul & Transport 8.4 Segmentation by Vertical Market 8.4.1 Critical Communications & Industrial IoT 8.4.1.1 RAN 8.4.1.2 Mobile Core 8.4.1.3 Backhaul & Transport 8.4.2 Public Safety 8.4.2.1 RAN 8.4.2.2 Mobile Core 8.4.2.3 Backhaul & Transport 8.4.3 Military 8.4.3.1 RAN 8.4.3.2 Mobile Core 8.4.3.3 Backhaul & Transport 8.4.4 Energy 8.4.4.1 RAN 8.4.4.2 Mobile Core 8.4.4.3 Backhaul & Transport 8.4.5 Utilities 8.4.5.1 RAN 8.4.5.2 Mobile Core 8.4.5.3 Backhaul & Transport 8.4.6 Mining 8.4.6.1 RAN 8.4.6.2 Mobile Core 8.4.6.3 Backhaul & Transport 8.4.7 Transportation 8.4.7.1 RAN 8.4.7.2 Mobile Core 8.4.7.3 Backhaul & Transport 8.4.8 Factories & Warehouses 8.4.8.1 RAN 8.4.8.2 Mobile Core 8.4.8.3 Backhaul & Transport 8.4.9 Other Critical Communications & Industrial IoT Sectors 8.4.9.1 RAN 8.4.9.2 Mobile Core 8.4.9.3 Backhaul & Transport 8.4.10 Enterprise & Campus Environments 8.4.10.1 RAN 8.4.10.2 Mobile Core 8.4.10.3 Backhaul & Transport 8.4.11 Public Venues & Other Neutral Hosts 8.4.11.1 RAN 8.4.11.2 Mobile Core 8.4.11.3 Backhaul & Transport 8.5 Segmentation by Region 8.5.1 Submarkets 8.5.1.1 RAN 8.5.1.2 Mobile Core 8.5.1.3 Backhaul & Transport 8.5.2 Vertical Markets 8.5.2.1 Critical Communications & Industrial IoT 8.5.2.2 Enterprise & Campus Environments 8.5.2.3 Public Venues & Other Neutral Hosts 8.6 Asia Pacific 8.6.1 Submarkets 8.6.1.1 RAN 8.6.1.2 Mobile Core 8.6.1.3 Backhaul & Transport 8.6.2 Vertical Markets 8.6.2.1 Critical Communications & Industrial IoT 8.6.2.2 Enterprise & Campus Environments 8.6.2.3 Public Venues & Other Neutral Hosts 8.7 Eastern Europe 8.7.1 Submarkets 8.7.1.1 RAN 8.7.1.2 Mobile Core 8.7.1.3 Backhaul & Transport 8.7.2 Vertical Markets 8.7.2.1 Critical Communications & Industrial IoT 8.7.2.2 Enterprise & Campus Environments 8.7.2.3 Public Venues & Other Neutral Hosts 8.8 Latin & Central America 8.8.1 Submarkets 8.8.1.1 RAN 8.8.1.2 Mobile Core 8.8.1.3 Backhaul & Transport 8.8.2 Vertical Markets 8.8.2.1 Critical Communications & Industrial IoT 8.8.2.2 Enterprise & Campus Environments 8.8.2.3 Public Venues & Other Neutral Hosts 8.9 Middle East & Africa 8.9.1 Submarkets 8.9.1.1 RAN 8.9.1.2 Mobile Core 8.9.1.3 Backhaul & Transport 8.9.2 Vertical Markets 8.9.2.1 Critical Communications & Industrial IoT 8.9.2.2 Enterprise & Campus Environments 8.9.2.3 Public Venues & Other Neutral Hosts 8.10 North America 8.10.1 Submarkets 8.10.1.1 RAN 8.10.1.2 Mobile Core 8.10.1.3 Backhaul & Transport 8.10.2 Vertical Markets 8.10.2.1 Critical Communications & Industrial IoT 8.10.2.2 Enterprise & Campus Environments 8.10.2.3 Public Venues & Other Neutral Hosts 8.11 Western Europe 8.11.1 Submarkets 8.11.1.1 RAN 8.11.1.2 Mobile Core 8.11.1.3 Backhaul & Transport 8.11.2 Vertical Markets 8.11.2.1 Critical Communications & Industrial IoT 8.11.2.2 Enterprise & Campus Environments 8.11.2.3 Public Venues & Other Neutral Hosts =20 9 Chapter 9: Conclusion & Strategic Recommendations 9.1 Why is the Market Poised to Grow=3F 9.2 Competitive Industry Landscape: Acquisitions, Alliances & Consolidation 9.3 Geographic Outlook: Which Regions Offer the Highest Growth Potential=3F 9.4 Which Vertical will Lead the Market=3F 9.5 Which Spectrum Bands Dominate the Market=3F 9.6 Prospects of Unlicensed & Shared Spectrum Networks 9.7 Opening the Door for Industrial & Mission-Critical IoT 9.8 The Race for 5G: Implications for Private Wireless Networks 9.9 MVNO Arrangements for Critical Communications: Opportunities for Mobile= Core Investments 9.10 Emergence of the BYON (Build Your Own Network) Business Model 9.11 Commercial Operator-Branded Critical Communications LTE Platforms 9.12 Replacing GSM-R with LTE for Railway Communications 9.13 Growing Use of Deployable LTE Systems 9.14 Strategic Recommendations 9.14.1 Vertical Markets & End Users 9.14.2 LTE & 5G Network Infrastructure OEMs 9.14.3 System Integrators 9.14.4 Commercial & Private Mobile Operators =20 List of Figures: =20 Figure 1: Basic Components of a Digital LMR Network Figure 2: LTE Speed Compared to 3G & Wi-Fi Networks (Mbps) Figure 3: Global LTE & 5G Subscriptions: 2018 =96 2030 (Millions) Figure 4: 5G Performance Requirements Figure 5: Private LTE Network Architecture Figure 6: 5G Network Architecture & Interaction with Other Networks Figure 7: Sidelink Air Interface for ProSe Figure 8: Transition from Normal Backhaul Connectivity to Isolated E-UTRAN = Operation Figure 9: Telef=F3nica's Portable LTE NIB (Network-in-Box) System Figure 10: Use Cases of eMTC and NB-IoT Technologies Figure 11: End-to-End Security in Private LTE Networks Figure 12: Conceptual Architecture for End-to-End Network Slicing in Mobile= Networks Figure 13: NFV Concept Figure 14: C-RAN Architecture Figure 15: Independent Private LTE/5G Network Figure 16: Managed Private LTE/5G Network Figure 17: Commercial LTE/5G Network with a Private Mobile Core Figure 18: Military LTE Network Architecture Figure 19: Key Elements & RF Site Coverage of Air France's Private LTE Netw= ork Figure 20: Air France's LTE & 5G Adoption Roadmap Figure 21: Beach Energy's LTE-Equipped Vehicles Figure 22: Busan Transportation Corporation=92s LTE-R Network Figure 23: Inmarsat and Deutsche Telekom's European Aviation Network Figure 24: FirstNet Deployment Plan & Timeline Figure 25: Airbus' BLR-LTE Platform for the French Army Figure 26: Infrastructure Networks' Fast L2 Architecture Figure 27: Infrastructure Networks' Private LTE Network for Critical Infras= tructure Figure 28: KRNA's Wonju-Gangneung HSR (High-Speed Railway) Line Figure 29: LG Chem's Private LTE Network for IoT Services Figure 30: Ocado's LTE-based Smart Platform Figure 31: User Segments and Applications of the RESCAN LTE Network Figure 32: Rio Tinto's Private LTE Network Figure 33: Key Architectural Elements of the Rivas Vaciamadrid Smart eLTE N= etwork Figure 34: Shanghai Police Convergent Command Center Figure 35: South Korea=92s Safe-Net Deployment Plan & Timeline Figure 36: Southern Linc's LTE Network Structure Figure 37: Tampnet's LTE Coverage in the North Sea Figure 38: Tampnet's LTE Coverage in the Gulf of Mexico Figure 39: Ukkoverkot's Architecture for a Hardened, Multi-Access Mobile Br= oadband Service for Critical Communications Figure 40: United Kingdom's ESN Deployment Timeline Figure 41: Zhengzhou Metro's LTE-Based Train-Ground Communications Network Figure 42: 3.5 GHz CBRS 3-Tiered Shared Spectrum in the United States Figure 43: ETSI's Critical Communications System Reference Model Figure 44: Private LTE & 5G Network Industry Roadmap Figure 45: Private LTE & 5G Network Value Chain Figure 46: Global Private LTE & 5G Network Infrastructure Revenue: 2018 =96= 2030 ($ Million) Figure 47: Global Private LTE & 5G Network Infrastructure Revenue by Techno= logy: 2018 =96 2030 ($ Million) Figure 48: Global Private LTE Network Infrastructure Revenue: 2018 =96 2030= ($ Million) Figure 49: Global Private 5G Network Infrastructure Revenue: 2019 =96 2030 = ($ Million) Figure 50: Global Private LTE & 5G Network Infrastructure Revenue by Submar= ket: 2018 =96 2030 ($ Million) Figure 51: Global Private LTE & 5G RAN Revenue: 2018 =96 2030 ($ Million) Figure 52: Global Private LTE & 5G Mobile Core Revenue: 2018 =96 2030 ($ Mi= llion) Figure 53: Global Private LTE & 5G Backhaul & Transport Revenue: 2018 =96 2= 030 ($ Million) Figure 54: Global Private LTE & 5G Network Infrastructure Revenue by Vertic= al Market: 2018 =96 2030 ($ Million) Figure 55: Global Private LTE & 5G Network Infrastructure Revenue in Critic= al Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 56: Global Private LTE & 5G Network Infrastructure Revenue in Critic= al Communications & Industrial IoT, by Submarket: 2018 =96 2030 ($ Million) Figure 57: Global Private LTE & 5G Base Station Unit Shipments in Critical = Communications & Industrial IoT: 2018 =96 2030 Figure 58: Global Private LTE & 5G Base Station Unit Shipment Revenue in Cr= itical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 59: Global Private LTE & 5G Mobile Core Revenue in Critical Communic= ations & Industrial IoT: 2018 =96 2030 ($ Million) Figure 60: Global Private LTE & 5G Backhaul & Transport Revenue in Critical= Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 61: Global Private LTE & 5G Network Infrastructure Revenue in the Pu= blic Safety Sector: 2018 =96 2030 ($ Million) Figure 62: Global Private LTE & 5G Network Infrastructure Revenue in the Pu= blic Safety Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 63: Global Private LTE & 5G Base Station Unit Shipments in the Publi= c Safety Sector: 2018 =96 2030 Figure 64: Global Private LTE & 5G Base Station Unit Shipment Revenue in th= e Public Safety Sector: 2018 =96 2030 ($ Million) Figure 65: Global Private LTE & 5G Mobile Core Revenue in the Public Safety= Sector: 2018 =96 2030 ($ Million) Figure 66: Global Private LTE & 5G Backhaul & Transport Revenue in the Publ= ic Safety Sector: 2018 =96 2030 ($ Million) Figure 67: Global Private LTE & 5G Network Infrastructure Revenue in the Mi= litary Sector: 2018 =96 2030 ($ Million) Figure 68: Global Private LTE & 5G Network Infrastructure Revenue in the Mi= litary Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 69: Global Private LTE & 5G Base Station Unit Shipments in the Milit= ary Sector: 2018 =96 2030 Figure 70: Global Private LTE & 5G Base Station Unit Shipment Revenue in th= e Military Sector: 2018 =96 2030 ($ Million) Figure 71: Global Private LTE & 5G Mobile Core Revenue in the Military Sect= or: 2018 =96 2030 ($ Million) Figure 72: Global Private LTE & 5G Backhaul & Transport Revenue in the Mili= tary Sector: 2018 =96 2030 ($ Million) Figure 73: Global Private LTE & 5G Network Infrastructure Revenue in the En= ergy Sector: 2018 =96 2030 ($ Million) Figure 74: Global Private LTE & 5G Network Infrastructure Revenue in the En= ergy Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 75: Global Private LTE & 5G Base Station Unit Shipments in the Energ= y Sector: 2018 =96 2030 Figure 76: Global Private LTE & 5G Base Station Unit Shipment Revenue in th= e Energy Sector: 2018 =96 2030 ($ Million) Figure 77: Global Private LTE & 5G Mobile Core Revenue in the Energy Sector= : 2018 =96 2030 ($ Million) Figure 78: Global Private LTE & 5G Backhaul & Transport Revenue in the Ener= gy Sector: 2018 =96 2030 ($ Million) Figure 79: Global Private LTE & 5G Network Infrastructure Revenue in the Ut= ilities Sector: 2018 =96 2030 ($ Million) Figure 80: Global Private LTE & 5G Network Infrastructure Revenue in the Ut= ilities Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 81: Global Private LTE & 5G Base Station Unit Shipments in the Utili= ties Sector: 2018 =96 2030 Figure 82: Global Private LTE & 5G Base Station Unit Shipment Revenue in th= e Utilities Sector: 2018 =96 2030 ($ Million) Figure 83: Global Private LTE & 5G Mobile Core Revenue in the Utilities Sec= tor: 2018 =96 2030 ($ Million) Figure 84: Global Private LTE & 5G Backhaul & Transport Revenue in the Util= ities Sector: 2018 =96 2030 ($ Million) Figure 85: Global Private LTE & 5G Network Infrastructure Revenue in the Mi= ning Sector: 2018 =96 2030 ($ Million) Figure 86: Global Private LTE & 5G Network Infrastructure Revenue in the Mi= ning Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 87: Global Private LTE & 5G Base Station Unit Shipments in the Minin= g Sector: 2018 =96 2030 Figure 88: Global Private LTE & 5G Base Station Unit Shipment Revenue in th= e Mining Sector: 2018 =96 2030 ($ Million) Figure 89: Global Private LTE & 5G Mobile Core Revenue in the Mining Sector= : 2018 =96 2030 ($ Million) Figure 90: Global Private LTE & 5G Backhaul & Transport Revenue in the Mini= ng Sector: 2018 =96 2030 ($ Million) Figure 91: Global Private LTE & 5G Network Infrastructure Revenue in the Tr= ansportation Sector: 2018 =96 2030 ($ Million) Figure 92: Global Private LTE & 5G Network Infrastructure Revenue in the Tr= ansportation Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 93: Global Private LTE & 5G Base Station Unit Shipments in the Trans= portation Sector: 2018 =96 2030 Figure 94: Global Private LTE & 5G Base Station Unit Shipment Revenue in th= e Transportation Sector: 2018 =96 2030 ($ Million) Figure 95: Global Private LTE & 5G Mobile Core Revenue in the Transportatio= n Sector: 2018 =96 2030 ($ Million) Figure 96: Global Private LTE & 5G Backhaul & Transport Revenue in the Tran= sportation Sector: 2018 =96 2030 ($ Million) Figure 97: Global Private LTE & 5G Network Infrastructure Revenue in the Fa= ctories & Warehouses Sector: 2018 =96 2030 ($ Million) Figure 98: Global Private LTE & 5G Network Infrastructure Revenue in the Fa= ctories & Warehouses Sector, by Submarket: 2018 =96 2030 ($ Million) Figure 99: Global Private LTE & 5G Base Station Unit Shipments in the Facto= ries & Warehouses Sector: 2018 =96 2030 Figure 100: Global Private LTE & 5G Base Station Unit Shipment Revenue in t= he Factories & Warehouses Sector: 2018 =96 2030 ($ Million) Figure 101: Global Private LTE & 5G Mobile Core Revenue in the Factories & = Warehouses Sector: 2018 =96 2030 ($ Million) Figure 102: Global Private LTE & 5G Backhaul & Transport Revenue in the Fac= tories & Warehouses Sector: 2018 =96 2030 ($ Million) Figure 103: Global Private LTE & 5G Network Infrastructure Revenue in Other= Critical Communications & Industrial IoT Sectors: 2018 =96 2030 ($ Million) Figure 104: Global Private LTE & 5G Network Infrastructure Revenue in Other= Critical Communications & Industrial IoT Sectors, by Submarket: 2018 =96 2= 030 ($ Million) Figure 105: Global Private LTE & 5G Base Station Unit Shipments in Other Cr= itical Communications & Industrial IoT Sectors: 2018 =96 2030 Figure 106: Global Private LTE & 5G Base Station Unit Shipment Revenue in O= ther Critical Communications & Industrial IoT Sectors: 2018 =96 2030 ($ Mil= lion) Figure 107: Global Private LTE & 5G Mobile Core Revenue in Other Critical C= ommunications & Industrial IoT Sectors: 2018 =96 2030 ($ Million) Figure 108: Global Private LTE & 5G Backhaul & Transport Revenue in Other C= ritical Communications & Industrial IoT Sectors: 2018 =96 2030 ($ Million) Figure 109: Global Private LTE & 5G Network Infrastructure Revenue in Enter= prise & Campus Environments: 2018 =96 2030 ($ Million) Figure 110: Global Private LTE & 5G Network Infrastructure Revenue in Enter= prise & Campus Environments, by Submarket: 2018 =96 2030 ($ Million) Figure 111: Global Private LTE & 5G Small Cell Unit Shipments in Enterprise= & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 112: Global Private LTE & 5G Small Cell Unit Shipment Revenue in Ent= erprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 113: Global Private LTE & 5G Mobile Core Revenue in Enterprise & Cam= pus Environments: 2018 =96 2030 ($ Million) Figure 114: Global Private LTE & 5G Backhaul & Transport Revenue in Enterpr= ise & Campus Environments: 2018 =96 2030 ($ Million) Figure 115: Global Private LTE & 5G Network Infrastructure Revenue in Publi= c Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 116: Global Private LTE & 5G Network Infrastructure Revenue in Publi= c Venues & Other Neutral Hosts, by Submarket: 2018 =96 2030 ($ Million) Figure 117: Global Private LTE & 5G Small Cell Unit Shipments in Public Ven= ues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Units) Figure 118: Global Private LTE & 5G Small Cell Unit Shipment Revenue in Pub= lic Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 119: Global Private LTE & 5G Mobile Core Revenue in Public Venues & = Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 120: Global Private LTE & 5G Backhaul & Transport Revenue in Public = Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 121: Private LTE & 5G Network Infrastructure Revenue by Region: 2018= =96 2030 ($ Million) Figure 122: Private LTE & 5G RAN Revenue by Region: 2018 =96 2030 ($ Millio= n) Figure 123: Private LTE & 5G Mobile Core Revenue by Region: 2018 =96 2030 (= $ Million) Figure 124: Private LTE & 5G Backhaul & Transport Revenue by Region: 2018 = =96 2030 ($ Million) Figure 125: Private LTE & 5G Network Infrastructure Revenue in Critical Com= munications & Industrial IoT, by Region: 2018 =96 2030 ($ Million) Figure 126: Private LTE & 5G Base Station Unit Shipments in Critical Commun= ications & Industrial IoT, by Region: 2018 =96 2030 Figure 127: Private LTE & 5G Base Station Unit Shipment Revenue in Critical= Communications & Industrial IoT, by Region: 2018 =96 2030 ($ Million) Figure 128: Private LTE & 5G Mobile Core Revenue in Critical Communications= & Industrial IoT, by Region: 2018 =96 2030 ($ Million) Figure 129: Private LTE & 5G Backhaul & Transport Revenue in Critical Commu= nications & Industrial IoT, by Region: 2018 =96 2030 ($ Million) Figure 130: Private LTE & 5G Network Infrastructure Revenue in Enterprise &= Campus Environments, by Region: 2018 =96 2030 ($ Million) Figure 131: Private LTE & 5G Small Cell Unit Shipments in Enterprise & Camp= us Environments, by Region: 2018 =96 2030 (Thousands of Units) Figure 132: Private LTE & 5G Small Cell Unit Shipment Revenue in Enterprise= & Campus Environments, by Region: 2018 =96 2030 ($ Million) Figure 133: Private LTE & 5G Mobile Core Revenue in Enterprise & Campus Env= ironments, by Region: 2018 =96 2030 ($ Million) Figure 134: Private LTE & 5G Backhaul & Transport Revenue in Enterprise & C= ampus Environments, by Region: 2018 =96 2030 ($ Million) Figure 135: Private LTE & 5G Network Infrastructure Revenue in Public Venue= s & Other Neutral Hosts, by Region: 2018 =96 2030 ($ Million) Figure 136: Private LTE & 5G Small Cell Unit Shipments in Public Venues & O= ther Neutral Hosts, by Region: 2018 =96 2030 (Thousands of Units) Figure 137: Private LTE & 5G Small Cell Unit Shipment Revenue in Public Ven= ues & Other Neutral Hosts, by Region: 2018 =96 2030 ($ Million) Figure 138: Private LTE & 5G Mobile Core Revenue in Public Venues & Other N= eutral Hosts, by Region: 2018 =96 2030 ($ Million) Figure 139: Private LTE & 5G Backhaul & Transport Revenue in Public Venues = & Other Neutral Hosts, by Region: 2018 =96 2030 ($ Million) Figure 140: Asia Pacific Private LTE & 5G Network Infrastructure Revenue: 2= 018 =96 2030 ($ Million) Figure 141: Asia Pacific Private LTE & 5G RAN Revenue: 2018 =96 2030 ($ Mil= lion) Figure 142: Asia Pacific Private LTE & 5G Mobile Core Revenue: 2018 =96 203= 0 ($ Million) Figure 143: Asia Pacific Private LTE & 5G Backhaul & Transport Revenue: 201= 8 =96 2030 ($ Million) Figure 144: Asia Pacific Private LTE & 5G Network Infrastructure Revenue in= Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 145: Asia Pacific Private LTE & 5G Base Station Unit Shipments in Cr= itical Communications & Industrial IoT: 2018 =96 2030 Figure 146: Asia Pacific Private LTE & 5G Base Station Unit Shipment Revenu= e in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 147: Asia Pacific Private LTE & 5G Mobile Core Revenue in Critical C= ommunications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 148: Asia Pacific Private LTE & 5G Backhaul & Transport Revenue in C= ritical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 149: Asia Pacific Private LTE & 5G Network Infrastructure Revenue in= Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 150: Asia Pacific Private LTE & 5G Small Cell Unit Shipments in Ente= rprise & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 151: Asia Pacific Private LTE & 5G Small Cell Unit Shipment Revenue = in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 152: Asia Pacific Private LTE & 5G Mobile Core Revenue in Enterprise= & Campus Environments: 2018 =96 2030 ($ Million) Figure 153: Asia Pacific Private LTE & 5G Backhaul & Transport Revenue in E= nterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 154: Asia Pacific Private LTE & 5G Network Infrastructure Revenue in= Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 155: Asia Pacific Private LTE & 5G Small Cell Unit Shipments in Publ= ic Venues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Units) Figure 156: Asia Pacific Private LTE & 5G Small Cell Unit Shipment Revenue = in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 157: Asia Pacific Private LTE & 5G Mobile Core Revenue in Public Ven= ues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 158: Asia Pacific Private LTE & 5G Backhaul & Transport Revenue in P= ublic Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 159: Eastern Europe Private LTE & 5G Network Infrastructure Revenue:= 2018 =96 2030 ($ Million) Figure 160: Eastern Europe Private LTE & 5G RAN Revenue: 2018 =96 2030 ($ M= illion) Figure 161: Eastern Europe Private LTE & 5G Mobile Core Revenue: 2018 =96 2= 030 ($ Million) Figure 162: Eastern Europe Private LTE & 5G Backhaul & Transport Revenue: 2= 018 =96 2030 ($ Million) Figure 163: Eastern Europe Private LTE & 5G Network Infrastructure Revenue = in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 164: Eastern Europe Private LTE & 5G Base Station Unit Shipments in = Critical Communications & Industrial IoT: 2018 =96 2030 Figure 165: Eastern Europe Private LTE & 5G Base Station Unit Shipment Reve= nue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 166: Eastern Europe Private LTE & 5G Mobile Core Revenue in Critical= Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 167: Eastern Europe Private LTE & 5G Backhaul & Transport Revenue in= Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 168: Eastern Europe Private LTE & 5G Network Infrastructure Revenue = in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 169: Eastern Europe Private LTE & 5G Small Cell Unit Shipments in En= terprise & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 170: Eastern Europe Private LTE & 5G Small Cell Unit Shipment Revenu= e in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 171: Eastern Europe Private LTE & 5G Mobile Core Revenue in Enterpri= se & Campus Environments: 2018 =96 2030 ($ Million) Figure 172: Eastern Europe Private LTE & 5G Backhaul & Transport Revenue in= Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 173: Eastern Europe Private LTE & 5G Network Infrastructure Revenue = in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 174: Eastern Europe Private LTE & 5G Small Cell Unit Shipments in Pu= blic Venues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Units) Figure 175: Eastern Europe Private LTE & 5G Small Cell Unit Shipment Revenu= e in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 176: Eastern Europe Private LTE & 5G Mobile Core Revenue in Public V= enues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 177: Eastern Europe Private LTE & 5G Backhaul & Transport Revenue in= Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 178: Latin & Central America Private LTE & 5G Network Infrastructure= Revenue: 2018 =96 2030 ($ Million) Figure 179: Latin & Central America Private LTE & 5G RAN Revenue: 2018 =96 = 2030 ($ Million) Figure 180: Latin & Central America Private LTE & 5G Mobile Core Revenue: 2= 018 =96 2030 ($ Million) Figure 181: Latin & Central America Private LTE & 5G Backhaul & Transport R= evenue: 2018 =96 2030 ($ Million) Figure 182: Latin & Central America Private LTE & 5G Network Infrastructure= Revenue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Mill= ion) Figure 183: Latin & Central America Private LTE & 5G Base Station Unit Ship= ments in Critical Communications & Industrial IoT: 2018 =96 2030 Figure 184: Latin & Central America Private LTE & 5G Base Station Unit Ship= ment Revenue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ = Million) Figure 185: Latin & Central America Private LTE & 5G Mobile Core Revenue in= Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 186: Latin & Central America Private LTE & 5G Backhaul & Transport R= evenue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Millio= n) Figure 187: Latin & Central America Private LTE & 5G Network Infrastructure= Revenue in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 188: Latin & Central America Private LTE & 5G Small Cell Unit Shipme= nts in Enterprise & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 189: Latin & Central America Private LTE & 5G Small Cell Unit Shipme= nt Revenue in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 190: Latin & Central America Private LTE & 5G Mobile Core Revenue in= Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 191: Latin & Central America Private LTE & 5G Backhaul & Transport R= evenue in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 192: Latin & Central America Private LTE & 5G Network Infrastructure= Revenue in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 193: Latin & Central America Private LTE & 5G Small Cell Unit Shipme= nts in Public Venues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Uni= ts) Figure 194: Latin & Central America Private LTE & 5G Small Cell Unit Shipme= nt Revenue in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 195: Latin & Central America Private LTE & 5G Mobile Core Revenue in= Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 196: Latin & Central America Private LTE & 5G Backhaul & Transport R= evenue in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 197: Middle East & Africa Private LTE & 5G Network Infrastructure Re= venue: 2018 =96 2030 ($ Million) Figure 198: Middle East & Africa Private LTE & 5G RAN Revenue: 2018 =96 203= 0 ($ Million) Figure 199: Middle East & Africa Private LTE & 5G Mobile Core Revenue: 2018= =96 2030 ($ Million) Figure 200: Middle East & Africa Private LTE & 5G Backhaul & Transport Reve= nue: 2018 =96 2030 ($ Million) Figure 201: Middle East & Africa Private LTE & 5G Network Infrastructure Re= venue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 202: Middle East & Africa Private LTE & 5G Base Station Unit Shipmen= ts in Critical Communications & Industrial IoT: 2018 =96 2030 Figure 203: Middle East & Africa Private LTE & 5G Base Station Unit Shipmen= t Revenue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Mil= lion) Figure 204: Middle East & Africa Private LTE & 5G Mobile Core Revenue in Cr= itical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 205: Middle East & Africa Private LTE & 5G Backhaul & Transport Reve= nue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 206: Middle East & Africa Private LTE & 5G Network Infrastructure Re= venue in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 207: Middle East & Africa Private LTE & 5G Small Cell Unit Shipments= in Enterprise & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 208: Middle East & Africa Private LTE & 5G Small Cell Unit Shipment = Revenue in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 209: Middle East & Africa Private LTE & 5G Mobile Core Revenue in En= terprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 210: Middle East & Africa Private LTE & 5G Backhaul & Transport Reve= nue in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 211: Middle East & Africa Private LTE & 5G Network Infrastructure Re= venue in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 212: Middle East & Africa Private LTE & 5G Small Cell Unit Shipments= in Public Venues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Units) Figure 213: Middle East & Africa Private LTE & 5G Small Cell Unit Shipment = Revenue in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 214: Middle East & Africa Private LTE & 5G Mobile Core Revenue in Pu= blic Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 215: Middle East & Africa Private LTE & 5G Backhaul & Transport Reve= nue in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 216: North America Private LTE & 5G Network Infrastructure Revenue: = 2018 =96 2030 ($ Million) Figure 217: North America Private LTE & 5G RAN Revenue: 2018 =96 2030 ($ Mi= llion) Figure 218: North America Private LTE & 5G Mobile Core Revenue: 2018 =96 20= 30 ($ Million) Figure 219: North America Private LTE & 5G Backhaul & Transport Revenue: 20= 18 =96 2030 ($ Million) Figure 220: North America Private LTE & 5G Network Infrastructure Revenue i= n Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 221: North America Private LTE & 5G Base Station Unit Shipments in C= ritical Communications & Industrial IoT: 2018 =96 2030 Figure 222: North America Private LTE & 5G Base Station Unit Shipment Reven= ue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 223: North America Private LTE & 5G Mobile Core Revenue in Critical = Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 224: North America Private LTE & 5G Backhaul & Transport Revenue in = Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 225: North America Private LTE & 5G Network Infrastructure Revenue i= n Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 226: North America Private LTE & 5G Small Cell Unit Shipments in Ent= erprise & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 227: North America Private LTE & 5G Small Cell Unit Shipment Revenue= in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 228: North America Private LTE & 5G Mobile Core Revenue in Enterpris= e & Campus Environments: 2018 =96 2030 ($ Million) Figure 229: North America Private LTE & 5G Backhaul & Transport Revenue in = Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 230: North America Private LTE & 5G Network Infrastructure Revenue i= n Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 231: North America Private LTE & 5G Small Cell Unit Shipments in Pub= lic Venues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Units) Figure 232: North America Private LTE & 5G Small Cell Unit Shipment Revenue= in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 233: North America Private LTE & 5G Mobile Core Revenue in Public Ve= nues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 234: North America Private LTE & 5G Backhaul & Transport Revenue in = Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 235: Western Europe Private LTE & 5G Network Infrastructure Revenue:= 2018 =96 2030 ($ Million) Figure 236: Western Europe Private LTE & 5G RAN Revenue: 2018 =96 2030 ($ M= illion) Figure 237: Western Europe Private LTE & 5G Mobile Core Revenue: 2018 =96 2= 030 ($ Million) Figure 238: Western Europe Private LTE & 5G Backhaul & Transport Revenue: 2= 018 =96 2030 ($ Million) Figure 239: Western Europe Private LTE & 5G Network Infrastructure Revenue = in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 240: Western Europe Private LTE & 5G Base Station Unit Shipments in = Critical Communications & Industrial IoT: 2018 =96 2030 Figure 241: Western Europe Private LTE & 5G Base Station Unit Shipment Reve= nue in Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 242: Western Europe Private LTE & 5G Mobile Core Revenue in Critical= Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 243: Western Europe Private LTE & 5G Backhaul & Transport Revenue in= Critical Communications & Industrial IoT: 2018 =96 2030 ($ Million) Figure 244: Western Europe Private LTE & 5G Network Infrastructure Revenue = in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 245: Western Europe Private LTE & 5G Small Cell Unit Shipments in En= terprise & Campus Environments: 2018 =96 2030 (Thousands of Units) Figure 246: Western Europe Private LTE & 5G Small Cell Unit Shipment Revenu= e in Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 247: Western Europe Private LTE & 5G Mobile Core Revenue in Enterpri= se & Campus Environments: 2018 =96 2030 ($ Million) Figure 248: Western Europe Private LTE & 5G Backhaul & Transport Revenue in= Enterprise & Campus Environments: 2018 =96 2030 ($ Million) Figure 249: Western Europe Private LTE & 5G Network Infrastructure Revenue = in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 250: Western Europe Private LTE & 5G Small Cell Unit Shipments in Pu= blic Venues & Other Neutral Hosts: 2018 =96 2030 (Thousands of Units) Figure 251: Western Europe Private LTE & 5G Small Cell Unit Shipment Revenu= e in Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 252: Western Europe Private LTE & 5G Mobile Core Revenue in Public V= enues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 253: Western Europe Private LTE & 5G Backhaul & Transport Revenue in= Public Venues & Other Neutral Hosts: 2018 =96 2030 ($ Million) Figure 254: Private LTE & 5G Network Infrastructure Spending Breakdown by R= egion: 2018 (%) Figure 255: Global Private LTE & 5G Network Infrastructure Spending Breakdo= wn by Vertical: 2018 (%) Figure 256: Global Unlicensed/Shared Spectrum Private LTE & 5G Small Cell S= hipments: 2018 =96 2030 (Thousands of Units) Figure 257: Global Mobile Core Investments in Critical Communications MVNO = Broadband Networks: 2018 =96 2030 ($ Million) Figure 258: Global Private LTE & 5G Network Investments in Railway Communic= ations: 2018 =96 2030 ($ Million) Figure 259: Global Deployable Private LTE & 5G System Shipments by Vertical= : 2018 =96 2030 =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com =20 From owner-freebsd-ppc@freebsd.org Fri May 18 15:11:26 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DD363EAB174; Fri, 18 May 2018 15:11:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pl0-x242.google.com (mail-pl0-x242.google.com [IPv6:2607:f8b0:400e:c01::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 614E97A13A; Fri, 18 May 2018 15:11:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pl0-x242.google.com with SMTP id w19-v6so4756521plq.4; Fri, 18 May 2018 08:11:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=8wCpiNzu9sm6HYU41FTNvfeU6u5ocXmr9sw74+ewt4M=; b=kc6ln7mKra6aQUCd4QfOSUEhPYYj2dqVIdr8XnbTi+KOgAeVzBrV03hAX6j7SvOUr5 pgeBrVb/DXp0SEGTah1rdiM9wj81TaGJ4xbCzKYQVI5q1kSFJy4pNj6O8KDeptCJp05H 5KeBZ7whTTtZCGKwnFEYjpNU3R5xoGxqC5BtG79HUsG9qBbXfmJiX6trZk+Ka3MLHIeb eSd5yFf4Zbp8EaxPWkGs7s/Lg7ePgu70MnE3ZMSkbcUDwIy98McNBDlAY+ns0KN3Dy+J 7KzS6UIfYopkPvNgv4F6uRklrzl/Ht6ir6B/BGbUx0FRc4vWHABcI8Zs89dUrnJyM6Ji dWTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=8wCpiNzu9sm6HYU41FTNvfeU6u5ocXmr9sw74+ewt4M=; b=lcN7Bd5pnhqvGKj8exrprGpFkDNIqeCYYRCzBCyf2331MZqRnzrt1ZU/Pt/CsVOooM QXWLQuXnNv5rkp2bhbKzM2E25i7FZ5vqnBf0eQ1e1eKOh6P9hojUOTC8sctlmKf6fZEu avBuyXfKFkA6lCrrzFxfNfzO+sGce1gHT5LQ4LIZXhqPGD1DRcrdN4OKP8d8zhsjUrcZ rfkZE9s0dg9k1U8Xt6/IyKmYm7/BbccsytPMD6MtQ0SuAnqCBaRn+PBWznwfO+1XGKDN wKFoSBzbjOD+KH3rV1qAqwqwUOu2zev1xsUuKEFjeTQIzCVIwEdQyjvlHD8ERYIwDmG4 Tx1w== X-Gm-Message-State: ALKqPwerrm5GYPEXvDnOqnZZCqdHMEjbtW1AJZlaDTwKcE8booVY+OcX Im7dbronp+G0LN5cVE6t7fM= X-Google-Smtp-Source: AB8JxZo4B90wHlVx2cF569A3dyOti72O5dKLTNt5MPWL1BJ2tXWwdZCVybT3w2v5LQ8X9LFDFCOL+Q== X-Received: by 2002:a17:902:7e05:: with SMTP id b5-v6mr9717775plm.230.1526656284478; Fri, 18 May 2018 08:11:24 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-130.dsl.bell.ca. [70.49.169.130]) by smtp.gmail.com with ESMTPSA id u6-v6sm10181530pgo.46.2018.05.18.08.11.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 08:11:23 -0700 (PDT) Sender: Mark Johnston Date: Fri, 18 May 2018 11:11:20 -0400 From: Mark Johnston To: Mark Millard Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Subject: Re: enabling kernel dump options in GENERIC Message-ID: <20180518151120.GE5515@raichu> References: <20180518061739.GC5515@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 15:11:26 -0000 On Fri, May 18, 2018 at 06:14:50AM -0700, Mark Millard wrote: > On 2018-May-17, at 11:17 PM, Mark Johnston wrote: > > > On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: > >> Mark Johnston markj at FreeBSD.org wrote on > >> Thu May 17 17:24:19 UTC 2018 : > >> > >>> Over the past couple of years, a number of kernel dump features have > >>> been added: encryption, compression and dumping to a remote host > >>> (netdump). These features are currently all omitted from GENERIC. > >>> > >>> . . . > >>> Therefore, I'd like to propose enabling these features by default > >>> on i386, amd64, arm64, powerpc(64) and sparc64 so that they're available > >>> out of the box in 12.0. > >>> . . . > >> > >> Bugzilla 214598 (from late 2016) was about > >> dump for TARGET_ARCH=powerpc64 builds getting > >> failures like: > >> > >> KDB: enter: manual escape to debugger > >> [ thread pid 12 tid 10018 ] > >> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 > >> db> dump > >> Dumping 9 MB (3 chunks) > >> chunk 0: 10MB (2510 pages) ... ok > >> chunk 1: 1MB (24 pages) ... ok > >> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr: c000000000022000 > >> > >> (A 32-bit powerpc build on the same machine worked > >> fine for dumping.) > >> > >> I just tried it with head -r333594 and I got something > >> similar. (Old and new mention routines with _bus_dma_map_ > >> in the names near the trap in the call stack. I've not > >> done a detailed comparison.) > > > > What is the call stack? > > I'll have to induce the failure, take a picture of > the screen that results, and hand type in the > material for the fairly modern backtrace (-r333594). > I will not be able to do this until later today. > > The bugzilla report has the old backtrace. I did not > quote all the material from that report in the above. > So there is something to compare against once I > supply a modern one. My apologies, I missed the fact that the backtrace was included in that PR. Since the problem still occurs and apparently manifests with a similar backtrace, it wouldn't be useful to retest. I'm afraid I don't have any suggestions on how to make progress here. Given that the new options give only a small increase in the kernel size, I'm still inclined to enable them on powerpc64 for consistency with other architectures. > Also: in about a week I'll lose access to the PowerMacs > for an unknown period of time (weeks? months?). > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > From owner-freebsd-ppc@freebsd.org Fri May 18 19:37:19 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69116ED91FD for ; Fri, 18 May 2018 19:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0FC9885FEF for ; Fri, 18 May 2018 19:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 08D7C124D4; Fri, 18 May 2018 19:37:19 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 069AA124D3 for ; Fri, 18 May 2018 19:37:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C361A85FED for ; Fri, 18 May 2018 19:37:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 23A39219D3 for ; Fri, 18 May 2018 19:37:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4IJbIJH051113 for ; Fri, 18 May 2018 19:37:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4IJbIrp051111 for powerpc@FreeBSD.org; Fri, 18 May 2018 19:37:18 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 221645] www/webkit2-gtk3 build fails on PPC because of exception for PPC Date: Fri, 18 May 2018 19:37:17 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kwm@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Overcome By Events X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gnome@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: resolution cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 May 2018 19:37:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221645 Koop Mast changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Overcome By Events CC| |kwm@FreeBSD.org Status|New |Closed --- Comment #2 from Koop Mast --- Thanks Justin Hibbits for the feedback. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat May 19 00:57:54 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B274DEE272B for ; Sat, 19 May 2018 00:57:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 49C6C725AD for ; Sat, 19 May 2018 00:57:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 03FCCEE2729; Sat, 19 May 2018 00:57:54 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D587EEE2728 for ; Sat, 19 May 2018 00:57:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7175D725AC for ; Sat, 19 May 2018 00:57:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 98EBF245FF for ; Sat, 19 May 2018 00:57:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4J0vq0C018256 for ; Sat, 19 May 2018 00:57:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4J0vqrj018253 for ppc@FreeBSD.org; Sat, 19 May 2018 00:57:52 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 214598] head -r333594: dump from ddb unsuccessful on a powerpc64 PowerMac G5. . . Date: Sat, 19 May 2018 00:57:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 00:57:54 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214598 Mark Millard changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|head -r308247: dump from |head -r333594: dump from |ddb unsuccessful on a |ddb unsuccessful on a |powerpc64 PowerMac G5. . . |powerpc64 PowerMac G5. . . --- Comment #2 from Mark Millard --- A more modern version of head ( -r333594 ) gets the following backtrace (again hand typed from a screen shot and with leading zeros frequently omitted and the like): db> dump Dumping 11 MB (3 chunks) chunk 0: 12MB (2868 pages) ... ok chunk 1: 1MB (24 pages) ... ok chunk 2: 1MB (2 pages)KDB: reentering KDB: stack backtrace: 0xe7c930: at kdb_backtrace+0x68 0xe7ca40: at kdb_reenter+0x54 0xe7cab0: at trap+0x8f0 0xe7cbd0: at powerpc_interrupt+0x74 0xe7cc20: kernel DSI read trap @0xe000000000022ff8 by memcpy+0x148: srr1=3D0x9000000000001032 r1 =3D 0xe7ced0 cr =3D 0x40002224 xer =3D 0x20000000 ctr =3D 0x200 r2 =3D 0x11e4000 sr =3D 0x40000000 0xe7ced0: at 0xc00000006ab17fc 0xe7cf00: at bus_dmamap_load_ccb+0xb0 0xe7cf30: at bus_dmamap_load_sync+0xb0 0xe7cf80: at ata_dmaload+0x200 0xe7d010: at ata_begin_transaction+0x250 0xe7d0a0: at ataaction+0x4b8 0xe7d140: at xpt_run_devq+0x334 0xe7d210: at xpt_action_default+0x63c 0xe7d2c0: at ata_action+0x58 0xe7d300: at xpt_action+0x40 0xe7d330: at cam_periph_runccb+0xbc 0xe7d3c0: at adadump+0x27c 0xe7d580: at dump_write+0x110 0xe7d5f0: at _dump_append+0x34 0xe7d630: at dump_append+0x9c 0xe7d670: at dumpsys_cb_dumpdata+0x144 0xe7d750: at dumpsys_foreach_chunk+0x68 0xe7d7a0: at dumpsys_generic+0x2a0 0xe7d880: at doadump+0xc8 0xe7d8c0: at db_dump+0x38 0xe7d930: at db_command+0x13c 0xe7da60: at db_command_loop+0x9c 0xe7dae0: at db_trap+0xfc 0xe7dc50: at kdb_trap+0x1a8 0xe7dd10: at db_trap_glue+0x70 0xe7dd40: at dbtrap+0x134 0x0a3390: at kdb_enter+0x60 0x0a3410: at kdb_break+0x3c 0x0a3440: at scgetc+0x978 0x0a34f0: at sckdbevent+0x1ec 0x0a3580: at kdbmux_intr+0x8c 0x0a35c0: at kdbmux_kdb_intr+0x4c 0x0a35f0: at taskqueue_run_locked+0xb0 0x0a3690: at taskqueue_run+0x9c 0x0a36e0: at taskqueue_swi_giant_run+0x28 0x0a3710: at intr_event_execute_handlers+0x224 0x0a3790: at ithread_loop+0x138 0x0a3860: at fork_exit+0xb0 0x0a38f0: at fork_trampoline+0x18 0x0a3920: at -0x4 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Sat May 19 01:07:12 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07975EE29BA for ; Sat, 19 May 2018 01:07:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE57729B9 for ; Sat, 19 May 2018 01:07:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4EA83EE29B5; Sat, 19 May 2018 01:07:11 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BDC2EE29B4 for ; Sat, 19 May 2018 01:07:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC796729B7 for ; Sat, 19 May 2018 01:07:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id F2E8A2476F for ; Sat, 19 May 2018 01:07:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w4J179Gm057052 for ; Sat, 19 May 2018 01:07:09 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4J179BD057051 for ppc@FreeBSD.org; Sat, 19 May 2018 01:07:09 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 214598] head -r333594: dump from ddb unsuccessful on a powerpc64 PowerMac G5. . . Date: Sat, 19 May 2018 01:07:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: marklmi26-fbsd@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 01:07:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214598 --- Comment #3 from Mark Millard --- (In reply to Mark Millard from comment #2) Looks like I missed a 0 in: 0xe7ced0: at 0xc00000006ab17fc it should be: 0xe7ced0: at 0xc000000006ab17fc I've no clue why this address has no symbol. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Sat May 19 01:14:25 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3A565EE3506 for ; Sat, 19 May 2018 01:14:25 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic311-23.consmr.mail.ne1.yahoo.com (sonic311-23.consmr.mail.ne1.yahoo.com [66.163.188.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BB9B9730E2 for ; Sat, 19 May 2018 01:14:24 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: EwX6AUIVM1lUPOUXdR2CMcSo3rD78JVZu8CXtjGghZMOU5L4PB8VWRYEfIjtFiC SUK2qYU4m8MEAsoTOpna1L8CimXeb7p67RG_ZliOUy1ITLvI7edhRv_Vba7KeXhgf5R1JbnrUy2m pe4JoNAjyG.i6m.YV71dTVBtc0KZbx60Bjn2BrQdz2aG5ci5ZLVlC6s051N1fRW6cV57Zw3hwFU. LxqepViORRhYZ8rUZDd54XINyQkpMtYkIW_YZyZMlMgMmM33ZehvNO0gFvPU3pk5OiIcW9PLfl2v x5UDcN3EB1jzjZ2VhXWgHsTNIJhYVs56CdVXhUaqqpV00OLU_tHgyu5jszOFo_dY6HsH8digCbSD gyZejFG8OQ14QHKUhRSzCFnLbQ7pHQZUH3ablCZhwGzVxonBN2agmHfQEv3UkNVw.93JHt9NcE8Q 6wS6oyHu_HUbq.WJMRrk1xMLmgUDY1AK38skLyVKK_fK2FVzjFpFY679Idvs6mj7XBJdR3FvQ7bm RM1Ea5fOqOeB.g3vf4KDgwciq630KBnBXNprpgS1Ihjgw3PlBSYijUmI1sNbtVw1vN9Yzi0qdGpo 57H0S6u1zd_rKGQrGlasFbtH6rxGJwcpz1ppOZVi7RzLwtqJTqU1frZI0VgJlaBNFMXftx5sFE.. dk3KBnb2z Received: from sonic.gate.mail.ne1.yahoo.com by sonic311.consmr.mail.ne1.yahoo.com with HTTP; Sat, 19 May 2018 01:14:18 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp409.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 4b44c99488cf204d5d8b53f8e16ac17c; Sat, 19 May 2018 01:14:13 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: enabling kernel dump options in GENERIC From: Mark Millard In-Reply-To: <20180518151120.GE5515@raichu> Date: Fri, 18 May 2018 18:14:12 -0700 Cc: freebsd-arch@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <7F24144E-62CC-480F-A605-D06D2A4C7142@yahoo.com> References: <20180518061739.GC5515@raichu> <20180518151120.GE5515@raichu> To: Mark Johnston X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 01:14:25 -0000 On 2018-May-18, at 8:11 AM, Mark Johnston wrote: > On Fri, May 18, 2018 at 06:14:50AM -0700, Mark Millard wrote: >> On 2018-May-17, at 11:17 PM, Mark Johnston = wrote: >>=20 >>> On Thu, May 17, 2018 at 08:58:16PM -0700, Mark Millard wrote: >>>> . . . >>>> Bugzilla 214598 (from late 2016) was about >>>> dump for TARGET_ARCH=3Dpowerpc64 builds getting >>>> failures like: >>>>=20 >>>> KDB: enter: manual escape to debugger >>>> [ thread pid 12 tid 10018 ] >>>> Stopped at .kdb_enter+0x70: ori r0, r0, 0x0 >>>> db> dump >>>> Dumping 9 MB (3 chunks) >>>> chunk 0: 10MB (2510 pages) ... ok >>>> chunk 1: 1MB (24 pages) ... ok >>>> chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, = addr: c000000000022000 >>>>=20 >>>> (A 32-bit powerpc build on the same machine worked >>>> fine for dumping.) >>>>=20 >>>> I just tried it with head -r333594 and I got something >>>> similar. (Old and new mention routines with _bus_dma_map_ >>>> in the names near the trap in the call stack. I've not >>>> done a detailed comparison.) >>>=20 >>> What is the call stack? >>=20 >> I'll have to induce the failure, take a picture of >> the screen that results, and hand type in the >> material for the fairly modern backtrace (-r333594). >> I will not be able to do this until later today. >>=20 >> The bugzilla report has the old backtrace. I did not >> quote all the material from that report in the above. >> So there is something to compare against once I >> supply a modern one. >=20 > My apologies, I missed the fact that the backtrace was included in = that > PR. Since the problem still occurs and apparently manifests with a > similar backtrace, it wouldn't be useful to retest. I'm afraid I don't > have any suggestions on how to make progress here. Given that the new > options give only a small increase in the kernel size, I'm still > inclined to enable them on powerpc64 for consistency with other > architectures. Seems reasonable. May be there are other powerpc64 contexts that can test the updates. Useful or not, I've updated bugzilla 214598 with a backtrace from head -r333594 and have updated its one-line summary to reference -r333594 . Looks like I missed a 0 in: 0xe7ced0: at 0xc00000006ab17fc it should be: 0xe7ced0: at 0xc000000006ab17fc I've no clue why this address has no symbol. I showed more of the stack this time. At least now the old and new can be compared. That is better than forcing folks to rely on my earlier quick look. >> Also: in about a week I'll lose access to the PowerMacs >> for an unknown period of time (weeks? months?). >>=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Sat May 19 04:52:02 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89194EEE58E for ; Sat, 19 May 2018 04:52:02 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic306-22.consmr.mail.ne1.yahoo.com (sonic306-22.consmr.mail.ne1.yahoo.com [66.163.189.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D1E1F7DC8F for ; Sat, 19 May 2018 04:52:01 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: iQu9abAVM1m_rad.a0jGC9PXqHvtfI04vgrf.2y2p.Q3QnpkDJqvep0IHuJXTy4 zrJ8Ei9QbgTykYT.XohoKvVFNURYzlsVR7vlU4VpEf4lnsKWbVfGj1eBwos5D58Y8UzwNxhjyddr pY366TmZvpub3YK8GLfCGJyfIeOCUoUa3bEezSoy3yTHdkk8iT4XP5MB0Q0PQWruf5EeUEVtzcdM _7lM9k4f7LGOQnR2bAqo0rOoHx_DUdOPGrlRP.uWGwRtdFHBr9IRzN7BXU9dgtLwGUx2CL6Qsdog SxX_vRMDilT2pDM09114V1AELvjwUTsgLoZIncyFy3Z1jlFglDmjvlYx7d5ve.cNeJ8XPKUMjn19 EqXjCym6QU_xuhHYtEqMrw4qduLoKeCDDdMjkitCpuAGx2e87qrxq.jX224_SN_.c1zw8WeZC0zo 9c7OCna4tVNmlb8YUDq7YrQ0MUCw6Mvg0ZgLzIrjEgiQ874GZOqnacGeY6WhLQBVx_x0gExw1k72 2VA34s6H7KUxSDNVfZPL2wT5s1vShPBreXDHhQI7IjMVOih5KCwaJLUjlIoc4quO7PCSuM8bEywk XX4eZuzkkroKVwjlryLOlpNF3ZZ.NRPFkIQXgMGTqREIMODb0T1FHGE7AsVvlnbFAswZma1Tlreb FOIrY9LmVvqGoKXwq6xjsG0_fNhn7Q1rmoQivQJ6pqDDOO7U3_yfNmjsjNmGaBf5JlrSz Received: from sonic.gate.mail.ne1.yahoo.com by sonic306.consmr.mail.ne1.yahoo.com with HTTP; Sat, 19 May 2018 04:52:00 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp429.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 227013b88a182f6f30d5da6c9509a55d; Sat, 19 May 2018 04:51:55 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: svn commit: r333825 - head/sys/powerpc/ofw [broke powerpc64 build?] Message-Id: Date: Fri, 18 May 2018 21:51:54 -0700 To: jhibbits@FreeBSD.org, FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 04:52:02 -0000 This seems to have broken the powerpc64 build. https://ci.freebsd.org/job/FreeBSD-head-powerpc64-build/5382/consoleText reports: At revision 333846 . . . --- locore.o --- /usr/src/sys/powerpc/aim/trap_subr64.S: Assembler messages: /usr/src/sys/powerpc/aim/trap_subr64.S:776: Error: unsupported = relocation against SPR_HSRR0 /usr/src/sys/powerpc/aim/trap_subr64.S:778: Error: unsupported = relocation against SPR_HSRR1 *** [locore.o] Error code 1 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Sat May 19 04:56:57 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 520DBEEE8B9 for ; Sat, 19 May 2018 04:56:57 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B42747E011 for ; Sat, 19 May 2018 04:56:56 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id h197-v6so16793617lfg.11 for ; Fri, 18 May 2018 21:56:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Cn1UkQOmBxOteJFjKwQih819hlXBHPRnFm2LX7GaOAk=; b=oBDKP8k1s4F+J8S1q6RaatyvaJEgKr8cVUW7zskqbm0E0lHvdZxEgTDZNANPI/Gcie PYPe1Rycb7T8x9PoJU2HPcpcSHWDh/+9yLP7S6l0lh42cnk28Oc2LzL5yxfqvFcv0BP/ /MXmaILqf7AQzfjypeDhiApSdMHvHW5/mNdCwxl5PTVtqBlnMlQO85Iik2aw9CLDkCkU dz87u3Ly1CPtu00g60jz/2svnhVGoujT345CNXFaKVQHsNXXLgOIb7DxV886dFO2OVKc 0nO59VWBT9mNTzN7lXtNgSm1NOCHrbLa6+qW/Hms/t4WvW1SmV87OJiPBh/2p41G3Clz fWxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Cn1UkQOmBxOteJFjKwQih819hlXBHPRnFm2LX7GaOAk=; b=O9W0LDCg+//TNkHiNTOSNAS2osPqw3X3zKaIse2VwqEXIAekHTiOkM4pPPA/MDp3oy LdFbgeLFM4UwVTDBSS0LRHmGZvJYW1IjwrmYah8pNPf3nKBic8RBUhgPl+Q64nmC6Zps HezmmO9/lwNd6NcPEHCLy4R2/BzmFGA2Zj2KI/4cPTQmBjbcOGuAhCdBEw24dskLhvBP 8kR6BVeoLlJylV+KoDOSa1qivsIK1ixIEj6caWKRxJYjbwAvyF2Qr0OYrkUpV12ExV9j gs8d/DJN9ConBovpp1VDz+zpdrsJHtnsi6FGyBM53IULMUl9EC2q28PUh31lh+3ilCQN 9KTA== X-Gm-Message-State: ALKqPwfzweTm0n9qdwICUAG7mK3uocbDKk2X27Bs1Tc0XPJMxKm7AgfZ xS4vtr+KEJUOHskDawQQDSPNKi7APCiybvb9WM8= X-Google-Smtp-Source: AB8JxZo4vsOuhxjTcyoVpZ9gsWUmx4r1XO1Gs5o1veJvwZ0CT4roarNunJS4MmlLFaeu2hz6lqGARxx3ztsgFZoyiyY= X-Received: by 2002:a2e:1d53:: with SMTP id d80-v6mr7502661ljd.104.1526705815225; Fri, 18 May 2018 21:56:55 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 2002:a2e:3a13:0:0:0:0:0 with HTTP; Fri, 18 May 2018 21:56:54 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Fri, 18 May 2018 23:56:54 -0500 X-Google-Sender-Auth: oT6_Y3AikH_Ecrco84qtvNjWCOs Message-ID: Subject: Re: svn commit: r333825 - head/sys/powerpc/ofw [broke powerpc64 build?] To: Mark Millard Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 04:56:57 -0000 On Fri, May 18, 2018 at 11:51 PM, Mark Millard wrote: > This seems to have broken the powerpc64 build. > > https://ci.freebsd.org/job/FreeBSD-head-powerpc64-build/5382/consoleText > > reports: > > At revision 333846 > . . . > --- locore.o --- > /usr/src/sys/powerpc/aim/trap_subr64.S: Assembler messages: > /usr/src/sys/powerpc/aim/trap_subr64.S:776: Error: unsupported relocation against SPR_HSRR0 > /usr/src/sys/powerpc/aim/trap_subr64.S:778: Error: unsupported relocation against SPR_HSRR1 > *** [locore.o] Error code 1 > > > === > Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > Oops, sorry. Fixed in r333851. - Justin From owner-freebsd-ppc@freebsd.org Sat May 19 04:57:50 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48F85EEE91E for ; Sat, 19 May 2018 04:57:50 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic312-23.consmr.mail.ne1.yahoo.com (sonic312-23.consmr.mail.ne1.yahoo.com [66.163.191.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BFE5A7E052 for ; Sat, 19 May 2018 04:57:49 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: 2qtLbUQVM1lgA.eT2Dm_FjPuLvcHrUsACCPjcMeiMre1bjZrPHcj1QoaOp_keXD .D4jxIcF6PGa0yzpkv0WQoDmPXfh2XHuaKUsOslQ0f480ScDo_s9q6Aff9afjpocN7D7o5tQktXP x8SPrMiFfqyyOFpfGlGXx5MuJxNu9DfYxEBhvNP4n4ZeMPthozybo3Ak_7sFNf5LluccaQNGjMXq 8knCHYv0.kFAtGed3MciGtj.sZ1L782NPXLFOsAVm6dwNkhpkzvws7DqYrYYM.k4TdxGVTVW1U7_ K1QjRQsI8mcxAEXJuUajc2sKxaXwE4iSMs5zUpfVtHoIJt3Jk7oFCalrVwDPVMf4po6OzVdVrbJG t1_ZW8c22sQkY_ue2CbudPjm3dnKN9QP4u10dOFrwvD_SzHWwqZ4QFM3nbsSVDjBRCgpcGljTTSs 6dIR.HKpUPU3ygUDpQ0a5G7L8fdOgitBuqOmj4vO8I3SH424P1.G7vKU0E9LHf5vUzFFMEvZOl4I 9L3lT9Jt_OuUTDqmhED7G9BvsWksj4Al3RjmEFo03j9xR97gerHZcRr1QSBpWIqbla8489Tdw5.6 q1DzJUAwxwv2XsF8YSLm4GnuQ_U_K3OK6GnAeoJM5CbHD.S5XUzh1OObyqGO7WFu2yEB3QZD8A4_ Vz_pdxLKmsFvb2K180C.lzOFaYErHCRnRyefJU8MXptXKNmUJO5sJFWEXym34cgRIBZgX Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.ne1.yahoo.com with HTTP; Sat, 19 May 2018 04:57:43 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp412.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID de35255f13830c61d296de598ae194df; Sat, 19 May 2018 04:57:42 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: svn commit: r333825 - head/sys/powerpc/ofw [broke powerpc64 build?] [Should have been r333846 commit] Date: Fri, 18 May 2018 21:57:41 -0700 References: To: jhibbits@FreeBSD.org, FreeBSD PowerPC ML In-Reply-To: Message-Id: <960C439A-F84F-4CEB-85DD-B6AA256E9C35@yahoo.com> X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2018 04:57:50 -0000 "Re: svn commit: r333825" is the wrong message: I should have replied to r333846's message. On 2018-May-18, at 9:51 PM, Mark Millard = wrote: This seems to have broken the powerpc64 build. https://ci.freebsd.org/job/FreeBSD-head-powerpc64-build/5382/consoleText reports: At revision 333846 . . . --- locore.o --- /usr/src/sys/powerpc/aim/trap_subr64.S: Assembler messages: /usr/src/sys/powerpc/aim/trap_subr64.S:776: Error: unsupported = relocation against SPR_HSRR0 /usr/src/sys/powerpc/aim/trap_subr64.S:778: Error: unsupported = relocation against SPR_HSRR1 *** [locore.o] Error code 1 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)