From owner-freebsd-ppc@FreeBSD.ORG Mon Jul 22 01:51:24 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BDB5FBF0; Mon, 22 Jul 2013 01:51:24 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-bk0-x22b.google.com (mail-bk0-x22b.google.com [IPv6:2a00:1450:4008:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 29EC81C62; Mon, 22 Jul 2013 01:51:23 +0000 (UTC) Received: by mail-bk0-f43.google.com with SMTP id jm2so2288096bkc.16 for ; Sun, 21 Jul 2013 18:51:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=8Q6eurn5suzu7pzNDCtFihUl+Bgo4K3UWf6D5rmIWzI=; b=qlRvIPeNM4fFTDi//ByOIPNM4mr0qwv2fuHwrCePZidsoLQJnTI7VC5KaqqtvXgK3P wUmgltKvv0+1aWTZ298DXXbf7AoueORrzob89WufXA9SzEmPznqyuIZB1z1lyZ8J1Jgq ISYAu/Q2VJMb1bjjVuM9OKkJ+U2+6RPnRczyUpQD/PrnrP/OPCP/LU/fWeBxIJMtKhLQ AwmMQHL1fPMZoDmnpP+xCl7XRo7+81TPy8NGGq+p2o8GNtKoyKC8ZH7a8Uqb3arnC/Cf 6NDYQErYdaxbr3bRdhzIBQQ4c60kaOL4lr8ATZ6TPgpKpxGldJzXHlcZV4OhLyfcuEqP p8AQ== MIME-Version: 1.0 X-Received: by 10.204.163.142 with SMTP id a14mr3554858bky.59.1374457882118; Sun, 21 Jul 2013 18:51:22 -0700 (PDT) Sender: chmeeedalf@gmail.com Received: by 10.204.9.148 with HTTP; Sun, 21 Jul 2013 18:51:22 -0700 (PDT) Date: Sun, 21 Jul 2013 18:51:22 -0700 X-Google-Sender-Auth: SUyy0p7lUPPlorhhJDhqJqd-uSg Message-ID: Subject: contigmalloc won't allocate more than one page From: Justin Hibbits To: FreeBSD PowerPC ML , Nathan Whitehorn Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 01:51:24 -0000 I've been spending the day trying to get ofwdump to work correctly on ppc64, and found that for at least one property it needs a full page for the property value. So, to fix this I checked the maximum ioctl sizes, and with a buffer it totals 5 pages, so I tried to get ofw_real_bounce_alloc() to allocate 5 pages instead of one. WIth this, it hangs when allocating the memory for the buffer. So, I tried just two pages, and got the same result. After this failure, I tried creating a static array of 8192 bytes, and it doesn't even get to the black screen now. Obviously, the better way to go would be to allocate it, but I don't have enough understanding of the VM system and the OEA64 VM code to fix this bug. - Justin From owner-freebsd-ppc@FreeBSD.ORG Mon Jul 22 04:54:49 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 08252E9F; Mon, 22 Jul 2013 04:54:49 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8A0E521D9; Mon, 22 Jul 2013 04:54:48 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r6M4sPLd080185; Mon, 22 Jul 2013 07:54:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r6M4sPLd080185 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r6M4sPQ1080184; Mon, 22 Jul 2013 07:54:25 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 22 Jul 2013 07:54:25 +0300 From: Konstantin Belousov To: Justin Hibbits Subject: Re: contigmalloc won't allocate more than one page Message-ID: <20130722045425.GF5991@kib.kiev.ua> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XGa5gNSGTk93P04E" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 04:54:49 -0000 --XGa5gNSGTk93P04E Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 21, 2013 at 06:51:22PM -0700, Justin Hibbits wrote: > I've been spending the day trying to get ofwdump to work correctly on > ppc64, and found that for at least one property it needs a full page for > the property value. So, to fix this I checked the maximum ioctl sizes, a= nd > with a buffer it totals 5 pages, so I tried to get ofw_real_bounce_alloc() > to allocate 5 pages instead of one. WIth this, it hangs when allocating > the memory for the buffer. So, I tried just two pages, and got the same > result. Could you test on other architectures, esp. on x86i, please ? What version do you use, head ? >=20 > After this failure, I tried creating a static array of 8192 bytes, and it > doesn't even get to the black screen now. >=20 > Obviously, the better way to go would be to allocate it, but I don't have > enough understanding of the VM system and the OEA64 VM code to fix this b= ug. >=20 > - Justin > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" --XGa5gNSGTk93P04E Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJR7LsAAAoJEJDCuSvBvK1BwLQP/35wr3rLUkhQKcepHt2+l8pz IjCsRiRl91m5GHHBBWEoJYqCDM8G1tja8Qb3UoZFor1sElmndE+ZZIeoMYhRY7yb lvh8+1BmxoLsLlNceG+1aCrjFQVHOIxps8VvX1TblAQ2yPSinwrHqxBg1XlOtt91 82ou+D1y2LlYZ8+tlxlAklq4KU32HA5+YJOYzD/VL3y1RWOQ8W8gUywb78fsKopU XFHFeTjOY9bcHkyK51z7fPpv+U3d86EKMzPEiBGasTRv8DkPJTY2VdorKljpoMKv I1/4FzIgdNdX8oLcPmYgB09xk/urf7assJU49WWMIt808B4mPrFH5VGteaBaxQhP QEwDuO3T/T37/GNFvCBzOgrnHJ8Yp+sI3rbkE61z/St2hJG7I5/AVHxQIfyKyP3f PNQSuEWupq5w0VPt7D79dQq5/ZwItUs6/yBGLhSN3sBoylkXh+Z9eGxkXZgQC2If eQwnKO3n3xx/tS93TYZsqpmcSNmYWn2DVDZmFtBdzXPnswx/w+LiMQkakKbiU46g SehkzP3ecgN7QB/2JekydXAiVuNW3rPT1bjv2Uw0JpNfmwRdwE4pNJSZWNyH4opA diusdWTLC6qk+B0OlupgvunmA2qjSLyJ1vSw329JwWP9pZXx2TiUbOkLwGgf6bx9 o/DzTKp/YY9wVVJCEoRZ =M1We -----END PGP SIGNATURE----- --XGa5gNSGTk93P04E-- From owner-freebsd-ppc@FreeBSD.ORG Mon Jul 22 11:06:50 2013 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3EE7849C for ; Mon, 22 Jul 2013 11:06:50 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2FF1B24A8 for ; Mon, 22 Jul 2013 11:06:50 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6MB6owY053797 for ; Mon, 22 Jul 2013 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6MB6nXg053795 for freebsd-ppc@FreeBSD.org; Mon, 22 Jul 2013 11:06:49 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Jul 2013 11:06:49 GMT Message-Id: <201307221106.r6MB6nXg053795@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-ppc@FreeBSD.org Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 11:06:50 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o power/180593 ppc PowerMac G5 shuts down when building pcre o power/178038 ppc clang++ fails to produce a binary in powerpc64 o power/175151 ppc Loader fails to load modules on PPC64 o power/170340 ppc Enabling geom-mirror on 9.1-powerpc64 prevents the sys o power/164225 ppc Boot fails on IBM 7028-6E1 (heap memory claim failed) o power/161947 ppc multimedia/libdvdnav builds broken binaries on big end o power/161045 ppc X doesn't detect ADB mouse up event until another even o power/149009 ppc sysinstall(8) on powerpc fails to install manpages, so o power/140241 ppc [kernel] [patch] Linker set problems on PowerPC EABI o power/135576 ppc gdb cannot debug threaded programs on ppc o power/133503 ppc [sound] Sound stutter after switching ttys o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer 12 problems total. From owner-freebsd-ppc@FreeBSD.ORG Mon Jul 22 20:35:50 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 62804EE8; Mon, 22 Jul 2013 20:35:50 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-bk0-x233.google.com (mail-bk0-x233.google.com [IPv6:2a00:1450:4008:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF3DB2337; Mon, 22 Jul 2013 20:35:49 +0000 (UTC) Received: by mail-bk0-f51.google.com with SMTP id ji1so2661041bkc.38 for ; Mon, 22 Jul 2013 13:35:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Q1SuMB4d40TKDdh2ajTY0qnCYLI60vtQbb55bVt5eps=; b=JmShtvKYYIpXIRP8zXUf0jsK5XbrROC1o6YkGGB7iuEYoG9kd1sm5QadTFw8oJNbrg nm/T8XKRE25/rhCK9VPoQaEmUod4I9sSenhEok0qqNdRFRK/B0MCGNlibXB3XAxjuNLx xq5JAM+wDHbNCN8woAC86C1fZ0PCxKpEvPkuu869U9k5tdv+AqjgFfQ9OHZ8bDXwXSs8 k72pPrryUg9JkI9XJGVUGmUvrOakjJgGDCLi/yCINqaCbDn/1kHe1DGavGOmifR8YEw9 KMeJXaS3DeFRVvgGOHgOa2hXANDHp6VnDLk/eJlHJ7w1O8IUPTqQ4S5+LIvgjvoxygBj WWRg== MIME-Version: 1.0 X-Received: by 10.204.66.133 with SMTP id n5mr4143976bki.38.1374525347784; Mon, 22 Jul 2013 13:35:47 -0700 (PDT) Sender: chmeeedalf@gmail.com Received: by 10.204.9.148 with HTTP; Mon, 22 Jul 2013 13:35:47 -0700 (PDT) In-Reply-To: <20130722045425.GF5991@kib.kiev.ua> References: <20130722045425.GF5991@kib.kiev.ua> Date: Mon, 22 Jul 2013 13:35:47 -0700 X-Google-Sender-Auth: vZamK6TpvUvQCNhXJnAKke4SHuw Message-ID: Subject: Re: contigmalloc won't allocate more than one page From: Justin Hibbits To: Konstantin Belousov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jul 2013 20:35:50 -0000 On Sun, Jul 21, 2013 at 9:54 PM, Konstantin Belousov wrote: > On Sun, Jul 21, 2013 at 06:51:22PM -0700, Justin Hibbits wrote: > > I've been spending the day trying to get ofwdump to work correctly on > > ppc64, and found that for at least one property it needs a full page for > > the property value. So, to fix this I checked the maximum ioctl sizes, > and > > with a buffer it totals 5 pages, so I tried to get > ofw_real_bounce_alloc() > > to allocate 5 pages instead of one. WIth this, it hangs when allocating > > the memory for the buffer. So, I tried just two pages, and got the same > > result. > Could you test on other architectures, esp. on x86i, please ? > Unfortunately for this test, all I have physical access to are PowerPC. It's possible that contigmalloc() can allocate more memory, but possibly later in the boot cycle, as this code runs very early on. > What version do you use, head ? > Yes, running head as of a few days ago. - Justin From owner-freebsd-ppc@FreeBSD.ORG Tue Jul 23 03:39:15 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 142AD6C1 for ; Tue, 23 Jul 2013 03:39:15 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D61A62393 for ; Tue, 23 Jul 2013 03:39:14 +0000 (UTC) Received: by mail-ob0-f176.google.com with SMTP id v19so9110387obq.35 for ; Mon, 22 Jul 2013 20:39:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gKoxhpb9qnEQg4p3aNqskIcUVU/f3DsI69SkE5dfDVI=; b=KeorwuH1y5g55gTJAAtTgPzoZg4w41uGIzbPxRiVZcwS70+EZPfLdG1r7iR5LdacNw 6zmKd7YxQ8gt3cRrIMtwhLU0zgEVfVthdj6P4m1lDxqmjF7BWMurZO2avs19KYHM5ybb 8NOXcg3ZnPvRgZPIAE4JI1bLObKOIxIz2vlkrlc4EncUtY7aINW96x4EocjMFchjz0rj JgMZK+BWayO278yIwwPkDqnXDPfGmXRVygQEb7MkoIQ0lGa9W83iImIhJqa9x8ggPG3X LqgdqPv4HGtV7xL/T9K31izWQ2V2e26x2wNS8OXDPMoBLTo6HwVo+wzvEeZaovFTFgxg zWTQ== MIME-Version: 1.0 X-Received: by 10.182.88.202 with SMTP id bi10mr22901892obb.91.1374550754041; Mon, 22 Jul 2013 20:39:14 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Mon, 22 Jul 2013 20:39:13 -0700 (PDT) In-Reply-To: References: <20130722045425.GF5991@kib.kiev.ua> Date: Mon, 22 Jul 2013 23:39:13 -0400 Message-ID: Subject: Re: contigmalloc won't allocate more than one page From: Super Bisquit To: Justin Hibbits Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 03:39:15 -0000 Why not post this to hackers or the normal questions list to see if anyone has an x86i machine for testing the code? On Mon, Jul 22, 2013 at 4:35 PM, Justin Hibbits wrote: > On Sun, Jul 21, 2013 at 9:54 PM, Konstantin Belousov >wrote: > > > On Sun, Jul 21, 2013 at 06:51:22PM -0700, Justin Hibbits wrote: > > > I've been spending the day trying to get ofwdump to work correctly on > > > ppc64, and found that for at least one property it needs a full page > for > > > the property value. So, to fix this I checked the maximum ioctl sizes, > > and > > > with a buffer it totals 5 pages, so I tried to get > > ofw_real_bounce_alloc() > > > to allocate 5 pages instead of one. WIth this, it hangs when > allocating > > > the memory for the buffer. So, I tried just two pages, and got the > same > > > result. > > Could you test on other architectures, esp. on x86i, please ? > > > > Unfortunately for this test, all I have physical access to are PowerPC. > It's possible that contigmalloc() can allocate more memory, but possibly > later in the boot cycle, as this code runs very early on. > > > > What version do you use, head ? > > > > Yes, running head as of a few days ago. > > - Justin > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@FreeBSD.ORG Tue Jul 23 14:25:48 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EDB5E94E for ; Tue, 23 Jul 2013 14:25:48 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-bk0-x22c.google.com (mail-bk0-x22c.google.com [IPv6:2a00:1450:4008:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7FDAF2167 for ; Tue, 23 Jul 2013 14:25:48 +0000 (UTC) Received: by mail-bk0-f44.google.com with SMTP id 6so3054408bkj.17 for ; Tue, 23 Jul 2013 07:25:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wT3ymwlVpzbpynQoItDwaQuvl+VMEUdcHzInw87zosU=; b=uJ7AIBq8cyf54FzVVmEz/qUgdck8N3c78HN8V2UbxH11ufrhB1Tyf0OfkCziaErmvi zOBspyT24Skq3DKM5aqt/YLUmnaFp6pVSmZ+3+CMVsKZ2hKXGuiBTAymMNysATWl51wH w/iCyIcL4C3aOs1ZHWEll2I27KJuPvgT9pYGdIlPZ4ff1T9tE13N3NNcSBu+gMx2SeQJ GB+EihJEvN+S9/rEr4gUbMjK9ELVUVfctWwDWUr031I2n9kls/BFWj1Ftfzm2pTVAqWD 4/w0jqN7L8MclFeaq0+DxPDC37YOUpKtxiHC+gvieGpFgbExTq+u0RjAn9s877i/oJD6 Qf+g== MIME-Version: 1.0 X-Received: by 10.204.198.9 with SMTP id em9mr4572515bkb.131.1374589546635; Tue, 23 Jul 2013 07:25:46 -0700 (PDT) Sender: chmeeedalf@gmail.com Received: by 10.204.9.148 with HTTP; Tue, 23 Jul 2013 07:25:46 -0700 (PDT) In-Reply-To: References: <20130722045425.GF5991@kib.kiev.ua> Date: Tue, 23 Jul 2013 07:25:46 -0700 X-Google-Sender-Auth: yPDv3IFMra9Kcry3qWzIrSIrGM8 Message-ID: Subject: Re: contigmalloc won't allocate more than one page From: Justin Hibbits To: Super Bisquit Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jul 2013 14:25:49 -0000 On Mon, Jul 22, 2013 at 8:39 PM, Super Bisquit wrote: > Why not post this to hackers or the normal questions list to see if anyone > has an x86i machine for testing the code? > Because my initial assumption was that it was ppc only. On Mon, Jul 22, 2013 at 4:35 PM, Justin Hibbits wrote: > >> On Sun, Jul 21, 2013 at 9:54 PM, Konstantin Belousov > >wrote: >> >> > On Sun, Jul 21, 2013 at 06:51:22PM -0700, Justin Hibbits wrote: >> > > I've been spending the day trying to get ofwdump to work correctly on >> > > ppc64, and found that for at least one property it needs a full page >> for >> > > the property value. So, to fix this I checked the maximum ioctl >> sizes, >> > and >> > > with a buffer it totals 5 pages, so I tried to get >> > ofw_real_bounce_alloc() >> > > to allocate 5 pages instead of one. WIth this, it hangs when >> allocating >> > > the memory for the buffer. So, I tried just two pages, and got the >> same >> > > result. >> > Could you test on other architectures, esp. on x86i, please ? >> > >> > Turns out this was noise only. I had adjusted the size but not the boundary. Adjusting the boundary fixed it. - Justin From owner-freebsd-ppc@FreeBSD.ORG Wed Jul 24 22:35:20 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A25313FC; Wed, 24 Jul 2013 22:35:20 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 54D802FB1; Wed, 24 Jul 2013 22:35:20 +0000 (UTC) Received: by mail-ob0-f178.google.com with SMTP id fb19so14624837obc.9 for ; Wed, 24 Jul 2013 15:35:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=pOCzLiuKd1ibPU7fSZEMbQaqzFFolWANlKsPVycHvXU=; b=CpepZoWPcyNBrI2iHLW6/py5yBCbd0NzoPG9TG2ViHGGMvB2+XvAjM4lZxELw74Evr JYTDVgOHf/OBE2g+1ge6vgjR6uidp9yAgzqc6A1AnNi4fjidGAvODj8u81up7V7pDDYF Leg8HHlsSmwBrYqvTp78jqWTZw85ByL3s7act65QURVnI8yHvN9/y3CW/h04b5COhj0+ NNPxmwHq4vRqKSU1c0h00FbyfM0ASKo4MxjBL4R8zSuIHAvyARULH8O8r2eb0/fuQO1p en4nCe6huo9z9KAnAo7TSdFfsPO6+NmYPrtJPwSryxd/JOmTV9fIUmJhLL5Ppa1OYM3a riug== MIME-Version: 1.0 X-Received: by 10.60.125.100 with SMTP id mp4mr39048715oeb.60.1374705319592; Wed, 24 Jul 2013 15:35:19 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Wed, 24 Jul 2013 15:35:19 -0700 (PDT) Date: Wed, 24 Jul 2013 18:35:19 -0400 Message-ID: Subject: Kern.hz= +1 hertz at anything 2500 and above. From: Super Bisquit To: FreeBSD PowerPC ML , FreeBSD Hackers , freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Jul 2013 22:35:20 -0000 http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html This is the thread that I was referring to earlier. Since the patch is for 2009, what are the chances it would work with 10.x or 9.x? On PowerPC machines with a low MHz rate- or any machine with a CPU rate of 800 MHz or less- increasing the kern.hz improves performance and cuts down on latency. I am building audio applications and suites that are used in different projects. A G3 based machine should be able to run a kernel with kern.hz=5000 with no problem. Unfortunately, this cannot be done. @PowerPC: some of you may find that performance does increase at a higher kern.hz rate. @Hackers & Current: What's the chance that the default rate limit can be raised to 5k? From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 00:16:24 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 22149A6C; Thu, 25 Jul 2013 00:16:24 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5CAD722C2; Thu, 25 Jul 2013 00:16:23 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so1046363wgh.7 for ; Wed, 24 Jul 2013 17:16:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=TzexVlQiR9mG3cTHzwSuiuEJNw3quhMjW8dJ5xYCjPg=; b=CTqBdsTRgSFLZzEX/jdbvhIPpZUZskhTB7fVQVBozWf+b+xZR+1Fic3CRMENsDzW2u sljRdO6r6EtdzjcYCJVZ5ZKzbnviRuXbCJ3kYXWLTqIF816i1LaiiCxlaq9GvYJrUFML HQBNWs8j3FOELLqT4zijxDH84YEIVkVkQmHKhXI7iiM8/jCS21gJwRnjd/DUfEL6YsYX Ec9P8tRR9LWXXXs4pop/uzzF/M6bgL2+X6GL/T2mu4GfGwYDK9Q2kTaybhbZKU0C5JNO pYfXjy316JelmhhUwovwgOb+30DOhHFpSIQiuTgIFiKIr/fFm3mHJBdf4Im+69tnY4ww X3bw== MIME-Version: 1.0 X-Received: by 10.194.92.6 with SMTP id ci6mr4577182wjb.79.1374711381631; Wed, 24 Jul 2013 17:16:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Wed, 24 Jul 2013 17:16:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jul 2013 17:16:21 -0700 X-Google-Sender-Auth: fsisARJh9DVWyxUH3IDFNYPF6pA Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Adrian Chadd To: Super Bisquit Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Hackers , freebsd-current , FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 00:16:24 -0000 Well, why is it reducing latency? That's the thing you should investigate. Is it because processes aren't getting enough time? or too much time? Or the audio device isn't getting enough time to run? etc. -adrian On 24 July 2013 15:35, Super Bisquit wrote: > http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html > > This is the thread that I was referring to earlier. Since the patch is for > 2009, what are the chances it would work with 10.x or 9.x? > > On PowerPC machines with a low MHz rate- or any machine with a CPU rate of > 800 MHz or less- increasing the kern.hz improves performance and cuts down > on latency. I am building audio applications and suites that are used in > different projects. A G3 based machine should be able to run a kernel with > kern.hz=5000 with no problem. Unfortunately, this cannot be done. > > @PowerPC: some of you may find that performance does increase at a higher > kern.hz rate. > > @Hackers & Current: What's the chance that the default rate limit can be > raised to 5k? > _______________________________________________ > freebsd-ppc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 01:04:18 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 43ED8606; Thu, 25 Jul 2013 01:04:18 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DB0102462; Thu, 25 Jul 2013 01:04:17 +0000 (UTC) Received: by mail-oa0-f42.google.com with SMTP id j6so2863393oag.29 for ; Wed, 24 Jul 2013 18:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2uN7lFesbOCR5N86YX2eUGdhDur1ZJFzmHKl1OtS+Oo=; b=BPk7dwXCJZldRhJOlkubjjSAhcQomMCVDzJ3E2JqL+wIb48bx51wgRi1yh5oOKlnLI iOAvL0FTUDmwe7HXcBYklrkDLynC7thZgBnZX81bquWYH2vJjffDZ6dFgFyDeSGzBMuF Vgwwhxgyq0ozktgr8IDhZm9hjC53oIqQc+Qehyg1hoPTGwn6Az5ytV1185evjm6bRUQa sjveWACp2JuuAQyJSN123IHXc0fiWGBMqSXqWDMGEODM6UiMSGSFVBaj0dlao8yVhIvn MKpqJufDAsEnYhLGhFg3koXTiK5yxrOm0GxDslMYFd5qECVwC8+hY4IsFAEjjAuSdamx uleA== MIME-Version: 1.0 X-Received: by 10.60.125.100 with SMTP id mp4mr39510828oeb.60.1374714257003; Wed, 24 Jul 2013 18:04:17 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Wed, 24 Jul 2013 18:04:16 -0700 (PDT) In-Reply-To: References: Date: Wed, 24 Jul 2013 21:04:16 -0400 Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Super Bisquit To: Adrian Chadd , FreeBSD PowerPC ML , freebsd-current , FreeBSD Hackers Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 01:04:18 -0000 When I started with FreeBSD on a G3 B&W, I noticed that the performance improved with a higher kern.hz rating. Unless the future holds an emu20k2, there will be RAM used from the motherboard. 1. I will need a real-time or a faster kernel- hence the high rate wanted- because the devices to be built will be used in an active environment: art, music, audio control. 2. Any system with limited memory and a low CPU hertz rate benefits from the higher kern.hz setting. 3. Why not? If it works for PowerPC, SPARC64, AMD64, and i386 then it may work for other architectures. 4. Some applications may be ran from within a jail. On Wed, Jul 24, 2013 at 8:16 PM, Adrian Chadd wrote: > Well, why is it reducing latency? That's the thing you should investigate. > > Is it because processes aren't getting enough time? or too much time? > Or the audio device isn't getting enough time to run? etc. > > > > -adrian > > On 24 July 2013 15:35, Super Bisquit wrote: > > > http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html > > > > This is the thread that I was referring to earlier. Since the patch is > for > > 2009, what are the chances it would work with 10.x or 9.x? > > > > On PowerPC machines with a low MHz rate- or any machine with a CPU rate > of > > 800 MHz or less- increasing the kern.hz improves performance and cuts > down > > on latency. I am building audio applications and suites that are used in > > different projects. A G3 based machine should be able to run a kernel > with > > kern.hz=5000 with no problem. Unfortunately, this cannot be done. > > > > @PowerPC: some of you may find that performance does increase at a higher > > kern.hz rate. > > > > @Hackers & Current: What's the chance that the default rate limit can be > > raised to 5k? > > _______________________________________________ > > freebsd-ppc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > > To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" > From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 10:13:20 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4E223AA2; Thu, 25 Jul 2013 10:13:20 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [188.252.31.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ABA9A2DA1; Thu, 25 Jul 2013 10:13:19 +0000 (UTC) Received: from wojtek.tensor.gdynia.pl (localhost [127.0.0.1]) by wojtek.tensor.gdynia.pl (8.14.7/8.14.7) with ESMTP id r6P9p2b2012860; Thu, 25 Jul 2013 11:51:02 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.7/8.14.7/Submit) with ESMTP id r6P9p2UC012857; Thu, 25 Jul 2013 11:51:02 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Thu, 25 Jul 2013 11:51:02 +0200 (CEST) From: Wojciech Puchar To: Super Bisquit Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.4.3 (wojtek.tensor.gdynia.pl [127.0.0.1]); Thu, 25 Jul 2013 11:51:02 +0200 (CEST) Cc: FreeBSD Hackers , freebsd-current , FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 10:13:20 -0000 > improved with a higher kern.hz rating. Unless the future holds an emu20k2, > there will be RAM used from the motherboard. > 1. I will need a real-time or a faster kernel- hence the high rate wanted- > because the devices to be built will be used in an active environment: art, > music, audio control. > 2. Any system with limited memory and a low CPU hertz rate benefits from > the higher kern.hz setting. rather opposite. more kern.hz=more interrupts. > 3. Why not? If it works for PowerPC, SPARC64, AMD64, and i386 then it may > work for other architectures. > 4. Some applications may be ran from within a jail. > > > On Wed, Jul 24, 2013 at 8:16 PM, Adrian Chadd wrote: > >> Well, why is it reducing latency? That's the thing you should investigate. >> >> Is it because processes aren't getting enough time? or too much time? >> Or the audio device isn't getting enough time to run? etc. >> >> >> >> -adrian >> >> On 24 July 2013 15:35, Super Bisquit wrote: >>> >> http://lists.freebsd.org/pipermail/freebsd-stable/2009-September/051789.html >>> >>> This is the thread that I was referring to earlier. Since the patch is >> for >>> 2009, what are the chances it would work with 10.x or 9.x? >>> >>> On PowerPC machines with a low MHz rate- or any machine with a CPU rate >> of >>> 800 MHz or less- increasing the kern.hz improves performance and cuts >> down >>> on latency. I am building audio applications and suites that are used in >>> different projects. A G3 based machine should be able to run a kernel >> with >>> kern.hz=5000 with no problem. Unfortunately, this cannot be done. >>> >>> @PowerPC: some of you may find that performance does increase at a higher >>> kern.hz rate. >>> >>> @Hackers & Current: What's the chance that the default rate limit can be >>> raised to 5k? >>> _______________________________________________ >>> freebsd-ppc@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 16:11:39 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BE406CF8; Thu, 25 Jul 2013 16:11:39 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 04C32217E; Thu, 25 Jul 2013 16:11:38 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so1846798wgh.19 for ; Thu, 25 Jul 2013 09:11:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=giv0WWIGpI3VrGnbHPt7xc3L6V+CXUsSA5jYbeAPgZY=; b=EcvK1suJsy8bt/l9zJ+y0GrDG4zuukGuxdOqOZw2SkiDjGKH+vaneXYK5SJ5eGZ5X8 YhGoY0Tqn01NIeFbYriDBAYdYHrmQ/wC8X6Pn8rIy/72J/ho/YPUnL7CtNKVP2oYvQin oR1F3f3TCkk+uldjlmf9tmHVYd7zfMliqxzSlubruBXGAm6pVHAVha2FP+gXiVks38BD a/qsv9IAZQ+SeUnBnHLfm1xqlGiBRgxOaNnhu8nGWO3Xxx7/1vRQ9WFQYuXJX2wq+9j8 LaDMlcFnplZmx4hae25jiMZD2x+xLQWUMLrK5vltU7I6oOl/wTpVuOtbfbEDMCG0jQE1 eKWg== MIME-Version: 1.0 X-Received: by 10.194.92.6 with SMTP id ci6mr7227233wjb.79.1374768697270; Thu, 25 Jul 2013 09:11:37 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 25 Jul 2013 09:11:37 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 09:11:37 -0700 X-Google-Sender-Auth: -vAecfRGuNGwy-4rjpi6FHKbS4E Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Adrian Chadd To: Wojciech Puchar Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , FreeBSD Hackers , FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 16:11:39 -0000 On 25 July 2013 02:51, Wojciech Puchar wrote: >> improved with a higher kern.hz rating. Unless the future holds an emu20k2, >> there will be RAM used from the motherboard. >> 1. I will need a real-time or a faster kernel- hence the high rate wanted- >> because the devices to be built will be used in an active environment: >> art, >> music, audio control. >> 2. Any system with limited memory and a low CPU hertz rate benefits from >> the higher kern.hz setting. > rather opposite. more kern.hz=more interrupts. Right. More hz == more interrupts and less ability for a CPU-bound process to chew all the CPU. So is it a scheduling issue, where you have multiple CPU bound userland processes that aren't being fair and consuming all the CPU? Is it that your device driver(s) aren't interrupting correctly, relying on the hz tick to make up the slack, etc. Is it a busted halt loop, which is being papered over with hz ticks? Have you tried -10 on that kit, with the more aggressive clock/timer code that won't interrupt unless it needs to? Has that changed things? -adrian From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 20:31:55 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 326FE6F2; Thu, 25 Jul 2013 20:31:55 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C3EFA2E64; Thu, 25 Jul 2013 20:31:54 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id n12so5499057oag.36 for ; Thu, 25 Jul 2013 13:31:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MWXqU+js3bXhIe/rtkwsupkW59SZPsfz2LuMMeYKeTs=; b=qSmbQWpn41VlKDsHvI9XN3X0O/twhX5lmqx22ipULqUNvahKpzTUC8wLuJG1meRXDL z9Hn1iv3E6T2Lxv/HJEIx6lgM32m0znBVclEk9QcnNcbMvdoHHz3K9wuAEGi1cbVNrpO TTl9SRBGEDrM/dmw/HSRYt4835XIK19Jmhbqi6nUFwLMdDXsYcCOInYt7UGOc6Tis0gd WvLFQ4Adga8/HfqTM1v98iq+yDk0UPR3M61kW6UzDxJthLS+fUzpCfi8k129VberpJah kjt5mMMBul54WsjaD0zQd23imL0jWTsuudvBdvfc7LVFB5trZlDYKsZm66mxB6wLxVcl Swxg== MIME-Version: 1.0 X-Received: by 10.60.52.78 with SMTP id r14mr45103404oeo.9.1374784314010; Thu, 25 Jul 2013 13:31:54 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Thu, 25 Jul 2013 13:31:53 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 16:31:53 -0400 Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Super Bisquit To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Wojciech Puchar , freebsd-current , FreeBSD Hackers , FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 20:31:55 -0000 I haven't done much messing with scheduling. It is set at the default ULE for this machine. On Thu, Jul 25, 2013 at 12:11 PM, Adrian Chadd wrote: > On 25 July 2013 02:51, Wojciech Puchar > wrote: > >> improved with a higher kern.hz rating. Unless the future holds an > emu20k2, > >> there will be RAM used from the motherboard. > >> 1. I will need a real-time or a faster kernel- hence the high rate > wanted- > >> because the devices to be built will be used in an active environment: > >> art, > >> music, audio control. > >> 2. Any system with limited memory and a low CPU hertz rate benefits from > >> the higher kern.hz setting. > > > rather opposite. more kern.hz=more interrupts. > > Right. > > More hz == more interrupts and less ability for a CPU-bound process to > chew all the CPU. > > So is it a scheduling issue, where you have multiple CPU bound > userland processes that aren't being fair and consuming all the CPU? > Is it that your device driver(s) aren't interrupting correctly, > relying on the hz tick to make up the slack, etc. > > Is it a busted halt loop, which is being papered over with hz ticks? > > Have you tried -10 on that kit, with the more aggressive clock/timer > code that won't interrupt unless it needs to? Has that changed things? > > > > -adrian > From owner-freebsd-ppc@FreeBSD.ORG Thu Jul 25 20:37:23 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 59DDAA97; Thu, 25 Jul 2013 20:37:23 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 072AE2EED; Thu, 25 Jul 2013 20:37:22 +0000 (UTC) Received: by mail-oa0-f49.google.com with SMTP id n12so5513166oag.36 for ; Thu, 25 Jul 2013 13:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=GVKW2uqi4jjMHno3l5dHxzWLhhN5fQR6HD51M/2JFSM=; b=j8zl/ppDO53vdMLGaTyL34gYpQQ4I/A85gX4VT7p+9sILqPPThoIGKiamgQirQMwN8 5fttjop381Jod0LlSTQf/202oCAyvAAnnhtJn1G7HTaaROrhoGwE4HJO9Ke4BeKgk6CL PCaMDh1dGUpQcjHySoiqe2nZ1MxI9jsbf9FqbgqME2EVA5BdH081YcQlDCwKrnICx2uG Y0aYy6183wKKzlxyV1MIo+n8ZV9MtQjxUWZTb9YbOkMivP3gxal1xe3nCNbGuLz+8D2t BIa7lU0dwe3P7uxD4h2VDNBGnl9hr5WN8Gg9vHtFtYFpdEK/X5PI/O7pJUXJB4eJlZSu ErVg== MIME-Version: 1.0 X-Received: by 10.60.102.41 with SMTP id fl9mr44534074oeb.37.1374784642376; Thu, 25 Jul 2013 13:37:22 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Thu, 25 Jul 2013 13:37:22 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 16:37:22 -0400 Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Super Bisquit To: Adrian Chadd , FreeBSD PowerPC ML , freebsd-current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Jul 2013 20:37:23 -0000 On Thu, Jul 25, 2013 at 12:11 PM, Adrian Chadd wrote: > On 25 July 2013 02:51, Wojciech Puchar > wrote: > >> improved with a higher kern.hz rating. Unless the future holds an > emu20k2, > >> there will be RAM used from the motherboard. > >> 1. I will need a real-time or a faster kernel- hence the high rate > wanted- > >> because the devices to be built will be used in an active environment: > >> art, > >> music, audio control. > >> 2. Any system with limited memory and a low CPU hertz rate benefits from > >> the higher kern.hz setting. > > > rather opposite. more kern.hz=more interrupts. > > Right. > > More hz == more interrupts and less ability for a CPU-bound process to > chew all the CPU. > > So is it a scheduling issue, where you have multiple CPU bound > userland processes that aren't being fair and consuming all the CPU? > Is it that your device driver(s) aren't interrupting correctly, > relying on the hz tick to make up the slack, etc. > The G3 had the other scheduler- not ULE- when I built the system. > > Is it a busted halt loop, which is being papered over with hz ticks? > I wouldn't know. How would I test for this? > > Have you tried -10 on that kit, with the more aggressive clock/timer > code that won't interrupt unless it needs to? Set the rate to -10 ? I'll try the aggressive clock/timer code if someone would point me to a tutorial for setting it up. That sounds more like a solution I like. > Has that changed things? > If I can implement it, it may be the best solution. > > > > -adrian > From owner-freebsd-ppc@FreeBSD.ORG Fri Jul 26 03:13:19 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 5FB09B0; Fri, 26 Jul 2013 03:13:19 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C07F42FA6; Fri, 26 Jul 2013 03:13:18 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id n11so318374wgh.2 for ; Thu, 25 Jul 2013 20:13:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=bhWMmD+w+JxVKwgdEJ8655qzdF0R1W0gMKC7gB2gMb8=; b=OQndwZBFUfBJEN3LXvxQTaqyGEultRQ1XCt8q6yLCMGw2GE0GtNmyZS/meco8/gqj3 5vAoPSExjBPU9uywKvMbKC7IpglOK1UhEiVNHGADwRISz3Zyg5eR5iy/i3EGUh5WXCM8 ztsi8ieaHWjjJZBZVl78a2qkDie0sK9wxCONG9/iZpJVKaaXKbuT2P4exH5GjnP/INyO NQ/dtSDsOdwOBBIPGkvKixugH5HGuHIkiqs8gII78AJXbZusrNP93a3GFomGcf3b5znG ibGD3LYCXqES03U3YqasktNeqVhKbQZiqJZAkuwtqI6D5MhhcgTz0NmyjzoyE2CXUEae dxcA== MIME-Version: 1.0 X-Received: by 10.180.185.148 with SMTP id fc20mr4238558wic.0.1374808397082; Thu, 25 Jul 2013 20:13:17 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Thu, 25 Jul 2013 20:13:17 -0700 (PDT) In-Reply-To: References: Date: Thu, 25 Jul 2013 20:13:17 -0700 X-Google-Sender-Auth: S7FwV8QhAaymw-EJ_NK-935KXLc Message-ID: Subject: Re: Kern.hz= +1 hertz at anything 2500 and above. From: Adrian Chadd To: Super Bisquit Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current , FreeBSD PowerPC ML X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jul 2013 03:13:19 -0000 I mean, try -10 on it and report back. -adrian From owner-freebsd-ppc@FreeBSD.ORG Fri Jul 26 12:28:47 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 405EB4C2 for ; Fri, 26 Jul 2013 12:28:47 +0000 (UTC) (envelope-from nbounce-653-48846-53449960-c56a8-2e04f1ed@kiccall.eu) Received: from m4.kiccall.eu (m4.kiccall.eu [46.4.241.237]) by mx1.freebsd.org (Postfix) with ESMTP id A8708273B for ; Fri, 26 Jul 2013 12:28:46 +0000 (UTC) Received: from list653 (m4.kiccall.eu [46.4.241.237]) by m4.kiccall.eu (Postfix) with ESMTP id 0C92A22134F for ; Fri, 26 Jul 2013 14:19:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=kiccall.eu; s=default; t=1374841184; bh=995C0UmRv5gZF3BzHIBv9r5pDzU=; h=Content-Type:MIME-Version:From:Sender:Message-Id:List-Unsubscribe: Subject:To:Date; b=b9OxRPz6/iY6Pu4z4YDv8lY4DdXr//JMS8OtXcpXVH1ZmMUSifxqrkub0MCxLPr6c 2jBrYGuREg+eS75JAuWtMMGwWUidWcXspJ4kBg6nnVPJRKDG7WTW7A68R/NkkyN6+g s06qkJMcWDbcm4CVdXOx7v6GQSSkhyCMtrIWTvFQ= MIME-Version: 1.0 From: SWISS-CORNER.RO Sender: SWISS-CORNER.RO Precedence: bulk Message-Id: <20130726121944.13418.653.48846.53449960.nl@kiccall.ro> Subject: Mari reduceri!!!! To: Ppc Freebsd Date: Fri, 26 Jul 2013 12:19:44 -0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Reply-To: "SWISS-CORNER.RO" List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jul 2013 12:28:47 -0000 Pentru a vedea _[online][1]_ acest mesaj personalizat [click aici][2] Va rugam sa adaugati adresa de mail **office@swiss-corner.ro** in Address Book pentru a va asigura ca primiti mesajele noastre in **Inbox**. [1]: # [2]: # [3]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8= ?like=3Dfacebook [4]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8= ?share=3Dtwitter [5]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8= ?share=3Dlinkedin [6]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8= ?like=3Dplusone [7]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8= ?share=3Dpinterest Reduceri estivale in limita stocului disponibil! [8]: http://nl.kiccall.eu/clk/48846/53449960/996954/cec9538ac3dd65ce37e00d8= 9f4ea983f Blanc D`or Bracelet [9]: http://nl.kiccall.eu/clk/48846/53449960/996960/f636d2f19175bcbcbfb9ab8= c63f38458 Orange ## [10]: http://nl.kiccall.eu/clk/48846/53449960/996956/8c9d4e072911bc75e01953= 168b14c8e7 red [11]: http://nl.kiccall.eu/clk/48846/53449960/996953/91cffdbc139e2482a46d0b= 8d09eb22ec Rosie Mumu Cow ## **[http://nl.kiccall.eu/clk/48846/53449960/996958/8f25064abac4a090498a5617a= 5652180][12]** **[office@swiss-corner.ro][13]** [12]: http://nl.kiccall.eu/clk/48846/53449960/996952/773cfc5c4c4cf93ba07901= eab6dd8820 [13]: mailto:office@swiss-corner.ro **0256/220 823** **0728/692 891** Pentru a vedea [online][14] acest mesaj personalizat [click aici][15] Pentru dezabonare instant [click aici][16]. [14]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8 [15]: http://nl.kiccall.eu/v/48846/53449960/c56a8f136c83982d61aa1197a6b50db8 [16]: http://nl.kiccall.eu/unsubscribe/653/48846/53449960/c56a8f136c83982d6= 1aa1197a6b50db8 From owner-freebsd-ppc@FreeBSD.ORG Sat Jul 27 17:04:45 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 86FD9BF6 for ; Sat, 27 Jul 2013 17:04:45 +0000 (UTC) (envelope-from ritchey.17@osu.edu) Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe005.messaging.microsoft.com [216.32.180.188]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F8F32CB4 for ; Sat, 27 Jul 2013 17:04:44 +0000 (UTC) Received: from mail101-co1-R.bigfish.com (10.243.78.225) by CO1EHSOBE002.bigfish.com (10.243.66.65) with Microsoft SMTP Server id 14.1.225.22; Sat, 27 Jul 2013 16:34:29 +0000 Received: from mail101-co1 (localhost [127.0.0.1]) by mail101-co1-R.bigfish.com (Postfix) with ESMTP id 4C52B3C0348 for ; Sat, 27 Jul 2013 16:34:29 +0000 (UTC) X-Forefront-Antispam-Report: CIP:164.107.81.220; KIP:(null); UIP:(null); IPV:NLI; H:cio-tnc-pf06; RD:none; EFVD:NLI X-SpamScore: 2 X-BigFish: VPS2(zzc85dhzz1f42h1d77h208ch1ee6h1de0h1fdah2073h1202h1e76h1d1ah1d2ah1fc6hzz17326ah1de096h8275bh1de097hz2fh2a8h668h839hc60hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh1d0ch1d2eh1d3fh1dc1h1dfeh1dffh99di1b1bi1155h) Received-SPF: pass (mail101-co1: domain of osu.edu designates 164.107.81.220 as permitted sender) client-ip=164.107.81.220; envelope-from=ritchey.17@osu.edu; helo=cio-tnc-pf06 ; cio-tnc-pf06 ; Received: from mail101-co1 (localhost.localdomain [127.0.0.1]) by mail101-co1 (MessageSwitch) id 1374942822749257_27973; Sat, 27 Jul 2013 16:33:42 +0000 (UTC) Received: from CO1EHSMHS029.bigfish.com (unknown [10.243.78.244]) by mail101-co1.bigfish.com (Postfix) with ESMTP id B310D700047 for ; Sat, 27 Jul 2013 16:33:42 +0000 (UTC) Received: from cio-tnc-pf06 (164.107.81.220) by CO1EHSMHS029.bigfish.com (10.243.66.39) with Microsoft SMTP Server (TLS) id 14.16.227.3; Sat, 27 Jul 2013 16:33:42 +0000 Received: from CIO-TNC-HT07.osuad.osu.edu (localhost [127.0.0.1]) by cio-tnc-pf06 (Postfix) with ESMTP id 6C9043C0060 for ; Sat, 27 Jul 2013 12:32:45 -0400 (EDT) Received: from [10.119.77.30] (23.19.35.179) by smtp.service.osu.edu (164.107.81.254) with Microsoft SMTP Server (TLS) id 14.3.123.3; Sat, 27 Jul 2013 12:33:40 -0400 MIME-Version: 1.0 Subject: University - Update To: From: University Date: Sat, 27 Jul 2013 09:33:35 -0700 Message-ID: X-Originating-IP: [23.19.35.179] X-CFilter-Loop: Forward X-OriginatorOrg: osu.edu X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jul 2013 17:04:45 -0000 = Attention: Member, = Please click on the link below to update your e-mail account. = View = University E-mail Service Security Team =20 From owner-freebsd-ppc@FreeBSD.ORG Sat Jul 27 22:00:47 2013 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id F164A7D9; Sat, 27 Jul 2013 22:00:47 +0000 (UTC) (envelope-from superbisquit@gmail.com) Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B176D26FA; Sat, 27 Jul 2013 22:00:47 +0000 (UTC) Received: by mail-ob0-f177.google.com with SMTP id f8so1361240obp.36 for ; Sat, 27 Jul 2013 15:00:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=C13YTFUrK1rMU6eoWilFfYlpQxfv02EFmu+29VN9Nt4=; b=BXqpDAmf7RzcbVVFY1h5/lPzpUA2ZOIVeu6Jp0WB/cvtuSrwiYcL/KWxo1hwiD7qN8 HVgjU+3anlFlH4gbLk1VddNE+eNHA6K6geq2J6MBOYqFYjAVcEth+SYTJwLMh0g0MEpY 4zzyqfuxXSvwCOMiqtvHVyfDrt+QkZtGWgBrk6oQajSp8tjJICAr7un1LTm0PlcqHEhj Bnu3BMzyFM8ByNsK7MWpBsDVeedrG6H5uGnvg1/VdCYvEgfKrhCa3SqlKSTCSzGKevEl /4SLL9y9MTRZUtU+gCy/pJjFlJN+mt0J44AE/LczlqR5d17I4k5SYxlTO2wz2orqtkuy hIyw== MIME-Version: 1.0 X-Received: by 10.182.237.107 with SMTP id vb11mr47646012obc.84.1374962446825; Sat, 27 Jul 2013 15:00:46 -0700 (PDT) Received: by 10.182.115.194 with HTTP; Sat, 27 Jul 2013 15:00:46 -0700 (PDT) Date: Sat, 27 Jul 2013 18:00:46 -0400 Message-ID: Subject: Justin, about the open firmware problem. From: Super Bisquit To: FreeBSD PowerPC ML , Justin Hibbits , Justin Hibbits Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Jul 2013 22:00:48 -0000 The OLPC one laptop per child uses the open firmware for the boot loader. I have used the open firmware mailing lists to try solving problems. I am aware that this post/thread is a bit late; but, the solution to the problem may be there.