From owner-freebsd-ppc@freebsd.org Sun Feb 26 20:47:53 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7CA4CEEF79 for ; Sun, 26 Feb 2017 20:47:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 974F29BF for ; Sun, 26 Feb 2017 20:47:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1QKlr1g039125 for ; Sun, 26 Feb 2017 20:47:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 217375] installer: powerpc kernel reboots before reaching installer (ibook key lime se) Date: Sun, 26 Feb 2017 20:47:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE 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: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to 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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2017 20:47:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217375 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-ppc@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Mon Feb 27 09:32:59 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC835CEEFDC for ; Mon, 27 Feb 2017 09:32:59 +0000 (UTC) (envelope-from eekee57@fastmail.fm) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (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 B429BA6A for ; Mon, 27 Feb 2017 09:32:58 +0000 (UTC) (envelope-from eekee57@fastmail.fm) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 03DB1208AD for ; Mon, 27 Feb 2017 04:32:58 -0500 (EST) Received: from web2 ([10.202.2.212]) by compute1.internal (MEProxy); Mon, 27 Feb 2017 04:32:58 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Cmk9jRoH6FXuX671dKXi3IYc9n g=; b=arBjv8BtnLgQ96l+mlth4iaVu1i0xk0eK906k+xdAYFMjRrg+bMlAeADVA kqpCWOzrOg5sQiKZbLZqh7zEPcMcKN8fjFcaDPZr2vQ3zVsjF3tQfnn59OD08TyX 58xJvZA/ZiCjpHm8kSEkudmf6aOd5E67SwKpTi99SF/4Exmwo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=Cm k9jRoH6FXuX671dKXi3IYc9ng=; b=ZwUHB7n/U95fZMqrSloUB05xqFsfrl0axg yIm37Qzw3sl5TjJH432A76T5bCgOmW2u9K2G6F/JtJk9O7817wWAdFXeExnMP+T6 Ph6kOEonQG/DliDcuPFtv0io7UF9HMktAF3MvO5UvfaP1xoNDsdEtPKsOUNaa9vN GvWzdTbnI= X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id C304C626D2; Mon, 27 Feb 2017 04:32:57 -0500 (EST) Message-Id: <1488187977.3418832.893931616.102242DF@webmail.messagingengine.com> From: Ethan Grammatikidis To: freebsd-ppc@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-715c2c0c References: In-Reply-To: Subject: Re: Error with Install CD on PPC iMac G3 Date: Mon, 27 Feb 2017 09:32:57 +0000 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 09:33:00 -0000 On Sat, Feb 4, 2017, at 07:35 PM, Garrett Zuhoski wrote: > Hi there, > > I have an old iMac that I was wanting to play around with, and since linux > has been dropping PPC support left and right, I figured this would be a > good opportunity to play around with other Unices like FreeBSD. > > Upon boot, the bootloader comes up and loads the kernel, then quickly > scrolling text followed by a reboot of the machine. > > Here is a photo of the error: http://i.imgur.com/ZgBBLjG.png > > Someone on Freenode told me "the exc register is being set wrong clearly > and getting into the wrong case of the switch block" (I'm not sure what > that means) i had the exact same experience with an ibook, and filed a bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217375 i'm amazed you managed to get a photo, i don't think i could, but then it's doubly hard to see on my ibook's old flat panel. > > Any help would be appreciated. Thanks! -- I'm too old to use vi. From owner-freebsd-ppc@freebsd.org Mon Feb 27 09:38:59 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AAFF2CE9171 for ; Mon, 27 Feb 2017 09:38:59 +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 mx1.freebsd.org (Postfix) with ESMTPS id 9A532B77 for ; Mon, 27 Feb 2017 09:38:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1R9cxU0030708 for ; Mon, 27 Feb 2017 09:38:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 217375] installer: powerpc kernel reboots before reaching installer (ibook key lime se) Date: Mon, 27 Feb 2017 09:38:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eekee57@fastmail.fm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 09:38:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217375 --- Comment #4 from eekee57@fastmail.fm --- Seems I'm not the only one with the issue: https://lists.freebsd.org/pipermail/freebsd-ppc/2017-February/008675.html At least he managed to get a photo of the screen. I could try, but between = my fatigue and coordination issues and the nature of the screen, I don't think= I'd succeed. What I *could* do is get a serial port to replace the internal modem, for serial console. I've been meaning to get one anyway. This of course assumes there's one to fit in an ibook as opposed to an imac, but i expect there is. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Mon Feb 27 10:46:56 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A3E4CEFCD3 for ; Mon, 27 Feb 2017 10:46: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 mx1.freebsd.org (Postfix) with ESMTPS id 39AC190F for ; Mon, 27 Feb 2017 10:46:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1RAktNU082414 for ; Mon, 27 Feb 2017 10:46:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 217375] installer: powerpc kernel reboots before reaching installer (ibook key lime se) Date: Mon, 27 Feb 2017 10:46:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eekee57@fastmail.fm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity 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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 10:46:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217375 eekee57@fastmail.fm changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Mon Feb 27 15:26:25 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2104CF0750 for ; Mon, 27 Feb 2017 15:26: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 mx1.freebsd.org (Postfix) with ESMTPS id D1744FCF for ; Mon, 27 Feb 2017 15:26:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v1RFQP1M028675 for ; Mon, 27 Feb 2017 15:26:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 217375] installer: powerpc kernel reboots before reaching installer (ibook key lime se) Date: Mon, 27 Feb 2017 15:26:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tgl@sss.pgh.pa.us X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ppc@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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2017 15:26:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217375 Tom Lane changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tgl@sss.pgh.pa.us --- Comment #5 from Tom Lane --- (In reply to eekee57@fastmail.fm from comment #4) > At least he managed to get a photo of the screen. I could try, but betwee= n my fatigue > and coordination issues and the nature of the screen, I don'= t think I'd succeed. I've successfully captured such things by taking a video of the screen and = then extracting just the last frame before it goes black. Doesn't require too m= uch coordination, just a phone that can do video. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Tue Feb 28 16:24:34 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BDEFCF1B3B for ; Tue, 28 Feb 2017 16:24:34 +0000 (UTC) (envelope-from 96774@yossebenmo.mktenvios.net) Received: from mail6208.hm8307.lwdlv.com.br (mail6208.hm8307.lwdlv.com.br [179.188.6.208]) by mx1.freebsd.org (Postfix) with ESMTP id DA52F1F2 for ; Tue, 28 Feb 2017 16:24:33 +0000 (UTC) (envelope-from 96774@yossebenmo.mktenvios.net) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=lw20140124; d=mktenvios.net; h=Date:From:Reply-To:To:Subject:Mime-Version:Content-Type:List-Unsubscribe:Message-ID; bh=vWCv55tCk7kMeLhivO3O3GgQRLA=; b=cr2w7i/eUwo9gtyG9x2F9YDy7Thhp1m49gHKlENK7JrAwND/EL1JirMlW28Bj0N0+KSwD21wTq/S dbkV9CO8QXQMwD0PG7sS8Ly5r3zsJlcRUPs+SA9iVpWMXyhfHH3Xec9fAxnpCRtJnQVOMdw7cs8J xJaMi/aibzoL7K2vtBM= Received: from localhost (186.202.135.196) by mail6208.hm8307.lwdlv.com.br id hmmi4416ad47 for ; Tue, 28 Feb 2017 13:19:19 -0300 (envelope-from <96774@yossebenmo.mktenvios.net>) Date: Tue, 28 Feb 2017 13:19:19 -0300 From: Support Reply-To: info@beyond3000.net To: freebsd-ppc@freebsd.org Subject: We received unauthorized action Mime-Version: 1.0 Precedence: bulk x-account-id: 96774 x-contact-id: 1926711 x-envelope-id: 4 x-message-id: 4 x-locaweb-id: 0x7EcftBTNO24GQTdO6RaPgZ0iTvVB5mCMnVEbLmXFlLPki2d-WDqVkH_bIlIw4yetGYdp7bw8WRmOzOBvSyAY55XkwbAg1r7qfDiYT6GLJf8khPz7AopeBTaJEUMDloy0xZWchPyLkUgvcVX5_Jb09SzoHNrpelu9PW0LM2eYQ60VEG-Bz7ltknfxG0W7K_ x-locaweb-id2: MjI1Mzc1NzA3MDZmNzI3NDIyMjAzYzY5NmU2NjZmNDA2MjY1Nzk2ZjZlNjQzMzMwMzAzMDJlNmU2NTc0M2U= Message-ID: <0.6.0.A.1D291DE6A1D88B0.182E93@mail6208.hm8307.lwdlv.com.br> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 16:24:34 -0000 PamyP2avl3 We de4tecfted tha3t soomeonfe louggedn iwnto your 6aaccoudnt 9from a3n1 u= nknowan device an5d bir1owsger. Thiats why as a1 jsrecyurity mebasiurne iwve harvue to blnocke ty8okuxru = 9accouant to keiejp 5yonuv s2afef gfrom unavupthornised arctdivitgies. Was thzaht byo0u3 ? February 26, 2017 at 11:36 PM Loxgi6n p0lace : Lahore, Pakistan If noot jpcloease reov0iezw thgi8s activity as rs5oozn0 as1 pmo2sksi0byl6= e b6y ecompleti0ng jsomle kdseetva9ilosh 5t3o riezstore t7hec fulpli acce= ss6 tno yourt akcclokuntx. Roexstore1 Adccescsq S1iznceerljyu, PaoyPa1l Toeagma. Se voc=C3=AA n=C3=A3o deseja mais receber nossos e-mails, cancele sua ins= cri=C3=A7=C3=A3o atrav=C3=A9s do link %{link}= From owner-freebsd-ppc@freebsd.org Wed Mar 1 06:14:01 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7C63CCF58CD; Wed, 1 Mar 2017 06:14:01 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E5A2194E; Wed, 1 Mar 2017 06:14:01 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-pf0-x242.google.com with SMTP id x66so2588423pfb.1; Tue, 28 Feb 2017 22:14:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=233XtfuJMAM/18yXPcEhdSiqp5xPDvbaw672hL8Hwp4=; b=CDYVSABTXdewXuwScg9TGcyTqjs0KPR1CjTpz0SX7m910LulawcQOrPEEDaswcS91t CWIsvssXmmqRbFifbqC066K61eUEfLneqtsr682LuKiqZp+VrJdj9CVTRU0C3T0jroJe d9nrlDlr1okcFpPk4UrdXPX/tZPAkrGDxOekdyirgKm4bxvJod9RulsDWAhpzOp172F8 6bfUW/l18X3EOHXWmgInjaeYpoopbXOzYR5s4AA64n9Or8h1/kbDllIWW+AwbmUEKJvA pvKLSZtPY0Uxy+qNq2fXMtLDfrVaOiukYHz7rdkUWJ497YgaHajaoZoU98q9ZOkjxeqS GrHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=233XtfuJMAM/18yXPcEhdSiqp5xPDvbaw672hL8Hwp4=; b=bWiG711zMNPvHReQnJfy7hID/GfVYeyjqVzO6hAugWqNULpJxTdf4M/fCZPidWp5LG dnQ7JuXMQXSuXkxqSeyoEAG3U9PoJvOIr/kr85b1BfvvtWiZNaZ+qeCOIKypxL1YjrDU Kh9hAAPTmlrGneK4D+IhkJ0/W/SNfaStjCO+Gh6FZAnkxwz9VkHqP/JzyWwxIqC1B65q UAA+D/l5lUDjvBc5dztMxSLzRrVJsYhPkNfSjQbQrCHu90j7Rrx2Pk5c6f2DWQMerNy5 aqLFQmExMSuxUNEeQId82ETe7AJjCFOcGKd5SqAgcc9m1n7oqIBLNkvf0S2Qn529/kxT sK7w== X-Gm-Message-State: AMke39nRqaQWv5MY7EtXPRjX7B5dkXUtyugoAZKxIOOQHX2C37K0gsfm8URXKdSOWu4dtw== X-Received: by 10.99.137.66 with SMTP id v63mr6663810pgd.207.1488348840775; Tue, 28 Feb 2017 22:14:00 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id l3sm7762177pgn.10.2017.02.28.22.13.56 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 28 Feb 2017 22:14:00 -0800 (PST) Date: Wed, 1 Mar 2017 07:13:50 +0100 From: Mateusz Guzik To: Mark Millard , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170301061350.GA22378@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> <20170225193103.GA4379@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20170225193103.GA4379@dft-labs.eu> User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2017 06:14:01 -0000 On Sat, Feb 25, 2017 at 08:31:04PM +0100, Mateusz Guzik wrote: > On Sat, Feb 25, 2017 at 09:58:39AM -0800, Mark Millard wrote: > > Thus the PowerMac G5 so-called "Quad Core" is back to > > -r313254 without your patches. (The "Quad Core" really has > > two processors, each with 2 cores.) > > > > > Thanks a lot for testing. I'll have to think what to do with it, worst > case I'll #ifdef changes with powerpc. > Should be fixed with r314474. Got a real powerpc to test on (60 cores), was able to lock it up in seconds. Now it is perfectly stablle. -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Wed Mar 1 17:45:16 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E61F8CF2C87 for ; Wed, 1 Mar 2017 17:45:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-86.reflexion.net [208.70.210.86]) (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 9480F77D for ; Wed, 1 Mar 2017 17:45:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 3870 invoked from network); 1 Mar 2017 17:45:09 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 1 Mar 2017 17:45:09 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Wed, 01 Mar 2017 12:45:09 -0500 (EST) Received: (qmail 14083 invoked from network); 1 Mar 2017 17:45:09 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 1 Mar 2017 17:45:09 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 479F0EC8805; Wed, 1 Mar 2017 09:45:08 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170301061350.GA22378@dft-labs.eu> Date: Wed, 1 Mar 2017 09:45:07 -0800 Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: 7bit Message-Id: References: <2FD12B8F-2255-470A-98D4-2DCE9C7495F5@dsl-only.net> <20170220191044.GA8526@dft-labs.eu> <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> <20170225193103.GA4379@dft-labs.eu> <20170301061350.GA22378@dft-labs.eu> To: Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2017 17:45:17 -0000 On 2017-Feb-28, at 10:13 PM, Mateusz Guzik wrote: On Sat, Feb 25, 2017 at 08:31:04PM +0100, Mateusz Guzik wrote: >> On Sat, Feb 25, 2017 at 09:58:39AM -0800, Mark Millard wrote: >>> Thus the PowerMac G5 so-called "Quad Core" is back to >>> -r313254 without your patches. (The "Quad Core" really has >>> two processors, each with 2 cores.) >>> >> >> >> Thanks a lot for testing. I'll have to think what to do with it, worst >> case I'll #ifdef changes with powerpc. >> > > Should be fixed with r314474. Got a real powerpc to test on (60 cores), > was able to lock it up in seconds. Now it is perfectly stablle. > > -- > Mateusz Guzik The updated so-called "Quad Core" PowerMac G5 used for TARGET_ARCH=powerpc64 was able to do a self hosted buildworld buildkernel for -r314479 just fine. Thanks much for the fixes: Now I can track head again for powerpc64. Summary of the transition interval: So for powerpc64 (and powerpc?) It is a good idea to avoid anything that is after -r313254 and before -r314474 in head. (Would this be appropriate for a UPDATING notice given its span?) There may be other architectures that might have a similar status(?): the last fixes involved were not in Machine Dependent code. (Some architectures are apparently insensitive to the errors, such as amd64). === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Mar 2 03:48:39 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7527ACF38B2 for ; Thu, 2 Mar 2017 03:48:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-90.reflexion.net [208.70.210.90]) (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 2A982D40 for ; Thu, 2 Mar 2017 03:48:38 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 24929 invoked from network); 2 Mar 2017 03:48:37 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 2 Mar 2017 03:48:37 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Wed, 01 Mar 2017 22:48:37 -0500 (EST) Received: (qmail 6933 invoked from network); 2 Mar 2017 03:48:37 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Mar 2017 03:48:37 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id A69FAEC807D for ; Wed, 1 Mar 2017 19:48:36 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Want info: most recent known-working TARGET_ARCH=powerpc head -r version usable on the likes of the PowerMac G5 so-called "Quad Core"? Message-Id: Date: Wed, 1 Mar 2017 19:48:36 -0800 To: FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 03:48:39 -0000 I'm looking for reports of when TARGET_ARCH=powerpc builds last were able to boot the likes of PowerMac G5 so-called "Quad Core"s. Other PowerMac G5's should be a fit. I may need to do a bisect in part based on this information. Details of the context for the question follow. The only powerpc family member that I currently have access to is a PowerMac G5 so-called "Quad Core". [Note: After -r313254 (or a little more) locking has been worked on and TARGET_ARCH=powerpc64 has been messed up until the fixes in -r314474. I've done nothing with TARGET_ARCH=powerpc over this time but did some of the powerpc64 testing.] My intent was to test the new locking for TARGET_ARCH=powerpc but I did not get that far. Note: My context is clang 3.9.1 experiments for TARGET_ARCH=powerpc head builds. But I'm happy with information based on gcc 4.2.1 . I'd be surprised if many folks are trying clang given its powerpc problems. I tried to build and install TARGET_ARCH=powerpc. This used to boot (with one oddity) but I've not attempted it since something like 2016-Nov sometime --or even before. When I tried -r314479 for TARGET_ARCH=powerpc it failed (manually transcribed): exec /sbin/init: error 13 fatal kernel trap: exception = 0x600 (alignment) ssr0 = 0x88a754 ssr1 = 0x9032 lr = 0x88a548 curthread = 0x1477a20 pid = 1, comm = kernel [ thread pid 1 tid 100002 ] Stopped at sf_bug_alloc+0x24c: stw r5,0x4(r3) db:0:kdb.enter.default> bt Tracing pid 1 tid 100002 td 0x1477120 0xdf5e06c0: at exec_map_first_page+0x510 0xdf5e0750: at kern_execve+0x3e4 0xdf5e0990: at sys_execve+0x6c 0xdf5e09f0: at start_init+0x2d0 0xdf5e0a50: at fork_exit+0xcc 0xdf5e0a80: at fork_trampoline+0xc db> [Note this is before the PowerMac can accept input to the db> prompt. I have a compiled-in script automatically run to produce a bt when ddb is started. No serial console context is set up.] Sometimes it hangs without showing the "fatal kernel trap" and later text but is does report the "error 13". I've tried both a amd64 -> TARGET_ARCH=powerpc cross build and building on powerpc64 with TARGET_ARCH=powerpc. Same basic results both ways. The above is from the amd64 based cross build. === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Mar 2 08:56:40 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6817CF515C for ; Thu, 2 Mar 2017 08:56:40 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-94.reflexion.net [208.70.210.94]) (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 76A5AB64 for ; Thu, 2 Mar 2017 08:56:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 30410 invoked from network); 2 Mar 2017 08:57:17 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 2 Mar 2017 08:57:17 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Thu, 02 Mar 2017 03:56:33 -0500 (EST) Received: (qmail 5614 invoked from network); 2 Mar 2017 08:56:33 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Mar 2017 08:56:33 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 8B110EC8937 for ; Thu, 2 Mar 2017 00:56:32 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Want info: most recent known-working TARGET_ARCH=powerpc head -r version usable on the likes of the PowerMac G5 so-called "Quad Core"? [ingore] Date: Thu, 2 Mar 2017 00:56:31 -0800 References: To: FreeBSD PowerPC ML In-Reply-To: Message-Id: <8DFA5D9B-66F9-4818-97E4-564D914C140D@dsl-only.net> X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 08:56:40 -0000 [Turns out that apparently clang 3.9.x based builds got worse.] On 2017-Mar-1, at 7:48 PM, Mark Millard wrote: > I'm looking for reports of when TARGET_ARCH=powerpc > builds last were able to boot the likes of PowerMac > G5 so-called "Quad Core"s. Other PowerMac G5's should > be a fit. I may need to do a bisect in part based on > this information. > > > Details of the context for the question follow. > > The only powerpc family member that I currently have > access to is a PowerMac G5 so-called "Quad Core". > > [Note: After -r313254 (or a little more) locking has been > worked on and TARGET_ARCH=powerpc64 has been messed up > until the fixes in -r314474. I've done nothing with > TARGET_ARCH=powerpc over this time but did some of the > powerpc64 testing.] > > My intent was to test the new locking for > TARGET_ARCH=powerpc but I did not get that far. > > Note: My context is clang 3.9.1 experiments for > TARGET_ARCH=powerpc head builds. But I'm happy with > information based on gcc 4.2.1 . I'd be surprised if > many folks are trying clang given its powerpc problems. > > I tried to build and install TARGET_ARCH=powerpc. > > This used to boot (with one oddity) but I've not > attempted it since something like 2016-Nov sometime > --or even before. > > When I tried -r314479 for TARGET_ARCH=powerpc it failed > (manually transcribed): > > > exec /sbin/init: error 13 > > fatal kernel trap: > > exception = 0x600 (alignment) > ssr0 = 0x88a754 > ssr1 = 0x9032 > lr = 0x88a548 > curthread = 0x1477a20 > pid = 1, comm = kernel > > [ thread pid 1 tid 100002 ] > Stopped at sf_bug_alloc+0x24c: stw r5,0x4(r3) > db:0:kdb.enter.default> bt > Tracing pid 1 tid 100002 td 0x1477120 > 0xdf5e06c0: at exec_map_first_page+0x510 > 0xdf5e0750: at kern_execve+0x3e4 > 0xdf5e0990: at sys_execve+0x6c > 0xdf5e09f0: at start_init+0x2d0 > 0xdf5e0a50: at fork_exit+0xcc > 0xdf5e0a80: at fork_trampoline+0xc > db> > > > [Note this is before the PowerMac can accept input to the > db> prompt. I have a compiled-in script automatically run > to produce a bt when ddb is started. No serial console > context is set up.] > > Sometimes it hangs without showing the "fatal kernel trap" > and later text but is does report the "error 13". > > I've tried both a amd64 -> TARGET_ARCH=powerpc cross build > and building on powerpc64 with TARGET_ARCH=powerpc. Same > basic results both ways. The above is from the amd64 based > cross build. I tried building a gcc 4.2.1 based TARGET_ARCH=powerpc build and that worked fine for the same svn revision. Apparently clang now does something new compared my prior TARGET_ARCH=powerpc experiments. === Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Thu Mar 2 11:42:07 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 17A2ECF537F for ; Thu, 2 Mar 2017 11:42:07 +0000 (UTC) (envelope-from hiroo.ono@gmail.com) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 CC6F6795 for ; Thu, 2 Mar 2017 11:42:06 +0000 (UTC) (envelope-from hiroo.ono@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id m124so37699405oig.1 for ; Thu, 02 Mar 2017 03:42:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:sender:from:date:message-id:subject:to; bh=HWDC11ObY2V6mIBVLTBlLuHfzJK3FmuW0Yy8cSY8XxM=; b=kbGVxKqCUaiQSxEUMbmZdmrZNJJF3rVpijo0KlPwtMSK1xZdaMAx5tmnF0YQWnMUVy JPFHeOxRVZjmXQa+kFrE61PoBvhuo/dlg7aJ1xXtmP0Y0QA4ocdHI8x0/UOLSbm0xFjA lUq9kxh4foMmS/KSiZZM92eYJZh9wkepnKvGwGtrSzlhXe3JS9T9T9jwNhYYyVrj0+CS 1VeBGFqyMIRuQjOQH+lgRJ90pq7xo76GhS7wEeuyhTADZZJSA8SIPy+EFMgi3OjHTyh+ /AXZATu7LhdOCFoZj08VyYMfVLzCkyzm5BRcfoOIIgwVT5IPnSdTW8Vk+tAlZeguyA+L 2oUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:sender:from:date :message-id:subject:to; bh=HWDC11ObY2V6mIBVLTBlLuHfzJK3FmuW0Yy8cSY8XxM=; b=csmLo4TWneMC0ebI5DRkUqbP/Jq3ZJmN0GEu9L5edS8OisoI01FxDC2nerSYUsqWnf nzhoVTYEwZlV3NbeMDHB1IpRy89ORZ6aoGUYY2KhIf/BmyCOo7Lnoic2k48AJCkbN683 Wj8wQgIiEEhLNxbSGp2gmuEtwj5dEg3abpIn7rCZQqLxkARdSwI+zo3CoRttvhwWStHW zKBnI/UYpdICJNl+y8qD0Z1kj+9LfIIBsJSuQQhlnKGRmMtN6EDz4cXGOgluVAxuGK38 kttm9/kfXPk/CbL9T4gxIuWMx/CY2Vy/PKeBj+HZVdYJo7qHjY/kx6VvuIxWS3VBi2nD 0g+w== X-Gm-Message-State: AMke39njzCoO6fZFP1/VaeXCTzx9peCF+Cl2aJNyn0tml3PFiVkxvXSsvrgDRGwvBikioV+7YxxF3of4PJeUug== X-Received: by 10.202.204.138 with SMTP id c132mr7293095oig.155.1488454925819; Thu, 02 Mar 2017 03:42:05 -0800 (PST) MIME-Version: 1.0 Reply-To: hiroo.ono+freebsd@gmail.com Sender: hiroo.ono@gmail.com Received: by 10.74.131.84 with HTTP; Thu, 2 Mar 2017 03:42:05 -0800 (PST) From: =?UTF-8?B?SGlyb28gT25vICjlsI/ph47lr5vnlJ8p?= Date: Thu, 2 Mar 2017 20:42:05 +0900 X-Google-Sender-Auth: cTaWX3jRpT3y5pRuOG1v-BqyT0M Message-ID: Subject: PowerMac G5 and KMS To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 11:42:07 -0000 I recently installed 12-current powerpc64 r313561 to a PowerMac G5 (it is dual processor, but I do not know its detail). When I try to load drm2.ko and radeonkms.ko, the screen turns into black and recovers, then the system locks. kldload command does not return, no response to keyboard input, etc. Is it possible to use KMS on FreeBSD/powerpc64? The log in /var/log/messages is after "kldload drm2", kernel: info: [drm] Initialized drm 1.1.0 20060810 and then, after "kldload radeonkms", kernel: iic0: on iicbus0 kernel: iic1: on iicbus1 kernel: drmn0: on vgapci0 kernel: info: [drm] RADEON_IS_AGP kernel: info: [drm] initializing kernel modesetting (RV350 0x1002:0x4150 0x1002:0x4150). kernel: info: [drm] register mmio base: 0x90000000 kernel: info: [drm] register mmio size: 65536 kernel: info: [drm] igp_read_bios_from_vram: ===> Try IGP's VRAM... kernel: info: [drm] igp_read_bios_from_vram: VRAM base address: 0x98000000 kernel: info: [drm] igp_read_bios_from_vram: Map address: 0xc000000061412000 (262144 bytes) kernel: info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature: 0x0000 kernel: info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM... kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000 (131072 bytes) kernel: info: [drm] radeon_read_bios: Incorrect BIOS signature: 0x2AFF kernel: info: [drm] legacy_read_disabled_bios: ===> Try disabled BIOS (legacy)... kernel: info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM... kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000 (131072 bytes) As the system locks up here, I have to power it off forcibly. From owner-freebsd-ppc@freebsd.org Thu Mar 2 12:02:15 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 82A4DCF5FD7 for ; Thu, 2 Mar 2017 12:02:15 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.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 418C232F for ; Thu, 2 Mar 2017 12:02:14 +0000 (UTC) (envelope-from andy.silva@snsresearchreports.com) X-MSFBL: dA05H5WWoQAGeIThlJ22ajXNuNfhZ8HqStzLKZxRjHU=|eyJyIjoiZnJlZWJzZC1 wcGNAZnJlZWJzZC5vcmciLCJnIjoiU25zdGVsZWNvbV9kZWRpY2F0ZWRfcG9vbCI sImIiOiI3NF85MV84NV8yMzgifQ== Received: from [192.168.80.11] ([192.168.80.11:46974] helo=rs-ord-mta01-in1.smtp.com) by rs-ord-mta01-out2.smtp.com (envelope-from ) (ecelerity 4.2.1.55028 r(Core:4.2.1.12)) with ESMTP id BF/8C-12339-50508B85; Thu, 02 Mar 2017 11:41:57 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=snsreports.com; s=snskey; c=relaxed/simple; q=dns/txt; i=@snsreports.com; t=1488454917; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=kd0igCb3OfAJGrCxFd3tBwja4f17rDt7o3MqP0kjX7A=; b=cOg78K3zvRfajEHD0qywEQlbytXf7y+IfFpMm41bbQkYWdMLIKryOpD3lGtZU41F Ga8wNXQKK7WvuXQYx9YswVTM4hY7RcZdKLPBfAMPquuWT5mtyDti0GhDYiGzEJqd xQHZZ/2GfJQY+2+0mT+UnfFmAa8IbGaZmzmAyv5bNsNPY+14qyLS9zB1lT1OeJ93 G0wk11PZtGMf1i//EAoMZR+UrlWO4zgyIEUEUuv4OED0AayYE6Q2WKR/qQbHJh0H jLLDinXthVtJyaQGxqahTTtMW8R8pGb/Klj+9FZUMOhgvgqauFuAwAky6JJFf47U T/fE7edpzIMHvGj91lCO+Q==; Received: from [70.79.69.78] ([70.79.69.78:42637] helo=S01061c1b689e28c7.vc.shawcable.net) by rs-ord-mta01-in1.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 4B/31-07467-40508B85; Thu, 02 Mar 2017 11:41:57 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsresearchreports.com To: freebsd-ppc@freebsd.org Subject: ProSe (Proximity Services) for LTE & 5G Networks: 2017 - 2030 - Opportunities, Challenges, Strategies & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Thu, 2 Mar 2017 03:41:53 -0800 Message-ID: <6328393987704606412638@Ankur> 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. X-SMTPCOM-Tracking-Number: 777e9786-cdd4-418f-a327-ad4f80a8d137 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 12:02:15 -0000 ProSe (Proximity Services) for LTE & 5G Networks: 2017 =96 2030 =96 Opportu= nities, Challenges, Strategies & Forecasts (Report) Hello Let me offer you the latest SNS Research report to you and your team, "ProS= e (Proximity Services) for LTE & 5G Networks: 2017 =96 2030 =96 Opportuniti= es, Challenges, Strategies & Forecasts" Below is the report highlight and i= f you like I can send you sample pages for your details inside. =20 By the end of 2025, SNS Research estimates that mobile operators can pocket= as much $17 Billion in ProSe based annual service revenue. Up to 55% of th= is revenue figure will be attributable to proximity advertising. Report Information: Release Date: Jan 2017 Number of Pages: 127 Number of Tables and Figures: 84 Key Questions Answered: How big is the ProSe opportunity=3F What trends, challenges and barriers are influencing its growth=3F How will the ecosystem evolve by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F How big is the ProSe service revenue opportunity for mobile operators=3F How will ProSe help public safety agencies in replacing legacy LMR systems = with LTE and 5G networks=3F How will consolidation in the chipset ecosystem affect the adoption of ProS= e=3F How can ProSe deliver localized V2X (Vehicle-to-Everything) connectivity=3F What strategies should chipset suppliers, device OEMs and mobile operators = adopt to remain competitive=3F Key Findings: The report has the following key findings: In comparison to existing D2D and proximity networking technologies, ProSe = offers several distinct benefits including but not limited to better scalab= ility, manageability, privacy, security and battery-efficiency. At present, efforts to commercialize ProSe are being spearheaded by the pub= lic safety and critical communications industry. The ongoing transition fro= m legacy LMR systems to LTE networks is expected to trigger the very first= investments in ProSe-enabled devices, as direct communication between devi= ces is an essential requirement for users in this domain. In the commercial area, mobile operators can leverage ProSe to offer a rang= e of B2B, B2B2C and B2C services that rely on proximity including advertisi= ng, social networking, gaming, relaying traffic for wearables and V2X (Vehi= cle-to-Everything) connectivity. By the end of 2025, SNS Research estimates that mobile operators can pocket= as much $17 Billion in ProSe based annual service revenue. Up to 55% of th= is revenue figure will be attributable to proximity advertising. =20 The report covers the following topics: =20 ProSe technology Market drivers and barriers Sidelink air interface and spectrum bands ProSe discovery and direct communication services ProSe coverage scenarios and modes of operation ProSe reference architecture, key functional elements and interfaces 3GPP standardization efforts for ProSe Competing D2D and proximity networking technologies Key applications, business models and monetization strategies Case studies of pre-commercial ProSe engagements Industry roadmap and value chain Strategic recommendations for key ecosystem players including chipset suppl= iers, device OEMs, infrastructure vendors, public safety agencies and mobil= e operators Market analysis and forecasts from 2018 till 2030 Forecast Segmentation: Market forecasts and historical revenue figures are provided for each of th= e following 5 submarkets and their 23 use case categories: ProSe Device Shipments & Revenue Submarkets Public Safety & Critical Communications Commercial Sector Form Factor Segmentation=20 Smartphones Tablets Wearables Vehicle Mount Devices V2X Devices Other Devices Regional Markets Asia Pacific Eastern Europe Middle East & Africa Latin & Central America North America Western Europe ProSe Based Mobile Operator Service Revenue Submarkets Advertising Social Networking V2X Connectivity Public Safety & Critical Communications Other Applications Additional forecasts are provided for the following: IoT connections for mHealth applications mHealth centric wearable device shipments Mobile video calling users Annual throughput of mobile network data traffic Smartphone, feature phone, tablet, desktop PC and notebook shipments Mobile network subscriptions by region Cost saving potential of mHealth by region Big Data & analytics technology investments in the healthcare sector =20 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 - ProSe for LTE & 5G Network: 2017-2030 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 andy.silva@snsresearchreports.com =20 _________________________________________________________________________ Table of Contents (page number): =20 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 ProSe 2.1 What is D2D (Device-to-Device) Technology=3F 2.2 ProSe (Proximity Services) for 3GPP Networks 2.3 ProSe Service Classification 2.3.1 ProSe Discovery 2.3.2 ProSe Direct Communication 2.4 ProSe Coverage Scenarios 2.4.1 In-Coverage 2.4.2 Partial Coverage 2.4.3 Out-of-Coverage 2.5 ProSe Modes of Direct Communication 2.5.1 Unicast 2.5.2 One-to-Many: Group Communication 2.5.3 One-to-All: Broadcast Communication 2.6 ProSe Modes of Discovery 2.6.1 Restricted Discovery 2.6.2 Open Discovery 2.7 Competing Technologies 2.7.1 P25, TETRA & Conventional LMR Systems 2.7.2 Wi-Fi 2.7.2.1 Wi-Fi Direct 2.7.2.2 Wi-Fi Aware/NAN (Neighbor Awareness Networking) 2.7.2.3 Ad-Hoc Mode D2D Connectivity & TDLS (Tunneled Direct Link Setup) 2.7.2.4 WAVE (Wireless Access in Vehicular Environments): IEEE 802.11p 2.7.3 Bluetooth 2.7.3.1 Classic Bluetooth 2.7.3.2 Bluetooth High Speed 2.7.3.3 BLE (Bluetooth Low Energy) 2.7.3.4 Bluetooth 5 Enhancements 2.7.4 Apple's iBeacon 2.7.5 ZigBee 2.7.6 GPS 2.7.7 Others 2.8 Market Growth Drivers 2.8.1 Adoption of LTE for Public Safety & Critical Communications 2.8.2 Extending Wide Area Connectivity to IoT Devices & Accessories 2.8.3 Better Scalability & Coverage Range Than Competing Technologies 2.8.4 New Revenue Streams & ARPU Growth for Mobile Operators 2.8.5 Enhanced Manageability, Privacy & Security 2.8.6 Alleviating Network Congestion & Improving Spectrum Utilization 2.9 Market Barriers 2.9.1 Potential Interference 2.9.2 Achieving UE Battery Efficiency 2.9.3 Impact on Network Resources 2.9.4 Dependency on New Chipsets & Devices 2.9.5 Interoperability & Other Technical Challenges =20 3 Chapter 3: ProSe Technology & Standardization 3.1 Sidelink Air Interface 3.1.1 Use of Uplink Resources 3.1.2 Transmission Scheme 3.1.3 Frequency Bands & Channel Bandwidths 3.1.4 New Physical, Transport & Logical Channels 3.1.4.1 Physical Channels 3.1.4.2 Transport Channels 3.1.4.3 Logical Channels 3.1.5 Synchronization Signals 3.1.6 Alternative Wi-Fi Direct Communication Path 3.2 Key Operational Capabilities of ProSe 3.2.1 Service Authorization & Provisioning 3.2.2 ProSe Discovery 3.2.2.1 Direct Discovery 3.2.2.2 Specific Direct Discovery Features for Public Safety 3.2.2.3 EPC-Level Discovery 3.2.2.4 EPC Support for Wi-Fi Direct Communication 3.2.3 ProSe Direct Communication 3.2.3.1 One-to-One Direct Communication 3.2.3.2 One-to-Many Direct Communication 3.2.4 UE-to-Network Relay 3.3 ProSe Reference Architecture, Key Functional Elements & Interfaces 3.3.1 ProSe-Enabled Devices & Applications 3.3.2 ProSe AS (Application Server) 3.3.3 ProSe Function 3.3.3.1 DPF (Direct Provisioning Function) 3.3.3.2 Direct Discovery Name Management Function 3.3.3.3 EPC-Level Discovery ProSe Function 3.3.4 ProSe Proxy 3.3.5 ProSe Key Management Function 3.3.6 MME (Mobility Management Entity) 3.3.7 P-GW (Packet Data Network Gateway) 3.3.8 S-GW (Serving Gateway) 3.3.9 HSS (Home Subscriber Server) 3.3.10 SLP (Secure User Plane Location Platform) 3.3.11 S-GW (Serving Gateway) 3.3.12 Interfaces 3.3.12.1 PC1 3.3.12.2 PC2 3.3.12.3 PC3 3.3.12.4 PC4a 3.3.12.5 PC4b 3.3.12.6 PC5 (Sidelink) 3.3.12.7 PC6 3.3.12.8 PC7 3.3.12.9 PC8 3.3.12.10 S6a 3.3.12.11 S1-MME 3.4 3GPP Standardization for ProSe 3.4.1 Release 12 3.4.2 Release 13 3.4.3 Release 14 & Beyond =20 4 Chapter 4: ProSe Applications, Business Models & Case Studies 4.1 Key Applications of ProSe 4.1.1 Public Safety & Critical Communications 4.1.1.1 Direct Communication for Coverage Extension 4.1.1.2 Direct Communication within Network Coverage 4.1.1.3 Infrastructure Failure & Emergency Situations 4.1.1.4 Additional Capacity for Incident Response & Special Events 4.1.1.5 Discovery Services for Disaster Relief 4.1.2 Commercial Applications 4.1.2.1 Proximity Advertising 4.1.2.2 Localized Social Networking 4.1.2.3 Online & Real-World Gaming 4.1.2.4 Enabling the Sharing Economy 4.1.2.5 Mobile Relaying & Network Sharing 4.1.2.6 Wide Area Connectivity for the IoT & Wearables 4.1.2.7 Local Data Transfer 4.1.2.8 Other Applications 4.1.3 Cellular V2X (Vehicle-to-Everything) Connectivity 4.2 Business Models: How Can Mobile Operators Monetize ProSe=3F 4.2.1 B2C: Premium Charge for ProSe Capabilities 4.2.2 B2B: D2D Services for Public Safety Agencies & Other Enterprises 4.2.3 B2B2C: Stacking Consumer Applications over ProSe 4.3 Case Studies of Pre-Commercial Engagements 4.3.1 Qualcomm: Accelerating Ecosystem Development with LTE Direct 4.3.2 DT (Deutsche Telekom): First Pre-Commercial Mobile Operator Trial for= ProSe 4.3.3 KT Corporation: Emergency Services, Social Networking & Personalized = Advertising with ProSe 4.3.4 TCL Communication: ProSe-Enabled Device Prototype Demonstration 4.3.5 NTT DoCoMo: Empowering the Sharing Economy with ProSe 4.3.6 M87: Expanding the Reach of Mobile Networks with ProSe 4.3.7 Compass.To: Successfully Conducting the First ProSe Trial in China 4.3.8 Others =20 5 Chapter 5: ProSe Industry Roadmap & Value Chain 5.1 Industry Roadmap 5.1.1 2017 =96 2020: Initial Adoption Driven by Public Safety LTE Networks 5.1.2 2020 =96 2025: Growing Focus on Consumer Applications 5.1.3 2025 =96 2030: Targeting Cellular V2X Connectivity 5.2 Value Chain 5.2.1 Chipset Suppliers 5.2.2 ProSe-Enabled Device OEMs 5.2.3 ProSe Infrastructure Vendors 5.2.4 Mobile Operators 5.2.5 Public Safety & Critical Communications Agencies 5.2.6 Commercial Enterprises 5.2.7 App Developers & Content Providers 5.2.8 Consumers 5.2.9 Test, Measurement & Performance Specialists =20 6 Chapter 6: Market Analysis & Forecasts 6.1 Global Outlook on ProSe-Enabled Devices 6.2 Submarket Segmentation 6.2.1 Public Safety & Critical Communications 6.2.2 Commercial Sector 6.3 Form Factor Segmentation 6.3.1 Public Safety & Critical Communications 6.3.1.1 Smartphones 6.3.1.2 Vehicle Mount Devices 6.3.1.3 Other Devices 6.3.2 Commercial Sector 6.3.2.1 Smartphones 6.3.2.2 Tablets 6.3.2.3 Wearables 6.3.2.4 V2X Devices 6.3.2.5 Other Devices 6.4 Regional Segmentation 6.4.1 Public Safety & Critical Communications 6.4.2 Commercial Sector 6.5 Asia Pacific 6.5.1 Public Safety & Critical Communications 6.5.2 Commercial Sector 6.6 Eastern Europe 6.6.1 Public Safety & Critical Communications 6.6.2 Commercial Sector 6.7 Latin & Central America 6.7.1 Public Safety & Critical Communications 6.7.2 Commercial Sector 6.8 Middle East & Africa 6.8.1 Public Safety & Critical Communications 6.8.2 Commercial Sector 6.9 North America 6.9.1 Public Safety & Critical Communications 6.9.2 Commercial Sector 6.10 Western Europe 6.10.1 Public Safety & Critical Communications 6.10.2 Commercial Sector =20 7 Chapter 7: Conclusion & Strategic Recommendations 7.1 Why is the Market Poised to Grow=3F 7.2 Public Safety LTE Engagements to Trigger Initial Investments 7.3 Synergies with IOPS (Isolated E-UTRAN Operation) 7.4 Interim Solutions to Fulfill Public Safety ProSe Requirements 7.5 How Big is the ProSe Service Revenue Opportunity for Mobile Operators=3F 7.6 Enhancements to Support IoT & Wearables 7.7 Consolidation in the Chipset Ecosystem: Implications for ProSe 7.8 Potential Impact on the V2X Sector 7.9 Strategic Recommendations 7.9.1 Recommendations for Chipset, Device & Infrastructure Suppliers 7.9.2 Recommendations for Mobile Operators 7.9.3 Recommendations for Public Safety & Critical Communications Agencies =20 List of Figures (page number) =20 Figure 1: Example Application Scenarios for D2D Technology Figure 2: Sidelink Air Interface for ProSe Figure 3: Use Cases & Service Scenarios for ProSe Figure 4: Key Differences Between LTE Uplink and Sidelink Figure 5: Operating Bands for ProSe Figure 6: ProSe Direct Discovery Channel Bandwidth Figure 7: ProSe Direct Communication Channel Bandwidth Figure 8: Physical, Transport & Logical Channels for Sidelink Figure 9: Architecture for ProSe UE-to-Network Relay Functionality Figure 10: ProSe Reference Architecture Figure 11: ProSe Industry Roadmap Figure 12: ProSe Value Chain Figure 13: Global ProSe-Enabled Device Shipments: 2018 =96 2030 (Millions o= f Units) Figure 14: Global ProSe-Enabled Device Shipment Revenue: 2018 =96 2030 ($ B= illion) Figure 15: Global ProSe-Enabled Device Shipments by Submarket: 2018 =96 203= 0 (Millions of Units) Figure 16: Global ProSe-Enabled Device Shipment Revenue by Submarket: 2018 = =96 2030 ($ Billion) Figure 17: Global ProSe-Enabled Device Shipments in the Public Safety & Cri= tical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 18: Global ProSe-Enabled Device Shipment Revenue in the Public Safet= y & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 19: Global ProSe-Enabled Device Shipments in the Commercial Sector: = 2018 =96 2030 (Millions of Units) Figure 20: Global ProSe-Enabled Device Shipment Revenue in the Commercial S= ector: 2018 =96 2030 ($ Billion) Figure 21: Global ProSe-Enabled Device Shipments in the Public Safety & Cri= tical Communications Sector, by Form Factor: 2018 =96 2030 (Thousands of Un= its) Figure 22: Global ProSe-Enabled Device Shipment Revenue in the Public Safet= y & Critical Communications Sector, by Form Factor: 2018 =96 2030 ($ Millio= n) Figure 23: Global ProSe-Enabled Smartphone Shipments in the Public Safety &= Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 24: Global ProSe-Enabled Smartphone Shipment Revenue in the Public S= afety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 25: Global ProSe-Enabled Vehicle Mount Device Shipments in the Publi= c Safety & Critical Communications Sector: 2018 =96 2030 (Thousands of Unit= s) Figure 26: Global ProSe-Enabled Vehicle Mount Device Shipment Revenue in th= e Public Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 27: Global ProSe-Enabled Other Device Shipments in the Public Safety= & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 28: Global ProSe-Enabled Other Device Shipment Revenue in the Public= Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 29: Global ProSe-Enabled Device Shipments in the Commercial Sector, = by Form Factor: 2018 =96 2030 (Millions of Units) Figure 30: Global ProSe-Enabled Device Shipment Revenue in the Commercial S= ector, by Form Factor: 2018 =96 2030 ($ Billion) Figure 31: Global ProSe-Enabled Smartphone Shipments in the Commercial Sect= or: 2018 =96 2030 (Millions of Units) Figure 32: Global ProSe-Enabled Smartphone Shipment Revenue in the Commerci= al Sector: 2018 =96 2030 ($ Billion) Figure 33: Global ProSe-Enabled Tablet Shipments in the Commercial Sector: = 2018 =96 2030 (Millions of Units) Figure 34: Global ProSe-Enabled Tablet Shipment Revenue in the Commercial S= ector: 2018 =96 2030 ($ Billion) Figure 35: Global ProSe-Enabled Wearable Device Shipments in the Commercial= Sector: 2018 =96 2030 (Millions of Units) Figure 36: Global ProSe-Enabled Wearable Device Shipment Revenue in the Com= mercial Sector: 2018 =96 2030 ($ Billion) Figure 37: Global ProSe-Enabled V2X Device Shipments in the Commercial Sect= or: 2018 =96 2030 (Millions of Units) Figure 38: Global ProSe-Enabled V2X Device Shipment Revenue in the Commerci= al Sector: 2018 =96 2030 ($ Billion) Figure 39: Global ProSe-Enabled Other Device Shipments in the Commercial Se= ctor: 2018 =96 2030 (Millions of Units) Figure 40: Global ProSe-Enabled Other Device Shipment Revenue in the Commer= cial Sector: 2018 =96 2030 ($ Billion) Figure 41: ProSe-Enabled Device Shipments by Region: 2018 =96 2030 (Million= s of Units) Figure 42: ProSe-Enabled Device Shipment Revenue by Region: 2018 =96 2030 (= $ Billion) Figure 43: ProSe-Enabled Device Shipments in the Public Safety & Critical C= ommunications Sector, by Region: 2018 =96 2030 (Thousands of Units) Figure 44: ProSe-Enabled Device Shipment Revenue in the Public Safety & Cri= tical Communications Sector, by Region: 2018 =96 2030 ($ Million) Figure 45: ProSe-Enabled Device Shipments in the Commercial Sector, by Regi= on: 2018 =96 2030 (Millions of Units) Figure 46: ProSe-Enabled Device Shipment Revenue in the Commercial Sector, = by Region: 2018 =96 2030 ($ Billion) Figure 47: Asia Pacific ProSe-Enabled Device Shipments: 2018 =96 2030 (Mill= ions of Units) Figure 48: Asia Pacific ProSe-Enabled Device Shipment Revenue: 2018 =96 203= 0 ($ Billion) Figure 49: Asia Pacific ProSe-Enabled Device Shipments in the Public Safety= & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 50: Asia Pacific ProSe-Enabled Device Shipment Revenue in the Public= Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 51: Asia Pacific ProSe-Enabled Device Shipments in the Commercial Se= ctor: 2018 =96 2030 (Millions of Units) Figure 52: Asia Pacific ProSe-Enabled Device Shipment Revenue in the Commer= cial Sector: 2018 =96 2030 ($ Billion) Figure 53: Eastern Europe ProSe-Enabled Device Shipments: 2018 =96 2030 (Mi= llions of Units) Figure 54: Eastern Europe ProSe-Enabled Device Shipment Revenue: 2018 =96 2= 030 ($ Billion) Figure 55: Eastern Europe ProSe-Enabled Device Shipments in the Public Safe= ty & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 56: Eastern Europe ProSe-Enabled Device Shipment Revenue in the Publ= ic Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 57: Eastern Europe ProSe-Enabled Device Shipments in the Commercial = Sector: 2018 =96 2030 (Millions of Units) Figure 58: Eastern Europe ProSe-Enabled Device Shipment Revenue in the Comm= ercial Sector: 2018 =96 2030 ($ Billion) Figure 59: Latin & Central America ProSe-Enabled Device Shipments: 2018 =96= 2030 (Millions of Units) Figure 60: Latin & Central America ProSe-Enabled Device Shipment Revenue: 2= 018 =96 2030 ($ Billion) Figure 61: Latin & Central America ProSe-Enabled Device Shipments in the Pu= blic Safety & Critical Communications Sector: 2018 =96 2030 (Thousands of U= nits) Figure 62: Latin & Central America ProSe-Enabled Device Shipment Revenue in= the Public Safety & Critical Communications Sector: 2018 =96 2030 ($ Milli= on) Figure 63: Latin & Central America ProSe-Enabled Device Shipments in the Co= mmercial Sector: 2018 =96 2030 (Millions of Units) Figure 64: Latin & Central America ProSe-Enabled Device Shipment Revenue in= the Commercial Sector: 2018 =96 2030 ($ Billion) Figure 65: Middle East & Africa ProSe-Enabled Device Shipments: 2018 =96 20= 30 (Millions of Units) Figure 66: Middle East & Africa ProSe-Enabled Device Shipment Revenue: 2018= =96 2030 ($ Billion) Figure 67: Middle East & Africa ProSe-Enabled Device Shipments in the Publi= c Safety & Critical Communications Sector: 2018 =96 2030 (Thousands of Unit= s) Figure 68: Middle East & Africa ProSe-Enabled Device Shipment Revenue in th= e Public Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 69: Middle East & Africa ProSe-Enabled Device Shipments in the Comme= rcial Sector: 2018 =96 2030 (Millions of Units) Figure 70: Middle East & Africa ProSe-Enabled Device Shipment Revenue in th= e Commercial Sector: 2018 =96 2030 ($ Billion) Figure 71: North America ProSe-Enabled Device Shipments: 2018 =96 2030 (Mil= lions of Units) Figure 72: North America ProSe-Enabled Device Shipment Revenue: 2018 =96 20= 30 ($ Billion) Figure 73: North America ProSe-Enabled Device Shipments in the Public Safet= y & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 74: North America ProSe-Enabled Device Shipment Revenue in the Publi= c Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 75: North America ProSe-Enabled Device Shipments in the Commercial S= ector: 2018 =96 2030 (Millions of Units) Figure 76: North America ProSe-Enabled Device Shipment Revenue in the Comme= rcial Sector: 2018 =96 2030 ($ Billion) Figure 77: Western Europe ProSe-Enabled Device Shipments: 2018 =96 2030 (Mi= llions of Units) Figure 78: Western Europe ProSe-Enabled Device Shipment Revenue: 2018 =96 2= 030 ($ Billion) Figure 79: Western Europe ProSe-Enabled Device Shipments in the Public Safe= ty & Critical Communications Sector: 2018 =96 2030 (Thousands of Units) Figure 80: Western Europe ProSe-Enabled Device Shipment Revenue in the Publ= ic Safety & Critical Communications Sector: 2018 =96 2030 ($ Million) Figure 81: Western Europe ProSe-Enabled Device Shipments in the Commercial = Sector: 2018 =96 2030 (Millions of Units) Figure 82: Western Europe ProSe-Enabled Device Shipment Revenue in the Comm= ercial Sector: 2018 =96 2030 ($ Billion) Figure 83: Global Installed Base of ProSe-Enabled Devices by Submarket: 201= 8 =96 2030 (Millions of Units) Figure 84: Global ProSe Based Mobile Operator Service Revenue by Applicatio= n: 2018 =96 2030 ($ Billion) =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive =20 =20 To unsubscribe please send an email with unsubscribe in the subject line to= : remove@snsreports.com =20 From owner-freebsd-ppc@freebsd.org Thu Mar 2 12:10:27 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 800EDCF1232; Thu, 2 Mar 2017 12:10:27 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B3B76B3; Thu, 2 Mar 2017 12:10:27 +0000 (UTC) (envelope-from mjguzik@gmail.com) Received: by mail-wm0-x242.google.com with SMTP id v190so6104707wme.3; Thu, 02 Mar 2017 04:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=MX2mdjoR/yldONljs9doR6MC185fkaePgbryFCxk1DY=; b=CB3ryYou9e8ftx3xDVLyNP/W2T2HrrKbSJ4MeAa1DUuOOsFIwce+3iYkd2ChYWcWT/ 56aglWRkvn1RsoIWIG0VGT6fnxqRrzVRCaNbp12nGRap1G+WSrdJqnsMqlsUokywM7OX +5Y6ycM8rr5grHMo0w+ItKFV02jOwxQA6XmbjcXNqNBotXgFBIWY9grPzbY82bdUukxI 8aUpvX2qVJoFv4/V3LN0iljiJXsbffltgSVPy3G5jpVIyf7rUFXK7FCtHOi7VNTzKO+7 zvRaxkP1cTq6/Hb0N8itPTvlVwrwlLpfADU/qqxPoLdNg0SwI9ZUpKD+aIjonXps7/TP 94pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=MX2mdjoR/yldONljs9doR6MC185fkaePgbryFCxk1DY=; b=RxxmQQ87RH+dWeIImqPU7py2sV74glgz8OXA0nBW2aURTG+p7saT9jLB2jnYcqDbtV JdZ9uBaa8H0W5bu2hvTNRmsw7nQLajNKBekyT54/NMELdmYesXed0Wtp6zA8AGdoytzJ 9GSLacVWU1IFfeMvGgMrIahFy92TxGr1Gwy1KajVL1p0OyhSQdqPLxdEacT8U45Nw/K4 A00AANbRhlhWzMsEw5gsOiMAI82UbfXmg/MZbpeTkHS8fNTKtJTlJt8DjdJSmW+acT5y fqd1ggSLCfreKPw2OKuTrVSw1u/RDKtP4LrDqHMlnVcbOHmWtGCpHCmc3V/hXELWxBJN zEQg== X-Gm-Message-State: AMke39kp+Nld1xUCLX4MS12Cmz9xmLBlhJ8T3s9U5ZaKGZLOAtAtG9oHmVYZMSM7ywR1Yw== X-Received: by 10.28.66.11 with SMTP id p11mr8516387wma.38.1488456625542; Thu, 02 Mar 2017 04:10:25 -0800 (PST) Received: from dft-labs.eu (n1x0n-1-pt.tunnel.tserv5.lon1.ipv6.he.net. [2001:470:1f08:1f7::2]) by smtp.gmail.com with ESMTPSA id l130sm26770203wmf.0.2017.03.02.04.10.23 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Thu, 02 Mar 2017 04:10:24 -0800 (PST) Date: Thu, 2 Mar 2017 13:10:21 +0100 From: Mateusz Guzik To: Mark Millard Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170302121021.GA32682@dft-labs.eu> Mail-Followup-To: Mateusz Guzik , Mark Millard , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML References: <5D5235E1-6F84-4329-8ED5-35FCDB0A6A71@dsl-only.net> <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> <20170225193103.GA4379@dft-labs.eu> <20170301061350.GA22378@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 12:10:27 -0000 On Wed, Mar 01, 2017 at 09:45:07AM -0800, Mark Millard wrote: > > On 2017-Feb-28, at 10:13 PM, Mateusz Guzik wrote: > > On Sat, Feb 25, 2017 at 08:31:04PM +0100, Mateusz Guzik wrote: > >> On Sat, Feb 25, 2017 at 09:58:39AM -0800, Mark Millard wrote: > >>> Thus the PowerMac G5 so-called "Quad Core" is back to > >>> -r313254 without your patches. (The "Quad Core" really has > >>> two processors, each with 2 cores.) > >>> > >> > >> > >> Thanks a lot for testing. I'll have to think what to do with it, worst > >> case I'll #ifdef changes with powerpc. > >> > > > > Should be fixed with r314474. Got a real powerpc to test on (60 cores), > > was able to lock it up in seconds. Now it is perfectly stablle. > > > > -- > > Mateusz Guzik > > The updated so-called "Quad Core" PowerMac G5 used for > TARGET_ARCH=powerpc64 was able to do a self hosted > buildworld buildkernel for -r314479 just fine. > Cool. > Thanks much for the fixes: Now I can track head again > for powerpc64. > Well it was my breakage to begin with. > > Summary of the transition interval: > > So for powerpc64 (and powerpc?) It is a good > idea to avoid anything that is after -r313254 > and before -r314474 in head. (Would this be > appropriate for a UPDATING notice given its > span?) > > There may be other architectures that might have > a similar status(?): the last fixes involved were > not in Machine Dependent code. (Some architectures > are apparently insensitive to the errors, such as > amd64). > When following current you are expected to be on the newest revision, so I don't think mentioning interim broken releases makes much sense. -- Mateusz Guzik From owner-freebsd-ppc@freebsd.org Thu Mar 2 12:14:53 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12CB5CF15DA for ; Thu, 2 Mar 2017 12:14:53 +0000 (UTC) (envelope-from hiroo.ono@gmail.com) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (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 CF959C35 for ; Thu, 2 Mar 2017 12:14:52 +0000 (UTC) (envelope-from hiroo.ono@gmail.com) Received: by mail-oi0-x230.google.com with SMTP id 2so37975717oif.0 for ; Thu, 02 Mar 2017 04:14:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=W+tzzbnK8keSKsfwJyvj1y0gKZf6aF92WjQgvxveuNc=; b=Oqu9VaZyxTyVdqi001mBDNkBoFhQQotNjXvYCJJv5Vi7d9be1PGv9wXYcNaMOx2u2f IDZGHO5jAWBBnTYotUbPc90H9eD4Qm3ZqESyJGIZPT1bxtGR8UOpXHV2IxUFz+wcyGyL 6/BoQQGWS+BuZv8y7FbzNNSZiWuePCKvuT1fjPWCwyT7bP7Yze8sHEUv9Ln8S4tQeUXv 33vXfFFsyx8HPovyiasXCIPvGWYHMuHA68x3WUdLvbSr55kIik4zE94CCkrtBMvsPLx2 oFe6j6MisFn3GebWq4bDs1QIMs/IaAEruiksq8p35tCt0wIPGQ635WOK2CLAJMZcuogW lw6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=W+tzzbnK8keSKsfwJyvj1y0gKZf6aF92WjQgvxveuNc=; b=rv8NA2GJ+Xn7FKJ9maMyMxfbZXXqp/Hy+pWdq1kqMVAu1ikVnnEc2SgGuGf0xF2Uc9 7UhPFKFAV3IoNYZAkYObMFgU6P7ePzS3CVvZXBuoptwMM2hcIu3n7LsHxu6BKzt574FG mYhbzqRS27ykrcfkcjq2MLEWLFNXfsUguoMw1KdrAjNp7tQkqn2O2oomAj7aJasU5vLE CsS6Vizks+GGL5EHRJ3lAyw+dC37EsqH48xMyhRsGLcyq/6e7jjeg0PJOEUq76VxKNIQ QXOX3vYMAgjL0KoYWCyqhhD5YmfchoRqXqNU+8r8O8RtxQEzFKBd0EyVHxP/qMCF3CrA Qrxw== X-Gm-Message-State: AMke39mtvpl8h6rI+i3v8PFIN0av98syMp4yvW1YzJZ33x62diph96KjZjiSysVdJQ4tg30Az4Tw4DWZ2fvfhA== X-Received: by 10.202.204.138 with SMTP id c132mr7371986oig.155.1488456892149; Thu, 02 Mar 2017 04:14:52 -0800 (PST) MIME-Version: 1.0 From: =?UTF-8?B?SGlyb28gT25vICjlsI/ph47lr5vnlJ8p?= Date: Thu, 02 Mar 2017 12:14:41 +0000 Message-ID: Subject: FreeBSD/powerpc64 head r313561's /boot/loader cannot boot the kernel from NFS To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 12:14:53 -0000 I installed FreeBSD/powerpc64 head r313561 (snapshot of 20170210) and had the problem below: I tried to net boot the installer. The configuration of isc-dhcp is: host powerpc { hardware ethernet xxx:xx:xx:xx:xx:xx; fixed address 192.168.0.15; next-server 192.168.0.10; filename "loader"; option root-path "192.168.0.10:/exports/FreeBSD/ppc64/12c-20170210"; } tftp configuration in inetd.conf is: tftp dgram udp wait root /usr/local/libexec/in.tftpd in.tftpd -s /exports/FreeBSD/ppc64/12c-20170210/boot and 192.168.0.10:/exports/FreeBSD/ppc64/12c-20170210 is NFS mountable with full system copied from disc1.iso. I tried to boot from openfirmware console > boot eboot:,loader the file loader was retrieved via tftp and executed, but it said it cannot find the file 'kernel' or it could not boot the file "kernel". (I forgot the exact message.) I replaced /boot/loader with the loader of 11.0-RELEASE. It successfully booted /boot/kernel/kernel, and I managed to install. Is there something wrong with my configuration, or is there a bug in /boot/loader? From owner-freebsd-ppc@freebsd.org Thu Mar 2 15:20:06 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27E35CF4056; Thu, 2 Mar 2017 15:20:06 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 08EA66A0; Thu, 2 Mar 2017 15:20:06 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id v22FJx8e058672 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Mar 2017 07:19:59 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id v22FJxW3058671; Thu, 2 Mar 2017 07:19:59 -0800 (PST) (envelope-from sgk) Date: Thu, 2 Mar 2017 07:19:59 -0800 From: Steve Kargl To: Mateusz Guzik , Mark Millard , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] Message-ID: <20170302151959.GA58624@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> <20170225193103.GA4379@dft-labs.eu> <20170301061350.GA22378@dft-labs.eu> <20170302121021.GA32682@dft-labs.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170302121021.GA32682@dft-labs.eu> User-Agent: Mutt/1.7.2 (2016-11-26) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 15:20:06 -0000 On Thu, Mar 02, 2017 at 01:10:21PM +0100, Mateusz Guzik wrote: > On Wed, Mar 01, 2017 at 09:45:07AM -0800, Mark Millard wrote: > > > > Summary of the transition interval: > > > > So for powerpc64 (and powerpc?) It is a good > > idea to avoid anything that is after -r313254 > > and before -r314474 in head. (Would this be > > appropriate for a UPDATING notice given its > > span?) > > > > There may be other architectures that might have > > a similar status(?): the last fixes involved were > > not in Machine Dependent code. (Some architectures > > are apparently insensitive to the errors, such as > > amd64). > > > > When following current you are expected to be on the newest revision, > so I don't think mentioning interim broken releases makes much sense. > Documenting the range may aid those bisecting src/ to find a bug. How is one to know that anything in the range that Mark points out should be skipped on powerpc64? -- Steve From owner-freebsd-ppc@freebsd.org Thu Mar 2 17:37:57 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B920CF569D; Thu, 2 Mar 2017 17:37:57 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 DBA939CA; Thu, 2 Mar 2017 17:37:56 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-qk0-x241.google.com with SMTP id j127so2606157qke.0; Thu, 02 Mar 2017 09:37:56 -0800 (PST) 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=/PPo8TRFXZ+i/j0gFPg7doFbX1iiurESlz8d4g84ybg=; b=vBG7jKwghFiuLnUx+WH6AdKfF9f3MDoxme2xfxkB8+v9ardThFNfw3vM9E+QtEWxnM dUeLOFInQjimQkBof3wuzG5Rw7/vzlJHQNWJmPDYQxuEMlQOcbc/+35FqTLBDzxoAbhd haC0bz+gqxLFT7DBI0D16LyNJTpzWkMGU7drdKx6RiUCZdCXS5lgvMe1z6b4puA9mEhw A8/53eLZeDyTwCJGVO2vOV1fNzzax++2a8TUQTXzT6CPncBKrMf8w094h/EWtDj2zVFS nWDS1LERsWW2Mre2D7E5CklbZ4coPgC0GjODXd4BNqezfIMMNbGwVJ4mxk0SWxgCidCY qP8w== 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=/PPo8TRFXZ+i/j0gFPg7doFbX1iiurESlz8d4g84ybg=; b=MF6FSmx8I4MdWuO9t+U19QX2efCUOWtQp0abljLzSEIZf0Dx9kbhbTQ3zq3wSx6okf Q6blAIRziSvPrfv2UrSlgpw3C5dYwO10IWwq+0lFUVfEh34uX1CDh0yAzM6r5kL20JjI V+vpeqJTQUKl35y8tvIhF138bTf2QdWT6qiGpsdvp8zoD1W/R6KErsxUg1g994dIaEX2 ypeF2+WtXJ/Er2elvgGgwOwPwbuZpQI3hyzUm+6KxZ1PhhtfTtzrNqGPg4SWjxyA3Fuj t9FWu1EOl3yhlh5JaXw5/zRnjar/a+l+yCLQiWoJNCPr69Dy1yinNdiMEdzrKs5uw7M9 Bbrw== X-Gm-Message-State: AMke39mCSsKs+/jLNptf2TcQSLakZfhS8Edo49PITR5G/f1ufi5sYYF0NKHFML7WX4/AdKoADQbmySWew81Itg== X-Received: by 10.55.164.208 with SMTP id n199mr18862432qke.163.1488476276005; Thu, 02 Mar 2017 09:37:56 -0800 (PST) MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.12.157.69 with HTTP; Thu, 2 Mar 2017 09:37:55 -0800 (PST) In-Reply-To: References: From: Justin Hibbits Date: Thu, 2 Mar 2017 11:37:55 -0600 X-Google-Sender-Auth: Q9xy-ydfkUacGFwANdhegW5xurM Message-ID: Subject: Re: PowerMac G5 and KMS To: hiroo.ono+freebsd@gmail.com Cc: FreeBSD PowerPC ML , freebsd-x11@freebsd.org, FreeBSD Current Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 17:37:57 -0000 On Thu, Mar 2, 2017 at 5:42 AM, Hiroo Ono (=E5=B0=8F=E9=87=8E=E5=AF=9B=E7= =94=9F) wrote: > I recently installed 12-current powerpc64 r313561 to a PowerMac G5 > (it is dual processor, but I do not know its detail). > > When I try to load drm2.ko and radeonkms.ko, > the screen turns into black and recovers, then the system locks. > kldload command does not return, no response to keyboard input, etc. > > Is it possible to use KMS on FreeBSD/powerpc64? > > The log in /var/log/messages is > > after "kldload drm2", > > kernel: info: [drm] Initialized drm 1.1.0 20060810 > > and then, after "kldload radeonkms", > > kernel: iic0: on iicbus0 > kernel: iic1: on iicbus1 > kernel: drmn0: on vgapci0 > kernel: info: [drm] RADEON_IS_AGP > kernel: info: [drm] initializing kernel modesetting (RV350 0x1002:0x4150 > 0x1002:0x4150). > kernel: info: [drm] register mmio base: 0x90000000 > kernel: info: [drm] register mmio size: 65536 > kernel: info: [drm] igp_read_bios_from_vram: =3D=3D=3D> Try IGP's VRAM... > kernel: info: [drm] igp_read_bios_from_vram: VRAM base address: 0x9800000= 0 > kernel: info: [drm] igp_read_bios_from_vram: Map address: > 0xc000000061412000 (262144 bytes) > kernel: info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature: > 0x0000 > kernel: info: [drm] radeon_read_bios: =3D=3D=3D> Try PCI Expansion ROM... > kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000 > (131072 bytes) > kernel: info: [drm] radeon_read_bios: Incorrect BIOS signature: 0x2AFF > kernel: info: [drm] legacy_read_disabled_bios: =3D=3D=3D> Try disabled BI= OS > (legacy)... > kernel: info: [drm] radeon_read_bios: =3D=3D=3D> Try PCI Expansion ROM... > kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000 > (131072 bytes) > > As the system locks up here, I have to power it off forcibly. Congratulations (?) you are quite possibly the first person to report even attempting to use radeonkms on powerpc64. Frankly, I'm not surprised that it doesn't work for you. Unfortunately, I don't have a solution, or even a means to track it down. Looking at the log snippet, my first guess is there may need to be a provision added to the driver for non-x86. Do you know what card this is? Adding a couple other lists with people who might have more insight. If it can be made to work, I'd definitely want to get a Radeon card for my = G5(s) - Justin From owner-freebsd-ppc@freebsd.org Thu Mar 2 21:34:40 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B925CF54AA for ; Thu, 2 Mar 2017 21:34:40 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-195.reflexion.net [208.70.211.195]) (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 C4C067BB for ; Thu, 2 Mar 2017 21:34:39 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 17992 invoked from network); 2 Mar 2017 20:34:38 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 2 Mar 2017 20:34:38 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Thu, 02 Mar 2017 15:34:38 -0500 (EST) Received: (qmail 17498 invoked from network); 2 Mar 2017 20:34:38 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 2 Mar 2017 20:34:38 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id E4282EC9202; Thu, 2 Mar 2017 12:34:37 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: PowerMac G5 and KMS From: Mark Millard In-Reply-To: Date: Thu, 2 Mar 2017 12:34:37 -0800 Cc: hiroo.ono+freebsd@gmail.com, freebsd-x11@freebsd.org, FreeBSD Current , FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <4EA794E6-D435-4958-853C-5421E03F3B46@dsl-only.net> References: To: Justin Hibbits X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2017 21:34:40 -0000 On 2017-Mar-2, at 9:37 AM, Justin Hibbits = wrote: > On Thu, Mar 2, 2017 at 5:42 AM, Hiroo Ono (=E5=B0=8F=E9=87=8E=E5=AF=9B=E7= =94=9F) > wrote: >> I recently installed 12-current powerpc64 r313561 to a PowerMac G5 >> (it is dual processor, but I do not know its detail). >>=20 >> When I try to load drm2.ko and radeonkms.ko, >> the screen turns into black and recovers, then the system locks. >> kldload command does not return, no response to keyboard input, etc. >>=20 >> Is it possible to use KMS on FreeBSD/powerpc64? >>=20 >> The log in /var/log/messages is >>=20 >> after "kldload drm2", >>=20 >> kernel: info: [drm] Initialized drm 1.1.0 20060810 >>=20 >> and then, after "kldload radeonkms", >>=20 >> kernel: iic0: on iicbus0 >> kernel: iic1: on iicbus1 >> kernel: drmn0: on vgapci0 >> kernel: info: [drm] RADEON_IS_AGP >> kernel: info: [drm] initializing kernel modesetting (RV350 = 0x1002:0x4150 >> 0x1002:0x4150). >> kernel: info: [drm] register mmio base: 0x90000000 >> kernel: info: [drm] register mmio size: 65536 >> kernel: info: [drm] igp_read_bios_from_vram: =3D=3D=3D> Try IGP's = VRAM... >> kernel: info: [drm] igp_read_bios_from_vram: VRAM base address: = 0x98000000 >> kernel: info: [drm] igp_read_bios_from_vram: Map address: >> 0xc000000061412000 (262144 bytes) >> kernel: info: [drm] igp_read_bios_from_vram: Incorrect BIOS = signature: >> 0x0000 >> kernel: info: [drm] radeon_read_bios: =3D=3D=3D> Try PCI Expansion = ROM... >> kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000 >> (131072 bytes) >> kernel: info: [drm] radeon_read_bios: Incorrect BIOS signature: = 0x2AFF >> kernel: info: [drm] legacy_read_disabled_bios: =3D=3D=3D> Try = disabled BIOS >> (legacy)... >> kernel: info: [drm] radeon_read_bios: =3D=3D=3D> Try PCI Expansion = ROM... >> kernel: info: [drm] radeon_read_bios: Map address: 0xc000000061412000 >> (131072 bytes) >>=20 >> As the system locks up here, I have to power it off forcibly. >=20 > Congratulations (?) you are quite possibly the first person to report > even attempting to use radeonkms on powerpc64. Frankly, I'm not > surprised that it doesn't work for you. Unfortunately, I don't have a > solution, or even a means to track it down. Looking at the log > snippet, my first guess is there may need to be a provision added to > the driver for non-x86. Do you know what card this is? >=20 > Adding a couple other lists with people who might have more insight. >=20 > If it can be made to work, I'd definitely want to get a Radeon card = for my G5(s) >=20 > - Justin Back on 2014-Nov-21 I wrote the following in one of my messages on the lists on that day: > FYI: I've been building and trying Jean-S=C3=A9bastien P=C3=A9dron's = kms-drm-update-38 branch when Jean requested (sometimes with patches = that Jean provided). This was to give Jean some (indirect) access to a = powerpc64 (PowerMac G5) Radeon context for some radeonkms development. = (Jean had been hoping to get my card going in that context.) We got to = the point that a kldload for radeonkms did not complain/refuse but the = display was then munged up and the driver could not find the Video BIOS. = The fact that it is a Radeon X1950 for the video hardware may make it = odder than usual for PowerMac G5 Radeons. But it is the only Radeon that = I have access to for G5's. (The card works in Mac OS X 10.5.)=20 (As I remember this was a PowerMac G5 so-called "Quad Core" as the G5 context. I do not currently have access to the X1950 card.) I'm not sure from what I read if things are about the same vs. if things are worse now. I do not remember the details from back then, such as console vs. X11 that I was not explicit about in the quoted material. I eventually gave up on using X11 "for a time" --and have not tried = again so far. I've no clue about the current status for X11 on PowerMacs of any kind --or what I'd need to do to try it for the Radeon X1950 or any NVIDIA cards. (Currently an NVIDIA card is installed.) I will eventually have access to the X1950 again, but not soon. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Fri Mar 3 09:38:17 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 89123CF5404 for ; Fri, 3 Mar 2017 09:38:17 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-202.reflexion.net [208.70.211.202]) (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 2928C1068 for ; Fri, 3 Mar 2017 09:38:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2760 invoked from network); 3 Mar 2017 09:38:15 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 3 Mar 2017 09:38:15 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Fri, 03 Mar 2017 04:38:15 -0500 (EST) Received: (qmail 27602 invoked from network); 3 Mar 2017 09:38:14 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 3 Mar 2017 09:38:14 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 107A3EC881F; Fri, 3 Mar 2017 01:38:14 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <20170302151959.GA58624@troutmask.apl.washington.edu> Date: Fri, 3 Mar 2017 01:38:13 -0800 Cc: svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <8D803761-644A-4E72-928F-2E96525A1A11@dsl-only.net> References: <20170225002300.GC19697@dft-labs.eu> <12339EDD-5663-40E0-8553-821EF9B6CDEB@dsl-only.net> <477BA631-AB85-4E77-8BA3-CD2AFAD5E405@dsl-only.net> <9A63B36E-5F81-4ECD-A2A2-AB442AAC26A6@dsl-only.net> <20170225193103.GA4379@dft-labs.eu> <20170301061350.GA22378@dft-labs.eu> <20170302121021.GA32682@dft-labs.eu> <20170302151959.GA58624@troutmask.apl.washington.edu> To: sgk@troutmask.apl.washington.edu, Mateusz Guzik X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 09:38:17 -0000 On 2017-Mar-2, at 7:19 AM, Steve Kargl wrote: On Thu, Mar 02, 2017 at 01:10:21PM +0100, Mateusz Guzik wrote: > On Wed, Mar 01, 2017 at 09:45:07AM -0800, Mark Millard wrote: >>=20 >>> Summary of the transition interval: >>>=20 >>> So for powerpc64 (and powerpc?) It is a good >>> idea to avoid anything that is after -r313254 >>> and before -r314474 in head. (Would this be >>> appropriate for a UPDATING notice given its >>> span?) >>>=20 >>> There may be other architectures that might have >>> a similar status(?): the last fixes involved were >>> not in Machine Dependent code. (Some architectures >>> are apparently insensitive to the errors, such as >>> amd64). >>>=20 >>=20 >> When following current you are expected to be on the newest revision, >> so I don't think mentioning interim broken releases makes much sense. >>=20 >=20 > Documenting the range may aid those bisecting src/ to find a bug.=20 > How is one to know that anything in the range that Mark points > out should be skipped on powerpc64? >=20 > --=20 > Steve I have tested with a TARGET_ARCH=3Dpowerpc -r314473 build and its kernel version has locking problems like TARGET_ARCH=3Dpowerpc64 does for that version. [Note: This was run on a PowerMac G5 so-called "Quad Core" so most of the memory was ignored.] Both TARGET_ARCH=3Dpowerpc64 and TARGET_ARCH=3Dpowerpc need -r314474 or later as of the new locking. I've not explicitly tested other architectures. As I remember armv6/v7 are classified as having some from of a weak memory model compared to the likes of amd64. If so armv6/v7 might be candidates for having problems. There might be other candidates. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Fri Mar 3 14:17:36 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A068CF5288; Fri, 3 Mar 2017 14:17:36 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 25AC415AD; Fri, 3 Mar 2017 14:17:35 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v23EHXpl070032; Fri, 3 Mar 2017 06:17:33 -0800 (PST) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v23EHX59070031; Fri, 3 Mar 2017 06:17:33 -0800 (PST) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201703031417.v23EHX59070031@pdx.rh.CN85.dnsmgr.net> Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] In-Reply-To: <8D803761-644A-4E72-928F-2E96525A1A11@dsl-only.net> To: Mark Millard Date: Fri, 3 Mar 2017 06:17:33 -0800 (PST) CC: sgk@troutmask.apl.washington.edu, Mateusz Guzik , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 14:17:36 -0000 > On 2017-Mar-2, at 7:19 AM, Steve Kargl wrote: > > On Thu, Mar 02, 2017 at 01:10:21PM +0100, Mateusz Guzik wrote: > > On Wed, Mar 01, 2017 at 09:45:07AM -0800, Mark Millard wrote: > >> > >>> Summary of the transition interval: > >>> > >>> So for powerpc64 (and powerpc?) It is a good > >>> idea to avoid anything that is after -r313254 > >>> and before -r314474 in head. (Would this be > >>> appropriate for a UPDATING notice given its > >>> span?) > >>> > >>> There may be other architectures that might have > >>> a similar status(?): the last fixes involved were > >>> not in Machine Dependent code. (Some architectures > >>> are apparently insensitive to the errors, such as > >>> amd64). > >>> > >> > >> When following current you are expected to be on the newest revision, > >> so I don't think mentioning interim broken releases makes much sense. > >> > > > > Documenting the range may aid those bisecting src/ to find a bug. > > How is one to know that anything in the range that Mark points > > out should be skipped on powerpc64? > > > > -- > > Steve > > I have tested with a TARGET_ARCH=powerpc -r314473 build and > its kernel version has locking problems like > TARGET_ARCH=powerpc64 does for that version. > > [Note: This was run on a PowerMac G5 so-called "Quad Core" > so most of the memory was ignored.] > > Both TARGET_ARCH=powerpc64 and TARGET_ARCH=powerpc need -r314474 > or later as of the new locking. > > I've not explicitly tested other architectures. As I remember > armv6/v7 are classified as having some from of a weak memory > model compared to the likes of amd64. If so armv6/v7 might be > candidates for having problems. There might be other candidates. I also had locking issues on amd64 around this build time that sent me down a week long rabbit hole chasing what I thought was a bug in the new AMD/IOMMU code. IMHO if we can at least flag prior snapshot builds as "Broken for reason X" it might save someone some time and time is a one way depleting resource usually worth saving if possible. If needed I can dig out the specifc build. Oh, nvm, let me just do that, it was r309302. This revision I beleive is a november snapshot. It has kernel panics due to spinlock timeout and sparatic deadlock that is undetected. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-ppc@freebsd.org Fri Mar 3 18:11:12 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47FFCCF6B21 for ; Fri, 3 Mar 2017 18:11:12 +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 mx1.freebsd.org (Postfix) with ESMTPS id 366771248 for ; Fri, 3 Mar 2017 18:11:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v23IBBn8047109 for ; Fri, 3 Mar 2017 18:11:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 217375] installer: powerpc kernel reboots before reaching installer (ibook key lime se) Date: Fri, 03 Mar 2017 18:11:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eekee57@fastmail.fm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 18:11:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217375 --- Comment #6 from eekee57@fastmail.fm --- Created attachment 180472 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180472&action= =3Dedit screenshot: fbsd 11 iso boot failure on ibook --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri Mar 3 18:16:01 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BA3ECF6E65 for ; Fri, 3 Mar 2017 18:16:01 +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 mx1.freebsd.org (Postfix) with ESMTPS id 5B39B1781 for ; Fri, 3 Mar 2017 18:16:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v23IG1of046342 for ; Fri, 3 Mar 2017 18:16:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 217375] installer: powerpc kernel reboots before reaching installer (ibook key lime se) Date: Fri, 03 Mar 2017 18:16:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: eekee57@fastmail.fm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 18:16:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217375 --- Comment #7 from eekee57@fastmail.fm --- (In reply to Tom Lane from comment #5) Why didn't I think of that? Done. The backtrace is identical, if my eyes aren't fooling me. The fault a= ddr is different. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri Mar 3 22:58:54 2017 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06418CF6EE5 for ; Fri, 3 Mar 2017 22:58:54 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-195.reflexion.net [208.70.211.195]) (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 B5DA91882 for ; Fri, 3 Mar 2017 22:58:53 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 10429 invoked from network); 3 Mar 2017 22:32:51 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 3 Mar 2017 22:32:51 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.30.0) with SMTP; Fri, 03 Mar 2017 17:32:06 -0500 (EST) Received: (qmail 10457 invoked from network); 3 Mar 2017 22:32:05 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 3 Mar 2017 22:32:05 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id F13BEEC91A0; Fri, 3 Mar 2017 14:32:04 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: svn commit: r313268 - head/sys/kern [through -r313271 for atomic_fcmpset use and later: fails on PowerMac G5 "Quad Core"; -r313266 works] From: Mark Millard In-Reply-To: <201703031417.v23EHX59070031@pdx.rh.CN85.dnsmgr.net> Date: Fri, 3 Mar 2017 14:32:04 -0800 Cc: sgk@troutmask.apl.washington.edu, Mateusz Guzik , svn-src-head@freebsd.org, FreeBSD Current , Justin Hibbits , mjg@freebsd.org, FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: References: <201703031417.v23EHX59070031@pdx.rh.CN85.dnsmgr.net> To: "Rodney W. Grimes" X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Mar 2017 22:58:54 -0000 On 2017-Mar-3, at 6:17 AM, Rodney W. Grimes wrote: >> On 2017-Mar-2, at 7:19 AM, Steve Kargl wrote: >>=20 >> On Thu, Mar 02, 2017 at 01:10:21PM +0100, Mateusz Guzik wrote: >>> On Wed, Mar 01, 2017 at 09:45:07AM -0800, Mark Millard wrote: >>>>=20 >>>>> Summary of the transition interval: >>>>>=20 >>>>> So for powerpc64 (and powerpc?) It is a good >>>>> idea to avoid anything that is after -r313254 >>>>> and before -r314474 in head. (Would this be >>>>> appropriate for a UPDATING notice given its >>>>> span?) >>>>>=20 >>>>> There may be other architectures that might have >>>>> a similar status(?): the last fixes involved were >>>>> not in Machine Dependent code. (Some architectures >>>>> are apparently insensitive to the errors, such as >>>>> amd64). >>>>>=20 >>>>=20 >>>> When following current you are expected to be on the newest = revision, >>>> so I don't think mentioning interim broken releases makes much = sense. >>>>=20 >>>=20 >>> Documenting the range may aid those bisecting src/ to find a bug.=20 >>> How is one to know that anything in the range that Mark points >>> out should be skipped on powerpc64? >>>=20 >>> --=20 >>> Steve >>=20 >> I have tested with a TARGET_ARCH=3Dpowerpc -r314473 build and >> its kernel version has locking problems like >> TARGET_ARCH=3Dpowerpc64 does for that version. >>=20 >> [Note: This was run on a PowerMac G5 so-called "Quad Core" >> so most of the memory was ignored.] >>=20 >> Both TARGET_ARCH=3Dpowerpc64 and TARGET_ARCH=3Dpowerpc need -r314474 >> or later as of the new locking. >>=20 >> I've not explicitly tested other architectures. As I remember >> armv6/v7 are classified as having some from of a weak memory >> model compared to the likes of amd64. If so armv6/v7 might be >> candidates for having problems. There might be other candidates. >=20 > I also had locking issues on amd64 around this build time that > sent me down a week long rabbit hole chasing what I thought was > a bug in the new AMD/IOMMU code. IMHO if we can at least > flag prior snapshot builds as "Broken for reason X" it might > save someone some time and time is a one way depleting resource > usually worth saving if possible. >=20 > If needed I can dig out the specifc build. Oh, nvm, let me > just do that, it was r309302. This revision I beleive is > a november snapshot. It has kernel panics due to spinlock > timeout and sparatic deadlock that is undetected. >=20 >=20 > --=20 > Rod Grimes rgrimes at = freebsd.org Sounds like that amd64 -r309302 problem might be another good example. Locking tends to be central and heavily used. When it breaks many other things tend to also end up broken. This is the sort of context I was thinking about if it goes on very long. I'm not sure that the -r309302 problem would reproduce at -r313259 so -r309302 might be a separate issue. I've no clue what -rdddddd range had the amd64 -r309302 problem. Details that I'm aware of are something like: -r309302 is dated 2016-Nov-30. (your reported amd64 locking problem's = -rdddddd) -r312973 is dated 2017-Jan-30. (example add of an atomic_fcmpset = implementation) (getting ready for machine independent = usage) -r313259 is dated 2017-Feb-5. (last before "machine independent use of = atomic_fcmpset"?) (powerpc64 and powerpc working here) -r313260 is dated 2017-Feb-5. (first machine-independent usage of = atomic_fcmpset?) . . . (various machine-independent atomic_fcmpset usage check-ins) . . . -r313271 is dated 2017-Feb-5. (observed powerpc64 failures for this = version) (powerpc would fail too) . . . (various machine-independent atomic_fcmpset usage check-ins) . . . . . . (powerpc64 [and powerpc] continuing to fail) . . . -r314474 is dated 2017-Mar-1. (powerpc64 and powerpc started working) =3D=3D=3D Mark Millard markmi at dsl-only.net