From owner-freebsd-ppc@freebsd.org Sun Mar 11 06:51:35 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 C1159F3229A for ; Sun, 11 Mar 2018 06:51:35 +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 641587C056 for ; Sun, 11 Mar 2018 06:51:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 5D0D6116E8; Sun, 11 Mar 2018 06:51:35 +0000 (UTC) Delivered-To: freebsd-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 580F4116E7 for ; Sun, 11 Mar 2018 06:51:35 +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 2C33F7C054 for ; Sun, 11 Mar 2018 06:51:35 +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 700A624F5E for ; Sun, 11 Mar 2018 06:51:34 +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 w2B6pYg9037417 for ; Sun, 11 Mar 2018 06:51:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2B6pYnO037416 for freebsd-powerpc@FreeBSD.org; Sun, 11 Mar 2018 06:51:34 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: freebsd-powerpc@FreeBSD.org Subject: [Bug 221641] www/firefox build fails with segmentation fault when running dtrace on powerpc Date: Sun, 11 Mar 2018 06:51:34 +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: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gecko@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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.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, 11 Mar 2018 06:51:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221641 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|www/firefox build fails |www/firefox build fails |with segmentation fault |with segmentation fault |when running dtrace |when running dtrace on | |powerpc --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Mon Mar 12 20:27:34 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 3AB47F41A59 for ; Mon, 12 Mar 2018 20:27:34 +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 CBDE16F448 for ; Mon, 12 Mar 2018 20:27:33 +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 EC88518F4D for ; Mon, 12 Mar 2018 20:27:32 +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 w2CKRWMm067403 for ; Mon, 12 Mar 2018 20:27:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2CKRW4m067401 for freebsd-ppc@FreeBSD.org; Mon, 12 Mar 2018 20:27:32 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: freebsd-ppc@FreeBSD.org Subject: [Bug 200020] [patch] editors/libreoffice: enable build on powerpc64 Date: Mon, 12 Mar 2018 20:27:32 +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: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jhibbits@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: office@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? 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.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, 12 Mar 2018 20:27:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200020 --- Comment #21 from Justin Hibbits --- It looks like it can continue if oosplash is linked with g++6, not gcc6, so= a minor patch to unxgcc.mk could just drop the check for C++ objects, and alw= ays link with gb_CXX, never with gb_CC. A bit inefficient, but it looks like it should work. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Tue Mar 13 03:29:00 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 7BF2EB7B607 for ; Tue, 13 Mar 2018 03:29:00 +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 1A0D98545B for ; Tue, 13 Mar 2018 03:29:00 +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 461311C942 for ; Tue, 13 Mar 2018 03:28:59 +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 w2D3SxQc036640 for ; Tue, 13 Mar 2018 03:28:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2D3Sx0i036639 for freebsd-ppc@FreeBSD.org; Tue, 13 Mar 2018 03:28:59 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: freebsd-ppc@FreeBSD.org Subject: [Bug 200020] [patch] editors/libreoffice: enable build on powerpc64 Date: Tue, 13 Mar 2018 03:28:58 +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: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: lwhsu@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: office@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2018 03:29:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200020 Li-Wen Hsu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lwhsu@FreeBSD.org --- Comment #22 from Li-Wen Hsu --- FYI, I'm going to update editors/libreoffice to 6.0.2 in bug 224288 and you= may want to update the patch against to it. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Wed Mar 14 02:29:37 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 B99A2F4197F for ; Wed, 14 Mar 2018 02:29:37 +0000 (UTC) (envelope-from memereferencehere@gmail.com) Received: from mail-yw0-x232.google.com (mail-yw0-x232.google.com [IPv6:2607:f8b0:4002:c05::232]) (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 420DC8312C for ; Wed, 14 Mar 2018 02:29:37 +0000 (UTC) (envelope-from memereferencehere@gmail.com) Received: by mail-yw0-x232.google.com with SMTP id l24so1177894ywk.6 for ; Tue, 13 Mar 2018 19:29:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:mime-version:subject:message-id:date:to; bh=1i45ZYawHge1BPovGd+oInmXu7bsciJ7HRNVd91JX9o=; b=Fsr8IS7ZQNhNLa3KaOzLsjb5uiIDj5ITzKXWxrjwVmKzzW7SAHQ8k1PT67rZ2izAi0 yY2Z4hkskvQQiy3wipoDxBt/W4IKfLmmAsoUqsCpUO5Q1PjaMcit9oEzTYHsxmfhIATJ N/DoQ2h6UUjeotqeDXSHpQghyPOoiULUc4iDSSEVoCtuivK2LyirW3O7sOutgctc/ogv SpqO2w7OAs2+XTE9MnEshPDSqNUtRSiZD1q7ZNXwQj1f0BElX1x3SHvEIngoGsDUoqjS jAYovja9DoQi4NRME2aFX8Veu5m2nJe3kO3KVUHiw3ClD/CG4M+pHiIG5JzaXjFDLSNn fuyg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:to; bh=1i45ZYawHge1BPovGd+oInmXu7bsciJ7HRNVd91JX9o=; b=NVsNzUn711RsWNKTA18zoeE4eQ+JeOyoVaxIfpYCVnT/BthTLh3tRNpez7xM8jno1N bWY3QH4ocSkItkLxtn599Rd82CxgOD/N42C5yNKaVcFPLV5bt2ZNo6Mc6Aq484dxJHuT ugrMcBRqh+7LGzJLGSyCPyUD1vlmlAIwiUVbEm7R/npF3HWocgskbqcFmKHCzcqgtKfN 5RzhYIjEU7tNZE/IXkl/Kk5RhmRoNB4vVMhfizOD67SjnlFap+ST9bedLuphJj/9IR6+ k5aRAA+k2U6QhSrRxKkrIXiNLSfOWi+YInIK8gzPt4AnjfWOTfgIu8enYOV5BUObQ/fb EbVg== X-Gm-Message-State: AElRT7FrUF27xVwPoDCSWGwPOHb0VRICXpu68RwvBa5OkFuwVDZr2Tin 2/ELOKpKpOaD0qw5pozRd9lkKzpT X-Google-Smtp-Source: AG47ELv/AIBWy79gidUNc44/HJY7r9XDP+/2i5Pc+PmstUyqN5asTxO9190zVojtFEAfOXRcKbuWdw== X-Received: by 2002:a25:7704:: with SMTP id s4-v6mr2098000ybc.53.1520994576289; Tue, 13 Mar 2018 19:29:36 -0700 (PDT) Received: from ?IPv6:2601:cb:100:607:15f7:9075:2afd:7b45? ([2601:cb:100:607:15f7:9075:2afd:7b45]) by smtp.gmail.com with ESMTPSA id o62sm641162ywb.17.2018.03.13.19.29.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Mar 2018 19:29:34 -0700 (PDT) From: Evan Sabin Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Porting Xserve G5 Lights Drivers from OpenBSD to FreeBSD Message-Id: <3AC94C98-8A92-4D0C-8787-0873B5BE223C@gmail.com> Date: Tue, 13 Mar 2018 22:29:33 -0400 To: freebsd-ppc@freebsd.org X-Mailer: Apple Mail (2.3445.5.20) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Wed, 14 Mar 2018 02:29:38 -0000 I feel as though it would be nice to have a more complete set of drivers = on my Xserve G5 running the latest FreeBSD =E2=80=94 particularly, and = really only, to support the processor indicator lights and the system = identifier button and its corresponding rear light. As such, I did some = searching and discovered the most feature-complete drivers for these = hardware components could be found in the OpenBSD source code. = (https://github.com/openbsd/src/blob/master/sys/arch/macppc/dev/xlights.c = = ) = (https://github.com/openbsd/src/blob/master/sys/arch/macppc/dev/sysbutton.= c = ) I suppose my question is =E2=80=94 How do I get from point A to = point B, and how do I begin to port these drivers from OpenBSD to = FreeBSD? What are the core differences in driver development on these = two systems, particularity in regards to the PPC64 architecture?= From owner-freebsd-ppc@freebsd.org Wed Mar 14 04:28: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 45DC2F4F90B for ; Wed, 14 Mar 2018 04:28:25 +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 CC0BF697E7 for ; Wed, 14 Mar 2018 04:28:24 +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 w2E4HY9k003541 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Tue, 13 Mar 2018 21:17:35 -0700 Subject: Re: Porting Xserve G5 Lights Drivers from OpenBSD to FreeBSD To: freebsd-ppc@freebsd.org References: <3AC94C98-8A92-4D0C-8787-0873B5BE223C@gmail.com> From: Nathan Whitehorn Message-ID: <96fecfee-af1e-9550-3429-952d808423ca@freebsd.org> Date: Tue, 13 Mar 2018 21:17:33 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <3AC94C98-8A92-4D0C-8787-0873B5BE223C@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVbkJV8QxpAai7Qp6ky+gyGM3362Ogvc7pIaTTcFXLeLn46G817ibsPhDT9TW/puvIq+Nnk0yQj6/CrXNHmO6yjaY2OThROFEro= X-Sonic-ID: C;6AcNnz4n6BGslFDNXaHR5A== M;YNxbnz4n6BGslFDNXaHR5A== 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: Wed, 14 Mar 2018 04:28:25 -0000 It depends a very great deal on the driver. These don't look very hard to port, but there isn't a general porting guide, unfortunately. -Nathan On 03/13/18 19:29, Evan Sabin wrote: > I feel as though it would be nice to have a more complete set of drivers on my Xserve G5 running the latest FreeBSD — particularly, and really only, to support the processor indicator lights and the system identifier button and its corresponding rear light. As such, I did some searching and discovered the most feature-complete drivers for these hardware components could be found in the OpenBSD source code. (https://github.com/openbsd/src/blob/master/sys/arch/macppc/dev/xlights.c ) (https://github.com/openbsd/src/blob/master/sys/arch/macppc/dev/sysbutton.c ) I suppose my question is — How do I get from point A to point B, and how do I begin to port these drivers from OpenBSD to FreeBSD? What are the core differences in driver development on these two systems, particularity in regards to the PPC64 architecture? > _______________________________________________ > 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 Wed Mar 14 15:08:10 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 76971F57E7F for ; Wed, 14 Mar 2018 15:08:10 +0000 (UTC) (envelope-from memereferencehere@gmail.com) Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 0B26685454 for ; Wed, 14 Mar 2018 15:08:10 +0000 (UTC) (envelope-from memereferencehere@gmail.com) Received: by mail-yw0-x234.google.com with SMTP id l200so2361162ywb.0 for ; Wed, 14 Mar 2018 08:08:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=/Zu7ZqlntF8fTQoMCW92gT0ypqB2+/O0IlH1UM9ugks=; b=IP5lVTfyKqz2HeB2+coZ1HRv67z9xrOKe2o3HlBHq8gT7QKdONgivTpNplK4cQ9mJ7 eQqqnE2EAslTsgfMMyY30hReLtlId7TWSk2xqkaynGFKXY2lKb6KOo9plOPRNuFPFYQG Tc5S05mMW15IHHto/RsPtWgZTPkfNzJDCkrCZ7uoqEQdZBKVZ6QIO9PGtzuyt596b401 RNFbiZGXuSGSpGlX8DI854sCSXLVnUssAdysJ3JB6vSVHLhpwxVazAfKHhXFh/R3Dc7i FOO2gxkyHimyBqxdUf2xZjqS5kA20D632YGgIhmz/sOWVTUe8a8beX89FzbhxRsCOpfI mfsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=/Zu7ZqlntF8fTQoMCW92gT0ypqB2+/O0IlH1UM9ugks=; b=muDMW+adsopPEa71rw+87wquKnZDh/yo3lF/KrTin5dh4ew13RR5jyUnc2Fbv65zA0 OqScyPBIwskBNkHiYpmLrLLXnMkL6hkNimpwDdpB8nP/+QyTNNAGUbB5MgoGvGS08Pz5 zhbdDD/Q0oc89sErm//g8JRKR6quwItRbz7WGG8iQFn6janD3j4VROodwuAJuKVwUF+h BYpGLOtkSSVHDfXqKmtcvjero1USbVoE7XFA9dmFRLGmeigp1tMrx09YzNJzau1xrws9 ORag23O+7vpDhuOo9bIJQpgAfAPhxEDyKstWIJ6rJC5pMH545l94w7TricwIa46zgIDf zoRQ== X-Gm-Message-State: AElRT7E62O9JrfvAO0LUAobhGueLkeESoxjaP3Ws74FMOxkZrTy01JGC t1aGSZxRPSvDZXcNFUPatsYZ2YKC X-Google-Smtp-Source: AG47ELv1iu8rLY16O2fG8GvYS79rhyXFnyzvM2MiSXQXqGGOd4f+dac1QfwL1nZ6RnPoVDhLGsEfuw== X-Received: by 10.129.72.20 with SMTP id v20mr3473324ywa.53.1521040089009; Wed, 14 Mar 2018 08:08:09 -0700 (PDT) Received: from ?IPv6:2601:cb:100:607:c41e:fbec:7080:8bae? ([2601:cb:100:607:c41e:fbec:7080:8bae]) by smtp.gmail.com with ESMTPSA id q11sm1000085ywc.106.2018.03.14.08.08.07 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Mar 2018 08:08:07 -0700 (PDT) From: Evan Sabin Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: Porting Xserve G5 Lights Drivers from OpenBSD to FreeBSD Date: Wed, 14 Mar 2018 11:08:07 -0400 References: <3AC94C98-8A92-4D0C-8787-0873B5BE223C@gmail.com> <96fecfee-af1e-9550-3429-952d808423ca@freebsd.org> To: freebsd-ppc@freebsd.org In-Reply-To: <96fecfee-af1e-9550-3429-952d808423ca@freebsd.org> Message-Id: X-Mailer: Apple Mail (2.3445.5.20) 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: Wed, 14 Mar 2018 15:08:10 -0000 I suppose I=E2=80=99ll just play around until I get things to work. = That=E2=80=99s how you learn, right? Thanks! > On Mar 14, 2018, at 12:17 AM, Nathan Whitehorn = wrote: >=20 > It depends a very great deal on the driver. These don't look very hard = to port, but there isn't a general porting guide, unfortunately. > -Nathan >=20 > On 03/13/18 19:29, Evan Sabin wrote: >> I feel as though it would be nice to have a more complete set of = drivers on my Xserve G5 running the latest FreeBSD =E2=80=94 = particularly, and really only, to support the processor indicator lights = and the system identifier button and its corresponding rear light. As = such, I did some searching and discovered the most feature-complete = drivers for these hardware components could be found in the OpenBSD = source code. = (https://github.com/openbsd/src/blob/master/sys/arch/macppc/dev/xlights.c = = ) = (https://github.com/openbsd/src/blob/master/sys/arch/macppc/dev/sysbutton.= c = ) I suppose my question is =E2=80=94 How do I get from point A to = point B, and how do I begin to port these drivers from OpenBSD to = FreeBSD? What are the core differences in driver development on these = two systems, particularity in regards to the PPC64 architecture? >> _______________________________________________ >> 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" >>=20 >=20 > _______________________________________________ > 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 Wed Mar 14 15:24:17 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 63D05F58CF2 for ; Wed, 14 Mar 2018 15:24:17 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (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 BC27686057 for ; Wed, 14 Mar 2018 15:24:16 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id y19-v6so5429034lfd.4 for ; Wed, 14 Mar 2018 08:24:16 -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:content-transfer-encoding; bh=PjWR3iCY3ogvJWu+sHTGGOqGEJ49YRqwj5v6MZR8vz4=; b=j1BCboiXOamV7qg1vR0LcIvWAJpy19qBQe9DESm2FEYxZW62GSvmJflDHePbNifEkB xK45v5t8/hx1526x6Mnbg8EtYfgkCYR+zAkPnUB8w3JDPNKGXsv53cDOX/LuqJmxiNyh +X6ZKetACAvIvYeoM4I4IeNnIJmz9RiF84ZtUzv1vmKicruaXP9/JlJ35qgAy6wHW/Yy wrVYJAgKpds1dJX+uaqRa7QAjGzZ3MKP/yeQg1f0Ls6Mjms4eoop4yM7/Te3eRE+hZHP iN8Qb/c3YLiGfWnd6ZAEl2Q9PEqUgVNqhQ0fgYYdhyoPiaEYz74qre0w7ubBwSXjWquQ Tr+Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alumni-cwru-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=PjWR3iCY3ogvJWu+sHTGGOqGEJ49YRqwj5v6MZR8vz4=; b=vAQrujstgebYUidANdnNLiw7AIyoNbQbRQegulWW+gDJEmvb3uVzvJ5d3T4fcLEalK BwbJ8tzLrI0ETtFWNBo3lkn5zQ6lhG/bQvg8aCeagTz3U2KUiFenTuZnWZsvUknIAW61 ZS7uAmy+mt/LXwPt6b2AJlitfpqGlN7hN12PezLF7XMlxPMlcxM0loZPqAQltygE8SHu vKrU4HWh5D5W+rptThrl7adZ789VeVBDuOHAk/43Q+XpIf+zl1C98k77rzm/TMAUHtwQ 8uRAS35CMqTxEV7YDgbtLbtVWCJDjXY/Xuf3YdHzTd9u5LS/eYJhdMfeZDVmNH7sWvUi j+SA== 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:content-transfer-encoding; bh=PjWR3iCY3ogvJWu+sHTGGOqGEJ49YRqwj5v6MZR8vz4=; b=m9H//RpinVm2sLLrnJ/fTzoTvl4Prm7oDeuoAc3b8tQNaKIXhXMdP4f/e0f1xAJ98V 16OTmspoDHXGkTRz7ppIX3B1HyBEGNvZ/eLNIPgVZSIZU2WwUw8ngV6AJkHeYs2NK3Gl 2HCDavdccj/QecOavy3v+2nmJzIc3unUr6CJ8hMhoIZzEC9hnFtkWj7x8sYMQ0bNGtlJ axRRW8TPh2LfnyvFbB1Om6O/wpzS4FlGZt9EVdpfIjzR7+d7yWVlHlnD/PNbSQafy0od 9qGj3jhIQMOqWF06JOw4VvEQh916kAM4KuaajsGO2sJhRrnW+IaJTB5wkVYj3/XgzJsn 7buw== X-Gm-Message-State: AElRT7HI1GshUq2fPO236NmaIwIlQ7FCleFhoiUKqrT0gSOofBnSkhVG OiVKgAfcDnFadKeSSi4wqTLwPKFOxRM2iROYJnM= X-Google-Smtp-Source: AG47ELtSPCduCqkA/d1b9TKrK1ELGzfOTBGH5qOQn5YyXedY8IZ9qmOQJ614uTarzTERlfkQGj2vI5d3pGnWWm/tdN4= X-Received: by 2002:a19:d0c4:: with SMTP id h187-v6mr3576661lfg.107.1521041055186; Wed, 14 Mar 2018 08:24:15 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.46.85.26 with HTTP; Wed, 14 Mar 2018 08:24:14 -0700 (PDT) In-Reply-To: References: <3AC94C98-8A92-4D0C-8787-0873B5BE223C@gmail.com> <96fecfee-af1e-9550-3429-952d808423ca@freebsd.org> From: Justin Hibbits Date: Wed, 14 Mar 2018 10:24:14 -0500 X-Google-Sender-Auth: _3rdORNLz-2vuqzSaPG_DlETEcw Message-ID: Subject: Re: Porting Xserve G5 Lights Drivers from OpenBSD to FreeBSD To: Evan Sabin Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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: Wed, 14 Mar 2018 15:24:17 -0000 I ported the abtn driver (sys/dev/adb/adb_buttons.c) from NetBSD. That might be of some help to you. It's a trivial driver, so doesn't contain everything needed, but should be a useful start. - Justin On Wed, Mar 14, 2018 at 10:08 AM, Evan Sabin wrote: > I suppose I=E2=80=99ll just play around until I get things to work. That= =E2=80=99s how you learn, right? Thanks! > >> On Mar 14, 2018, at 12:17 AM, Nathan Whitehorn = wrote: >> >> It depends a very great deal on the driver. These don't look very hard t= o port, but there isn't a general porting guide, unfortunately. >> -Nathan >> >> On 03/13/18 19:29, Evan Sabin wrote: >>> I feel as though it would be nice to have a more complete set of driver= s on my Xserve G5 running the latest FreeBSD =E2=80=94 particularly, and re= ally only, to support the processor indicator lights and the system identif= ier button and its corresponding rear light. As such, I did some searching = and discovered the most feature-complete drivers for these hardware compone= nts could be found in the OpenBSD source code. (https://github.com/openbsd/= src/blob/master/sys/arch/macppc/dev/xlights.c ) (https://github.com/openbsd/= src/blob/master/sys/arch/macppc/dev/sysbutton.c ) I suppose my question is= =E2=80=94 How do I get from point A to point B, and how do I begin to port= these drivers from OpenBSD to FreeBSD? What are the core differences in dr= iver development on these two systems, particularity in regards to the PPC6= 4 architecture? >>> _______________________________________________ >>> 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" >>> >> >> _______________________________________________ >> 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" > > _______________________________________________ > 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 Wed Mar 14 16:05:17 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 537DAF5AFFB for ; Wed, 14 Mar 2018 16:05:16 +0000 (UTC) (envelope-from andy.silva@snsreports.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 D627587CA9 for ; Wed, 14 Mar 2018 16:05:15 +0000 (UTC) (envelope-from andy.silva@snsreports.com) X-MSFBL: NDnSq16CJkfdJ9nSdpP2YH9V8KpgRw7qaJ2alQdc2Lc=|eyJyIjoiZnJlZWJzZC1 wcGNAZnJlZWJzZC5vcmciLCJiIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbF8 3NF85MV84NV8yMzgiLCJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCJ9 Received: from [10.137.129.35] ([10.137.129.35:23876] helo=mtl-mtsp-c02-3.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 BD/B5-20152-48349AA5; Wed, 14 Mar 2018 15:45:08 +0000 Received: from 10.137.11.93 by Caffeine (mtl-mtsp-c02-3) with SMTP id 736d4c0e-dd2c-4036-a832-499504d84d93 for freebsd-ppc@freebsd.org; Wed, 14 Mar 2018 15:45:05 +0000 (UTC) Received: from [65.49.242.4] ([65.49.242.4:21512] helo=gull-dhcp-65-49-242-4.bloombb.net) by mtl-mtsp-mta05-in1 (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 8A/A7-17020-18349AA5; Wed, 14 Mar 2018 15:45:05 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsreports.com To: freebsd-ppc@freebsd.org Subject: =?iso-8859-1?Q?Private_LTE_&_5G_Network_Ecosystem:_2018_=96_2030_?= =?iso-8859-1?Q?=96_Opportunities,_Challenges,_Strategies,_Industry_Vertic?= =?iso-8859-1?Q?als_&_Forecasts_(Report)?= X-Mailer: Smart_Send_2_0_138 Date: Wed, 14 Mar 2018 11:45:02 -0400 Message-ID: <135004384856242566323271@Ankur> X-SMTPCOM-Tracking-Number: 736d4c0e-dd2c-4036-a832-499504d84d93 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smtpserver.email; i=@smtpserver.email; q=dns/txt; s=smtpcustomer; t=1521042306; h=MIME-Version : From : Reply-To : To : Subject : Content-Type : Date : Message-ID : From : Subject : Date; bh=/FIYmtEzgpk+cYHt/L0lc1u9cpet2+q5/NF6BpmQFrg=; b=FH7ltFs7sfykdv0fj/v943eczanudtX6a18KkSNclKFlU6Zjz+zzXz2XfQdQv0846p1xOi sm664SLTZllx78R7eaQ+o20FmLInSs+X+5+4gGGCt3cWi+UBvDYv31fEhQAZasJH4BWcigj2 7q1DGgR0tJ27+H8TLXyfNWd38VAl/z0juO0olmxwm2XaTawFA8/rT3EsJfqeJqy/T2ExTLmK ZAqRJpRnYc2rKHvHGu8AbB1bgRrGMiHJk6wcGB+BiveTEHJFIhfklkAZzjo8AFhiSkSS+pWE K1ClDA4JtnMiw9BxTdx03DGBjKhoAKrRZi5fkDzq/onszwA+WRtQ/5qw== 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.25 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: Wed, 14 Mar 2018 16:05:17 -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 Mar 16 14:29:24 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 9E230F53122 for ; Fri, 16 Mar 2018 14:29:24 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 42C1980E8B for ; Fri, 16 Mar 2018 14:29:24 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from lrrr.mouf.net (cpe-24-163-43-246.nc.res.rr.com [24.163.43.246]) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id w2GETF33068989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Fri, 16 Mar 2018 14:29:21 GMT (envelope-from swills@FreeBSD.org) To: freebsd-ppc@freebsd.org From: Steve Wills Subject: fatal kernel trap Message-ID: Date: Fri, 16 Mar 2018 10:29:10 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 16 Mar 2018 14:29:21 +0000 (UTC) X-Spam-Status: No, score=1.3 required=4.5 tests=RCVD_IN_RP_RNBL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net X-Virus-Status: Clean 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: Fri, 16 Mar 2018 14:29:24 -0000 My PowerMac G5 runs r328835 fine, but upgrading to r330240 results in: fatal kernel trap: exception = 0x300 (data storage interrupt) virtual address = 0xc186bff8 dsisr = 0x40000000 srr0 = 0x8ef510 (0x8ef510) srr1 = 0x9000000000009032 lr = 0x7be3e4 (0x7be3e4) curthread = 0x11b26560 pid = 38, comm = kldload [ thread pid 38 tid 100087 ] Stopped at strchr+0x70: lbzu r10, 0x1(r4) db> Note this was transcribed by hand and may have typos. Also note my kernel was compiled with gcc 6.3.0, although the previous kernel was as well and it works fine. Any suggestions would be appreciated. Thanks, Steve From owner-freebsd-ppc@freebsd.org Fri Mar 16 14:43:17 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 C28EEF5421A for ; Fri, 16 Mar 2018 14:43:17 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 1F41981AEA; Fri, 16 Mar 2018 14:43:17 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x233.google.com with SMTP id y19-v6so15751842lfd.4; Fri, 16 Mar 2018 07:43:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=I6qdMN27V/779UbaV0S5b6W2O6QfccmrCZkzqvv2fI8=; b=I+ltAn9TxWXVwuboY05YUFPoPexEaDik8kAY46JemQ7dlj1Q5WOb4ccgIAIxYpiNuk 3q05XXwO7ThQupAHNGwvC8Fii3HrU2S00ZZ1Aof+flOU1rVqGbKLq63CLzTPg/mUZI1W 3P5fOj0fsm9/IAZoAzaBZgelC7ymMM3V6ZkNklmLrUt7V8mEdPO2n+yZ5RG5J+haP8S3 EXr/h6LxJZgupb85arFacZ7Xc7SeHVRj6r+tWnrviQvBOJTgl8syotyYwtbgJi18q79N s/qdPGunKMD85zopPLPWDKAlYLjFIX2t3J3dDlB/SbDSsJM6Yq+V/6EsJOe6v5xkJAck Aq7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=I6qdMN27V/779UbaV0S5b6W2O6QfccmrCZkzqvv2fI8=; b=gXoiOR4MEPRXdCcu/BdpWi4NbGVtm0RmKZF4y7gr4/VwV6irRpQunkkMo544VFbyap GQAXsVc3LAQG5ERvxW1lDxB0WvEzSFr4LR8/UJDETrj1w0qb/1hTt20ryLy2473ak8kQ j+/fxBX57YUtnTGQBu6CosIBwaX/F/nk5UAr66x6EcbXE382WHwZ7pq6dZqE+Vxb6Z5Y TshQy7A/9CDQcQQ5ANxCmJiOdXsbhrOSl7iVzaco8+7zZjD3+1AoX4C3/M1F0VGocl2M m7xrOadovjUJb+QT8SedADztjbgIxR8RQujM2WkfyovAWXPjaFwIq8VNJdpsza8XewUM W0pA== X-Gm-Message-State: AElRT7Gk02GUTzB1VO7Gp0bwFOPFxv6DjC2On8/1X0PwGFJkydAe48Sr aHSYo4PmVsQqlVtPfIccRGzAvHL/PLJdCeb0rZo= X-Google-Smtp-Source: AG47ELtg3/hZGtWkaJSg30a79T9OTkrYJAKU5w+QV+dnGDLXbO7sQDc3/y6uIATGg+TQkX8QO/RejeU939z89Frwy0U= X-Received: by 10.46.144.208 with SMTP id o16mr1517210ljg.107.1521211395423; Fri, 16 Mar 2018 07:43:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.0.153 with HTTP; Fri, 16 Mar 2018 07:43:14 -0700 (PDT) Received: by 10.46.0.153 with HTTP; Fri, 16 Mar 2018 07:43:14 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Fri, 16 Mar 2018 09:43:14 -0500 Message-ID: Subject: Re: fatal kernel trap To: Steve Wills Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Fri, 16 Mar 2018 14:43:18 -0000 On Mar 16, 2018 09:29, "Steve Wills" wrote: My PowerMac G5 runs r328835 fine, but upgrading to r330240 results in: fatal kernel trap: exception = 0x300 (data storage interrupt) virtual address = 0xc186bff8 dsisr = 0x40000000 srr0 = 0x8ef510 (0x8ef510) srr1 = 0x9000000000009032 lr = 0x7be3e4 (0x7be3e4) curthread = 0x11b26560 pid = 38, comm = kldload [ thread pid 38 tid 100087 ] Stopped at strchr+0x70: lbzu r10, 0x1(r4) db> Note this was transcribed by hand and may have typos. Also note my kernel was compiled with gcc 6.3.0, although the previous kernel was as well and it works fine. Any suggestions would be appreciated. Thanks, Steve Hi Steve, I see the same thing with any attempt to upgrade the kernel on my G5 (PowerMac11,2) from a November 6 build to more recent. I've seen it since the January timeframe, and haven't yet figured it out. - Justin From owner-freebsd-ppc@freebsd.org Fri Mar 16 14:49:31 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 6F304F54839 for ; Fri, 16 Mar 2018 14:49:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0F21881E51 for ; Fri, 16 Mar 2018 14:49:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from lrrr.mouf.net (cpe-24-163-43-246.nc.res.rr.com [24.163.43.246]) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id w2GEnNGZ069250 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Mar 2018 14:49:29 GMT (envelope-from swills@FreeBSD.org) Subject: Re: fatal kernel trap To: Justin Hibbits Cc: FreeBSD PowerPC ML References: From: Steve Wills Message-ID: Date: Fri, 16 Mar 2018 10:49:18 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Fri, 16 Mar 2018 14:49:29 +0000 (UTC) X-Spam-Status: No, score=1.3 required=4.5 tests=RCVD_IN_RP_RNBL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net X-Virus-Status: Clean 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: Fri, 16 Mar 2018 14:49:31 -0000 Hi, On 03/16/2018 10:43, Justin Hibbits wrote: > > > > Hi Steve, > > I see the same thing with any attempt to upgrade the kernel on my G5 > (PowerMac11,2) from a November 6 build to more recent. I've seen it > since the January timeframe, and haven't yet figured it out. Odd. I would bisect, but now I'm unsure. The r328835 that I'm running is from 2018/02/03 so that's after the January time-frame.... I suppose I'll bisect anyway, not sure what else to do right now. Steve From owner-freebsd-ppc@freebsd.org Fri Mar 16 15:44:38 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 019E4F5859A for ; Fri, 16 Mar 2018 15:44:38 +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 9D53985998 for ; Fri, 16 Mar 2018 15:44:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 95A827253; Fri, 16 Mar 2018 15:44:37 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (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 79BB4724F for ; Fri, 16 Mar 2018 15:44:37 +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 34C1085993 for ; Fri, 16 Mar 2018 15:44:37 +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 59E7520793 for ; Fri, 16 Mar 2018 15:44:36 +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 w2GFiaY9094287 for ; Fri, 16 Mar 2018 15:44:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2GFiaoY094286 for freebsd-powerpc@FreeBSD.org; Fri, 16 Mar 2018 15:44:36 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: freebsd-powerpc@FreeBSD.org Subject: [Bug 226659] Error Building LibreOoffice 5.3.7.2 Date: Fri, 16 Mar 2018 15:44:36 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new 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: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc Message-ID: 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2018 15:44:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226659 Bug ID: 226659 Summary: Error Building LibreOoffice 5.3.7.2 Product: Ports & Packages Version: Latest Hardware: powerpc OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: hamiltcl@verizon.net CC: freebsd-powerpc@FreeBSD.org CC: freebsd-powerpc@FreeBSD.org I'm not sure what has changed, but after many successful builds, using my previously published patches. I'm now unable to build LO 5.3.7.2. I'm getting the following error: [LNK] Executable/gengal.bin S=3D/usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2 && I=3D$S/instd= ir && W=3D$S/workdir && /usr/local/bin/ccache g++6 -Wl,-z,origin '-Wl,-rpath,$ORIGIN' -Wl,-rpath-link,$I/program -fstack-protector-strong -Wl,-rpath-link,/lib:/usr/lib -Wl,-z,combreloc -Wl,--hash-style=3Dgnu=20 -Wl,--dynamic-list-cpp-new -Wl,--dynamic-list-cpp-typeinfo -Wl,-Bsymbolic-functions -L$W/LinkTarget/StaticLibrary -L$I/sdk/lib=20 -L$I/program -L$I/program -L/usr/local/lib -L/usr/local/lib -L/usr/local= /lib -R/usr/local/lib $W/CxxObject/svx/source/gengal/gengal.o -Wl,--start-g= roup $W/LinkTarget/StaticLibrary/libvclmain.a=20 $W/LinkTarget/StaticLibrary/libglxtest.a -lpthread -lX11 -Wl,--end-group -Wl,--no-as-needed -lbasegfxlo -luno_sal -ltllo -lsvllo -lsvtlo -lcomphelper -luno_cppu -luno_cppuhelpergcc3 -lutllo -lvcllo -lsvxcorelo -o $I/program/gengal.bin S=3D/usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2 && I=3D$S/instd= ir && W=3D$S/workdir && readelf -d $I/program/libmsformslo.so | grep SONAME > $W/LinkTarget/Library/libmsformslo.so.exports.tmp; nm --dynamic --extern-o= nly --defined-only --format=3Dposix $I/program/libmsformslo.so | cut -d' ' -f1-= 2 >> $W/LinkTarget/Library/libmsformslo.so.exports.tmp && if cmp -s $W/LinkTarget/Library/libmsformslo.so.exports.tmp=20 $W/LinkTarget/Library/libmsformslo.so.exports; then rm $W/LinkTarget/Library/libmsformslo.so.exports.tmp; else mv $W/LinkTarget/Library/libmsformslo.so.exports.tmp=20 $W/LinkTarget/Library/libmsformslo.so.exports && touch -r $I/program/libmsformslo.so $W/LinkTarget/Library/libmsformslo.so.exports; = fi TEMPFILE=3D/usr/ports/editors/libreoffice/work/gbuild.XXXXXX.2sIlfTDo && mv ${TEMPFILE} /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/workdir/LinkTarget/= Library/libmsformslo.so.objectlist /usr/local/bin/ld: warning: libstdc++.so.6, needed by //usr/local/lib/libGLU.so.1, may conflict with libstdc++.so.6.0.22 /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::toNativePath(COLLADABU::Utils::SystemType) const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::getURIString() const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::getPathFileBase() const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::getPathExtension() const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADAFW::UniqueId::toAscii() const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::getPathDir() const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::getPathFile() const' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::setPath(std::string const&, std::st= ring const&, std::string const&)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::Utils::createDirectoryIfNeeded(std::stri= ng const&)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADAFW::UniqueId::UniqueId(std::string const&)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADAFW::Root::loadDocument(std::string const&)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::URI(std::string const&, bool)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= sfxlo.so: undefined reference to `orcus::json::document_tree::load(std::string const&, orcus::json_config const&)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADABU::URI::setPathDir(std::string const&)' /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/lib= avmedialo.so: undefined reference to `COLLADAFW::Texture::getTexcoord() const' collect2: error: ld returned 1 exit status gmake[3]: *** [/usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/svx/Executable_gen= gal.mk:20: /usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2/instdir/program/gen= gal.bin] Error 1 gmake[3]: Leaving directory '/usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2' gmake[2]: *** [Makefile:265: build] Error 2 gmake[2]: Leaving directory '/usr/ports/editors/libreoffice/work/libreoffice-5.3.7.2' =3D=3D=3D> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=3Dyes and rebuild before reporting the failure = to the maintainer. *** Error code 1 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Fri Mar 16 15:57:10 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 7C8FFF5966E for ; Fri, 16 Mar 2018 15:57:10 +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 255258618F for ; Fri, 16 Mar 2018 15:57:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 121CE7495; Fri, 16 Mar 2018 15:57:10 +0000 (UTC) Delivered-To: freebsd-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 F0B0C7494 for ; Fri, 16 Mar 2018 15:57:09 +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 C770F8618E for ; Fri, 16 Mar 2018 15:57:09 +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 ECBCF208F0 for ; Fri, 16 Mar 2018 15:57:08 +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 w2GFv8a4028219 for ; Fri, 16 Mar 2018 15:57:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2GFv8Aj028218 for freebsd-powerpc@FreeBSD.org; Fri, 16 Mar 2018 15:57:08 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: freebsd-powerpc@FreeBSD.org Subject: [Bug 226659] Error Building LibreOoffice 5.3.7.2 Date: Fri, 16 Mar 2018 15:57:08 +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: jhibbits@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2018 15:57:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226659 Justin Hibbits changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jhibbits@FreeBSD.org --- Comment #1 from Justin Hibbits --- Hi Curtis, I was able to build with your patch from bug 200020 plus the following patc= h to the port Makefile just the other day: Index: /usr/local/poudriere/ports/default/editors/libreoffice/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/local/poudriere/ports/default/editors/libreoffice/Makefile=20=20= =20=20 (revision 463728) +++ /usr/local/poudriere/ports/default/editors/libreoffice/Makefile=20=20= =20=20 (working copy) @@ -298,6 +295,9 @@ post-patch: ${REINPLACE_CMD} -e 's|%%LOCALBASE%%|${LOCALBASE}|' \ ${WRKSRC}/shell/source/unix/exec/shellexec.cxx +.if ${COMPILER_FEATURES:Mlibstdc++} + ${REINPLACE_CMD} -e 's/gb_CC/gb_CXX/' ${WRKSRC}/solenv/gbuild/platform/unxgcc.mk +.endif pre-configure: @${TOUCH} ${WRKSRC}/autogen.lastrun --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Fri Mar 16 19:16: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 5BC34F32278 for ; Fri, 16 Mar 2018 19:16:57 +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 DF8F26FE54 for ; Fri, 16 Mar 2018 19:16:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id D821EC02A; Fri, 16 Mar 2018 19:16:56 +0000 (UTC) Delivered-To: freebsd-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 D659CC029 for ; Fri, 16 Mar 2018 19:16:56 +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 A2AAD6FE51 for ; Fri, 16 Mar 2018 19:16:56 +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 DF940224A4 for ; Fri, 16 Mar 2018 19:16:55 +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 w2GJGtX7043269 for ; Fri, 16 Mar 2018 19:16:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2GJGtfg043268 for freebsd-powerpc@FreeBSD.org; Fri, 16 Mar 2018 19:16:55 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: freebsd-powerpc@FreeBSD.org Subject: [Bug 226659] fix building editors/libreoffice 5.3.7.2 on powerpc64 Date: Fri, 16 Mar 2018 19:16:55 +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: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: office@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to see_also 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2018 19:16:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226659 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-ports-bugs@FreeBSD. |office@FreeBSD.org |org | See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 000 | |20 Summary|Error Building LibreOoffice |fix building |5.3.7.2 |editors/libreoffice 5.3.7.2 | |on powerpc64 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Fri Mar 16 19:16: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 D0F83F3227C for ; Fri, 16 Mar 2018 19:16:57 +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 687E96FE58 for ; Fri, 16 Mar 2018 19:16:57 +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 A1E66224A8 for ; Fri, 16 Mar 2018 19:16:56 +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 w2GJGuin043332 for ; Fri, 16 Mar 2018 19:16:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2GJGuPo043330 for freebsd-ppc@FreeBSD.org; Fri, 16 Mar 2018 19:16:56 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: freebsd-ppc@FreeBSD.org Subject: [Bug 200020] [patch] editors/libreoffice: enable build on powerpc64 Date: Fri, 16 Mar 2018 19:16:55 +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: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: office@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: see_also 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Mar 2018 19:16:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200020 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 266 | |59 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Mar 17 09:41: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 F14A7F57485 for ; Sat, 17 Mar 2018 09:41:47 +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 9C06071DE4 for ; Sat, 17 Mar 2018 09:41:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id 952E71B44D; Sat, 17 Mar 2018 09:41:47 +0000 (UTC) Delivered-To: freebsd-powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (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 930D21B44C for ; Sat, 17 Mar 2018 09:41: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 65A4171DE0 for ; Sat, 17 Mar 2018 09:41: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 A57D81BE9 for ; Sat, 17 Mar 2018 09:41: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 w2H9fkh4008750 for ; Sat, 17 Mar 2018 09:41:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2H9fkok008749 for freebsd-powerpc@FreeBSD.org; Sat, 17 Mar 2018 09:41: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: freebsd-powerpc@FreeBSD.org Subject: [Bug 226659] fix building editors/libreoffice 5.3.7.2 on powerpc64 Date: Sat, 17 Mar 2018 09:41: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: lwhsu@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: office@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Mar 2018 09:41:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226659 Li-Wen Hsu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lwhsu@FreeBSD.org Status|New |Open --- Comment #2 from Li-Wen Hsu --- Hi Justin, is it possible for you to check if this also works for 6.0.2? --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Sat Mar 17 15:39:29 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 7EAB3F52A36 for ; Sat, 17 Mar 2018 15:39:29 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 204BD81203; Sat, 17 Mar 2018 15:39:29 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from lrrr.mouf.net (cpe-24-163-43-246.nc.res.rr.com [24.163.43.246]) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id w2HFdHsH002286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 17 Mar 2018 15:39:23 GMT (envelope-from swills@FreeBSD.org) Subject: Re: fatal kernel trap To: Justin Hibbits Cc: FreeBSD PowerPC ML , jeff@FreeBSD.org References: From: Steve Wills Message-ID: Date: Sat, 17 Mar 2018 11:39:12 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Sat, 17 Mar 2018 15:39:23 +0000 (UTC) X-Spam-Status: No, score=1.3 required=4.5 tests=RCVD_IN_RP_RNBL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.2 at mouf.net X-Virus-Status: Clean 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: Sat, 17 Mar 2018 15:39:29 -0000 Finished bisecting, r329611 boots fine, r329612 does not. Steve On 03/16/2018 10:43, Justin Hibbits wrote: > > On Mar 16, 2018 09:29, "Steve Wills" > wrote: > > My PowerMac G5 runs r328835 fine, but upgrading to r330240 results in: > > fatal kernel trap: > >   exception           = 0x300 (data storage interrupt) >   virtual address     = 0xc186bff8 >   dsisr               = 0x40000000 >   srr0                = 0x8ef510 (0x8ef510) >   srr1                = 0x9000000000009032 >   lr                  = 0x7be3e4 (0x7be3e4) >   curthread           = 0x11b26560 >          pid = 38, comm = kldload > > [ thread pid 38 tid 100087 ] > Stopped at      strchr+0x70:    lbzu   r10, 0x1(r4) > db> > > Note this was transcribed by hand and may have typos. Also note my > kernel was compiled with gcc 6.3.0, although the previous kernel was > as well and it works fine. > > Any suggestions would be appreciated. > > Thanks, > Steve > > > Hi Steve, > > I see the same thing with any attempt to upgrade the kernel on my G5 > (PowerMac11,2) from a November 6 build to more recent. I've seen it > since the January timeframe, and haven't yet figured it out. > > - Justin > > From owner-freebsd-ppc@freebsd.org Sat Mar 17 23:57:30 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 AF438F501DF for ; Sat, 17 Mar 2018 23:57:30 +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 3E53E744B7 for ; Sat, 17 Mar 2018 23:57:29 +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 w2HNvKs9016610 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Sat, 17 Mar 2018 16:57:21 -0700 Subject: Re: fatal kernel trap To: freebsd-ppc@freebsd.org References: From: Nathan Whitehorn Message-ID: Date: Sat, 17 Mar 2018 16:57:20 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Sonic-CAuth: UmFuZG9tSVa6JK3OVPv9NNv/LqH64C+gyRx3yz8fiWkpbTwZVk8eKYLsoIlu7gShRLYVdc+K0q8XDug0es58yNSL73QxHYUbmkOXOd4rVns= X-Sonic-ID: C;imAL7j4q6BGISVDNXaHR5A== M;DNLa7j4q6BGISVDNXaHR5A== 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: Sat, 17 Mar 2018 23:57:30 -0000 Could you provide any other detail on your system? Amount of RAM, etc.? -Nathan On 03/17/18 08:39, Steve Wills wrote: > Finished bisecting, r329611 boots fine, r329612 does not. > > Steve > > On 03/16/2018 10:43, Justin Hibbits wrote: >> >> On Mar 16, 2018 09:29, "Steve Wills" > > wrote: >> >>     My PowerMac G5 runs r328835 fine, but upgrading to r330240 >> results in: >> >>     fatal kernel trap: >> >>        exception           = 0x300 (data storage interrupt) >>        virtual address     = 0xc186bff8 >>        dsisr               = 0x40000000 >>        srr0                = 0x8ef510 (0x8ef510) >>        srr1                = 0x9000000000009032 >>        lr                  = 0x7be3e4 (0x7be3e4) >>        curthread           = 0x11b26560 >>               pid = 38, comm = kldload >> >>     [ thread pid 38 tid 100087 ] >>     Stopped at      strchr+0x70:    lbzu   r10, 0x1(r4) >>     db> >> >>     Note this was transcribed by hand and may have typos. Also note my >>     kernel was compiled with gcc 6.3.0, although the previous kernel was >>     as well and it works fine. >> >>     Any suggestions would be appreciated. >> >>     Thanks, >>     Steve >> >> >> Hi Steve, >> >> I see the same thing with any attempt to upgrade the kernel on my G5 >> (PowerMac11,2) from a November 6 build to more recent. I've seen it >> since the January timeframe, and haven't yet figured it out. >> >> - Justin >> >> > _______________________________________________ > 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" >