From owner-freebsd-ppc@freebsd.org Sun Apr 15 07:10:36 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 3FC9AF9E290 for ; Sun, 15 Apr 2018 07:10:36 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 A85CF79C01 for ; Sun, 15 Apr 2018 07:10:35 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id r7-v6so10640985lfr.1 for ; Sun, 15 Apr 2018 00:10:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :to; bh=lW27Uw3Pn07rs5t5fSESNdFM8BijVKYCEA3+YanRWWw=; b=i9WokX2yyA51PI6/cADc45S6TEHZ+C0+H3QrlFAzu+pzBNB7tND0VxbfT+TgTdMt9h VE1UrMR/sZ/wanKf/d+wnxRIhsrzfOPgoiC/HnVxEsFAswi9VZw1cQ/O09dHxafgLvAo NQc7Hvaii5MRvhuZ4UqaR8jYrZiLZmx77SoOugPOpkInB7fHBFQbYjcu0URLrvBQYB6P 4N2+ziklXM4TCm0CSYwXcdELD7zimaG4ZGBHjtVIjSTMiQHmnoe/8yCNlo8bpcwMfumf /esd3Zhk446ULH2UmhLaBjnWV+zqjYsEHGW9C7PN+b9Q3nhPXs8uQPdn6jmlvVFLq/0h poyQ== 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:date :subject:message-id:to; bh=lW27Uw3Pn07rs5t5fSESNdFM8BijVKYCEA3+YanRWWw=; b=lT66N8VxE50F4DNLUjryZn8DPYomHjaXYu5G0Ou2PJLR9qNBzv44RUkmauiH4H7n7K JgMQDbjUgqZJH+qCTa91kGbghuHgDy/9X6Dtdo4lyS01ZDYe220MbeTNH/HJLRNFZl1I 4bYLqHL20H5OJ9c0tq1kjFesHHnhSmX3arLxu0Mg7IbzkHROMTSpvp/uP2Ga70aMxiII j8/G4ydeGzkV+R9lGjJgGAh8LxXRHxwhEHJ1MxPFmDRuNblOGsRyZkOm6sY0jUiZVSET QvxFGqRhpjqnCjBZzPLo/dLmRn2+8cuRIQaAjuGDJ3KtAXtjGacKISHIiMQRVYnutr/D BH8g== X-Gm-Message-State: ALQs6tCjcNgaF89XjBIAJgV3ljHJm1cJL1j6yPxj/Q/L/INEI4NEMRo4 85tnkfdo0HYLKHq8dDMpG8hp5Q== X-Google-Smtp-Source: AIpwx4+z2n9ESdTAdo4zJzvET6oqNy8jA59HWvxXahq95PWF0vQUiCyTwFRP7cb1O8iJyu/UHAiYgQ== X-Received: by 10.46.157.84 with SMTP id y20mr3432100ljj.107.1523776233236; Sun, 15 Apr 2018 00:10:33 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id h86-v6sm2161037lfl.73.2018.04.15.00.10.32 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Apr 2018 00:10:32 -0700 (PDT) From: Jukka Ukkonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (1.0) Date: Sun, 15 Apr 2018 10:10:25 +0300 Subject: 11.1 release CD image panics very early during boot on ppc. Message-Id: To: freebsd-ppc@FreeBSD.org X-Mailer: iPad Mail (15E216) 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, 15 Apr 2018 07:10:36 -0000 I had a bit of an accident with my old PowerMac G4 which had been running FreeBSD-10.4. To fix the mess I had to boot the system from a CD image. So, I decided to try 11.1 while at it. To my astonishment and disappointment the 11.1 images (both CD and DVD) paniced very early on during the boot. The messages flashed past the screen so quickly that I cannot be really sure about anything, but it kind of seemed like the issue might be yet another installment of the SPRG related problems (in ofw_machdep.c) which have been troubling ppc64 systems before. The 10.4 CD image boots just fine on ppc. --jau From owner-freebsd-ppc@freebsd.org Mon Apr 16 15:03: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 1406BF8A29B for ; Mon, 16 Apr 2018 15:03:57 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 6BCF27B5BF for ; Mon, 16 Apr 2018 15:03:56 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id q5-v6so22550290lff.12 for ; Mon, 16 Apr 2018 08:03:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:date:subject:message-id :to; bh=ZSEin+DEbbiVl6CG2sGr5gJrVxz2kJ/Jsmti0ydAz7Q=; b=QB/YngNr4kcL0XssgIovCFZYeBdef2RaVoP0fsbag627uBQrNeS80d2I46YZ8wR++v Ucyt6ANpUyXbP5IAbzPQ72XG6A8Uj0rc286U+HMEgu3OB1GIWQlD1HLIQgKUSte9DCS8 2lhIQC0Fq9+MpxLTNqIodfu1MMOUnYwr13uP/9JeI95pOJtubhf0inCGyv0sbKQqRA7a 3v/aGdY8/SlUqS5/bSE4ICrmh3Wly/SXIV9vdcf0dBRnJWCYemegjSeCzUrXdd2vsctN JfytBCkGZaWGzxGeB5dyN93eyP2xfNKhPG78al2rNRDsCeQB914jmFiTP205Ba0GvTSM 8NLQ== 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:date :subject:message-id:to; bh=ZSEin+DEbbiVl6CG2sGr5gJrVxz2kJ/Jsmti0ydAz7Q=; b=UBcjhBDZrusV6i1ECP9ZxhVtXGE6k1X97+UKdEdsKgyoAh4/wjCiS2vEteRPpbmo7O M4bSrjOPUiiqZwW/4LzgRZH/QGRk1fWAIJuPIZmuN5yDuiYc8fRqLQLEhifR/3yaDNPC PyRx89gqr8NDnQZdd/r/VrmO6Br33Nytm7w+bNSCnifhF0LWSQevlE+oIEJufkNo81nm AZISnbcHxxpwTGkqQ++TaMi0K7WorX4jTEv322EkleZWQgD5mgGZXFe1xlbIZQddrfMI DVdIiPoq23IOVme7gd9o5ftZ93pHM62l4A1YFVC4Ko+Lh+/nqHcRC0qI/5iPhDfJfURQ QsxA== X-Gm-Message-State: ALQs6tCbJsyld5ia9F4rNsYOwVXt7dRjMU5F3Z8epEZoANE6MStaovyE Y/rJjbWNK0OmKR2yXKZbHCTlBw== X-Google-Smtp-Source: AIpwx49r7NzkKezITL456nhxOVPVrbZeBNJZe/Hwu6WrSrsnaVEphjnegPFXZBJRLL5l8eT9pUQVBA== X-Received: by 10.46.62.12 with SMTP id l12mr9421131lja.66.1523891034762; Mon, 16 Apr 2018 08:03:54 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id j74-v6sm2885733lfg.92.2018.04.16.08.03.53 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Apr 2018 08:03:53 -0700 (PDT) From: Jukka Ukkonen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Mon, 16 Apr 2018 18:03:52 +0300 Subject: building 11.1-stable on 10.4 ppc system Message-Id: To: freebsd-ppc@FreeBSD.org X-Mailer: iPad Mail (15E216) 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, 16 Apr 2018 15:03:57 -0000 Has anyone successfully built 11.1-stable or any other 11 series kernel on a 10.4-stable ppc system? I mean is there a reasonable possibility to build a functional 11.1 environm= ent, though, the 11.1-release CD and DVD images are both broken? Will I need any special steps in addition to the usual... make kernel-toolchain make buildkernel make installkernel Will the old standalone boot branch (loaders, boot blocks, etc.) work or=20 will they have to be updated as well at the same time with the kernel? What about the tools needed to build them? --jau From owner-freebsd-ppc@freebsd.org Mon Apr 16 21:24:27 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6CABFA6B9E for ; Mon, 16 Apr 2018 21:24:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 58746873A6 for ; Mon, 16 Apr 2018 21:24:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0922FFA6B9A; Mon, 16 Apr 2018 21:24:26 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9945FA6B98 for ; Mon, 16 Apr 2018 21:24:25 +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 7243A87379 for ; Mon, 16 Apr 2018 21:24:25 +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 9BB6B1EE90 for ; Mon, 16 Apr 2018 21:24:24 +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 w3GLOOrk032431 for ; Mon, 16 Apr 2018 21:24:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3GLOO3f032430 for ppc@FreeBSD.org; Mon, 16 Apr 2018 21:24:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 226974] kernel DSI read trap at boot Date: Mon, 16 Apr 2018 21:24:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: leandro.lupori@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.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, 16 Apr 2018 21:24:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226974 --- Comment #12 from Leandro Lupori --- I have an update on this. I think I've found what is causing this issue. When ofw_mem_regions() is called during initialization, it looks for /chosen/fdtmemreserv property in the device tree. When FDT is enabled, this property will always exist, as it's a "fake" property returned by OFW FDT getprop itself. Then, if the fdtmemreserv property exists, excise_fdt_reserved() is called,= and it does 2 main things: 1- Excludes reserved memory from available memory regions 2- Excludes FDT memory region itself from available memory In my case, it's the second item that causes a problem later, at moea64_early_bootstrap(). There is one part of this function that checks for overlaps between availab= le memory regions and the region where the kernel was loaded. When this overla= p is found, the available memory list is supposed to be adjusted to exclude kern= el memory. But this code doesn't work correctly for some available memory regions, like the one that is produced by excise_fdt_reserved() when there is an overlap between FDT and kernel end. This is the relevant part of the available regions in my case: 0x00004000 - 0x01800074 (~24MB) 0x0180b04c - 0x02c00000 (~20MB) 0x0344d3f0 - 0x7dbe0000 (~2GB) kernelstart =3D 0x0100100 kernelend =3D 0x1b60000 fdt =3D 0x1b5b000 - 0x1b5f000 (upper bound rounded to page size) When FDT is not used, moea64_early_bootstrap() will adjust the regions like this: 0x00004000 - 0x01000000 0x01b60000 - 0x02c00000 0x0344d3f0 - 0x7dbe0000 And everything works fine. However, when FDT is used, excise_fdt_reserved() will change the available regions to this: 0x00004000 - 0x01800074 0x0180b04c - 0x01b5b000 0x01b5f000 - 0x02c00000 0x0344d3f0 - 0x7dbe0000 And then moea64_early_bootstrap() will adjust the regions and produce this: 0x00004000 - 0x01000000 0x0180b04c - 0x01b5b000 0x01b61000 - 0x02c00000 0x0344d3f0 - 0x7dbe0000 Which turns a large part of the kernel memory (0x0180b04c - 0x01b5b000) into available memory, causing the issue when this region starts being used as s= uch. I'm not sure about the best way to fix this. Maybe one (or more) of the following: 1- Change moea64_early_bootstrap() to make it able to detect and adjust reg= ions such as (0x0180b04c - 0x01b5b000), in which case the whole region should be removed from available list. 2- Change the boot loader to place the FDT after kernelend. And one last thing that I noticed and seems odd to me is that region (0x01800074 - 0x0180b04c) is not reported as available, but even so the ker= nel is loaded at (0x0100100 - 0x1b60000), which includes the not available regi= on. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Tue Apr 17 15:09:41 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 13E34F821C4 for ; Tue, 17 Apr 2018 15:09:41 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 73C4D8217A for ; Tue, 17 Apr 2018 15:09:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id q9-v6so27846883lfk.9 for ; Tue, 17 Apr 2018 08:09:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6HI7EDZii8ddUdi1IPCI7ZcWSC7wbTzFOM+XionKFaM=; b=nVE1JaF/fvC3VlLMoVAwUI4B/QZLLrgpn5K2A12ScNY5HT4ID22xpM3ENu5+axiTTE SwUfkc7hFW5Ll0SAAorFx+nDKCHSV6jTTMNfMEFXHvwaGJ2N++U2IJYExPrQrGHmLsHn 9gp52X8p5ayGLR4NXMoOGnR5nXCZPbMlcNrMMlYzN5+6Nk2kEs0vbCfjxhVr5W3hFR3d p80lxLHUYB+QzGEtDVW414tl+rbY9yFH1x/cRu/P8O+s8SzSrwCTGtXAxuoGN/WfLMPg 105i0ABuzSP/yus3QDytsc49+7reTnkZnii5oqWKDtymt/p2bKBObE9dcEqyQRFGHV0l AroQ== 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; bh=6HI7EDZii8ddUdi1IPCI7ZcWSC7wbTzFOM+XionKFaM=; b=JflktjpuSQmYwS/bmfntWXrnEI8/8BSrD5UWmX17xarUy+4VArFKQjzpqIIq8wsC6V arWq61WwenADRanMhcA16pFqCe3E6NcJ3bwRp8tZXcJl4ZC75G9lnACGak13jSpHqwJ2 qAVfahHmgek7xu+MdEoEbjGxl6M9S9mdwm18+3PJXtg9jwH7xD+BW6u0dkSVymHRNiOO VLoSuSzQTvmoRWbNkEfRCIAuPV56uIupbhmwa9c0KR1b/z7dNlO/OaHXeeAlDDfBdDeA 7Jr9EqSNZOkFrVZqGEHBAnZy/l59SqVtI/GEaEUTqb6K6cnhTK13V29XedbtaWKWR+Wb lz4g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6HI7EDZii8ddUdi1IPCI7ZcWSC7wbTzFOM+XionKFaM=; b=ee/GWo0B8dwNer01sjVrwKR9beL+19BrQSqQajPeWVuAcnel40DCum2Wuxz2e6MXMi E6Oc8sriJBsrHzZqyV/a+UnbUPZCPsQFGgRcusry6IHQFZJCrqY8P4i8H9cpeoD7oOpW oJQ1hbYK7zSEELTzjW0SP8TOOIZyeQlHhIvpY12v6wAnT17T05ESOFSTmEeReZY0fCx2 +knXkKyMdZKtJhzlTGDDAJPa2ZHaXDKji7jw8ZpUGuoWdG82QmN7JEl7yDl5cFPJk7ZT PAXLAp8eg14rxBN7CzaaWKqSNIlmDDbqrMHKxS5fAnt6I7XWaaBNVi2QgVWsb8H1TqhV sRhA== X-Gm-Message-State: ALQs6tB8S8fkfoavk3nC+xToVAQkMG3/Gca7u+YqP2TIusKEBM7NDnUI 8TshSewdf1Yv5+6rB2AmNbZW5VTxShmV6JHAXVY= X-Google-Smtp-Source: AIpwx4/fSA4In4kbvjW7eMMOOzsiFzAift4DIGUCTu/GIZGuwoY7BE/2NukLUiAk2ohK/GNOmczBos92Bmsp9mEo8rI= X-Received: by 2002:a19:4c46:: with SMTP id z67-v6mr1819912lfa.141.1523977778930; Tue, 17 Apr 2018 08:09:38 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.46.129.210 with HTTP; Tue, 17 Apr 2018 08:09:38 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Tue, 17 Apr 2018 10:09:38 -0500 X-Google-Sender-Auth: xrm9uMx84n462SM4k81f7sSCuaE Message-ID: Subject: Re: building 11.1-stable on 10.4 ppc system To: Jukka Ukkonen Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" 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, 17 Apr 2018 15:09:41 -0000 Hi, On Mon, Apr 16, 2018 at 10:03 AM, Jukka Ukkonen wrote: > > Has anyone successfully built 11.1-stable or any other 11 series kernel > on a 10.4-stable ppc system? > I mean is there a reasonable possibility to build a functional 11.1 environment, > though, the 11.1-release CD and DVD images are both broken? > Will I need any special steps in addition to the usual... > > make kernel-toolchain > make buildkernel > make installkernel > > Will the old standalone boot branch (loaders, boot blocks, etc.) work or > will they have to be updated as well at the same time with the kernel? > What about the tools needed to build them? > > --jau That should work fine. I don't know why the 11.1 images are broken, I can check later, maybe not until Thursday or the weekend though, on my computers. - Justin From owner-freebsd-ppc@freebsd.org Tue Apr 17 15:11:41 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 88518F82512 for ; Tue, 17 Apr 2018 15:11:41 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 DE17B823F6 for ; Tue, 17 Apr 2018 15:11:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-lf0-x229.google.com with SMTP id q9-v6so27857035lfk.9 for ; Tue, 17 Apr 2018 08:11:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=42tQ0ysHjKwi8tLVol34JjhZf5RlxH5FaKkgdYva7KM=; b=j4cJrdE7bqCrahgpm22+uL2YhOMR56bcKzB7B5YUeYVDJHeTjU5FmeEY8e0lA5/GeU 55B0Ts4wG1SAl2p7duWUlYDmMqQdZqsQrgXOW/PWF2hYamUzlwJwY1VHuFeGzCv/1V/T 9/XmwaNylL2WSpj/T3Qf2tWS/z7dbqMkBcVpO1M+mxh3xAApXd2d0fCpONtDok92l7qw YTnm9oSIelyhVPjAK6Q+YVBMiY/g4hXMVEhMFwvK57RP7qMnoh2FVDkMGG8bRhPg1BJO i76iT6LmYqQRQ31uZKXgJdNR7KQWGfkmMZytclBTmaV7PRJVi5l7j3TGgc5kq2QDRb/F Iesg== 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; bh=42tQ0ysHjKwi8tLVol34JjhZf5RlxH5FaKkgdYva7KM=; b=kFGdj5p1byQs1gy3gS+Pgmn1S9rzz1zMNVe7VlwHr386uqXNbuxvAlfbN9BVAVLi7i yMZhwyR9eFr8gVGXqoRm4lVORESPgv90SxgapUJZuMJoMbnEDj4Q8V+JVsmkRe/2a8/P cBasV7CcR70YsVbZQJ/cRJmw2uOl1MlUFO7JqxpZ1tqfxoZ8lsNRezGj+ZFbPMI8dhTc Q914ffjkcLnQR3TucwzWQNGDONOKu27PY1XNB2G544HlKTQOHxAmrLR5lUH4u6/wZ/kw zEhDYC/GTi96SNNLMh9DGii+Tps5AgwJAmSOTBMxhSQwiKC/x+ckqHZ6rtZE9BKHaBkf 0SxQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=42tQ0ysHjKwi8tLVol34JjhZf5RlxH5FaKkgdYva7KM=; b=ITn/ojH9852erBv/9bNeYiYpI80/gTDzA1c0S9nc31gj18a1Bo+5i3hAA0WtSwdpoi nW5G4WDg+JlYlo+aMfEZtP1OmD8uhR0GMZJVRkYcuvGvA0FDddtzly6Sd1e6PLD3gT0I qDPJEqsROETw5Bgof5+UZEpwy+59tpFzEXw3LZOsAesnt7Fdg7VB2At8bKQoEP0F9Q31 HUszfR9HQG8PJbCw7bjz20H/wCyW6nLyBe6pU54yp8MRd0KY5MhS9nOMuc4DzYRdo6SE Mw7+7huzn47/HrjzRIdvuGJqNJRkUhYUL7JndS0hhKSXM71Vb59Awj6TlBRiQUyK93Ds GfmQ== X-Gm-Message-State: ALQs6tAP78jr+mmbCTVMGI3U3rrk9g81rMBaG+aV1AS7LMRFiLUFoI0H EfLt7JYTCO7KenAGcyEGoatYgDTRBOrDZDlzU1E= X-Google-Smtp-Source: AIpwx4+mEj7DPO3DGKrKo9JzrU/GJqBhPHpcj+aDiJFK9W7zEavZrDl7AgC8pmhh/KWpD/jrXz2GTG47sIbjsbwYJl8= X-Received: by 2002:a19:1c0f:: with SMTP id c15-v6mr1829358lfc.44.1523977899406; Tue, 17 Apr 2018 08:11:39 -0700 (PDT) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.46.129.210 with HTTP; Tue, 17 Apr 2018 08:11:38 -0700 (PDT) In-Reply-To: References: From: Justin Hibbits Date: Tue, 17 Apr 2018 10:11:38 -0500 X-Google-Sender-Auth: gBTJK3OEyHht355bPsON04021qE Message-ID: Subject: Re: 11.1 release CD image panics very early during boot on ppc. To: Jukka Ukkonen Cc: FreeBSD PowerPC ML Content-Type: text/plain; charset="UTF-8" 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, 17 Apr 2018 15:11:41 -0000 Hi, On Sun, Apr 15, 2018 at 2:10 AM, Jukka Ukkonen wrote: > > I had a bit of an accident with my old PowerMac G4 which had been > running FreeBSD-10.4. To fix the mess I had to boot the system from > a CD image. So, I decided to try 11.1 while at it. To my astonishment > and disappointment the 11.1 images (both CD and DVD) paniced > very early on during the boot. The messages flashed past the screen > so quickly that I cannot be really sure about anything, but it kind of > seemed like the issue might be yet another installment of the SPRG > related problems (in ofw_machdep.c) which have been troubling > ppc64 systems before. > The 10.4 CD image boots just fine on ppc. > > --jau Can you try booting with 'boot -v' and also setting at the loader debug.debugger_on_panic=1? I think it's set to 0 on release ISOs, so this should let you get a screen capture. - Justin From owner-freebsd-ppc@freebsd.org Tue Apr 17 15:22:19 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E4D48F8336C for ; Tue, 17 Apr 2018 15:22:18 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (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 EC39D857E0 for ; Tue, 17 Apr 2018 15:22:17 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id v207-v6so27905484lfa.10 for ; Tue, 17 Apr 2018 08:22:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ao/0KuvVnnsvhMcAVksiX76j0CGOajqvnnFo9buNU9Q=; b=B7Rr0wQDRw2Ly7xyGUAW9Ub1nosCUDI+f85zpdKSPXLuBpbBk5xuCzazww/cSr2eyB LCnrmhNJ97JnYEu7J7hFZ19aTlgCJ+WI4u71V7oLHaeqHHPy6CuDIrT0lk3ATbokuTe6 dXSVgj0D8qswTPxHYoM1nqCOOd1xQf+4UtSLFhw5t63f80F0y6tLhAT+q5A8bIZpUHRX nUv5LTWFMO7FDO380cbmy45i13UDW0gXZu810ltbfD7yHKnxUoRAuXqEiiwGlsTJH5b2 PsGoCNWArr+IVtZR9Vqvi+/uDsligIm/81+dIEeXG4/B1J8sLArx5qUv/fIzZk4eDLdC sIkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ao/0KuvVnnsvhMcAVksiX76j0CGOajqvnnFo9buNU9Q=; b=WuAvxK9u7jemKYV8giHH7vBIHx4pdfG1mhrWr7w4I5cySIyLUrVTg9jbqHVnejGIJe aKCHEojgQdsVKiyUEh24v0Ni1S9vytJs9LMlE+uSENVF2uj2wIn/Gj9fDaGJjMWCK5DN 0IgdU0bNrxblV+dGF7bE9zl1Yu7QEs02mTYI0bJh5DpNpTblD3X7fw8W+VGYXJBdxidf jl97vEaz9cVp18niAxMuOZHqL6882OA4S++h/2OjmanBrShZkx9lYytGACAukFj41fbO bOFw5fuLOKrL9++mQVxmhRA0sG1IEUghsPiiN/4S/8Werb+pWEugWgGtQsoxHEFGRykC xdMg== X-Gm-Message-State: ALQs6tAYfOTlR70IO9MvBoh8OUFitXegOxY1Pxhx+S+gzgOp+9x3iByO l8s2VRcz0lFUOBomek8yog6MNQ== X-Google-Smtp-Source: AIpwx49QzsdBD4YKZnqPJyrqQoG3hsYO7NpCdTiyX/rFrofiVVIw0fStk8flhydNNJPDWwucTpvtzA== X-Received: by 10.46.84.66 with SMTP id y2mr1731936ljd.11.1523978532568; Tue, 17 Apr 2018 08:22:12 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id p75sm2610747lja.9.2018.04.17.08.22.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Apr 2018 08:22:11 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: 11.1 release CD image panics very early during boot on ppc. From: Jukka Ukkonen X-Mailer: iPad Mail (15E216) In-Reply-To: Date: Tue, 17 Apr 2018 18:22:10 +0300 Cc: FreeBSD PowerPC ML Content-Transfer-Encoding: 7bit Message-Id: References: To: Justin Hibbits 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, 17 Apr 2018 15:22:19 -0000 > On 17 Apr 2018, at 18.11, Justin Hibbits wrote: > > Hi, > >> On Sun, Apr 15, 2018 at 2:10 AM, Jukka Ukkonen wrote: >> >> I had a bit of an accident with my old PowerMac G4 which had been >> running FreeBSD-10.4. To fix the mess I had to boot the system from >> a CD image. So, I decided to try 11.1 while at it. To my astonishment >> and disappointment the 11.1 images (both CD and DVD) paniced >> very early on during the boot. The messages flashed past the screen >> so quickly that I cannot be really sure about anything, but it kind of >> seemed like the issue might be yet another installment of the SPRG >> related problems (in ofw_machdep.c) which have been troubling >> ppc64 systems before. >> The 10.4 CD image boots just fine on ppc. >> >> --jau > > Can you try booting with 'boot -v' and also setting at the loader > debug.debugger_on_panic=1? I think it's set to 0 on release ISOs, so > this should let you get a screen capture. > > - Justin I will try, but it might have to wait until the weekend. --jau From owner-freebsd-ppc@freebsd.org Tue Apr 17 20:30: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 2BA55F98726 for ; Tue, 17 Apr 2018 20:30:24 +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 C21BC71213 for ; Tue, 17 Apr 2018 20:30:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by freefall.freebsd.org (Postfix) id A0AAF3256; Tue, 17 Apr 2018 20:30:23 +0000 (UTC) Delivered-To: powerpc@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id 9DF7C3255 for ; Tue, 17 Apr 2018 20:30:23 +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 708BA71210 for ; Tue, 17 Apr 2018 20:30:23 +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 9C0BC2A78F for ; Tue, 17 Apr 2018 20:30:22 +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 w3HKUM2x008279 for ; Tue, 17 Apr 2018 20:30:22 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3HKUMUb008278 for powerpc@FreeBSD.org; Tue, 17 Apr 2018 20:30:22 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: powerpc@FreeBSD.org Subject: [Bug 225182] devel/powerpc64-xtoolchain-gcc: SLOF Data Storage Exception on boot with kernel built with devel/powerpc64-xtoolchain-gcc Date: Tue, 17 Apr 2018 20:30:22 +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: kennethsalerno@yahoo.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bapt@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: Tue, 17 Apr 2018 20:30:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225182 --- Comment #26 from Kenneth Salerno --- I have an update to this issue: when I set the CPU to POWER9 in QEMU, I get different results than I had with POWER8. Now, instead of a Data Storage Exception, I get the following message and a hang when building GENERIC64 w= ith gcc6: ...[normal boot]... Error initializing RTAS (-1902) ... run_interrupt_driven_hooks: still waiting after 60 seconds for 0x5f2888 I get this same error above if I build the GENERIC64 kernel with the system= gcc 4.2 and simply disable DDB_CTF, or if I copy the GENERIC64 kernel and use KERNCONF env. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-ppc@freebsd.org Wed Apr 18 13:28:53 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 297F0F8AFF5 for ; Wed, 18 Apr 2018 13:28:53 +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 B0D3A6D818 for ; Wed, 18 Apr 2018 13:28:52 +0000 (UTC) (envelope-from andy.silva@snsreports.com) X-MSFBL: kdSWvdvBQkf+NDDd/4JEhAWRgESXLxcGBpLsMoUQlRg=|eyJnIjoiU25zdGVsZWN vbV9kZWRpY2F0ZWRfcG9vbCIsInIiOiJmcmVlYnNkLXBwY0BmcmVlYnNkLm9yZyI sImIiOiJTbnN0ZWxlY29tX2RlZGljYXRlZF9wb29sXzc0XzkxXzg1XzIzOCJ9 Received: from [10.137.129.35] ([10.137.129.35:35670] 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 4E/7D-20152-D5347DA5; Wed, 18 Apr 2018 13:08:45 +0000 Received: from 10.137.11.77 by Caffeine (mtl-mtsp-c02-3) with SMTP id 899570e9-3cc8-4e31-a3a5-fb65f9c169d5 for freebsd-ppc@freebsd.org; Wed, 18 Apr 2018 13:08:43 +0000 (UTC) Received: from [65.49.242.4] ([65.49.242.4:26850] helo=gull-dhcp-65-49-242-4.bloombb.net) by mtl-mtsp-mta01-in1 (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 38/27-23685-B5347DA5; Wed, 18 Apr 2018 13:08:43 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsreports.com To: freebsd-ppc@freebsd.org Subject: The VoLTE (Voice over LTE) Ecosystem: 2018 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Wed, 18 Apr 2018 09:08:40 -0400 Message-ID: <54964994530163024826311@Ankur> X-SMTPCOM-Tracking-Number: 899570e9-3cc8-4e31-a3a5-fb65f9c169d5 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM X-SMTPCOM-Payload: =?utf-8?q?KTQPJmjbopv9ZP9NHZrYnOv2bGa0h17xkUHMtsVx4D2M?= =?utf-8?q?z4H43ebn=5FOv=5FiMNJiyWeLWzvB802Y=5FscY79gtuf-nYaKmdViicVEWFtCP?= =?utf-8?q?53v1MpVy8rgns0WdcDrDM9HnBz=5FWVdSrxAq6A9lnyqZzy6iQA=3D=3D?= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smtpserver.email; i=@smtpserver.email; q=dns/txt; s=smtpcustomer; t=1524056924; h=MIME-Version : From : Reply-To : To : Subject : Content-Type : Date : Message-ID : From : Subject : Date; bh=fAyP+yJOxrPFFOKgH4MU4V5x9rvg7S8/OSmEGdtebiI=; b=MPkbirgBeeCx87yRIbfl5ABF7nB79bDyYBdjznTHUXQ5IV0/FglzUDyOCSvwpEF1vd9Vc7 2o3Hdn+9N6mVf6v9G7kQAgtgbPme4eBC/1auaesMeTucwIg0AhPmoGwJO/I98QfINtXmX8QI SP8MaocTYImlrBISBmbx/aRbdqtgS6cClkOhGZVjzuHqIO/2L0jOYrmUzLNpYhPikAFot4bE FK5z43uWBUzof8D+/u2L0towbwRbGFva5nHsvRMp6REPoOM6aIb13Oj7ZEcr40W/m41ASJ74 2g4Rt3TWfBJkRh/TTQnGNn+l/1EEU5GO9XKSqjfWzY76OEMLnrQm5+HA== 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, 18 Apr 2018 13:28:53 -0000 The VoLTE (Voice over LTE) Ecosystem: 2018 =96 2030 =96 Opportunities, Chal= lenges, Strategies & Forecasts (Report) Hello Let me offer you the latest SNS Research report to you and your team, "The = VoLTE (Voice over LTE) Ecosystem: 2018 =96 2030 =96 Opportunities, Challeng= es, Strategies & Forecasts" Below is the report highlight and if you like I= can send you sample pages for your details inside.=20 VoLTE (Voice over LTE) technology allows a voice call to be placed over an = LTE network, enabling mobile operators to reduce reliance on legacy circuit= -switched networks. Powered by IMS (IP Multimedia Subsystem) architecture,= VoLTE brings a host of benefits to operators ranging from the ability to r= efarm legacy 2G and 3G spectrum to offering their subscribers a differentia= ted service experience through capabilities such as HD voice and video tele= phony. First deployed by South Korean operators in 2012, VoLTE is continuing to ga= in momentum globally. As of Q2=922018, more than 140 mobile operators have = commercially launched VoLTE services, and several roaming and interoperabil= ity agreements are already in place. SNS Telecom & IT estimates that VoLTE service revenue will grow at a CAGR o= f approximately 30% between 2018 and 2021. By the end of 2021, VoLTE subscr= iptions will account for more than $280 Billion in annual service revenue. = Although traditional voice services will constitute a major proportion of t= his figure, more than 16% of the revenue will be driven by voice based IoT = applications, video calling and supplementary services. The =93VoLTE (Voice over LTE) Ecosystem: 2018 =96 2030 =96 Opportunities, C= hallenges, Strategies & Forecasts=94 report presents an in-depth assessment= of the VoLTE ecosystem including market drivers, challenges, enabling tech= nologies, applications, key trends, standardization, regulatory landscape, = mobile operator case studies, opportunities, future roadmap, value chain, e= cosystem player profiles and strategies. The report also presents forecasts= for VoLTE-capable device shipments, subscriptions, service revenue and inf= rastructure investments from 2018 till 2030. The forecasts cover 14 submark= ets and 6 regions. Report Information: Release Date: April 2018 Number of Pages: 279 Number of Tables and Figures: 78 Key Questions Answered: How big is the VoLTE 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 regions and countries will see the highest percentage of growth=3F How will VoLTE-capable device shipments grow over time=3F Who are the key market players and what are their strategies=3F How can VoLTE help operators in reducing the flow of voice subscribers to O= TT application providers=3F What are the prospects of Wi-Fi calling, RCS and WebRTC=3F What much will operators invest in VoLTE service assurance solutions=3F How can mobile operators and MVNOs capitalize on VoLTE to drive revenue gro= wth=3F How can VoLTE help operators in refarming their 2G and 3G spectrum assets=3F What is the status of international roaming and VoLTE-to-VoLTE interconnect= ion agreements=3F What strategies should VoLTE solution providers and mobile operators adopt = to remain competitive=3F Key Findings: The report has the following key findings: By 2021, SNS Telecom & IT estimates that VoLTE subscriptions will account f= or over $280 Billion in annual service revenue, as mobile operators remain = committed to VoLTE as the long term solution to secure a fully native IP-ba= sed telephony experience. Besides smartphones, VoLTE technology is increasingly being integrated into= other devices including feature phones, IoT modules and wearables such as = smart watches. In certain technically advanced markets, mobile operators have already begu= n the process of switching off their legacy circuit switched 2G and 3G netw= orks, as voice traffic transitions to VoLTE networks. Nearly all VoLTE operators are integrating their VoLTE services with Wi-Fi = calling in a bid to offer voice services in areas where their licensed spec= trum coverage is limited. The VoLTE infrastructure vendor arena is continuing to consolidate with sev= eral prominent M&A deals such as the merger of Sonus Networks and GENBAND t= o form Ribbon Communications, Cisco's acquisition of BroadSoft, and Metaswi= tch Networks' acquisition of OpenCloud to offer a pure-play software VoLTE = solution. The report covers the following topics: VoLTE ecosystem Market drivers and barriers VoLTE infrastructure, devices, roaming and interconnection technology Case studies of over 20 commercial VoLTE deployments OTT mobile voice and video services Complimentary technologies including Wi-Fi calling, RCS and WebRTC Vertical market opportunities including voice based IoT applications and MC= PTT (Mission Critical Push-to-Talk) voice services VoLTE services over MVNO networks Service assurance platforms for VoLTE Regulatory landscape, collaborative initiatives and standardization Industry roadmap and value chain Profiles and strategies of more than 100 leading ecosystem players includin= g device OEMs, VoLTE solution providers and mobile operators Strategic recommendations for VoLTE solution providers and mobile operators Market analysis and forecasts from 2018 till 2030 Forecast Segmentation: VoLTE subscription, service revenue and infrastructure revenue forecasts ar= e provided for each of the following submarkets and their subcategories: VoLTE-Capable Devices Handsets Smartphones & Phablets Feature Phones Smartwatches & Wearables Tablets, CPEs & Other Devices IoT Modules VoLTE Subscriptions & Services Voice Telephony Video & Supplementary Services Voice Based IoT Applications VoLTE Infrastructure CSCF (Call Session Control Function) Servers SBCs (Session Border Controllers) VoLTE Application Servers Other IMS Elements (HSS, BGCF, MGCF & MRF) VoLTE-Capable Policy Control Solutions Regional Markets Asia Pacific Eastern Europe Latin & Central America Middle East & Africa North America Western Europe 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(page number): =20 1 Chapter 1: Chapter 1: Introduction 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 VoLTE 2.1 What is VoLTE=3F 2.2 Architectural Evolution of VoLTE 2.2.1 CSFB (Circuit-Switched Fallback): The First Step Towards VoLTE 2.2.2 The Push From CDMA Operators 2.2.3 Towards an IMS Based VoLTE Solution 2.2.4 SRVCC (Single Radio Voice Call Continuity) 2.2.5 Integrating Video Telephony 2.3 Key Enabling Technologies 2.3.1 VoLTE Infrastructure 2.3.1.1 IMS Core: CSCF, HSS, BGCF & MGCF 2.3.1.2 VoLTE Application Servers 2.3.1.3 SBC (Session Border Controller) 2.3.1.4 MRF (Media Resource Function) 2.3.1.5 PCRF (Policy and Charging Rules Function) 2.3.2 VoLTE Devices 2.3.3 Roaming & Interconnection Technology 2.3.3.1 LBO (Local Breakout) 2.3.3.2 S8HR (S8 Home Routing) 2.4 Market Growth Drivers 2.4.1 Spectral Efficiency & Cost Reduction 2.4.2 Enabling HD Voice, Video Calling & Rich IP Communications 2.4.3 Improved Battery Life 2.4.4 Integration with Wi-Fi: Enhanced Indoor Voice Coverage 2.4.5 Bundling Voice with Other Services 2.4.6 Fighting the OTT Threat 2.5 Market Barriers 2.5.1 Initial Lack of Compatible Devices 2.5.2 Roaming & Interconnect Issues 2.5.3 Limited Revenue Potential 2.5.4 Service Assurance Challenges =20 3 Chapter 3: Standardization, Regulatory & Collaborative Initiatives 3.1 3GPP (3rd Generation Partnership Project) 3.1.1 Release 8: VoLTE Interface Requirements 3.1.2 Release 9: Support for SRVCC & VoLTE Emergency Calls 3.1.3 Release 10: eSRVCC & aSRVCC 3.1.4 Release 11: vSRVCC, rSRVCC & VoLTE Roaming Architecture 3.1.5 Release 12: EVS & HEVC Codecs 3.1.6 Release 13: MCPTT for Critical Communications 3.1.7 Release 14: VoLTE Support for IoT Services 3.1.8 Release 15: Further Enhancements to Improve VoLTE User Experience 3.2 GSMA 3.2.1 Feature Requirements 3.2.1.1 IR.92: IMS Profile for Voice and SMS 3.2.1.2 IR.94: IMS Profile for Conversational Video Service 3.2.2 Roaming, Interworking & Other Guidelines 3.2.2.1 IR.64: IMS Service Centralization & Continuity Guidelines 3.2.2.2 IR.65: IMS Roaming & Interworking Guidelines 3.2.2.3 IR.88: LTE Roaming Guidelines 3.3 ETSI (European Telecommunications Standards Institute) 3.3.1 Virtualization for VoLTE Infrastructure 3.3.1.1 NFV ISG (Industry Specification Group): Releases 1 =96 3 3.4 Others =20 4 Chapter 4: VoLTE Deployment Case Studies 4.1 AT&T 4.1.1 Service Launch Strategy 4.1.2 Vendor Selection 4.1.3 Future Prospects 4.2 China Mobile 4.2.1 Service Launch Strategy 4.2.2 Vendor Selection 4.2.3 Future Prospects 4.3 DT (Deutsche Telekom) 4.3.1 Service Launch Strategy 4.3.2 Vendor Selection 4.3.3 Future Prospects 4.4 Du (Emirates Integrated Telecommunications Company) 4.4.1 Service Launch Strategy 4.4.2 Vendor Selection 4.4.3 Future Prospects 4.5 EE 4.5.1 Service Launch Strategy 4.5.2 Vendor Selection 4.5.3 Future Prospects 4.6 KDDI Corporation 4.6.1 Service Launch Strategy 4.6.2 Vendor Selection 4.6.3 Future Prospects 4.7 KT Corporation 4.7.1 Service Launch Strategy 4.7.2 Vendor Selection 4.7.3 Future Prospects 4.8 LG Uplus 4.8.1 Service Launch Strategy 4.8.2 Vendor Selection 4.8.3 Future Prospects 4.9 NTT DoCoMo 4.9.1 Service Launch Strategy 4.9.2 Vendor Selection 4.9.3 Future Prospects 4.10 Orange 4.10.1 Service Launch Strategy 4.10.2 Vendor Selection 4.10.3 Future Prospects 4.11 Reliance Jio Infocomm 4.11.1 Service Launch Strategy 4.11.2 Vendor Selection 4.11.3 Future Prospects 4.12 Rogers Communications 4.12.1 Service Launch Strategy 4.12.2 Vendor Selection 4.12.3 Future Prospects 4.13 Singtel 4.13.1 Service Launch Strategy 4.13.2 Vendor Selection 4.13.3 Future Prospects 4.14 SK Telecom 4.14.1 Service Launch Strategy 4.14.2 Vendor Selection 4.14.3 Future Prospects 4.15 SoftBank Group 4.15.1 Service Launch Strategy 4.15.2 Vendor Selection 4.15.3 Future Prospects 4.16 Swisscom 4.16.1 Service Launch Strategy 4.16.2 Vendor Selection 4.16.3 Future Prospects 4.17 Telef=F3nica Group 4.17.1 Service Launch Strategy 4.17.2 Vendor Selection 4.17.3 Future Prospects 4.18 Telenor Group 4.18.1 Service Launch Strategy 4.18.2 Vendor Selection 4.18.3 Future Prospects 4.19 Telstra 4.19.1 Service Launch Strategy 4.19.2 Vendor Selection 4.19.3 Future Prospects 4.20 TIM (Telecom Italia Mobile) 4.20.1 Service Launch Strategy 4.20.2 Vendor Selection 4.20.3 Future Prospects 4.21 Verizon Communications 4.21.1 Service Launch Strategy 4.21.2 Vendor Selection 4.21.3 Future Prospects 4.22 Vodafone Group 4.22.1 Service Launch Strategy 4.22.2 Vendor Selection 4.22.3 Future Prospects =20 5 Chapter 5: Industry Roadmap & Value Chain 5.1 Industry Roadmap 5.1.1 Pre-2020: Large-Scale VoLTE Service Rollouts 5.1.2 2020 =96 2025: Building IoT & Advanced Services on VoLTE Architecture 5.1.3 2025 =96 2030: Continued Investments with 5G Rollouts 5.2 Value Chain 5.2.1 Enabling Technology Providers 5.2.2 VoLTE & IMS Infrastructure Suppliers 5.2.3 VoLTE Device OEMs 5.2.4 Roaming, Billing & Supplementary Service Providers 5.2.5 Mobile Operators 5.2.6 Test, Measurement & Performance Specialists =20 6 Chapter 6: Key Ecosystem Players 6.1 Accedian Networks 6.2 Affirmed Networks 6.3 ALEPO 6.4 Alpha Networks 6.5 Altair Semiconductor 6.6 Amdocs 6.7 Anritsu Corporation 6.8 Apple 6.9 Aptilo Networks 6.10 Aricent/Altran 6.11 Astellia 6.12 ASUS (ASUSTeK Computer) 6.13 BBK Electronics Corporation/OPPO/Vivo 6.14 BICS 6.15 Broadcom 6.16 BT Group 6.17 CCN (Cirrus Core Networks) 6.18 Cellwize Wireless Technologies 6.19 CENX 6.20 CEVA 6.21 Cirpack 6.22 Cisco Systems 6.23 Continual (CellMining) 6.24 D2 Technologies 6.25 Dialogic 6.26 DigitalRoute 6.27 D-Link Corporation 6.28 Ecrio 6.29 ELUON Corporation 6.30 Empirix 6.31 Ericsson 6.32 EXFO 6.33 F5 Networks 6.34 Federos 6.35 Foxconn Technology Group 6.36 Fraunhofer IIS (Institute for Integrated Circuits) 6.37 Fujitsu 6.38 GCT Semiconductor 6.39 Gemalto 6.40 Gigamon 6.41 GL Communications 6.42 Google/Alphabet 6.43 Hitachi 6.44 HPE (Hewlett Packard Enterprise) 6.45 HTC Corporation 6.46 Huawei 6.47 iBasis 6.48 IBM Corporation 6.49 IMSWorkX 6.50 InfoVista 6.51 Intel Corporation 6.52 InterDigital 6.53 Interop Technologies 6.54 Iskratel 6.55 Italtel 6.56 Keysight Technologies/Ixia 6.57 Lenovo 6.58 LG Electronics 6.59 Mavenir Systems 6.60 Meeami Technologies 6.61 Metaswitch Networks 6.62 Mobileum 6.63 Mushroom Networks 6.64 MYCOM OSI 6.65 Napatech 6.66 NEC Corporation 6.67 NetComm Wireless 6.68 NETGEAR 6.69 NETSCOUT Systems 6.70 NewNet Mobile Communications 6.71 Nokia Networks 6.72 NXP Semiconductors 6.73 Openet 6.74 Optiva 6.75 Oracle Communications 6.76 Polystar 6.77 Qualcomm 6.78 Quortus 6.79 RADCOM 6.80 Radisys Corporation 6.81 Ribbon Communications 6.82 Rohde & Schwarz 6.83 Samsung Electronics 6.84 Sandvine 6.85 Sansay 6.86 Sequans Communications 6.87 Sierra Wireless 6.88 SIGOS 6.89 Softil 6.90 Sony Mobile Communications 6.91 Spirent Communications 6.92 SPIRIT DSP 6.93 Spreadtrum Communications 6.94 Summit Tech 6.95 Syniverse Technologies 6.96 SysMech 6.97 Systemics Group 6.98 Telit Communications 6.99 TNS (Transaction Network Services) 6.100 Viavi Solutions 6.101 VMware 6.102 VoiceAge Corporation 6.103 Voipfuture 6.104 WIT Software 6.105 Xiaomi 6.106 ZTE =20 7 Chapter 7: Market Sizing & Forecasts 7.1 Global Outlook for VoLTE 7.2 VoLTE-Capable Devices 7.2.1 VoLTE-Capable Device Unit Shipments 7.2.2 VoLTE-Capable Device Unit Shipment Revenue 7.2.3 Segmentation by Form Factor 7.2.4 Handsets 7.2.4.1 Smartphones & Phablets 7.2.4.2 Feature Phones 7.2.5 Smartwatches & Wearables 7.2.6 Tablets, CPEs & Other Devices 7.2.7 IoT Modules 7.3 VoLTE Subscriptions & Service Revenue 7.3.1 VoLTE Subscriptions 7.3.2 VoLTE Service Revenue 7.3.3 Segmentation by Application 7.3.4 Voice Telephony 7.3.5 Video & Supplementary Services 7.3.6 Voice Based IoT Applications 7.4 VoLTE Infrastructure 7.4.1 Segmentation by Submarket 7.4.2 CSCF Servers 7.4.3 SBCs 7.4.4 VoLTE Application Servers 7.4.5 Other IMS Elements (HSS, BGCF, MGCF & MRF) 7.4.6 VoLTE-Capable Policy Control Solutions 7.5 Segmentation by Region 7.5.1 VoLTE-Capable Devices 7.5.2 VoLTE Subscriptions & Service Revenue 7.5.3 VoLTE Infrastructure 7.6 Asia Pacific 7.6.1 VoLTE-Capable Devices 7.6.2 VoLTE Subscriptions & Service Revenue 7.6.3 VoLTE Infrastructure 7.7 Eastern Europe 7.7.1 VoLTE-Capable Devices 7.7.2 VoLTE Subscriptions & Service Revenue 7.7.3 VoLTE Infrastructure 7.8 Latin & Central America 7.8.1 VoLTE-Capable Devices 7.8.2 VoLTE Subscriptions & Service Revenue 7.8.3 VoLTE Infrastructure 7.9 Middle East & Africa 7.9.1 VoLTE-Capable Devices 7.9.2 VoLTE Subscriptions & Service Revenue 7.9.3 VoLTE Infrastructure 7.10 North America 7.10.1 VoLTE-Capable Devices 7.10.2 VoLTE Subscriptions & Service Revenue 7.10.3 VoLTE Infrastructure 7.11 Western Europe 7.11.1 VoLTE-Capable Devices 7.11.2 VoLTE Subscriptions & Service Revenue 7.11.3 VoLTE Infrastructure =20 8 Chapter 8: Conclusion, Key Trends & Strategic Recommendations 8.1 Why is the Market Poised to Grow=3F 8.2 Competitive Industry Landscape: Acquisitions, Alliances & Consolidation 8.3 Geographic Outlook: Which Countries Offer the Highest Growth Potential=3F 8.4 Monetization: Can VoLTE Drive Revenue Growth=3F 8.5 Enabling Voice Calls for Wearables & IoT Devices 8.5.1 Certification of VoLTE-Capable IoT Modules 8.5.2 VoLTE Integration in Consumer Oriented Wearables 8.6 Operator Branded OTT Services: Implications for VoLTE 8.7 Virtualization: Moving VoLTE to the Cloud 8.8 Growing Investments in VoLTE Service Assurance 8.9 Prospects of the EVS (Enhanced Voice Services) Codec 8.10 Convergence with Wi-Fi Calling 8.10.1 Moving Towards IMS-Based Wi-Fi Calling Services 8.10.2 Future Prospects 8.11 Opportunities for MVNOs 8.11.1 Enabling Service Differentiation 8.11.2 Growing MVNE (Mobile Virtual Network Enabler) Investments in VoLTE I= nfrastructure 8.11.3 How Big is the VoLTE Service Revenue Opportunity for MVNOs=3F 8.12 WebRTC: Friend or Foe=3F 8.13 Status of RCS Adoption 8.14 Prospects of Roaming and Interconnected VoLTE Services 8.15 MCPTT over VoLTE: Enabling Critical Communications 8.16 Strategic Recommendations 8.16.1 VoLTE Solution Providers 8.16.2 Mobile Operators & MVNOs =20 List of Figures: =20 Figure 1: The CSFB Mechanism for LTE Figure 2: VoLTE via IMS Figure 3: SRVCC Network Architecture Figure 4: Video Telephony with VoLTE Figure 5: ETSI NFV Architecture Figure 6: VoLTE Industry Roadmap Figure 7: VoLTE Value Chain Figure 8: Global VoLTE-Capable Device Shipments: 2018 =96 2030 (Millions of= Units) Figure 9: Global VoLTE-Capable Device Shipment Revenue: 2018 =96 2030 ($ Bi= llion) Figure 10: Global VoLTE-Capable Device Shipments by Form Factor: 2018 =96 2= 030 (Millions of Units) Figure 11: Global VoLTE-Capable Device Shipment Revenue by Form Factor: 201= 8 =96 2030 ($ Billion) Figure 12: Global VoLTE-Capable Handset Shipments: 2018 =96 2030 (Millions = of Units) Figure 13: Global VoLTE-Capable Handset Shipment Revenue: 2018 =96 2030 ($ = Billion) Figure 14: Global VoLTE-Capable Smartphone & Phablet Shipments: 2018 =96 20= 30 (Millions of Units) Figure 15: Global VoLTE-Capable Smartphone & Phablet Shipment Revenue: 2018= =96 2030 ($ Billion) Figure 16: Global VoLTE-Capable Feature Phone Shipments: 2018 =96 2030 (Mil= lions of Units) Figure 17: Global VoLTE-Capable Feature Phone Shipment Revenue: 2018 =96 20= 30 ($ Billion) Figure 18: Global VoLTE-Capable Smartwatch & Wearable Device Shipments: 201= 8 =96 2030 (Millions of Units) Figure 19: Global VoLTE-Capable Smartwatch & Wearable Device Shipment Reven= ue: 2018 =96 2030 ($ Billion) Figure 20: Global VoLTE-Capable Tablet, CPE & Other Device Shipments: 2018 = =96 2030 (Millions of Units) Figure 21: Global VoLTE-Capable Tablet, CPE & Other Device Shipment Revenue= : 2018 =96 2030 ($ Billion) Figure 22: Global VoLTE-Capable IoT Module Shipments: 2018 =96 2030 (Millio= ns of Units) Figure 23: Global VoLTE-Capable IoT Module Shipment Revenue: 2018 =96 2030 = ($ Billion) Figure 24: Global VoLTE Subscriptions: 2018 =96 2030 (Millions) Figure 25: Global VoLTE Service Revenue: 2018 =96 2030 ($ Billion) Figure 26: Global VoLTE Service Revenue by Application: 2018 =96 2030 ($ Bi= llion) Figure 27: Global VoLTE Based Voice Telephony Service Revenue: 2018 =96 203= 0 ($ Billion) Figure 28: Global VoLTE Based Video & Supplementary Applications Service Re= venue: 2018 =96 2030 ($ Billion) Figure 29: Global VoLTE Based IoT Applications Service Revenue: 2018 =96 20= 30 ($ Billion) Figure 30: Global VoLTE Infrastructure Revenue: 2018 =96 2030 ($ Million) Figure 31: Global VoLTE Infrastructure Revenue by Submarket: 2018 =96 2030 = ($ Million) Figure 32: Global CSCF Server Revenue: 2018 =96 2030 ($ Million) Figure 33: Global SBC Revenue: 2018 =96 2030 ($ Million) Figure 34: Global VoLTE Application Server Revenue: 2018 =96 2030 ($ Millio= n) Figure 35: Global Other IMS Elements (HSS, BGCF, MGCF & MRF) Revenue: 2018 = =96 2030 ($ Million) Figure 36: Global VoLTE-Capable Policy Control Solution Revenue: 2018 =96 2= 030 ($ Million) Figure 37: VoLTE-Capable Device Shipments by Region: 2018 =96 2030 (Million= s of Units) Figure 38: VoLTE-Capable Device Shipment Revenue by Region: 2018 =96 2030 (= $ Billion) Figure 39: VoLTE Subscriptions by Region: 2018 =96 2030 (Millions) Figure 40: VoLTE Service Revenue by Region: 2018 =96 2030 ($ Billion) Figure 41: VoLTE Infrastructure Revenue by Region: 2018 =96 2030 ($ Million) Figure 42: Asia Pacific VoLTE-Capable Device Shipments: 2018 =96 2030 (Mill= ions of Units) Figure 43: Asia Pacific VoLTE-Capable Device Shipment Revenue: 2018 =96 203= 0 ($ Billion) Figure 44: Asia Pacific VoLTE Subscriptions: 2018 =96 2030 (Millions) Figure 45: Asia Pacific VoLTE Service Revenue: 2018 =96 2030 ($ Billion) Figure 46: Asia Pacific VoLTE Infrastructure Revenue: 2018 =96 2030 ($ Mill= ion) Figure 47: Eastern Europe VoLTE-Capable Device Shipments: 2018 =96 2030 (Mi= llions of Units) Figure 48: Eastern Europe VoLTE-Capable Device Shipment Revenue: 2018 =96 2= 030 ($ Billion) Figure 49: Eastern Europe VoLTE Subscriptions: 2018 =96 2030 (Millions) Figure 50: Eastern Europe VoLTE Service Revenue: 2018 =96 2030 ($ Billion) Figure 51: Eastern Europe VoLTE Infrastructure Revenue: 2018 =96 2030 ($ Mi= llion) Figure 52: Latin & Central America VoLTE-Capable Device Shipments: 2018 =96= 2030 (Millions of Units) Figure 53: Latin & Central America VoLTE-Capable Device Shipment Revenue: 2= 018 =96 2030 ($ Billion) Figure 54: Latin & Central America VoLTE Subscriptions: 2018 =96 2030 (Mill= ions) Figure 55: Latin & Central America VoLTE Service Revenue: 2018 =96 2030 ($ = Billion) Figure 56: Latin & Central America VoLTE Infrastructure Revenue: 2018 =96 2= 030 ($ Million) Figure 57: Middle East & Africa VoLTE-Capable Device Shipments: 2018 =96 20= 30 (Millions of Units) Figure 58: Middle East & Africa VoLTE-Capable Device Shipment Revenue: 2018= =96 2030 ($ Billion) Figure 59: Middle East & Africa VoLTE Subscriptions: 2018 =96 2030 (Million= s) Figure 60: Middle East & Africa VoLTE Service Revenue: 2018 =96 2030 ($ Bil= lion) Figure 61: Middle East & Africa VoLTE Infrastructure Revenue: 2018 =96 2030= ($ Million) Figure 62: North America VoLTE-Capable Device Shipments: 2018 =96 2030 (Mil= lions of Units) Figure 63: North America VoLTE-Capable Device Shipment Revenue: 2018 =96 20= 30 ($ Billion) Figure 64: North America VoLTE Subscriptions: 2018 =96 2030 (Millions) Figure 65: North America VoLTE Service Revenue: 2018 =96 2030 ($ Billion) Figure 66: North America VoLTE Infrastructure Revenue: 2018 =96 2030 ($ Mil= lion) Figure 67: Western Europe VoLTE-Capable Device Shipments: 2018 =96 2030 (Mi= llions of Units) Figure 68: Western Europe VoLTE-Capable Device Shipment Revenue: 2018 =96 2= 030 ($ Billion) Figure 69: Western Europe VoLTE Subscriptions: 2018 =96 2030 (Millions) Figure 70: Western Europe VoLTE Service Revenue: 2018 =96 2030 ($ Billion) Figure 71: Western Europe VoLTE Infrastructure Revenue: 2018 =96 2030 ($ Mi= llion) Figure 72: Global Spending on VoLTE Service Assurance Solutions: 2018 =96 2= 030 ($ Million) Figure 73: Audio Bandwidth Comparison between EVS and Legacy Codecs Figure 74: Wi-Fi Calling Scenarios Figure 75: IMS-based Wi-Fi Calling Service Architecture Figure 76: Managed IMS Core/IP Services for MVNOs Figure 77: Global VoLTE Service Revenue over MVNO Networks: 2018 =96 2030 (= $ Billion) Figure 78: RCS Business Model =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 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com =20 From owner-freebsd-ppc@freebsd.org Thu Apr 19 14:07:36 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 BEE77FA81B3 for ; Thu, 19 Apr 2018 14:07:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 51E8D7B2DB for ; Thu, 19 Apr 2018 14:07:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0D477FA81AE; Thu, 19 Apr 2018 14:07:36 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDA76FA81AD for ; Thu, 19 Apr 2018 14:07: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 82C6B7B2B6 for ; Thu, 19 Apr 2018 14:07: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 CDD651BF8E for ; Thu, 19 Apr 2018 14:07: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 w3JE7YTw057456 for ; Thu, 19 Apr 2018 14:07:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3JE7Y59057455 for ppc@FreeBSD.org; Thu, 19 Apr 2018 14:07: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: ppc@FreeBSD.org Subject: [Bug 226974] kernel DSI read trap at boot Date: Thu, 19 Apr 2018 14:07:35 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: leandro.lupori@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2018 14:07:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226974 --- Comment #13 from Leandro Lupori --- The fix is under review, here: https://reviews.freebsd.org/D15121 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Thu Apr 19 18:02:39 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 E73E1F91A51 for ; Thu, 19 Apr 2018 18:02:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7AF0472583 for ; Thu, 19 Apr 2018 18:02:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3C78FF91A50; Thu, 19 Apr 2018 18:02:38 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A3E1F91A4E for ; Thu, 19 Apr 2018 18:02:38 +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 BAB2272579 for ; Thu, 19 Apr 2018 18:02: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 EC7F91DF7C for ; Thu, 19 Apr 2018 18:02: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 w3JI2afs021660 for ; Thu, 19 Apr 2018 18:02:36 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3JI2aO6021650 for ppc@FreeBSD.org; Thu, 19 Apr 2018 18:02: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: ppc@FreeBSD.org Subject: [Bug 226974] kernel DSI read trap at boot Date: Thu, 19 Apr 2018 18:02:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: swills@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2018 18:02:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226974 --- Comment #14 from Steve Wills --- (In reply to Leandro Lupori from comment #13) This fixed it for me. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Thu Apr 19 18:34:49 2018 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C1F73F945D7 for ; Thu, 19 Apr 2018 18:34:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4925278DCF for ; Thu, 19 Apr 2018 18:34:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 08FD5F945D6; Thu, 19 Apr 2018 18:34:49 +0000 (UTC) Delivered-To: ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB2FDF945D5 for ; Thu, 19 Apr 2018 18:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8840978DC9 for ; Thu, 19 Apr 2018 18:34:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id AEBE51E38D for ; Thu, 19 Apr 2018 18:34:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3JIYlQ4002586 for ; Thu, 19 Apr 2018 18:34:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3JIYlcl002585 for ppc@FreeBSD.org; Thu, 19 Apr 2018 18:34:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ppc@FreeBSD.org Subject: [Bug 226974] kernel DSI read trap at boot Date: Thu, 19 Apr 2018 18:34:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2018 18:34:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226974 --- Comment #15 from commit-hook@freebsd.org --- A commit references this bug: Author: nwhitehorn Date: Thu Apr 19 18:34:38 UTC 2018 New revision: 332788 URL: https://svnweb.freebsd.org/changeset/base/332788 Log: Fix detection of memory overlap with the kernel in the case where a memory region marked "available" by firmware is contained entirely in the kernel. This had a tendency to happen with FDTs passed by loader, though could for other reasons as well, and would result in the kernel slowly cannibalizing itself for other purposes, eventually resulting in a crash. A similar fix is needed for mmu_oea.c and should probably just be rolled at that point into some generic code in platform.c for taking a mem_region list and removing chunks. PR: 226974 Submitted by: leandro.lupori@gmail.com Reviewed by: jhibbits Differential Revision: D15121 Changes: head/sys/powerpc/aim/mmu_oea64.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri Apr 20 17:23:08 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 56B45F85B2F for ; Fri, 20 Apr 2018 17:23:08 +0000 (UTC) (envelope-from jau789@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 BA2CF6A1F7 for ; Fri, 20 Apr 2018 17:23:07 +0000 (UTC) (envelope-from jau789@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id d20-v6so6201531lfe.3 for ; Fri, 20 Apr 2018 10:23:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QW8TbcD0udqpcKQ1pPR3fFMk4PPkYgXHBx077kTkUgU=; b=uNLYoOy1US+WzGlXGodVsPnzaY0tN7+oEkNE+kPVmvFzJP8DaK5QKw7AuTCLbADp7s nY4VtJOMZx314vYJbmeMCEywsXGBuEc2kQICLYSNAudzDPUfh5CiKmZ2HET+qWkhR1pm Lio5DOaZtYx0dO/fBaFNfwaNdvl1/yz9ndikOTCrhrPVXS2oLD2tkIdAU92YMrp/PcDJ dvr1ZmYXp9VX0EdMzm8NFbnoz/aTl9p3y+HXyy+FkjXhD+IwgmG06VdblSHo40g9CT/s aqEm/qk+ul7Oknng+ySmxpUFIiOXSl6HopWBfWHaVnicanUsxAhUUvKqelBsAwLzXfh+ SIdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QW8TbcD0udqpcKQ1pPR3fFMk4PPkYgXHBx077kTkUgU=; b=Uk7tgkIwlLtxZQJ/xASwPLP09PhrCjGEXQ12FPQBhUMhUoeiOOg2mlqFwK1hdE3hk4 RZGop/A+hCuIvj1fsa0YhLhDfBodwapzIQSAG+ogyGmnA3I7+s6ndUpSCTtMfj5OFNAL WzFQ8Vp4fLvoJFJntBaNWBLB1QfjBZ1qKCo02Mw9nHvpvqNThBi/O9UQXaKqvQKJ9CbM XEMz1Zlxfwi2AWCLliDFb1hmsL3RgHUiXeLbtqP967/soQOdLMT+hxRWYYtwfKFxyzxE uJDhwZxwj5KLVPOsvetDw2avHgUjWUIBqTJsWoD+QNOnAWE46cK0rDdgU+3nmT+VsGrB QfWA== X-Gm-Message-State: ALQs6tDhVgSv+az+MdZ1LpxjtgMCVrd17yE3ivm8hQv0mu2p7Ph5H/5Q NK225kZ5ueYKGRUSQmj3/UMAFw== X-Google-Smtp-Source: AIpwx4+SkbMdIupRfewPXG7jjiFV703XypfLY9mGizKI0iR0/qhhGtLy/l0y9naAhG6wqE1b2cdD1Q== X-Received: by 10.46.77.214 with SMTP id c83mr7412007ljd.126.1524244986165; Fri, 20 Apr 2018 10:23:06 -0700 (PDT) Received: from [192.168.1.193] (xdsl-205-1.nblnetworks.fi. [83.145.205.1]) by smtp.gmail.com with ESMTPSA id z18-v6sm1431688lfj.8.2018.04.20.10.23.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Apr 2018 10:23:05 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: 11.1 release CD image panics very early during boot on ppc. From: Jukka Ukkonen X-Mailer: iPad Mail (15E216) In-Reply-To: Date: Fri, 20 Apr 2018 20:23:03 +0300 Cc: FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Justin Hibbits 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, 20 Apr 2018 17:23:08 -0000 So, I tried setting debug.debugger_on_panic=3D1 and =E2=80=9Dboot -v=E2=80=9D= . The first time I tried the ofw did not see the full-HD display which was connected to another system via a KVM switch at that time. I only got the KVM switched to the correct system only when I had got the booting stopped at the ofw prompt. So, the early boot assumed a very traditional 80 columns by 25 to 30 lines display with a large font. Surprisingly the 11.1 CD booted just fine. Obviously I wanted to double check and rebooted the system. This time the display was connected via the KVM switch to the system right from the start. The ofw obviously figured out the true full-HD resolution and used a tiny font. When the kernel=20 got control of the system it selected a bit larger font, showed some of the autoconfig messages, and went down hard no matter whether I set the debug.debugger_on_panic=3D1 or not. This raises the obvious assumption that there must be something going awry with how vt and ofw communicate and how they try to control the display. Supposedly this could lead to mismanagement of a large chunk of memory such that even the debugger is left totally powerless when the crash happens. Because vt is new to 11.1 and the properly booting 10.4 uses sc, memory corruption seems like a plausible explanation to the mysterious crash. I hope this helps. --jau > On 17 Apr 2018, at 18.11, Justin Hibbits wrote: >=20 > Hi, >=20 >> On Sun, Apr 15, 2018 at 2:10 AM, Jukka Ukkonen wrote: >>=20 >> I had a bit of an accident with my old PowerMac G4 which had been >> running FreeBSD-10.4. To fix the mess I had to boot the system from >> a CD image. So, I decided to try 11.1 while at it. To my astonishment >> and disappointment the 11.1 images (both CD and DVD) paniced >> very early on during the boot. The messages flashed past the screen >> so quickly that I cannot be really sure about anything, but it kind of >> seemed like the issue might be yet another installment of the SPRG >> related problems (in ofw_machdep.c) which have been troubling >> ppc64 systems before. >> The 10.4 CD image boots just fine on ppc. >>=20 >> --jau >=20 > Can you try booting with 'boot -v' and also setting at the loader > debug.debugger_on_panic=3D1? I think it's set to 0 on release ISOs, so > this should let you get a screen capture. >=20 > - Justin From owner-freebsd-ppc@freebsd.org Sat Apr 21 00:53:18 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 B84F0FB0980 for ; Sat, 21 Apr 2018 00:53:18 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic313-11.consmr.mail.ne1.yahoo.com (sonic313-11.consmr.mail.ne1.yahoo.com [66.163.185.34]) (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 527676EE6D for ; Sat, 21 Apr 2018 00:53:18 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: Nlm0ib4VM1kKbJ20fb5qDWJTSX9J.jKdrYULqzDns47hZHk1igFEmTAvG7UnVsO uzSp7OEmDSKy6utMA82wBSnXl6_Cj0X9FvIwQHArSUGaeuQpkIMmrFYcw8QPtyMuNBGO62FRcvH3 nf6pfjfw41ZHWeEva_lGD9XLUGNpktiZ1IpxtyS3fmQ1oeoOeC2lkXFsCACT7jyuUkmbqBylkuOQ Os0k5L2922UcBJ8wsUfG2ZAeWQRaSaGBIwUsN.h9XxiLIbFWkGgmLS2VP087nEMS8Mh1x4Hwb.sA 9RnV3h.pSGLZD.mily0Zj0pkEFEOvU5DbvgDlxUhNklraXp0x8ZXyytq9lP.dS8Y9qPwA1md3C9K OUca_8dl7g.I_UlG1E6eYER_qJ4QCVLj.mT4FBm9IKdZfFxhjuOB2azUCQKCX.wzPpthN8RxFLgF KUjP0VIfw8RnYcQKVp3GYdHF.YmWYI.i2NAMmtfcBgdItTNOPjc0p_UA0o1J78sPs5pWtpCiiVrE uoerVWRkJL67iZNsUevopYozSBiEz5pIt4BP7Q4lUjMIUTFARafs4Is8LyuAEk3Q3keODXjGaK99 XxxYvXzKWiVwbWem4fw0N0idtR1Za Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.ne1.yahoo.com with HTTP; Sat, 21 Apr 2018 00:53:17 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp424.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID e1b0cf39c9f983e0c288881b2bafeaf8; Sat, 21 Apr 2018 00:43:07 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: 11.1 release CD image panics very early during boot on ppc. From: Mark Millard In-Reply-To: Date: Fri, 20 Apr 2018 17:43:05 -0700 Cc: Justin Hibbits , FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Jukka Ukkonen X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2018 00:53:19 -0000 On 2018-Apr-20, at 10:23 AM, Jukka Ukkonen wrote: > So, I tried setting debug.debugger_on_panic=3D1 and =E2=80=9Dboot = -v=E2=80=9D. > The first time I tried the ofw did not see the full-HD display > which was connected to another system via a KVM switch at > that time. I only got the KVM switched to the correct system > only when I had got the booting stopped at the ofw prompt. > So, the early boot assumed a very traditional 80 columns by > 25 to 30 lines display with a large font. Surprisingly the 11.1 CD > booted just fine. Obviously I wanted to double check and rebooted > the system. This time the display was connected via the KVM > switch to the system right from the start. The ofw obviously figured > out the true full-HD resolution and used a tiny font. When the kernel=20= > got control of the system it selected a bit larger font, showed some > of the autoconfig messages, and went down hard no matter whether > I set the debug.debugger_on_panic=3D1 or not. > This raises the obvious assumption that there must be something > going awry with how vt and ofw communicate and how they try to > control the display. Supposedly this could lead to mismanagement > of a large chunk of memory such that even the debugger is left > totally powerless when the crash happens. Because vt is new to 11.1 > and the properly booting 10.4 uses sc, memory corruption seems > like a plausible explanation to the mysterious crash. >=20 > I hope this helps. >=20 > --jau It has been a long time since I've booted an old PowerMac with vt on my larger displays. I actually build a kernel with both vt and sc in it (no PS3 support) and normally boot sc. My historical reason for avoiding vt was the early stages having a fixed sized memory area tied to what was to be displayed and it going out of bounds of that area and trashing things when I had a large enough display attached. But it has been a very long time since I've done such experiments in this area. So take this note as only suggestive. As I remember, the display types that had the problem were 2560x1440 or something like that. vt would boot fine for smaller displays that I used, such as 1920x1200, as I remember. Looking in the list history (10.x time frames): = https://lists.freebsd.org/pipermail/freebsd-ppc/2014-September/007260.html= = https://lists.freebsd.org/pipermail/freebsd-ppc/2014-September/007263.html= It mattered for GeForce 7800 GT vs. Radeon X1950 for the 2560x1440 behavior. As I remember, the maximum screen size involved in the kernel was changed as Nathan indicates, but still to some fixed figures for the early code. Likely still a problem for a sufficiently large display. (Beyond what I have access to now.) (The xf86-video-scfb suggestion did not work for the X1950. I stopped using X on the old PowerMac long ago.) >> On 17 Apr 2018, at 18.11, Justin Hibbits = wrote: >>=20 >> Hi, >>=20 >>> On Sun, Apr 15, 2018 at 2:10 AM, Jukka Ukkonen = wrote: >>>=20 >>> I had a bit of an accident with my old PowerMac G4 which had been >>> running FreeBSD-10.4. To fix the mess I had to boot the system from >>> a CD image. So, I decided to try 11.1 while at it. To my = astonishment >>> and disappointment the 11.1 images (both CD and DVD) paniced >>> very early on during the boot. The messages flashed past the screen >>> so quickly that I cannot be really sure about anything, but it kind = of >>> seemed like the issue might be yet another installment of the SPRG >>> related problems (in ofw_machdep.c) which have been troubling >>> ppc64 systems before. >>> The 10.4 CD image boots just fine on ppc. >>>=20 >>> --jau >>=20 >> Can you try booting with 'boot -v' and also setting at the loader >> debug.debugger_on_panic=3D1? I think it's set to 0 on release ISOs, = so >> this should let you get a screen capture. >>=20 >> - Justin =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-ppc@freebsd.org Sat Apr 21 08:10: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 0BFFCFAD894 for ; Sat, 21 Apr 2018 08:10:30 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic316-22.consmr.mail.ne1.yahoo.com (sonic316-22.consmr.mail.ne1.yahoo.com [66.163.187.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A0409732AB for ; Sat, 21 Apr 2018 08:10:29 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: vWwurOUVM1lW0VGtKMHaaeDZ78IQGBLLT1y2mw2PF3.5JO72dWUIQ9gq0meB.rT wlGuBb8VIGxWNWJwvc9ZWHXRKxGzEATld3ZZaPON6rr7wxoo9QA.JflldxiJbpEAwmfMdtxCwk.v 9mtAd5xuenG.V9m_RmKAkVD7i70Do4n8H9EW6NAHjrS7jlRFTX1XTQMkaFnP6h5nI450dnh6lFzr WLFO.MczFqifuOmJj.5wIkmDiCXeX.wU9_tQ49s46vhMWw8WPscaczle0P4OLWNrS9rE8HDHKjr_ lAWcNw1iHtYRBT5dClKxgP5UiuPZFEVIw5ghtM3fI56b41myY27YrEZWLpdiKMZBagdiS04qtWh3 k2mq1vumVAtfPdMtkiArnXTThyLfStg3OVgmA5g35uPqGtb9FnkQ4GeVNtsiRUZBoywC9Cw6X84N afjIv7QNQNqqUK2MAcZKvoeQrcEuxx6LeOTTN9nqnJVEW7HzeW1MGhtko.u78CZiRer5YBfeOoIU yQFB5TwOQOh77cqOPqV2bq01RJ4JS3zGLo5vxFoZGfC7DqhXvjIqxasLAu4MZZYT0VUUZBk0Gcy2 LQg18dBrJ04yzkg-- Received: from sonic.gate.mail.ne1.yahoo.com by sonic316.consmr.mail.ne1.yahoo.com with HTTP; Sat, 21 Apr 2018 08:10:23 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp415.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 21e4afd4ecf8e319c37122e1e054ab41; Sat, 21 Apr 2018 08:10:22 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: 11.1 release CD image panics very early during boot on ppc. From: Mark Millard In-Reply-To: Date: Sat, 21 Apr 2018 01:10:20 -0700 Cc: Justin Hibbits , FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <5770E2A2-9AD8-4B5A-A211-E04326B2A997@yahoo.com> References: To: Jukka Ukkonen X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2018 08:10:30 -0000 On 2018-Apr-20, at 5:43 PM, Mark Millard = wrote: > On 2018-Apr-20, at 10:23 AM, Jukka Ukkonen wrote: >=20 >=20 >> So, I tried setting debug.debugger_on_panic=3D1 and =E2=80=9Dboot = -v=E2=80=9D. >> The first time I tried the ofw did not see the full-HD display >> which was connected to another system via a KVM switch at >> that time. I only got the KVM switched to the correct system >> only when I had got the booting stopped at the ofw prompt. >> So, the early boot assumed a very traditional 80 columns by >> 25 to 30 lines display with a large font. Surprisingly the 11.1 CD >> booted just fine. Obviously I wanted to double check and rebooted >> the system. This time the display was connected via the KVM >> switch to the system right from the start. The ofw obviously figured >> out the true full-HD resolution and used a tiny font. When the kernel=20= >> got control of the system it selected a bit larger font, showed some >> of the autoconfig messages, and went down hard no matter whether >> I set the debug.debugger_on_panic=3D1 or not. >> This raises the obvious assumption that there must be something >> going awry with how vt and ofw communicate and how they try to >> control the display. Supposedly this could lead to mismanagement >> of a large chunk of memory such that even the debugger is left >> totally powerless when the crash happens. Because vt is new to 11.1 >> and the properly booting 10.4 uses sc, memory corruption seems >> like a plausible explanation to the mysterious crash. >>=20 >> I hope this helps. >>=20 >> --jau >=20 > It has been a long time since I've booted an old PowerMac with > vt on my larger displays. I actually build a kernel with both > vt and sc in it (no PS3 support) and normally boot sc. >=20 > My historical reason for avoiding vt was the early stages having > a fixed sized memory area tied to what was to be displayed and it > going out of bounds of that area and trashing things when I had a > large enough display attached. >=20 > But it has been a very long time since I've done such experiments > in this area. So take this note as only suggestive. >=20 > As I remember, the display types that had the problem were > 2560x1440 or something like that. vt would boot fine for > smaller displays that I used, such as 1920x1200, as I > remember. >=20 > Looking in the list history (10.x time frames): >=20 > = https://lists.freebsd.org/pipermail/freebsd-ppc/2014-September/007260.html= > = https://lists.freebsd.org/pipermail/freebsd-ppc/2014-September/007263.html= >=20 > It mattered for GeForce 7800 GT vs. Radeon X1950 for the 2560x1440 > behavior. >=20 > As I remember, the maximum screen size involved in the kernel > was changed as Nathan indicates, but still to some fixed figures > for the early code. Likely still a problem for a sufficiently > large display. (Beyond what I have access to now.) >=20 > (The xf86-video-scfb suggestion did not work for the X1950. I stopped > using X on the old PowerMac long ago.) It looks like later there was a size increase to 4096x2400: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210382 https://svnweb.freebsd.org/base?view=3Drevision&revision=3D303043 Looking at the modern code quickly, what I see is (material from multiple files): #ifdef SC_HISTORY_SIZE #define VBF_DEFAULT_HISTORY_SIZE SC_HISTORY_SIZE #else #define VBF_DEFAULT_HISTORY_SIZE 500 #endif #ifndef VT_FB_MAX_WIDTH #define VT_FB_MAX_WIDTH 4096 #endif #ifndef VT_FB_MAX_HEIGHT #define VT_FB_MAX_HEIGHT 2400 #endif #define PIXEL_WIDTH(w) ((w) / 8) #define PIXEL_HEIGHT(h) ((h) / 16) #define _VTDEFH MAX(100, PIXEL_HEIGHT(VT_FB_MAX_HEIGHT)) #define _VTDEFW MAX(200, PIXEL_WIDTH(VT_FB_MAX_WIDTH)) (NOTE: _VTDEFH =3D=3D 2400/16 =3D=3D 150 and _VTDEFW =3D=3D 4096/8 =3D=3D= 512) (So if the SC_HISTORY_SIZE default is 100, as documented, and is defined, it is smaller than _VTDEFH.) static term_char_t vt_constextbuf[(_VTDEFW) * = (VBF_DEFAULT_HISTORY_SIZE)]; static term_char_t *vt_constextbufrows[VBF_DEFAULT_HISTORY_SIZE]; (NOTE: The above is problematical for: SC_HISTORY_SIZE =3D=3D 100 =3D=3D VBF_DEFAULT_HISTORY_SIZE but _VTDEFH =3D=3D 150 =3D=3D .vw_buf.vb_scr_size.tp_row) .vw_buf =3D { .vb_buffer =3D &vt_constextbuf[0], .vb_rows =3D &vt_constextbufrows[0], .vb_history_size =3D VBF_DEFAULT_HISTORY_SIZE, .vb_flags =3D VBF_STATIC, . . . .vb_scr_size =3D { .tp_row =3D _VTDEFH, .tp_col =3D _VTDEFW, }, . . . vtbuf_init(struct vt_buf *vb, const term_pos_t *p) { . . . vb->vb_scr_size =3D *p; vb->vb_history_size =3D VBF_DEFAULT_HISTORY_SIZE; if ((vb->vb_flags & VBF_STATIC) =3D=3D 0) { sz =3D vb->vb_history_size * p->tp_col * = sizeof(term_char_t); vb->vb_buffer =3D malloc(sz, M_VTBUF, M_WAITOK | = M_ZERO); sz =3D vb->vb_history_size * sizeof(term_char_t *); vb->vb_rows =3D malloc(sz, M_VTBUF, M_WAITOK | M_ZERO); } . . . vtbuf_grow(struct vt_buf *vb, const term_pos_t *p, unsigned int = history_size) { . . . vb->vb_history_size =3D history_size; vb->vb_buffer =3D new; vb->vb_rows =3D rows; vb->vb_flags &=3D ~VBF_STATIC; vb->vb_scr_size =3D *p; vtbuf_init_rows(vb); . . . (NOTE: That last vtbuf_init_rows(vb) can increase vb->vb_history_size without adjusting the allocations associated with vb->vb_rows and vb->vb_buffer, despite overwriting the content of vb->vb_rows based on the potentially larger size and referencing more based off of vb->vb_buffer:) static void vtbuf_init_rows(struct vt_buf *vb) { int r; =20 vb->vb_history_size =3D MAX(vb->vb_history_size, = vb->vb_scr_size.tp_row); =20 for (r =3D 0; r < vb->vb_history_size; r++) vb->vb_rows[r] =3D &vb->vb_buffer[r * = vb->vb_scr_size.tp_col]; } (NOTE: No call to vtbuf_init when vtbuf_init_rows increases = vb->vb_history_size .) May be some of this is tied to what you ware seeing. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)