From owner-freebsd-ppc@FreeBSD.ORG Sun Feb 21 23:28:27 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F4081065676 for ; Sun, 21 Feb 2010 23:28:27 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mx1.freebsd.org (Postfix) with ESMTP id EB8508FC12 for ; Sun, 21 Feb 2010 23:28:26 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 8so419313qwh.7 for ; Sun, 21 Feb 2010 15:28:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=KY8+eUtIwBUJepnZnyPOosbR/5ys7K9p4l7M1lgzETs=; b=c1xGEraEOJh7ptZ8s2ix4bao8KCOLuLPjPsrDeDRtWiSNcQb3D5tzsyDSThqtcvf6f 3H1eJ1ebpMAOP8tGomk88bO7wydUmqBr++gVxnIm5EDZ3XyqqL9m9l89ivgD4jzkMgfT ejUgc5VtHK7ObytZMTOk5Lo/uGrYguv0HttpE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=wDIkKvvdvaMt0sEwM1+tEvrTODvRQDCS0b/bnRkbfwl3d1QEiEKe4pDqdoS4ALphfK 50a3P25ZGBsaWXx8HYbalbhNpT4NeMjJSa8vATlG420Ftprn7CO5OcebB9lx7gtsPjmJ 1IopXHDFBuFEs3FhYNtijmShxGZg20ndxI87k= Received: by 10.224.80.16 with SMTP id r16mr5420662qak.340.1266793419826; Sun, 21 Feb 2010 15:03:39 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 7sm7730791qwf.24.2010.02.21.15.03.38 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 21 Feb 2010 15:03:39 -0800 (PST) Message-ID: <4B81BBC7.5050100@gmail.com> Date: Sun, 21 Feb 2010 18:03:35 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 22 Feb 2010 01:28:42 +0000 Subject: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Feb 2010 23:28:27 -0000 Hi, I recently got a power mac g5, and am trying to install freebsd 8.0. I am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after booting, I get "panic: moea 64 bootstrap: too many ofw translations." Is there a fix for this issue? Thank you, Alexander From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 22 01:54:58 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EFC4106566C for ; Mon, 22 Feb 2010 01:54:58 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mx1.freebsd.org (Postfix) with ESMTP id C42768FC13 for ; Mon, 22 Feb 2010 01:54:57 +0000 (UTC) Received: by bwz8 with SMTP id 8so1390478bwz.3 for ; Sun, 21 Feb 2010 17:54:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=TmU+WH5SzByLGy5+8UjhzPx7p/q2ud/aww1y4iUAbos=; b=RA/ZXeiHMcdS+8Q5qR4RmGisEqkYPD8IoBmVrLfUKTz660H7eo5z8HxqbQKTCAk0hE d3+EpaDVwV2OwpFUjfK+f4jjaZ8ia1mo/iB0/yhO64hID3GfWgTj6fcpLp+aqo5pQAwo gm0QJTb/JbvBNUdJ9yPsRoa1mmp4kfDcOgMB4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=RyLlL0P/j+ZEgo+MeHiURFm1j2kX6ShtT0MHB5QOc0RKAu1hHAdCH4mOjACOaCQyhN VL/AiLm+LDAEd4tHqPPenvEzGGwTAgWU/3J2Vgl2Jlni3oKo4+HbsGirR8FmMUGBaQ70 bfOHPY56593zXLqLBCkrCLJIOVhudlmkhjER8= MIME-Version: 1.0 Sender: chmeeedalf@gmail.com Received: by 10.204.39.203 with SMTP id h11mr1990794bke.153.1266803688464; Sun, 21 Feb 2010 17:54:48 -0800 (PST) In-Reply-To: <4B81BBC7.5050100@gmail.com> References: <4B81BBC7.5050100@gmail.com> Date: Sun, 21 Feb 2010 20:54:48 -0500 X-Google-Sender-Auth: eb265a78ec3f7a77 Message-ID: From: Justin Hibbits To: Alexander Bakst Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 01:54:58 -0000 On Sun, Feb 21, 2010 at 6:03 PM, Alexander Bakst wrote: > Hi, > > I recently got a power mac g5, and am trying to install freebsd 8.0. I am > using "8.0-RELEASE-powerpc-disc1.iso". Immediately after booting, I get > "panic: moea 64 bootstrap: too many ofw translations." > > Is there a fix for this issue? > > Thank you, > Alexander > Nathan just put in a fix for moea last week. If you have another machine you can build with, you might want to check the thread regarding powerpc64: http://lists.freebsd.org/pipermail/freebsd-ppc/2010-February/004073.html - Justin From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 22 01:58:54 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68AEC106568B for ; Mon, 22 Feb 2010 01:58:54 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from mail-qy0-f188.google.com (mail-qy0-f188.google.com [209.85.221.188]) by mx1.freebsd.org (Postfix) with ESMTP id 194878FC16 for ; Mon, 22 Feb 2010 01:58:53 +0000 (UTC) Received: by qyk26 with SMTP id 26so1641805qyk.12 for ; Sun, 21 Feb 2010 17:58:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type; bh=qgZPEAPZspTAr1mWYUmCUkOFhO7cepA4CYFxg5vyGUY=; b=sd0XB9EXLiXZUq+jtJj8jeBjylMZsJontdVOPK1OPPJv6D5BhBONK+9XuG6/EbrOds vpQMVB7+W4qU6DKcE8z3ey8NVRsWvWAVV4ccha5gO4AgBjgushVx8NUHRxEqJlrPTaWC 67YPZMcU1mmnmf4q6JhQ/oiFqm+1IHaIa8k1U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type; b=ISc9kq+txGl0T7b6de6J1L8kzsToHKveoRqtXDsRjlTNWo8R9YwvPYbjCi6BZmTbL9 0MjR9myXx8M5LE5XCTLfPWZqBfa3A4ZJK5is9itjEiNUQrCVoRkw+HDTrNDtkiWlQuPw IFHa/pUsPwoAoFHdkh6+iM4g4Nuc5jy8Av3wQ= Received: by 10.224.113.218 with SMTP id b26mr5500541qaq.184.1266803927961; Sun, 21 Feb 2010 17:58:47 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 7sm8073149qwf.34.2010.02.21.17.58.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 21 Feb 2010 17:58:46 -0800 (PST) Message-ID: <4B81E4D4.8020806@gmail.com> Date: Sun, 21 Feb 2010 20:58:44 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: Justin Hibbits References: <4B81BBC7.5050100@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 01:58:54 -0000 Thanks, I will give that a look. --Alexander On 2/21/10 8:54 PM, Justin Hibbits wrote: > On Sun, Feb 21, 2010 at 6:03 PM, Alexander Bakst > > wrote: > > Hi, > > I recently got a power mac g5, and am trying to install freebsd > 8.0. I am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after > booting, I get "panic: moea 64 bootstrap: too many ofw translations." > > Is there a fix for this issue? > > Thank you, > Alexander > > > Nathan just put in a fix for moea last week. If you have another > machine you can build with, you might want to check the thread > regarding powerpc64: > > http://lists.freebsd.org/pipermail/freebsd-ppc/2010-February/004073.html > > - Justin From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 22 11:07:04 2010 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F0B91065670 for ; Mon, 22 Feb 2010 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 6D7398FC2A for ; Mon, 22 Feb 2010 11:07:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id o1MB74Lx039793 for ; Mon, 22 Feb 2010 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o1MB73LW039791 for freebsd-ppc@FreeBSD.org; Mon, 22 Feb 2010 11:07:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 22 Feb 2010 11:07:03 GMT Message-Id: <201002221107.o1MB73LW039791@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 Cc: Subject: Current problem reports assigned to freebsd-ppc@FreeBSD.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 11:07:04 -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/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/133383 ppc firefox thr_kill crash with heavy vm load o power/133382 ppc [install] Installer gets signal 11 o power/131548 ppc ofw_syscons no longer supports 32-bit framebuffer a power/121407 ppc [panic] Won't boot up; strange error message. o power/111296 ppc [kernel] [patch] [request] Support IMISS, DLMISS an DS o power/93203 ppc FreeBSD PPC Can't Write to Partitions. 9 problems total. From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 22 11:21:49 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C8881065745 for ; Mon, 22 Feb 2010 11:21:49 +0000 (UTC) (envelope-from gnoahb@gmail.com) Received: from mail-yw0-f204.google.com (mail-yw0-f204.google.com [209.85.211.204]) by mx1.freebsd.org (Postfix) with ESMTP id F24128FC12 for ; Mon, 22 Feb 2010 11:21:48 +0000 (UTC) Received: by ywh42 with SMTP id 42so928296ywh.7 for ; Mon, 22 Feb 2010 03:21:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=3KkFik4iTEqMoCi5MDC3lw2BIDsdJGibWZgqocggjSA=; b=U19YD32Y/wsdPZptdJlgLhiLqh6KgDVWKWMJnbVpUAcjvpEgg1JoURNOmb0CObkihi 8S6zZIXy3/EXSbbTRtFtH8LxXXd/ivjgHvAI632lOVo7AXCY26O3nFRZ2zS1miYW/57T IYHv/bGR5Ygdgn5OLuCeZZRR0UeAs0OOAmtoo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=UNfav8O/6PSadZG+RsyHbOMeDg+/k+MZtd09dS1eMwJD//cB67IneBN/FMKQHdqsKE W2oA686b9dG6wVKtubzFnLarxP9zPvty6pN02akhpH1hfkM1MvQ/uBlBsjN+sWhyHGGF FyeH8CkdaZV5hm9b0qpZ9R2W5S6B6yaTv5DoE= MIME-Version: 1.0 Received: by 10.101.179.34 with SMTP id g34mr5424706anp.85.1266836158879; Mon, 22 Feb 2010 02:55:58 -0800 (PST) Date: Mon, 22 Feb 2010 17:55:58 +0700 Message-ID: <85b619e41002220255k326a017kb3d1ab521571eeef@mail.gmail.com> From: G B To: xcllnt@mac.com, freebsd-ppc@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: PowerPC FreeBSD port for Freescale QorIQ X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 11:21:49 -0000 Hi Marcel, I saw your GIT commit message from the end of January 2010 that the FreeBSD port now works with QorIQ processors. I'm curious if you are using the P2020RDB-PA development board from Freescale to do your testing with the QorIQ processors. If not, what are you using for testing? If so, are all peripherals on the dev board working properly? I'm considering buying one of them for work with FreeBSD and I wand to know what I'm getting into in advance if possible. What is the install and boot process like? Thanks, Gabriel From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 22 17:58:06 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DA06106568D for ; Mon, 22 Feb 2010 17:58:06 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from asmtpout026.mac.com (asmtpout026.mac.com [17.148.16.101]) by mx1.freebsd.org (Postfix) with ESMTP id 262F48FC14 for ; Mon, 22 Feb 2010 17:58:05 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from [172.24.240.11] (natint3.juniper.net [66.129.224.36]) by asmtp026.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0KY900ELI8KLUA30@asmtp026.mac.com> for freebsd-ppc@freebsd.org; Mon, 22 Feb 2010 09:58:05 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-1002220171 From: Marcel Moolenaar In-reply-to: <85b619e41002220255k326a017kb3d1ab521571eeef@mail.gmail.com> Date: Mon, 22 Feb 2010 09:57:56 -0800 Message-id: <7A3E561E-5F71-4EA0-882B-D289DCA2D5EF@mac.com> References: <85b619e41002220255k326a017kb3d1ab521571eeef@mail.gmail.com> To: G B X-Mailer: Apple Mail (2.1077) Cc: freebsd-ppc@freebsd.org Subject: Re: PowerPC FreeBSD port for Freescale QorIQ X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 17:58:06 -0000 On Feb 22, 2010, at 2:55 AM, G B wrote: > Hi Marcel, > > I saw your GIT commit message from the end of January 2010 that the > FreeBSD port now works with QorIQ processors. I'm curious if you are > using the P2020RDB-PA development board from Freescale to do your > testing with the QorIQ processors. If not, what are you using for > testing? I have a P2020DS (aka Stingray). > If so, are all peripherals on the dev board working properly? I'm > considering buying one of them for work with FreeBSD and I wand to > know what I'm getting into in advance if possible. Not all peripherals are working yet, I haven't had the time to flesh that out. > What is the install and boot process like? I netboot right now. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-ppc@FreeBSD.ORG Mon Feb 22 23:06:10 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E93F106566B for ; Mon, 22 Feb 2010 23:06:10 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119]) by mx1.freebsd.org (Postfix) with ESMTP id 2747C8FC0A for ; Mon, 22 Feb 2010 23:06:09 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 6DCC2582C4; Mon, 22 Feb 2010 17:06:09 -0600 (CST) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from mail.icecube.wisc.edu ([127.0.0.1]) by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id rgOkC0NpfFTZ; Mon, 22 Feb 2010 17:06:09 -0600 (CST) Received: from wanderer.tachypleus.net (i3-dhcp-172-16-55-157.icecube.wisc.edu [172.16.55.157]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 52F9D582EC; Mon, 22 Feb 2010 17:00:05 -0600 (CST) Message-ID: <4B830C74.3020603@freebsd.org> Date: Mon, 22 Feb 2010 17:00:04 -0600 From: Nathan Whitehorn User-Agent: Thunderbird 2.0.0.23 (X11/20100215) MIME-Version: 1.0 To: Alexander Bakst References: <4B81BBC7.5050100@gmail.com> In-Reply-To: <4B81BBC7.5050100@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 23:06:10 -0000 Alexander Bakst wrote: > Hi, > > I recently got a power mac g5, and am trying to install freebsd 8.0. I > am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after booting, I > get "panic: moea 64 bootstrap: too many ofw translations." > > Is there a fix for this issue? > There was a bug in the 8.0 install CDs that prevents them from booting on a large number of G5 systems. You can use a 9.0-SNAP image I made in November to get a bootable CD: http://people.freebsd.org/~nwhitehorn/9.0-20091112-SNAP/9.0-20091112-SNAP-powerpc-disc1.iso Also, -CURRENT now has some updates to smu(4) that prevent the fans in SMU-based machines from running at maximum all the time, which should be MFCed shortly and will be in 8.1. Once those are MFCed in the next week or two, I will make an 8.0-STABLE CD with those updates. -Nathan From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 00:37:32 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 075BF1065672 for ; Tue, 23 Feb 2010 00:37:32 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id 8C8CD8FC13 for ; Tue, 23 Feb 2010 00:37:30 +0000 (UTC) Received: by ewy3 with SMTP id 3so3042977ewy.13 for ; Mon, 22 Feb 2010 16:37:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=SrKKg9BkH7aBkUibR5gJmodWMZGYcEaTdHllF1Y5QH4=; b=pRLP1xsmeJTxOmrf94xQoi8vuH7lC3QrpsqVIgY/MNWvnuxzV0EPkYXy86j/WOtjUU /Ny6CGDd20PQXn+BHAAp2fmZiUzHDqdKBB8RIB/l2ydrLSI8HLZKkQAc4Bzwb3YVI4Uv XBbl0R5v6jeiJbEwxKv88WVHc2dEuqyd+ELtg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=b6Nnab8NGhlRZy73ChNsi4CeJeFsD6R9NgihRCcBsFJUsoIoUXkLsi04KlI10LZS0S v6UrDcoAHrSVR1knbpdxZXpxH2mqhQHtU9iw90efpU4TTRgwh1p8HkxsfV1N41SWougt N0IyNNdvfRERhwW6Dl8amoy3KRitRjbpfbUg4= Received: by 10.213.102.202 with SMTP id h10mr20867ebo.94.1266885444901; Mon, 22 Feb 2010 16:37:24 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 16sm2887015ewy.10.2010.02.22.16.37.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Feb 2010 16:37:23 -0800 (PST) Message-ID: <4B83233F.5050601@gmail.com> Date: Mon, 22 Feb 2010 19:37:19 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: Nathan Whitehorn References: <4B81BBC7.5050100@gmail.com> <4B830C74.3020603@freebsd.org> In-Reply-To: <4B830C74.3020603@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 00:37:32 -0000 Thanks - to tell the truth, I installed Debian last night. However, I haven't quite committed to Debian, so I think I'll give this a shot. It'd be nice to learn an actual unix. If I install the 9.0-SNAP image, is there also a way to pull in the changes to fix the fan issue? Thanks, Alexander On 2/22/10 6:00 PM, Nathan Whitehorn wrote: > Alexander Bakst wrote: >> Hi, >> >> I recently got a power mac g5, and am trying to install freebsd 8.0. >> I am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after >> booting, I get "panic: moea 64 bootstrap: too many ofw translations." >> >> Is there a fix for this issue? >> > There was a bug in the 8.0 install CDs that prevents them from booting > on a large number of G5 systems. You can use a 9.0-SNAP image I made > in November to get a bootable CD: > > http://people.freebsd.org/~nwhitehorn/9.0-20091112-SNAP/9.0-20091112-SNAP-powerpc-disc1.iso > > > Also, -CURRENT now has some updates to smu(4) that prevent the fans in > SMU-based machines from running at maximum all the time, which should > be MFCed shortly and will be in 8.1. Once those are MFCed in the next > week or two, I will make an 8.0-STABLE CD with those updates. > -Nathan From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 04:06:01 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0A861065672 for ; Tue, 23 Feb 2010 04:06:01 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 9407F8FC25 for ; Tue, 23 Feb 2010 04:06:01 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0KYA002020Q07R00@smtpauth3.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Mon, 22 Feb 2010 22:06:00 -0600 (CST) Received: from comporellon.tachypleus.net (adsl-76-233-146-74.dsl.mdsnwi.sbcglobal.net [76.233.146.74]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0KYA00G7X0PYGV70@smtpauth3.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Mon, 22 Feb 2010 22:05:59 -0600 (CST) Date: Mon, 22 Feb 2010 22:05:58 -0600 From: Nathan Whitehorn In-reply-to: <4B83233F.5050601@gmail.com> To: Alexander Bakst Message-id: <4B835426.1090002@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.233.146.74 X-Spam-PmxInfo: Server=avs-11, Version=5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2010.2.23.35118, SenderIP=76.233.146.74 References: <4B81BBC7.5050100@gmail.com> <4B830C74.3020603@freebsd.org> <4B83233F.5050601@gmail.com> User-Agent: Thunderbird 2.0.0.23 (X11/20100206) Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 04:06:01 -0000 Yes, you just need to upgrade to the latest sources in -CURRENT. Follow the source upgrade directions in the handbook (http://www.freebsd.org/doc/handbook/updating-upgrading.html), starting in the section titled "Tracking a development branch". You shouldn't have to live with your computer sounding like it is full of angry bees for more than an hour or so. -Nathan Alexander Bakst wrote: > Thanks - to tell the truth, I installed Debian last night. However, I > haven't quite committed to Debian, so I think I'll give this a shot. > It'd be nice to learn an actual unix. > > If I install the 9.0-SNAP image, is there also a way to pull in the > changes to fix the fan issue? > > Thanks, > Alexander > > On 2/22/10 6:00 PM, Nathan Whitehorn wrote: >> Alexander Bakst wrote: >>> Hi, >>> >>> I recently got a power mac g5, and am trying to install freebsd 8.0. >>> I am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after >>> booting, I get "panic: moea 64 bootstrap: too many ofw translations." >>> >>> Is there a fix for this issue? >>> >> There was a bug in the 8.0 install CDs that prevents them from >> booting on a large number of G5 systems. You can use a 9.0-SNAP image >> I made in November to get a bootable CD: >> >> http://people.freebsd.org/~nwhitehorn/9.0-20091112-SNAP/9.0-20091112-SNAP-powerpc-disc1.iso >> >> >> Also, -CURRENT now has some updates to smu(4) that prevent the fans >> in SMU-based machines from running at maximum all the time, which >> should be MFCed shortly and will be in 8.1. Once those are MFCed in >> the next week or two, I will make an 8.0-STABLE CD with those updates. >> -Nathan From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 04:26:04 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88BA410656C4; Tue, 23 Feb 2010 04:26:04 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.24]) by mx1.freebsd.org (Postfix) with ESMTP id D01A78FC0C; Tue, 23 Feb 2010 04:25:56 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 8so712122qwh.7 for ; Mon, 22 Feb 2010 20:25:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=6sZeLVYfyWGGNuDmvWbbvDIBBzWarcSYXD6lwbxPqd8=; b=SGEpgssGtwgp1jeRItUA3NDpNSLLjeZ0Mabdsx0u9Kqa9Lxbfr+5gh4qAM0A9cxus+ nf4XCvu0gtgaVnmp+dG9FWlFrFH30IYUCMqpG9w0YJ7lPg4HkFQXBB8a/Ejxb/98QB2y 5DCpPvrpyl5B3bOqUAMOnAvDbtqeqlgjJSReI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=DXIAxStEB6h+wkpaiEVQatFmmrjT9bSOTCcgQ/zWqD+bLJ8l9eO5hmo7FSRFVN82lk TF4KhLPRI9WG+dV1R/Bjq2cnRBCM5MtZANl8cl23hDVyGInjsLB3/gJc/+kxOWYUPZs5 VwjxqodKma0S4SgxizRE7V71oplrrcgl+3Ybs= Received: by 10.224.114.200 with SMTP id f8mr78416qaq.116.1266899135899; Mon, 22 Feb 2010 20:25:35 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 7sm268002qwb.57.2010.02.22.20.25.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 22 Feb 2010 20:25:35 -0800 (PST) Message-ID: <4B8358BB.10703@gmail.com> Date: Mon, 22 Feb 2010 23:25:31 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: Nathan Whitehorn References: <4B81BBC7.5050100@gmail.com> <4B830C74.3020603@freebsd.org> <4B83233F.5050601@gmail.com> <4B835426.1090002@freebsd.org> In-Reply-To: <4B835426.1090002@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 04:26:04 -0000 Perfect. Maybe if I can find some spare cycles I can look into contributing somehow. I spent the first hour of work today looking at ibm's power 970 manual. --Alexander On 2/22/10 11:05 PM, Nathan Whitehorn wrote: > Yes, you just need to upgrade to the latest sources in -CURRENT. > Follow the source upgrade directions in the handbook > (http://www.freebsd.org/doc/handbook/updating-upgrading.html), > starting in the section titled "Tracking a development branch". You > shouldn't have to live with your computer sounding like it is full of > angry bees for more than an hour or so. > -Nathan > > Alexander Bakst wrote: >> Thanks - to tell the truth, I installed Debian last night. However, I >> haven't quite committed to Debian, so I think I'll give this a shot. >> It'd be nice to learn an actual unix. >> >> If I install the 9.0-SNAP image, is there also a way to pull in the >> changes to fix the fan issue? >> >> Thanks, >> Alexander >> >> On 2/22/10 6:00 PM, Nathan Whitehorn wrote: >>> Alexander Bakst wrote: >>>> Hi, >>>> >>>> I recently got a power mac g5, and am trying to install freebsd >>>> 8.0. I am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after >>>> booting, I get "panic: moea 64 bootstrap: too many ofw translations." >>>> >>>> Is there a fix for this issue? >>>> >>> There was a bug in the 8.0 install CDs that prevents them from >>> booting on a large number of G5 systems. You can use a 9.0-SNAP >>> image I made in November to get a bootable CD: >>> >>> http://people.freebsd.org/~nwhitehorn/9.0-20091112-SNAP/9.0-20091112-SNAP-powerpc-disc1.iso >>> >>> >>> Also, -CURRENT now has some updates to smu(4) that prevent the fans >>> in SMU-based machines from running at maximum all the time, which >>> should be MFCed shortly and will be in 8.1. Once those are MFCed in >>> the next week or two, I will make an 8.0-STABLE CD with those updates. >>> -Nathan > From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 07:19:04 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D14291065670; Tue, 23 Feb 2010 07:19:04 +0000 (UTC) (envelope-from rajatjain@juniper.net) Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by mx1.freebsd.org (Postfix) with ESMTP id 3DCE18FC12; Tue, 23 Feb 2010 07:19:04 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKS4OBZ34W5IL1/4ymY+6O/BE5E9sukt0M@postini.com; Mon, 22 Feb 2010 23:19:04 PST Received: from emailbng1.jnpr.net (10.209.194.15) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server id 8.1.393.1; Mon, 22 Feb 2010 23:16:44 -0800 Received: from emailbng3.jnpr.net ([10.209.194.27]) by emailbng1.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 23 Feb 2010 12:46:41 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 23 Feb 2010 12:46:40 +0530 Message-ID: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Strategy for PCI resource management (for supporting hot-plug) Thread-Index: Acq0WCUiblKr9+OlQeafGqGQtTgEow== From: Rajat Jain To: , X-OriginalArrivalTime: 23 Feb 2010 07:16:41.0758 (UTC) FILETIME=[25C9BBE0:01CAB458] Cc: freebsd-ia32@freebsd.org, freebsd-ppc@freebsd.org Subject: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 07:19:05 -0000 Hi, I'm trying to add PCI-E hotplug support to the FreeBSD. As a first step for the PCI-E hotplug support, I'm trying to decide on a resource management / allocation strategy for the PCI memory / IO and the bus numbers. Can you please comment on the following approach that I am considering for resource allocation: PROBLEM STATEMENT: ------------------ Given a memory range [A->B], IO range [C->D], and limited (256) bus numbers, enumerate the PCI tree of a system, leaving enough "holes" in between to allow addition of future devices. PROPOSED STRATEGY: ------------------ 1) When booting, start enumerating in a depth-first-search order. While enumeration, always keep track of: * The next bus number (x) that can be allocated * The next Memory space pointer (A + y) starting which allocation can be=20 done. ("y" is the memory already allocated). * The next IO Space pointer (C + z) starting which allocation can be done. ("z" is the IO space already allocated). Keep incrementing the above as the resources are allocated. 2) Allocate bus numbers sequentially while traversing down from root to a leaf node (end point). When going down traversing a bridge: * Allocate the next available bus number (x) to the secondary bus of=20 bridge. * Temporarily mark the subordinate bridge as 0xFF (to allow discovery of=20 maximum buses). * Temporarily assign all the remaining available memory space to bridge [(A+x) -> B]. Ditto for IO space. 3) When a leaf node (End point) is reached, allocate the memory / IO resource requested by the device, and increment the pointers.=20 4) While passing a bridge in the upward direction, tweak the bridge registers such that its resources are ONLY ENOUGH to address the needs of all the PCI tree below it, and if it has its own internal memory mapped registers, some memory for it as well. The above is the standard depth-first algorithm for resource allocation. Here is the addition to support hot-plug: At each bridge that supports hot-plug, in addition to the resources that would have normally been allocated to this bridge, additionally pre-allocate and assign to bridge (in anticipation of any new devices that may be added later): a) "RSRVE_NUM_BUS" number of busses, to cater to any bridges, PCI trees=20 present on the device plugged. b) "RSRVE_MEM" amount of memory space, to cater to all the PCI devices that=20 may be attached later on. c) "RESRVE_IO" amount of IO space, to cater to all PCI devices that may be=20 attached later on. Please note that the above RSRVE* are constants defining the amount of resources to be set aside for /below each HOT-PLUGGABLE bridge; their values may be tweaked via a compile time option or via a sysctl.=20 FEW COMMENTS ------------ =20 1) The strategy is fairly generic and tweak-able since it does not waste a lot of resources (The developer neds to pick up a smart bvalue for howmuch resources to reserve at each hot-pluggable slot): * The reservations shall be done only for hot-pluggable bridges * The developer can tweak the values (even disable it) for how much=20 Resources shall be allocated for each hot-pluggable bridge. =20 2) One point of debate is what happens if there are too much resource demands in the system (too many devices or the developer configures too many resources to be allocated for each hot-pluggable devices). For e.g. consider that while enumeration we find that all the resources are already allocated, while there are more devices that need resources. So do we simply do not enumerate them? Etc... Overall, how does the above look? Thanks & Best Regards, Rajat Jain From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 08:21:14 2010 Return-Path: Delivered-To: freebsd-ppc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCB0A1065694; Tue, 23 Feb 2010 08:21:14 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 673CA8FC15; Tue, 23 Feb 2010 08:21:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.3/8.14.1) with ESMTP id o1N8GVCm035900; Tue, 23 Feb 2010 01:16:31 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 23 Feb 2010 01:16:30 -0700 (MST) Message-Id: <20100223.011630.74715282.imp@bsdimp.com> To: rajatjain@juniper.net From: Warner Losh In-Reply-To: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> References: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ia32@FreeBSD.org, freebsd-new-bus@FreeBSD.org, freebsd-ppc@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 08:21:14 -0000 From: Rajat Jain Subject: Strategy for PCI resource management (for supporting hot-plug) Date: Tue, 23 Feb 2010 12:46:40 +0530 > > Hi, > > I'm trying to add PCI-E hotplug support to the FreeBSD. As a first step > for the PCI-E hotplug support, I'm trying to decide on a resource > management / allocation strategy for the PCI memory / IO and the bus > numbers. Can you please comment on the following approach that I am > considering for resource allocation: > > PROBLEM STATEMENT: > ------------------ > Given a memory range [A->B], IO range [C->D], and limited (256) bus > numbers, enumerate the PCI tree of a system, leaving enough "holes" in > between to allow addition of future devices. > > PROPOSED STRATEGY: > ------------------ > 1) When booting, start enumerating in a depth-first-search order. While > enumeration, always keep track of: > > * The next bus number (x) that can be allocated > > * The next Memory space pointer (A + y) starting which allocation can > be > done. ("y" is the memory already allocated). > > * The next IO Space pointer (C + z) starting which allocation can be > done. > ("z" is the IO space already allocated). > > Keep incrementing the above as the resources are allocated. IO space and memory space are bus addresses, which may have a mapping to another domain. > 2) Allocate bus numbers sequentially while traversing down from root to > a leaf node (end point). When going down traversing a bridge: > > * Allocate the next available bus number (x) to the secondary bus of > bridge. > > * Temporarily mark the subordinate bridge as 0xFF (to allow discovery > of > maximum buses). > > * Temporarily assign all the remaining available memory space to bridge > > [(A+x) -> B]. Ditto for IO space. I'm sure this is wise. > 3) When a leaf node (End point) is reached, allocate the memory / IO > resource requested by the device, and increment the pointers. keep in mind that devices may not have drivers allocataed to them at bus enumeration of time. with hot-plug devices, you might not even know all the devices that are there or could be there. > 4) While passing a bridge in the upward direction, tweak the bridge > registers such that its resources are ONLY ENOUGH to address the needs > of all the PCI tree below it, and if it has its own internal memory > mapped registers, some memory for it as well. How does one deal with adding a device that has a bridge on it? I think that the only enough part is likely going to lead to prroblems as you'll need to move other resources if a new device arrives here. > The above is the standard depth-first algorithm for resource allocation. > Here is the addition to support hot-plug: the above won't quite work for cardbus :) But that's a hot-plug device... > At each bridge that supports hot-plug, in addition to the resources that > would have normally been allocated to this bridge, additionally > pre-allocate and assign to bridge (in anticipation of any new devices > that may be added later): In addition, or total? if it were total, you could more easily allocate memory or io space ranges in a more determnistic way when you have to deal with booting with or without a device that's present. > a) "RSRVE_NUM_BUS" number of busses, to cater to any bridges, PCI trees > present on the device plugged. This one might make sense, but if we have multiple levels then you'll run out. if you have 4 additional bridges, you can't allocate X additional busses at the root, then you can only (X-4)/4 at each level. > b) "RSRVE_MEM" amount of memory space, to cater to all the PCI devices > that > may be attached later on. > > c) "RESRVE_IO" amount of IO space, to cater to all PCI devices that may > be > attached later on. similar comments apply here. > Please note that the above RSRVE* are constants defining the amount of > resources to be set aside for /below each HOT-PLUGGABLE bridge; their > values may be tweaked via a compile time option or via a sysctl. > > FEW COMMENTS > ------------ > > 1) The strategy is fairly generic and tweak-able since it does not waste > a lot of resources (The developer neds to pick up a smart bvalue for > howmuch resources to reserve at each hot-pluggable slot): > > * The reservations shall be done only for hot-pluggable bridges > > * The developer can tweak the values (even disable it) for how much > Resources shall be allocated for each hot-pluggable bridge. I'd like to understand the details of this better. especially when you have multiple layers where devices that have bridges are hot-plugged into the system. For example, three's a cardbus to pci bridge, which has 3 PCI slots behind it. These slots may have, say, a quad ethernet card which has a pci bridge to allow the 4 pci nics behind it. New while this example may be dated, newer pci-e also allows for it... > 2) One point of debate is what happens if there are too much resource > demands in the system (too many devices or the developer configures too > many resources to be allocated for each hot-pluggable devices). For e.g. > consider that while enumeration we find that all the resources are > already allocated, while there are more devices that need resources. So > do we simply do not enumerate them? Etc... How is this different than normal resource failure? And how will you know at initial enumearation what devices will be plugged in? > Overall, how does the above look? In general, it looks fairly good. I'm just worried about the multiple layer case :) Warner > Thanks & Best Regards, > > Rajat Jain > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 14:31:42 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2BE2106568B; Tue, 23 Feb 2010 14:31:42 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-iw0-f185.google.com (mail-iw0-f185.google.com [209.85.223.185]) by mx1.freebsd.org (Postfix) with ESMTP id 7B0178FC1B; Tue, 23 Feb 2010 14:31:42 +0000 (UTC) Received: by iwn15 with SMTP id 15so3103121iwn.7 for ; Tue, 23 Feb 2010 06:31:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=CDL/sZejUu4e5XX6eURcWG9ZHhZNnOYYNcRg2XDBSVc=; b=spixNNFzS6IKAJm4B+Qb1rP08mvDFHf8jv7dxnETZ183Qf56xjDhl7ikEiQ41uk+L6 so9+FOpmedQkMjnKNOBuHX01a3KSj/WrFdWpoZcdjNKZhO5+YdOCEIik1RCYHCfXurXU 9YvzMu3kYy4eYNkEJIxNjfB6xHXCwcN9+ibfI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=U+Funx24cSSbuve18uOPYTbvf91fm0xbIITeo+P1ADNd+0BEuvTUkqG9Sdx7zUDmDM g6lTnuW50sJgTYHjT9Z6BnSogY3ajgggTAkZm52NEqw1Np65k0yMnQSgzSMtMO14ycSe gLCwmnYGRtD6a9kHeQiQgmMhNAvla/JtOL4AE= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.231.154.207 with SMTP id p15mr227861ibw.71.1266933759014; Tue, 23 Feb 2010 06:02:39 -0800 (PST) In-Reply-To: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> References: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> Date: Tue, 23 Feb 2010 15:02:38 +0100 X-Google-Sender-Auth: 1238ac7ec9e8960b Message-ID: <3bbf2fe11002230602t28701370l2712f836ebaee03@mail.gmail.com> From: Attilio Rao To: Rajat Jain Content-Type: text/plain; charset=UTF-8 Cc: freebsd-ia32@freebsd.org, freebsd-new-bus@freebsd.org, freebsd-ppc@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 14:31:42 -0000 2010/2/23 Rajat Jain : > > Hi, > > I'm trying to add PCI-E hotplug support to the FreeBSD. As a first step > for the PCI-E hotplug support, I'm trying to decide on a resource > management / allocation strategy for the PCI memory / IO and the bus > numbers. Can you please comment on the following approach that I am > considering for resource allocation: You may also coordinate with jhb@ which is working on a multipass layer for improving resource mapping/allocation. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 17:04:34 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6DF21065672; Tue, 23 Feb 2010 17:04:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 877AB8FC0A; Tue, 23 Feb 2010 17:04:34 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 022D046B03; Tue, 23 Feb 2010 12:04:34 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 859EF8A021; Tue, 23 Feb 2010 12:04:21 -0500 (EST) From: John Baldwin To: freebsd-arch@freebsd.org Date: Tue, 23 Feb 2010 10:27:20 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20100120; KDE/4.3.1; amd64; ; ) References: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> In-Reply-To: <8506939B503B404A84BBB12293FC45F606B88C39@emailbng3.jnpr.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201002231027.20749.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 23 Feb 2010 12:04:21 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.3 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-ia32@freebsd.org, freebsd-new-bus@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 17:04:34 -0000 On Tuesday 23 February 2010 2:16:40 am Rajat Jain wrote: > > Hi, > > I'm trying to add PCI-E hotplug support to the FreeBSD. As a first step > for the PCI-E hotplug support, I'm trying to decide on a resource > management / allocation strategy for the PCI memory / IO and the bus > numbers. Can you please comment on the following approach that I am > considering for resource allocation: > > PROBLEM STATEMENT: > ------------------ > Given a memory range [A->B], IO range [C->D], and limited (256) bus > numbers, enumerate the PCI tree of a system, leaving enough "holes" in > between to allow addition of future devices. > > PROPOSED STRATEGY: > ------------------ > 1) When booting, start enumerating in a depth-first-search order. While > enumeration, always keep track of: > > * The next bus number (x) that can be allocated > > * The next Memory space pointer (A + y) starting which allocation can > be > done. ("y" is the memory already allocated). > > * The next IO Space pointer (C + z) starting which allocation can be > done. > ("z" is the IO space already allocated). > > Keep incrementing the above as the resources are allocated. > > 2) Allocate bus numbers sequentially while traversing down from root to > a leaf node (end point). When going down traversing a bridge: > > * Allocate the next available bus number (x) to the secondary bus of > bridge. > > * Temporarily mark the subordinate bridge as 0xFF (to allow discovery > of > maximum buses). > > * Temporarily assign all the remaining available memory space to bridge > > [(A+x) -> B]. Ditto for IO space. > > 3) When a leaf node (End point) is reached, allocate the memory / IO > resource requested by the device, and increment the pointers. > > 4) While passing a bridge in the upward direction, tweak the bridge > registers such that its resources are ONLY ENOUGH to address the needs > of all the PCI tree below it, and if it has its own internal memory > mapped registers, some memory for it as well. > > The above is the standard depth-first algorithm for resource allocation. > Here is the addition to support hot-plug: > > At each bridge that supports hot-plug, in addition to the resources that > would have normally been allocated to this bridge, additionally > pre-allocate and assign to bridge (in anticipation of any new devices > that may be added later): > > a) "RSRVE_NUM_BUS" number of busses, to cater to any bridges, PCI trees > present on the device plugged. > > b) "RSRVE_MEM" amount of memory space, to cater to all the PCI devices > that > may be attached later on. > > c) "RESRVE_IO" amount of IO space, to cater to all PCI devices that may > be > attached later on. > > Please note that the above RSRVE* are constants defining the amount of > resources to be set aside for /below each HOT-PLUGGABLE bridge; their > values may be tweaked via a compile time option or via a sysctl. > > FEW COMMENTS > ------------ > > 1) The strategy is fairly generic and tweak-able since it does not waste > a lot of resources (The developer neds to pick up a smart bvalue for > howmuch resources to reserve at each hot-pluggable slot): > > * The reservations shall be done only for hot-pluggable bridges > > * The developer can tweak the values (even disable it) for how much > Resources shall be allocated for each hot-pluggable bridge. > > 2) One point of debate is what happens if there are too much resource > demands in the system (too many devices or the developer configures too > many resources to be allocated for each hot-pluggable devices). For e.g. > consider that while enumeration we find that all the resources are > already allocated, while there are more devices that need resources. So > do we simply do not enumerate them? Etc... > > Overall, how does the above look? I think one wrinkle is that we should try to preserve the resources that the firmware has set for devices, at least on x86. I had also wanted to make use of multipass for this, but that requires a bit more work to split the PCI bus attach up into separate steps. -- John Baldwin From owner-freebsd-ppc@FreeBSD.ORG Tue Feb 23 20:36:21 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 763351065743; Tue, 23 Feb 2010 20:36:21 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id EC3288FC15; Tue, 23 Feb 2010 20:36:20 +0000 (UTC) Received: from sirius.springdaemons.com (c-71-198-20-159.hsd1.ca.comcast.net [71.198.20.159]) by mx0.deglitch.com (Postfix) with ESMTPA id 79DFB8FC51; Tue, 23 Feb 2010 23:26:08 +0300 (MSK) Received: from sirius.springdaemons.com (localhost [127.0.0.1]) by sirius.springdaemons.com (Postfix) with SMTP id 00F2B22831; Tue, 23 Feb 2010 12:26:04 -0800 (PST) Date: Tue, 23 Feb 2010 12:26:04 -0800 From: Stanislav Sedov To: freebsd-ppc@freebsd.org Message-Id: <20100223122604.69000cbf.stas@FreeBSD.org> In-Reply-To: <4B7970D7.4010702@freebsd.org> References: <4B7970D7.4010702@freebsd.org> Organization: The FreeBSD Project X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.6; powerpc-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: powerpc64 status and request for testers X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 20:36:21 -0000 On Mon, 15 Feb 2010 10:05:43 -0600 Nathan Whitehorn mentioned: > I have been working on a full 64-bit PowerPC port of FreeBSD which is > now mature enough that wider exposure and testing would be appreciated. > It boots multiuser and most ports seem to just work, etc. Note that this > is still very raw, however; building it remains tricky, and it may have > fatal bugs resulting in data loss. > > Caveats: > - Memory above 2 GB is not really supported yet, due to lack of IOMMU > support or bounce buffers. > - snd_ai2s causes panics on 64-bit kernels Actually it panics on my G4 as well, so I think it is not ppc64 related. I'm now looking into it. Congratulations for the good work! -- Stanislav Sedov ST4096-RIPE From owner-freebsd-ppc@FreeBSD.ORG Wed Feb 24 01:36:31 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34819106566C; Wed, 24 Feb 2010 01:36:31 +0000 (UTC) (envelope-from babkin@verizon.net) Received: from vms173019pub.verizon.net (vms173019pub.verizon.net [206.46.173.19]) by mx1.freebsd.org (Postfix) with ESMTP id F256C8FC13; Wed, 24 Feb 2010 01:36:30 +0000 (UTC) Received: from vms061.mailsrvcs.net ([unknown] [192.168.1.2]) by vms173019.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0KYB00JFIG3V29A5@vms173019.mailsrvcs.net>; Tue, 23 Feb 2010 16:35:56 -0600 (CST) Received: from 65.242.108.162 ([65.242.108.162]) by vms061.mailsrvcs.net (Verizon Webmail) with HTTP; Tue, 23 Feb 2010 16:35:55 -0600 (CST) Date: Tue, 23 Feb 2010 16:35:55 -0600 (CST) From: Sergey Babkin To: jhb@freebsd.org Message-id: <24099271.347187.1266964555857.JavaMail.root@vms061.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-Originating-IP: [65.242.108.162] Cc: freebsd-ia32@freebsd.org, freebsd-new-bus@freebsd.org, freebsd-ppc@freebsd.org, freebsd-arch@freebsd.org Subject: Re: Re: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 01:36:31 -0000 (Sorry, if the email comes out looking weird, I want to give another try to see if the provider has fixed the formatting issues i nthe web interface or not). On Tuesday 23 February 2010 2:16:40 am Rajat Jain wrote: > > Hi, > > I'm trying to add PCI-E hotplug support to the FreeBSD. As a first step > for the PCI-E hotplug support, I'm trying to decide on a resource > management / allocation strategy for the PCI memory / IO and the bus > numbers. Can you please comment on the following approach that I am > considering for resource allocation: > > PROBLEM STATEMENT: > ------------------ > Given a memory range [A->B], IO range [C->D], and limited (256) bus > numbers, enumerate the PCI tree of a system, leaving enough "holes" in > between to allow addition of future devices. > > PROPOSED STRATEGY: > ------------------ > 1) When booting, start enumerating in a depth-first-search order. While > enumeration, always keep track of: > > * The next bus number (x) that can be allocated > > * The next Memory space pointer (A + y) starting which allocation can > be > done. ("y" is the memory already allocated). > > * The next IO Space pointer (C + z) starting which allocation can be > done. > ("z" is the IO space already allocated). > > Keep incrementing the above as the resources are allocated. > > 2) Allocate bus numbers sequentially while traversing down from root to > a leaf node (end point). When going down traversing a bridge: > > * Allocate the next available bus number (x) to the secondary bus of > bridge. > > * Temporarily mark the subordinate bridge as 0xFF (to allow discovery > of > maximum buses). > > * Temporarily assign all the remaining available memory space to bridge > > [(A+x) -> B]. Ditto for IO space. > > 3) When a leaf node (End point) is reached, allocate the memory / IO > resource requested by the device, and increment the pointers. > > 4) While passing a bridge in the upward direction, tweak the bridge > registers such that its resources are ONLY ENOUGH to address the needs > of all the PCI tree below it, and if it has its own internal memory > mapped registers, some memory for it as well. > > The above is the standard depth-first algorithm for resource allocation. > Here is the addition to support hot-plug: > > At each bridge that supports hot-plug, in addition to the resources that > would have normally been allocated to this bridge, additionally > pre-allocate and assign to bridge (in anticipation of any new devices > that may be added later): > > a) "RSRVE_NUM_BUS" number of busses, to cater to any bridges, PCI trees > present on the device plugged. > > b) "RSRVE_MEM" amount of memory space, to cater to all the PCI devices > that > may be attached later on. > > c) "RESRVE_IO" amount of IO space, to cater to all PCI devices that may > be > attached later on. A kind of stupid question: should the reserve amounts depend on the level of the bridge? Perhaps the priidges closer to the root should get more reserves. Perhaps it doesn't matter so much durin gthe initial enumeration but ma matter latter after a hot plug. Suppose we have the Bridge B1 that gets RSRVE resources attached to it during the initial enumeration. Then someone comes and hot-plugs a bridge B2 under B1. B2 then I guess will also try to get a reserve of RSRVE resources for itself, so it would take the whole original reserve of B1 to itself. If someone comes later and tries to hot-plug another bridge B3 under B1, that bridge would not get any resources and the plugging would fail. -SB From owner-freebsd-ppc@FreeBSD.ORG Wed Feb 24 04:35:19 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDADB106566B; Wed, 24 Feb 2010 04:35:19 +0000 (UTC) (envelope-from rajatjain@juniper.net) Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by mx1.freebsd.org (Postfix) with ESMTP id CCD708FC16; Wed, 24 Feb 2010 04:35:18 +0000 (UTC) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKS4SshmVUaDSyL+FTm5ptlGPCuZEBf9AD@postini.com; Tue, 23 Feb 2010 20:35:19 PST Received: from gaugeboson.jnpr.net (10.209.194.17) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server id 8.1.393.1; Tue, 23 Feb 2010 20:32:39 -0800 Received: from emailbng3.jnpr.net ([10.209.194.27]) by gaugeboson.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Feb 2010 10:02:36 +0530 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 24 Feb 2010 10:02:35 +0530 Message-ID: <8506939B503B404A84BBB12293FC45F606B88E55@emailbng3.jnpr.net> In-Reply-To: <24099271.347187.1266964555857.JavaMail.root@vms061.mailsrvcs.net> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Re: Strategy for PCI resource management (for supporting hot-plug) Thread-Index: Acq02NJfpnyCYOSsRvKUNhQqcZ9VZQAMFnBg References: <24099271.347187.1266964555857.JavaMail.root@vms061.mailsrvcs.net> From: Rajat Jain To: Sergey Babkin , X-OriginalArrivalTime: 24 Feb 2010 04:32:36.0576 (UTC) FILETIME=[6403EE00:01CAB50A] Cc: freebsd-ia32@freebsd.org, freebsd-new-bus@freebsd.org, freebsd-ppc@freebsd.org, freebsd-arch@freebsd.org Subject: RE: Re: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 04:35:19 -0000 Hello Sergey, > A kind of stupid question: should the reserve amounts depend on the level > of the bridge? > Perhaps the priidges closer to the root should get more reserves. Perhaps > it doesn't > matter so much durin gthe initial enumeration but ma matter latter after a > hot plug. One clarification perhaps I did not give in my proposal. We would reserve resources (bus numbers / memory / IO) only for bridges that are CAPABLE of HOT-PLUG. The rest of the bridges would get their usual share of resources.=20 Now, the same amount of reserved resources gets assigned to each HOT-PLUG capable bridge, irrespective of at which level it is in hierarchy. This is because no matter where it is, there is equal probability of a new card being plugged in at ANY of those slots.=20 The only problem as you say is when we plug in a PCI card, which has a HOT-PLUGGABLE SLOT on it (on which we can plug in more cards). (This is because a bridge wants extra reserved resources only when it is hot-plug capable). Do such devices exist? Since theoretically possible, but practically extremely rare, I say we do not support this case. Comments? Thanks, Rajat Jain > -----Original Message----- > From: Sergey Babkin [mailto:babkin@verizon.net] > Sent: Wednesday, February 24, 2010 4:06 AM > To: jhb@freebsd.org > Cc: freebsd-arch@freebsd.org; Rajat Jain; freebsd-ia32@freebsd.org; > freebsd-new-bus@freebsd.org; freebsd-ppc@freebsd.org > Subject: Re: Re: Strategy for PCI resource management (for supporting hot- > plug) >=20 > (Sorry, if the email comes out looking weird, I want to give another try > to see if the provider has > fixed the formatting issues i nthe web interface or not). >=20 > On Tuesday 23 February 2010 2:16:40 am Rajat Jain wrote: > > > > Hi, > > > > I'm trying to add PCI-E hotplug support to the FreeBSD. As a first step > > for the PCI-E hotplug support, I'm trying to decide on a resource > > management / allocation strategy for the PCI memory / IO and the bus > > numbers. Can you please comment on the following approach that I am > > considering for resource allocation: > > > > PROBLEM STATEMENT: > > ------------------ > > Given a memory range [A->B], IO range [C->D], and limited (256) bus > > numbers, enumerate the PCI tree of a system, leaving enough "holes" in > > between to allow addition of future devices. > > > > PROPOSED STRATEGY: > > ------------------ > > 1) When booting, start enumerating in a depth-first-search order. While > > enumeration, always keep track of: > > > > * The next bus number (x) that can be allocated > > > > * The next Memory space pointer (A + y) starting which allocation can > > be > > done. ("y" is the memory already allocated). > > > > * The next IO Space pointer (C + z) starting which allocation can be > > done. > > ("z" is the IO space already allocated). > > > > Keep incrementing the above as the resources are allocated. > > > > 2) Allocate bus numbers sequentially while traversing down from root to > > a leaf node (end point). When going down traversing a bridge: > > > > * Allocate the next available bus number (x) to the secondary bus of > > bridge. > > > > * Temporarily mark the subordinate bridge as 0xFF (to allow discovery > > of > > maximum buses). > > > > * Temporarily assign all the remaining available memory space to bridge > > > > [(A+x) -> B]. Ditto for IO space. > > > > 3) When a leaf node (End point) is reached, allocate the memory / IO > > resource requested by the device, and increment the pointers. > > > > 4) While passing a bridge in the upward direction, tweak the bridge > > registers such that its resources are ONLY ENOUGH to address the needs > > of all the PCI tree below it, and if it has its own internal memory > > mapped registers, some memory for it as well. > > > > The above is the standard depth-first algorithm for resource allocation. > > Here is the addition to support hot-plug: > > > > At each bridge that supports hot-plug, in addition to the resources that > > would have normally been allocated to this bridge, additionally > > pre-allocate and assign to bridge (in anticipation of any new devices > > that may be added later): > > > > a) "RSRVE_NUM_BUS" number of busses, to cater to any bridges, PCI trees > > present on the device plugged. > > > > b) "RSRVE_MEM" amount of memory space, to cater to all the PCI devices > > that > > may be attached later on. > > > > c) "RESRVE_IO" amount of IO space, to cater to all PCI devices that may > > be > > attached later on. >=20 > A kind of stupid question: should the reserve amounts depend on the level > of the bridge? > Perhaps the priidges closer to the root should get more reserves. Perhaps > it doesn't > matter so much durin gthe initial enumeration but ma matter latter after a > hot plug. >=20 > Suppose we have the Bridge B1 that gets RSRVE resources attached to it > during > the initial enumeration. Then someone comes and hot-plugs a bridge B2 > under B1. > B2 then I guess will also try to get a reserve of RSRVE resources for > itself, so it would > take the whole original reserve of B1 to itself. If someone comes later > and tries > to hot-plug another bridge B3 under B1, that bridge would not get any > resources > and the plugging would fail. >=20 > -SB From owner-freebsd-ppc@FreeBSD.ORG Wed Feb 24 12:23:27 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F86C106564A; Wed, 24 Feb 2010 12:23:27 +0000 (UTC) (envelope-from tf@slash10.com) Received: from mail.openoffice.net (mail.openoffice.net [80.76.0.11]) by mx1.freebsd.org (Postfix) with ESMTP id 703498FC1A; Wed, 24 Feb 2010 12:23:25 +0000 (UTC) Received: from localhost.localdomain ([88.82.102.20]) (AUTH: CRAM-MD5 t.fritz@openoffice.ch, TLS: TLSv1/SSLv3, 256bits, CAMELLIA256-SHA) by mail.openoffice.net with esmtp; Wed, 24 Feb 2010 13:13:21 +0100 id 0110C883.4B8517E1.00006E0A Message-ID: <4B8517DB.7090406@slash10.com> Date: Wed, 24 Feb 2010 13:13:15 +0100 From: Thomas Fritz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100120 Fedora/3.0.1-1.fc12 Thunderbird/3.0.1 MIME-Version: 1.0 To: Nathan Whitehorn References: <4B81BBC7.5050100@gmail.com> <4B830C74.3020603@freebsd.org> In-Reply-To: <4B830C74.3020603@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Panic on install boot X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 12:23:27 -0000 Is the partitioning problem solved on this special image as well? On 02/23/2010 12:00 AM, Nathan Whitehorn wrote: > Alexander Bakst wrote: >> Hi, >> >> I recently got a power mac g5, and am trying to install freebsd 8.0. I >> am using "8.0-RELEASE-powerpc-disc1.iso". Immediately after booting, I >> get "panic: moea 64 bootstrap: too many ofw translations." >> >> Is there a fix for this issue? >> > There was a bug in the 8.0 install CDs that prevents them from booting > on a large number of G5 systems. You can use a 9.0-SNAP image I made in > November to get a bootable CD: > > http://people.freebsd.org/~nwhitehorn/9.0-20091112-SNAP/9.0-20091112-SNAP-powerpc-disc1.iso > > > Also, -CURRENT now has some updates to smu(4) that prevent the fans in > SMU-based machines from running at maximum all the time, which should be > MFCed shortly and will be in 8.1. Once those are MFCed in the next week > or two, I will make an 8.0-STABLE CD with those updates. > -Nathan > _______________________________________________ > 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 Feb 25 01:16:43 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9A7D106564A; Thu, 25 Feb 2010 01:16:43 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id B04178FC12; Thu, 25 Feb 2010 01:16:43 +0000 (UTC) Received: from hydrogen.funkthat.com (rfi20yj7t50f7r9j@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id o1P0wgOC012002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Feb 2010 16:58:43 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id o1P0wfDi012001; Wed, 24 Feb 2010 16:58:41 -0800 (PST) (envelope-from jmg) Date: Wed, 24 Feb 2010 16:58:41 -0800 From: John-Mark Gurney To: Rajat Jain Message-ID: <20100225005841.GB58753@funkthat.com> Mail-Followup-To: Rajat Jain , Sergey Babkin , jhb@freebsd.org, freebsd-ia32@freebsd.org, freebsd-new-bus@freebsd.org, freebsd-ppc@freebsd.org, freebsd-arch@freebsd.org References: <24099271.347187.1266964555857.JavaMail.root@vms061.mailsrvcs.net> <8506939B503B404A84BBB12293FC45F606B88E55@emailbng3.jnpr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8506939B503B404A84BBB12293FC45F606B88E55@emailbng3.jnpr.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hydrogen.funkthat.com [127.0.0.1]); Wed, 24 Feb 2010 16:58:43 -0800 (PST) Cc: freebsd-ia32@freebsd.org, freebsd-new-bus@freebsd.org, Sergey Babkin , freebsd-arch@freebsd.org, freebsd-ppc@freebsd.org Subject: Re: Re: Strategy for PCI resource management (for supporting hot-plug) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 01:16:44 -0000 Rajat Jain wrote this message on Wed, Feb 24, 2010 at 10:02 +0530: > The only problem as you say is when we plug in a PCI card, which has a > HOT-PLUGGABLE SLOT on it (on which we can plug in more cards). (This is > because a bridge wants extra reserved resources only when it is hot-plug > capable). Do such devices exist? Since theoretically possible, but > practically extremely rare, I say we do not support this case. There is an ExpressCard PCI-E expansion box (I have one) which you could put a PCI-E cardbus adapter card in which would I believe be the case that you are asking about... Now how many people would do that? Not many, but more might put in multiport PCI-E cards. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-ppc@FreeBSD.ORG Fri Feb 26 22:32:53 2010 Return-Path: Delivered-To: powerpc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B54201065670; Fri, 26 Feb 2010 22:32:53 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8E7478FC12; Fri, 26 Feb 2010 22:32:53 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o1QMWqRU012390; Fri, 26 Feb 2010 17:32:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o1QMWqWS012389; Fri, 26 Feb 2010 22:32:52 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 26 Feb 2010 22:32:52 GMT Message-Id: <201002262232.o1QMWqWS012389@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [releng_8 tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2010 22:32:53 -0000 TB --- 2010-02-26 21:24:43 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-02-26 21:24:43 - starting RELENG_8 tinderbox run for powerpc/powerpc TB --- 2010-02-26 21:24:43 - cleaning the object tree TB --- 2010-02-26 21:25:00 - cvsupping the source tree TB --- 2010-02-26 21:25:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/powerpc/powerpc/supfile TB --- 2010-02-26 21:25:29 - building world TB --- 2010-02-26 21:25:29 - MAKEOBJDIRPREFIX=/obj TB --- 2010-02-26 21:25:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-02-26 21:25:29 - TARGET=powerpc TB --- 2010-02-26 21:25:29 - TARGET_ARCH=powerpc TB --- 2010-02-26 21:25:29 - TZ=UTC TB --- 2010-02-26 21:25:29 - __MAKE_CONF=/dev/null TB --- 2010-02-26 21:25:29 - cd /src TB --- 2010-02-26 21:25:29 - /usr/bin/make -B buildworld >>> World build started on Fri Feb 26 21:25:29 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Feb 26 22:21:53 UTC 2010 TB --- 2010-02-26 22:21:53 - generating LINT kernel config TB --- 2010-02-26 22:21:53 - cd /src/sys/powerpc/conf TB --- 2010-02-26 22:21:53 - /usr/bin/make -B LINT TB --- 2010-02-26 22:21:53 - building LINT kernel TB --- 2010-02-26 22:21:53 - MAKEOBJDIRPREFIX=/obj TB --- 2010-02-26 22:21:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-02-26 22:21:53 - TARGET=powerpc TB --- 2010-02-26 22:21:53 - TARGET_ARCH=powerpc TB --- 2010-02-26 22:21:53 - TZ=UTC TB --- 2010-02-26 22:21:53 - __MAKE_CONF=/dev/null TB --- 2010-02-26 22:21:53 - cd /src TB --- 2010-02-26 22:21:53 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Feb 26 22:21:53 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] :> export_syms awk -f /src/sys/conf/kmod_syms.awk atapicam.kld export_syms | xargs -J% objcopy % atapicam.kld ld -Bshareable -d -warn-common -o atapicam.ko atapicam.kld objcopy --strip-debug atapicam.ko ===> ath (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/powerpc/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mlongcall -fno-omit-frame-pointer -I/obj/powerpc/src/sys/LINT -msoft-float -mno-altivec -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c /src/sys/modules/ath/../../dev/ath/if_ath.c /src/sys/modules/ath/../../dev/ath/if_ath.c: In function 'ath_key_alloc': /src/sys/modules/ath/../../dev/ath/if_ath.c:2240: error: expected expression before '/' token *** Error code 1 Stop in /src/sys/modules/ath. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-02-26 22:32:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-02-26 22:32:52 - ERROR: failed to build lint kernel TB --- 2010-02-26 22:32:52 - 3311.13 user 560.65 system 4088.76 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-powerpc-powerpc.full From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 19:09:09 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D18A1065672 for ; Sat, 27 Feb 2010 19:09:09 +0000 (UTC) (envelope-from chad@csbint.biz) Received: from mail.macristy.com (mail.macristy.com [64.179.29.95]) by mx1.freebsd.org (Postfix) with ESMTP id E8EED8FC0C for ; Sat, 27 Feb 2010 19:09:08 +0000 (UTC) Received: from [10.0.9.10] (c-98-217-31-115.hsd1.ct.comcast.net [98.217.31.115]) by mail.macristy.com (Postfix) with ESMTP id 388681D07E26 for ; Sat, 27 Feb 2010 13:56:35 -0500 (EST) Message-ID: <4B896950.5000001@csbint.biz> Date: Sat, 27 Feb 2010 13:49:52 -0500 From: Chad Thompson User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701) MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Installing FreeBSD via USB or network? X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 19:09:09 -0000 Hello, I have a PowerBook DVI and my DVD-ROM drive won't accept discs. Can I copy the FreeBSD install files to a USB drive and have it start install process? Are there network boot options with a TFTP or such? Thanks for any help in advance. C From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 21:06:30 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5328106566B for ; Sat, 27 Feb 2010 21:06:30 +0000 (UTC) (envelope-from alexander.bakst@oracle.com) Received: from rcsinet14.oracle.com (rcsinet14.oracle.com [148.87.113.126]) by mx1.freebsd.org (Postfix) with ESMTP id 975CA8FC14 for ; Sat, 27 Feb 2010 21:06:30 +0000 (UTC) Received: from rcsinet12.oracle.com (rcsinet12.oracle.com [148.87.113.124]) by rcsinet14.oracle.com (Sentrion-MP-4.0.0/Sentrion-MP-4.0.0) with ESMTP id o1RKlbqc016318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 27 Feb 2010 20:47:38 GMT Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by rcsinet12.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id o1RKlZMf031345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sat, 27 Feb 2010 20:47:36 GMT Received: from acsmt354.oracle.com (acsmt354.oracle.com [141.146.40.154]) by rcsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id o1RKlX3g003914 for ; Sat, 27 Feb 2010 20:47:33 GMT Received: from abhmt003.oracle.com by acsmt354.oracle.com with ESMTP id 54444741267303616; Sat, 27 Feb 2010 12:46:56 -0800 Received: from Faptop.local (/66.31.201.186) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sat, 27 Feb 2010 12:46:56 -0800 Message-ID: <4B8984BF.5080607@oracle.com> Date: Sat, 27 Feb 2010 15:46:55 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: acsmt354.oracle.com [141.146.40.154] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090202.4B8984E7.0114:SCFMA4539814,ss=1,fgs=0 Subject: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 21:06:30 -0000 Hi all, I just set up a system running a recent kernel on a G5 7,3: [abakst@ ~/ddclient-3.7.3]$ uname -a FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #314 r204309:204312M: Thu Feb 25 09:28:38 CST 2010 root@comporellon.tachypleus.net:/usr/obj/powerpc/usr/src/sys/GENERIC powerpc I think fan controls are supposed to be enabled for this version, but my machine still sounds like a jet engine. Is there a way to check if thermal management is supported? And if it is, how do I tell it to 'go'? I assume that acpi and apm related documentation isn't relevant on the ppc platform. Thanks, Alexander From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 21:22:12 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C930106566B for ; Sat, 27 Feb 2010 21:22:12 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id EEB9D8FC08 for ; Sat, 27 Feb 2010 21:22:11 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-8-131.flashcable.ch [91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id o1RLM8pB019292; Sat, 27 Feb 2010 22:22:09 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4B898D00.9030706@fgznet.ch> Date: Sat, 27 Feb 2010 22:22:08 +0100 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 MIME-Version: 1.0 To: Alexander Bakst References: <4B8984BF.5080607@oracle.com> In-Reply-To: <4B8984BF.5080607@oracle.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 21:22:12 -0000 Hi Alexander, On 27.02.10 21:46, Alexander Bakst wrote: > I just set up a system running a recent kernel on a G5 7,3: > > [abakst@ ~/ddclient-3.7.3]$ uname -a > FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #314 r204309:204312M: Thu Feb > 25 09:28:38 CST 2010 > root@comporellon.tachypleus.net:/usr/obj/powerpc/usr/src/sys/GENERIC > powerpc > > I think fan controls are supposed to be enabled for this version, but my > machine still sounds like a jet engine. Is there a way to check if > thermal management is supported? And if it is, how do I tell it to 'go'? > I assume that acpi and apm related documentation isn't relevant on the > ppc platform. I guess your machine belongs to the category of mine, a plain old IBM970. No FX, right? You can check your /var/log/messages and see if there is an entry about 'smu'. If not, then you're lost at the moment. The fan management support for these machines is lacking atm. Only the newer machines (G5) which have an IBM970FX/MP have support for a simple fan management. I even guess your CPU clock is not running at its highest speed, right? Would be great if you could post your dmesg. Thanks, Andreas From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 21:28:50 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71F30106564A for ; Sat, 27 Feb 2010 21:28:50 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1CDE48FC17 for ; Sat, 27 Feb 2010 21:28:49 +0000 (UTC) Received: by vws14 with SMTP id 14so559969vws.13 for ; Sat, 27 Feb 2010 13:28:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ESYn9YujuZy9P7RMHyprQ6TN3I7A0ZeX0ynLlbRx4wA=; b=I8gOaeMA9yx0Js6nLjPdcCHG6ewJQIPDKIFYa3e/t5pjE/EdEMb/DP0RcWSslR/fz/ j7XfFULucoyzCxEEyQu3OllKkc5QjMWopmBchp8qObDNg5rVB4z0dP5WBMWbYxMOL5+Q FDvLLQ9Styg5jughMnYhNpy7gffmH9PvCjCGg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=bQHSziFMbX8o3tSJdj2MTUCd2bMDOcnrgCp0+8G/dnWb0K5PORfz5YcAvWvtkTQQBJ x9rLcxvOXZ++5pekbzZ5U0NPLUj9EgHRuhzAjM09MWTMWPcOH6gXMvIJTNEE2PIMeLp7 VdGJJfsHn07L3F1W3511pn5YZxFMJChp7d/VQ= Received: by 10.220.123.92 with SMTP id o28mr1658968vcr.116.1267306119714; Sat, 27 Feb 2010 13:28:39 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 22sm13997484vws.14.2010.02.27.13.28.37 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 27 Feb 2010 13:28:38 -0800 (PST) Message-ID: <4B898E84.1040200@gmail.com> Date: Sat, 27 Feb 2010 16:28:36 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: Andreas Tobler References: <4B8984BF.5080607@oracle.com> <4B898D00.9030706@fgznet.ch> In-Reply-To: <4B898D00.9030706@fgznet.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 21:28:50 -0000 (Switched my non-work e-mail) Well, I actually am using a fancy apple G5 - I belive it is a power 970fx, not sure though. I'm not even sure how to check the current clock frequency of my cpu. To be honest, it would be fantastic if it weren't running at the highest speed, since I would like to save power. I don't know if the kernel will tell the cpu to snooze/nap. Thanks, Alexander dmesg output: Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #314 r204309:204312M: Thu Feb 25 09:28:38 CST 2010 root@comporellon.tachypleus.net:/usr/obj/powerpc/usr/src/sys/GENERIC powerpc cpu0: IBM PowerPC 970FX revision 3.0, 2000.36 MHz cpu0: Features dc000000 cpu0: HID0 511081 real memory = 1060220928 (1011 MB) avail memory = 986472448 (940 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0: dev=ff899e08 (BSP) cpu1: dev=ff89b2e8 ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware ispfw: registered firmware kbd0 at kbdmux0 nexus0: cpulist0: on nexus0 cpu0: on cpulist0 pcr0: on cpu0 pcr0: No power mode data in device tree! device_attach: pcr0 attach returned 6 cpu1: on cpulist0 pcr1: on cpu1 pcr1: No power mode data in device tree! device_attach: pcr1 attach returned 6 pcib0: on nexus0 pci0: on pcib0 vgapci0: port 0x400-0x4ff mem 0xa0000000-0xafffffff,0x90000000-0x9000ffff irq 48 at device 16.0 on pci0 cpcht0: on nexus0 pcib1: on cpcht0 pci1: on pcib1 macio0: mem 0x80000000-0x8007ffff at device 7.0 on pci1 openpic0: mem 0x40000-0x7ffff on macio0 macgpio0: mem 0x50-0x8a on macio0 scc0: mem 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff irq 22,5,6,23,7,8 on macio0 scc0: [FILTER] scc0: [FILTER] uart0: on scc0 uart0: [FILTER] uart1: on scc0 uart1: [FILTER] iichb0: mem 0x18000-0x18fff irq 26 on macio0 iichb0: [ITHREAD] iicbus0: on iichb0 iicbus0: at addr 0x1c0 iicbus0: at addr 0x6a pmu0: mem 0x16000-0x17fff irq 25 on macio0 ohci0: mem 0x80081000-0x80081fff irq 27 at device 8.0 on pci1 ohci0: [ITHREAD] usbus0: on ohci0 ohci1: mem 0x80080000-0x80080fff irq 28 at device 9.0 on pci1 ohci1: [ITHREAD] usbus1: on ohci1 pcib2: on cpcht0 pci2: on pcib2 ohci2: mem 0x80702000-0x80702fff irq 63 at device 11.0 on pci2 ohci2: [ITHREAD] usbus2: on ohci2 ohci3: mem 0x80701000-0x80701fff irq 63 at device 11.1 on pci2 ohci3: [ITHREAD] usbus3: on ohci3 ehci0: mem 0x80700000-0x807000ff irq 63 at device 11.2 on pci2 ehci0: [ITHREAD] usbus4: EHCI version 1.0 usbus4: on ehci0 pcib3: on cpcht0 pci3: on pcib3 ata0: mem 0x80104000-0x80107fff irq 39 at device 13.0 on pci3 ata0: [ITHREAD] fwohci0: <1394 Open Host Controller Interface> mem 0x80100000-0x80100fff irq 40 at device 14.0 on pci3 fwohci0: [ITHREAD] fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:0d:93:ff:fe:62:62:7c fwohci0: invalid speed 7 (fixed to 3). fwohci0: Phy 1394a available S800, 3 ports. fwohci0: Link S800, max_rec 4096 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:0d:93:62:62:7c fwe0: Ethernet address: 02:0d:93:62:62:7c sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=2, CYCLEMASTER mode pcib4: on cpcht0 pci4: on pcib4 gem0: mem 0x80400000-0x805fffff irq 41 at device 15.0 on pci4 miibus0: on gem0 brgphy0: PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto gem0: 10kB RX FIFO, 4kB TX FIFO gem0: Ethernet address: 00:0d:93:62:62:7c gem0: [ITHREAD] pcib5: on cpcht0 pci5: on pcib5 atapci0: mem 0x80600000-0x80601fff irq 0 at device 12.0 on pci5 atapci0: [ITHREAD] ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] atapci1: at device 12.1 on pci5 atapci1: unable to map interrupt device_attach: atapci1 attach returned 6 sc0: on nexus0 sc0: Unknown <16 virtual consoles, flags=0x300> Timecounter "decrementer" frequency 33333333 Hz quality 0 Timecounters tick every 10.000 msec firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) firewire0: bus manager 0 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 12Mbps Full Speed USB v1.0 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 usbus4: 480Mbps High Speed USB v2.0 ugen4.1: at usbus4 uhub4: on usbus4 uhub0: 2 ports with 2 removable, self powered acd0: DVDR at ata0-master UDMA66 uhub1: 2 ports with 2 removable, self powered ad0: 152627MB at ata2-master UDMA100 SATA 1.5Gb/s uhub2: 3 ports with 3 removable, self powered uhub3: 2 ports with 2 removable, self powered uhub4: 5 ports with 5 removable, self powered ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only; quirks = 0x0000 SMP: AP CPU #1 launched Root mount waiting for: usbus4 umass0:1:0:-1: Attached to scbus1d a0 at umass-sim0 bus 0 scbus1 target 0 lun 0 da0: < 2090E 5.00> Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 249MB (509952 512 byte sectors: 64H 32S/T 249C) (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) Trying to mount root from ufs:/dev/ad0s3 GEOM_PART: Partition 'ad0s4' not suitable for kernel dumps (wrong type?) ugen2.2: at usbus2 uhub5: on usbus2 uhub5: 4 ports with 4 removable, bus powered ugen2.3: at usbus2 ukbd0: on usbus2 kbd1 at ukbd0 ugen2.4: at usbus2 ums0: on usbus2 ums0: 1 buttons and [XY] coordinates ID=0 gem0: link state changed to DOWN gem0: link state changed to UP gem0: link state changed to DOWN gem0: link state changed to UP On 2/27/10 4:22 PM, Andreas Tobler wrote: > Hi Alexander, > > On 27.02.10 21:46, Alexander Bakst wrote: > >> I just set up a system running a recent kernel on a G5 7,3: >> >> [abakst@ ~/ddclient-3.7.3]$ uname -a >> FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #314 r204309:204312M: Thu Feb >> 25 09:28:38 CST 2010 >> root@comporellon.tachypleus.net:/usr/obj/powerpc/usr/src/sys/GENERIC >> powerpc >> >> I think fan controls are supposed to be enabled for this version, but my >> machine still sounds like a jet engine. Is there a way to check if >> thermal management is supported? And if it is, how do I tell it to 'go'? >> I assume that acpi and apm related documentation isn't relevant on the >> ppc platform. > > I guess your machine belongs to the category of mine, a plain old > IBM970. No FX, right? > > You can check your /var/log/messages and see if there is an entry > about 'smu'. If not, then you're lost at the moment. The fan > management support for these machines is lacking atm. Only the newer > machines (G5) which have an IBM970FX/MP have support for a simple fan > management. > > I even guess your CPU clock is not running at its highest speed, right? > > Would be great if you could post your dmesg. > > Thanks, > Andreas From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 21:48:02 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63AC0106566B; Sat, 27 Feb 2010 21:48:02 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id DD57C8FC1D; Sat, 27 Feb 2010 21:48:01 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-8-131.flashcable.ch [91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id o1RLlvtJ080309; Sat, 27 Feb 2010 22:47:59 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4B89930D.3060800@fgznet.ch> Date: Sat, 27 Feb 2010 22:47:57 +0100 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 MIME-Version: 1.0 To: Alexander Bakst References: <4B8984BF.5080607@oracle.com> <4B898D00.9030706@fgznet.ch> <4B898E84.1040200@gmail.com> In-Reply-To: <4B898E84.1040200@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 21:48:02 -0000 On 27.02.10 22:28, Alexander Bakst wrote: > (Switched my non-work e-mail) > > Well, I actually am using a fancy apple G5 - I belive it is a power > 970fx, not sure though. I'm not even sure how to check the current clock > frequency of my cpu. To be honest, it would be fantastic if it weren't > running at the highest speed, since I would like to save power. I don't > know if the kernel will tell the cpu to snooze/nap. Hm, it is a 970FX @ 2000.36 MHz. I'm confused that there is no smu? Maybe this one lacks the smu. According to the docs I have, the 7,3 behaves similar to the 7,2. And the 7,2/3 do not have an smu. The cpu speed is controlled via freq and volt. And some nasty gpio interrupts @ Nathan :) This bites me currently! Can you boot this machine into OS-X and see what it tells you about the CPU speed? Hopefully I'm wrong :) Andreas > dmesg output: > > Copyright (c) 1992-2010 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-CURRENT #314 r204309:204312M: Thu Feb 25 09:28:38 CST 2010 > > root@comporellon.tachypleus.net:/usr/obj/powerpc/usr/src/sys/GENERIC powerpc > cpu0: IBM PowerPC 970FX revision 3.0, 2000.36 MHz > cpu0: Features dc000000 > cpu0: HID0 511081 > real memory = 1060220928 (1011 MB) > avail memory = 986472448 (940 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0: dev=ff899e08 (BSP) > cpu1: dev=ff89b2e8 > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > ispfw: registered firmware > kbd0 at kbdmux0 > nexus0: > cpulist0: on nexus0 > cpu0: on cpulist0 > pcr0: on cpu0 > pcr0: No power mode data in device tree! > device_attach: pcr0 attach returned 6 > cpu1: on cpulist0 > pcr1: on cpu1 > pcr1: No power mode data in device tree! > device_attach: pcr1 attach returned 6 > pcib0: on nexus0 > pci0: on pcib0 > vgapci0: port 0x400-0x4ff mem > 0xa0000000-0xafffffff,0x90000000-0x9000ffff irq 48 at device 16.0 on pci0 > cpcht0: on nexus0 > pcib1: on cpcht0 > pci1: on pcib1 > macio0: mem 0x80000000-0x8007ffff at device > 7.0 on pci1 > openpic0: mem 0x40000-0x7ffff on macio0 > macgpio0: mem 0x50-0x8a on macio0 > scc0: mem > 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff > irq 22,5,6,23,7,8 on macio0 > scc0: [FILTER] > scc0: [FILTER] > uart0: on scc0 > uart0: [FILTER] > uart1: on scc0 > uart1: [FILTER] > iichb0: mem 0x18000-0x18fff irq 26 on macio0 > iichb0: [ITHREAD] > iicbus0: on iichb0 > iicbus0: at addr 0x1c0 > iicbus0: at addr 0x6a > pmu0: mem 0x16000-0x17fff irq 25 on macio0 > ohci0: mem 0x80081000-0x80081fff irq 27 > at device 8.0 on pci1 > ohci0: [ITHREAD] > usbus0: on ohci0 > ohci1: mem 0x80080000-0x80080fff irq 28 > at device 9.0 on pci1 > ohci1: [ITHREAD] > usbus1: on ohci1 > pcib2: on cpcht0 > pci2: on pcib2 > ohci2: mem 0x80702000-0x80702fff irq 63 at > device 11.0 on pci2 > ohci2: [ITHREAD] > usbus2: on ohci2 > ohci3: mem 0x80701000-0x80701fff irq 63 at > device 11.1 on pci2 > ohci3: [ITHREAD] > usbus3: on ohci3 > ehci0: mem 0x80700000-0x807000ff irq > 63 at device 11.2 on pci2 > ehci0: [ITHREAD] > usbus4: EHCI version 1.0 > usbus4: on ehci0 > pcib3: on cpcht0 > pci3: on pcib3 > ata0: mem 0x80104000-0x80107fff irq 39 at > device 13.0 on pci3 > ata0: [ITHREAD] > fwohci0:<1394 Open Host Controller Interface> mem 0x80100000-0x80100fff > irq 40 at device 14.0 on pci3 > fwohci0: [ITHREAD] > fwohci0: OHCI version 1.0 (ROM=0) > fwohci0: No. of Isochronous channels is 8. > fwohci0: EUI64 00:0d:93:ff:fe:62:62:7c > fwohci0: invalid speed 7 (fixed to 3). > fwohci0: Phy 1394a available S800, 3 ports. > fwohci0: Link S800, max_rec 4096 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:0d:93:62:62:7c > fwe0: Ethernet address: 02:0d:93:62:62:7c > sbp0: on firewire0 > fwohci0: Initiate bus reset > fwohci0: fwohci_intr_core: BUS reset > fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=2, > CYCLEMASTER mode > pcib4: on cpcht0 > pci4: on pcib4 > gem0: mem 0x80400000-0x805fffff irq 41 at > device 15.0 on pci4 > miibus0: on gem0 > brgphy0: PHY 1 on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, > 1000baseT-FDX, auto > gem0: 10kB RX FIFO, 4kB TX FIFO > gem0: Ethernet address: 00:0d:93:62:62:7c > gem0: [ITHREAD] > pcib5: on cpcht0 > pci5: on pcib5 > atapci0: mem 0x80600000-0x80601fff > irq 0 at device 12.0 on pci5 > atapci0: [ITHREAD] > ata2: on atapci0 > ata2: [ITHREAD] > ata3: on atapci0 > ata3: [ITHREAD] > ata4: on atapci0 > ata4: [ITHREAD] > ata5: on atapci0 > ata5: [ITHREAD] > atapci1: at device 12.1 on pci5 > atapci1: unable to map interrupt > device_attach: atapci1 attach returned 6 > sc0: on nexus0 > sc0: Unknown<16 virtual consoles, flags=0x300> > Timecounter "decrementer" frequency 33333333 Hz quality 0 > Timecounters tick every 10.000 msec > firewire0: 1 nodes, maxhop<= 0 cable IRM irm(0) (me) > firewire0: bus manager 0 > usbus0: 12Mbps Full Speed USB v1.0 > usbus1: 12Mbps Full Speed USB v1.0 > ugen0.1: at usbus0 > uhub0: on usbus0 > ugen1.1: at usbus1 > uhub1: on usbus1 > usbus2: 12Mbps Full Speed USB v1.0 > usbus3: 12Mbps Full Speed USB v1.0 > ugen2.1: at usbus2 > uhub2: on usbus2 > ugen3.1: at usbus3 > uhub3: on usbus3 > usbus4: 480Mbps High Speed USB v2.0 > ugen4.1: at usbus4 > uhub4: on usbus4 > uhub0: 2 ports with 2 removable, self powered > acd0: DVDR at ata0-master UDMA66 > uhub1: 2 ports with 2 removable, self powered > ad0: 152627MB at ata2-master UDMA100 SATA > 1.5Gb/s > uhub2: 3 ports with 3 removable, self powered > uhub3: 2 ports with 2 removable, self powered > uhub4: 5 ports with 5 removable, self powered > ugen4.2: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x0000 > SMP: AP CPU #1 launched > Root mount waiting for: usbus4 > umass0:1:0:-1: Attached to scbus1d > a0 at umass-sim0 bus 0 scbus1 target 0 lun 0 > da0:< 2090E 5.00> Removable Direct Access SCSI-2 device > da0: 40.000MB/s transfers > da0: 249MB (509952 512 byte sectors: 64H 32S/T 249C) > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) > (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 > (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not present) > Trying to mount root from ufs:/dev/ad0s3 > GEOM_PART: Partition 'ad0s4' not suitable for kernel dumps (wrong type?) > > ugen2.2: at usbus2 > uhub5: > on usbus2 > uhub5: 4 ports with 4 removable, bus powered > ugen2.3: at usbus2 > ukbd0: on usbus2 > kbd1 at ukbd0 > ugen2.4: at usbus2 > ums0: on usbus2 > ums0: 1 buttons and [XY] coordinates ID=0 > gem0: link state changed to DOWN > gem0: link state changed to UP > gem0: link state changed to DOWN > gem0: link state changed to UP From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 21:53:56 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D579C106564A; Sat, 27 Feb 2010 21:53:56 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6DE1A8FC14; Sat, 27 Feb 2010 21:53:56 +0000 (UTC) Received: by vws14 with SMTP id 14so565240vws.13 for ; Sat, 27 Feb 2010 13:53:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=ZiaAIDNUVYvpQxe+/a118tnAt8cXdgkEamyGuJCm+lg=; b=c7wbVQA465TRJdKyw4QRf9MQEA+kY9meV6n+rtMmBMVxaCuVnt4klwrjjfcN4D9FNG cYI6eNxhKTqo8ldf18fSt06QzK0KE57g7RoU1/ePV3jGK0vJdSlrH6wyMT7beF/fjfi2 l5vKLK+qsWX2eHC2E2m/ilRb2yeERm6+HCYh4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=v6a2PyBh/4BcbhJiC7B0HBKFCVHilEUpS30eOLM4ruoc/PPAuSTT4m/xksW0VhRuxG 31ve5VxcRI4JrQ165er7pS6Ouzm9W8riSiWEaygYQYe6DtNnQLwn267o3rKdE6+qtMyB nrDsppIa8njn1klcB2j+AZhDd7QLNOPNKV9bU= Received: by 10.220.123.215 with SMTP id q23mr1700389vcr.59.1267307627871; Sat, 27 Feb 2010 13:53:47 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 29sm14188024vws.3.2010.02.27.13.53.45 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 27 Feb 2010 13:53:46 -0800 (PST) Message-ID: <4B899468.6050406@gmail.com> Date: Sat, 27 Feb 2010 16:53:44 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: Andreas Tobler References: <4B8984BF.5080607@oracle.com> <4B898D00.9030706@fgznet.ch> <4B898E84.1040200@gmail.com> <4B89930D.3060800@fgznet.ch> In-Reply-To: <4B89930D.3060800@fgznet.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 21:53:56 -0000 Well, I would boot into OS X, but I nuked everything on the HD :). So it doesn't exist. This is one of the dual 2.0 GHz G5 machines. --Alexander On 2/27/10 4:47 PM, Andreas Tobler wrote: > On 27.02.10 22:28, Alexander Bakst wrote: >> (Switched my non-work e-mail) >> >> Well, I actually am using a fancy apple G5 - I belive it is a power >> 970fx, not sure though. I'm not even sure how to check the current clock >> frequency of my cpu. To be honest, it would be fantastic if it weren't >> running at the highest speed, since I would like to save power. I don't >> know if the kernel will tell the cpu to snooze/nap. > > Hm, it is a 970FX @ 2000.36 MHz. > I'm confused that there is no smu? > Maybe this one lacks the smu. According to the docs I have, the 7,3 > behaves similar to the 7,2. And the 7,2/3 do not have an smu. The cpu > speed is controlled via freq and volt. And some nasty gpio interrupts > @ Nathan :) This bites me currently! > > Can you boot this machine into OS-X and see what it tells you about > the CPU speed? > > Hopefully I'm wrong :) > > Andreas > >> dmesg output: >> >> Copyright (c) 1992-2010 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 >> The Regents of the University of California. All rights reserved. >> FreeBSD is a registered trademark of The FreeBSD Foundation. >> FreeBSD 9.0-CURRENT #314 r204309:204312M: Thu Feb 25 09:28:38 CST 2010 >> >> root@comporellon.tachypleus.net:/usr/obj/powerpc/usr/src/sys/GENERIC >> powerpc >> cpu0: IBM PowerPC 970FX revision 3.0, 2000.36 MHz >> cpu0: Features dc000000 >> cpu0: HID0 511081 >> real memory = 1060220928 (1011 MB) >> avail memory = 986472448 (940 MB) >> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs >> cpu0: dev=ff899e08 (BSP) >> cpu1: dev=ff89b2e8 >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> ispfw: registered firmware >> kbd0 at kbdmux0 >> nexus0: >> cpulist0: on nexus0 >> cpu0: on cpulist0 >> pcr0: on cpu0 >> pcr0: No power mode data in device tree! >> device_attach: pcr0 attach returned 6 >> cpu1: on cpulist0 >> pcr1: on cpu1 >> pcr1: No power mode data in device tree! >> device_attach: pcr1 attach returned 6 >> pcib0: on nexus0 >> pci0: on pcib0 >> vgapci0: port 0x400-0x4ff mem >> 0xa0000000-0xafffffff,0x90000000-0x9000ffff irq 48 at device 16.0 on >> pci0 >> cpcht0: on nexus0 >> pcib1: on cpcht0 >> pci1: on pcib1 >> macio0: mem 0x80000000-0x8007ffff at device >> 7.0 on pci1 >> openpic0: mem 0x40000-0x7ffff on macio0 >> macgpio0: mem 0x50-0x8a on macio0 >> scc0: mem >> 0x13000-0x13fff,0x8400-0x84ff,0x8500-0x85ff,0x8600-0x86ff,0x8700-0x87ff >> irq 22,5,6,23,7,8 on macio0 >> scc0: [FILTER] >> scc0: [FILTER] >> uart0: on scc0 >> uart0: [FILTER] >> uart1: on scc0 >> uart1: [FILTER] >> iichb0: mem 0x18000-0x18fff irq 26 on macio0 >> iichb0: [ITHREAD] >> iicbus0: on iichb0 >> iicbus0: at addr 0x1c0 >> iicbus0: at addr 0x6a >> pmu0: mem 0x16000-0x17fff irq 25 on macio0 >> ohci0: mem 0x80081000-0x80081fff irq 27 >> at device 8.0 on pci1 >> ohci0: [ITHREAD] >> usbus0: on ohci0 >> ohci1: mem 0x80080000-0x80080fff irq 28 >> at device 9.0 on pci1 >> ohci1: [ITHREAD] >> usbus1: on ohci1 >> pcib2: on cpcht0 >> pci2: on pcib2 >> ohci2: mem 0x80702000-0x80702fff irq 63 at >> device 11.0 on pci2 >> ohci2: [ITHREAD] >> usbus2: on ohci2 >> ohci3: mem 0x80701000-0x80701fff irq 63 at >> device 11.1 on pci2 >> ohci3: [ITHREAD] >> usbus3: on ohci3 >> ehci0: mem 0x80700000-0x807000ff irq >> 63 at device 11.2 on pci2 >> ehci0: [ITHREAD] >> usbus4: EHCI version 1.0 >> usbus4: on ehci0 >> pcib3: on cpcht0 >> pci3: on pcib3 >> ata0: mem 0x80104000-0x80107fff irq 39 at >> device 13.0 on pci3 >> ata0: [ITHREAD] >> fwohci0:<1394 Open Host Controller Interface> mem 0x80100000-0x80100fff >> irq 40 at device 14.0 on pci3 >> fwohci0: [ITHREAD] >> fwohci0: OHCI version 1.0 (ROM=0) >> fwohci0: No. of Isochronous channels is 8. >> fwohci0: EUI64 00:0d:93:ff:fe:62:62:7c >> fwohci0: invalid speed 7 (fixed to 3). >> fwohci0: Phy 1394a available S800, 3 ports. >> fwohci0: Link S800, max_rec 4096 bytes. >> firewire0: on fwohci0 >> fwe0: on firewire0 >> if_fwe0: Fake Ethernet address: 02:0d:93:62:62:7c >> fwe0: Ethernet address: 02:0d:93:62:62:7c >> sbp0: on firewire0 >> fwohci0: Initiate bus reset >> fwohci0: fwohci_intr_core: BUS reset >> fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=2, >> CYCLEMASTER mode >> pcib4: on cpcht0 >> pci4: on pcib4 >> gem0: mem 0x80400000-0x805fffff irq 41 at >> device 15.0 on pci4 >> miibus0: on gem0 >> brgphy0: PHY 1 on miibus0 >> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, >> 1000baseT-FDX, auto >> gem0: 10kB RX FIFO, 4kB TX FIFO >> gem0: Ethernet address: 00:0d:93:62:62:7c >> gem0: [ITHREAD] >> pcib5: on cpcht0 >> pci5: on pcib5 >> atapci0: mem 0x80600000-0x80601fff >> irq 0 at device 12.0 on pci5 >> atapci0: [ITHREAD] >> ata2: on atapci0 >> ata2: [ITHREAD] >> ata3: on atapci0 >> ata3: [ITHREAD] >> ata4: on atapci0 >> ata4: [ITHREAD] >> ata5: on atapci0 >> ata5: [ITHREAD] >> atapci1: at device 12.1 on pci5 >> atapci1: unable to map interrupt >> device_attach: atapci1 attach returned 6 >> sc0: on nexus0 >> sc0: Unknown<16 virtual consoles, flags=0x300> >> Timecounter "decrementer" frequency 33333333 Hz quality 0 >> Timecounters tick every 10.000 msec >> firewire0: 1 nodes, maxhop<= 0 cable IRM irm(0) (me) >> firewire0: bus manager 0 >> usbus0: 12Mbps Full Speed USB v1.0 >> usbus1: 12Mbps Full Speed USB v1.0 >> ugen0.1: at usbus0 >> uhub0: on usbus0 >> ugen1.1: at usbus1 >> uhub1: on usbus1 >> usbus2: 12Mbps Full Speed USB v1.0 >> usbus3: 12Mbps Full Speed USB v1.0 >> ugen2.1: at usbus2 >> uhub2: on usbus2 >> ugen3.1: at usbus3 >> uhub3: on usbus3 >> usbus4: 480Mbps High Speed USB v2.0 >> ugen4.1: at usbus4 >> uhub4: on usbus4 >> uhub0: 2 ports with 2 removable, self powered >> acd0: DVDR at ata0-master UDMA66 >> uhub1: 2 ports with 2 removable, self powered >> ad0: 152627MB at ata2-master UDMA100 SATA >> 1.5Gb/s >> uhub2: 3 ports with 3 removable, self powered >> uhub3: 2 ports with 2 removable, self powered >> uhub4: 5 ports with 5 removable, self powered >> ugen4.2: at usbus4 >> umass0: on >> usbus4 >> umass0: SCSI over Bulk-Only; quirks = 0x0000 >> SMP: AP CPU #1 launched >> Root mount waiting for: usbus4 >> umass0:1:0:-1: Attached to scbus1d >> a0 at umass-sim0 bus 0 scbus1 target 0 lun 0 >> da0:< 2090E 5.00> Removable Direct Access SCSI-2 device >> da0: 40.000MB/s transfers >> da0: 249MB (509952 512 byte sectors: 64H 32S/T 249C) >> (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 >> (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not >> present) >> (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 >> (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not >> present) >> (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 >> (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not >> present) >> (da0:umass-sim0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0 0 0 >> (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:3a,0 (Medium not >> present) >> Trying to mount root from ufs:/dev/ad0s3 >> GEOM_PART: Partition 'ad0s4' not suitable for kernel dumps (wrong type?) >> >> ugen2.2: at usbus2 >> uhub5: >> on usbus2 >> uhub5: 4 ports with 4 removable, bus powered >> ugen2.3: at usbus2 >> ukbd0: on usbus2 >> kbd1 at ukbd0 >> ugen2.4: at usbus2 >> ums0: on usbus2 >> ums0: 1 buttons and [XY] coordinates ID=0 >> gem0: link state changed to DOWN >> gem0: link state changed to UP >> gem0: link state changed to DOWN >> gem0: link state changed to UP > > From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 22:08:00 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C80A2106564A for ; Sat, 27 Feb 2010 22:08:00 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from argol.doit.wisc.edu (argol.doit.wisc.edu [144.92.197.212]) by mx1.freebsd.org (Postfix) with ESMTP id 99EFE8FC0C for ; Sat, 27 Feb 2010 22:08:00 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII; format=flowed Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) id <0KYI00I00THBET00@smtpauth3.wiscmail.wisc.edu> for freebsd-ppc@freebsd.org; Sat, 27 Feb 2010 16:07:59 -0600 (CST) Received: from comporellon.tachypleus.net (adsl-76-233-146-74.dsl.mdsnwi.sbcglobal.net [76.233.146.74]) by smtpauth3.wiscmail.wisc.edu (Sun Java(tm) System Messaging Server 7u2-7.05 32bit (built Jul 30 2009)) with ESMTPSA id <0KYI00962THANG60@smtpauth3.wiscmail.wisc.edu>; Sat, 27 Feb 2010 16:07:59 -0600 (CST) Date: Sat, 27 Feb 2010 16:07:57 -0600 From: Nathan Whitehorn In-reply-to: <4B89930D.3060800@fgznet.ch> To: Andreas Tobler Message-id: <4B8997BD.5080601@freebsd.org> X-Spam-Report: AuthenticatedSender=yes, SenderIP=76.233.146.74 X-Spam-PmxInfo: Server=avs-14, Version=5.5.5.374460, Antispam-Engine: 2.7.1.369594, Antispam-Data: 2010.2.27.215134, SenderIP=76.233.146.74 References: <4B8984BF.5080607@oracle.com> <4B898D00.9030706@fgznet.ch> <4B898E84.1040200@gmail.com> <4B89930D.3060800@fgznet.ch> User-Agent: Thunderbird 2.0.0.23 (X11/20100206) Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 22:08:00 -0000 Andreas Tobler wrote: > On 27.02.10 22:28, Alexander Bakst wrote: >> (Switched my non-work e-mail) >> >> Well, I actually am using a fancy apple G5 - I belive it is a power >> 970fx, not sure though. I'm not even sure how to check the current clock >> frequency of my cpu. To be honest, it would be fantastic if it weren't >> running at the highest speed, since I would like to save power. I don't >> know if the kernel will tell the cpu to snooze/nap. > > Hm, it is a 970FX @ 2000.36 MHz. > I'm confused that there is no smu? > Maybe this one lacks the smu. According to the docs I have, the 7,3 > behaves similar to the 7,2. And the 7,2/3 do not have an smu. The cpu > speed is controlled via freq and volt. And some nasty gpio interrupts > @ Nathan :) This bites me currently! > > Can you boot this machine into OS-X and see what it tells you about > the CPU speed? > > Hopefully I'm wrong :) The CPU speed is only low if you break into OF at boot. If you just let it autoboot on PowerMac 7,2 and 7,3 (and RackMac 3,1), it has the correct value. Unfortunately, Andreas is right that your machine is SMU-free, and so there is no fan control at the moment. I believe he is working on fixing that, and, if you are feeling ambitious, you could try working together. It should be fairly straightforward, and your other options, unfortunately, are waiting or falling back to Debian. -Nathan From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 22:44:09 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84BFD1065670; Sat, 27 Feb 2010 22:44:09 +0000 (UTC) (envelope-from andreast-list@fgznet.ch) Received: from smtp.fgznet.ch (mail.fgznet.ch [81.92.96.47]) by mx1.freebsd.org (Postfix) with ESMTP id 1F1328FC16; Sat, 27 Feb 2010 22:44:08 +0000 (UTC) Received: from deuterium.andreas.nets (dhclient-91-190-8-131.flashcable.ch [91.190.8.131]) by smtp.fgznet.ch (8.13.8/8.13.8/Submit_SMTPAUTH) with ESMTP id o1RMi5MR008409; Sat, 27 Feb 2010 23:44:06 +0100 (CET) (envelope-from andreast-list@fgznet.ch) Message-ID: <4B89A035.6060807@fgznet.ch> Date: Sat, 27 Feb 2010 23:44:05 +0100 From: Andreas Tobler User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.7) Gecko/20100111 Lightning/1.0b1 Thunderbird/3.0.1 MIME-Version: 1.0 To: Nathan Whitehorn References: <4B8984BF.5080607@oracle.com> <4B898D00.9030706@fgznet.ch> <4B898E84.1040200@gmail.com> <4B89930D.3060800@fgznet.ch> <4B8997BD.5080601@freebsd.org> In-Reply-To: <4B8997BD.5080601@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.64 on 81.92.96.47 Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 22:44:09 -0000 On 27.02.10 23:07, Nathan Whitehorn wrote: > Andreas Tobler wrote: >> On 27.02.10 22:28, Alexander Bakst wrote: >>> (Switched my non-work e-mail) >>> >>> Well, I actually am using a fancy apple G5 - I belive it is a power >>> 970fx, not sure though. I'm not even sure how to check the current clock >>> frequency of my cpu. To be honest, it would be fantastic if it weren't >>> running at the highest speed, since I would like to save power. I don't >>> know if the kernel will tell the cpu to snooze/nap. >> >> Hm, it is a 970FX @ 2000.36 MHz. >> I'm confused that there is no smu? >> Maybe this one lacks the smu. According to the docs I have, the 7,3 >> behaves similar to the 7,2. And the 7,2/3 do not have an smu. The cpu >> speed is controlled via freq and volt. And some nasty gpio interrupts >> @ Nathan :) This bites me currently! >> >> Can you boot this machine into OS-X and see what it tells you about >> the CPU speed? >> >> Hopefully I'm wrong :) > The CPU speed is only low if you break into OF at boot. If you just let > it autoboot on PowerMac 7,2 and 7,3 (and RackMac 3,1), it has the > correct value. Hm, for my understanding, how can I boot w/o OF into netboot mode? IOW, my CPU speed is always wrong while doing so. > Unfortunately, Andreas is right that your machine is > SMU-free, and so there is no fan control at the moment. I believe he is > working on fixing that, and, if you are feeling ambitious, you could try > working together. It should be fairly straightforward, and your other > options, unfortunately, are waiting or falling back to Debian. I currently work on a cpufreq driver for these 'cranky' PowerMac7,2/3,RackMac3.1. And I suffer some gpio understanding. The fan control will take some more time since I need some i2c drivers first. Andreas From owner-freebsd-ppc@FreeBSD.ORG Sat Feb 27 22:44:55 2010 Return-Path: Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18DFE106566B; Sat, 27 Feb 2010 22:44:55 +0000 (UTC) (envelope-from alexander.bakst@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 570BA8FC13; Sat, 27 Feb 2010 22:44:53 +0000 (UTC) Received: by vws14 with SMTP id 14so575620vws.13 for ; Sat, 27 Feb 2010 14:44:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=SjHaEsJlOt7derFtpRPRggjuOe3BzeuTUtqCCUgfWBU=; b=K433SbzWuawz/zwbL03vzIHt7PWdGBn2r7dICYlPMr1OrR6Anzm6uAOlHSz46OjivB urMHR8T2GVQo9mMcw4hCNKOspBhzBway3WJwGgYNKK7fV/Yj6HpEBYfcSBcCwdEjm/le 1ATjSox49+xYKZB8/559Nx0t6nbvAy+j8L7OU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=oiGG4GLX3FuI5NJDqe1T45wZQcfNfT+ODHHssDuWtu12sjuD19SfICP9N8hH4oqWJc PyT7ZSIgLWoVLAnhYOjWsh4JxZs5mqbPG3udSQJMKxKeoBhS+Bh/mnLDxpc4k/DXfC1z 5Aqklz5jrHVY+PsQdquxSCGmRhMI31PaMMi/M= Received: by 10.220.48.22 with SMTP id p22mr1709742vcf.93.1267310682283; Sat, 27 Feb 2010 14:44:42 -0800 (PST) Received: from Faptop.local (c-66-31-201-186.hsd1.ma.comcast.net [66.31.201.186]) by mx.google.com with ESMTPS id 40sm14546328vws.2.2010.02.27.14.44.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 27 Feb 2010 14:44:41 -0800 (PST) Message-ID: <4B89A057.3090309@gmail.com> Date: Sat, 27 Feb 2010 17:44:39 -0500 From: Alexander Bakst User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.8) Gecko/20100216 Thunderbird/3.0.2 MIME-Version: 1.0 To: Nathan Whitehorn References: <4B8984BF.5080607@oracle.com> <4B898D00.9030706@fgznet.ch> <4B898E84.1040200@gmail.com> <4B89930D.3060800@fgznet.ch> <4B8997BD.5080601@freebsd.org> In-Reply-To: <4B8997BD.5080601@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ppc@freebsd.org Subject: Re: Fan/Power controls X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.5 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 Feb 2010 22:44:55 -0000 Sure - Andreas, I'd be willing to help in some capacity - though I'm more or unless unfamiliar with the power970...and the freebsd kernel, for that matter. --Alexander On 2/27/10 5:07 PM, Nathan Whitehorn wrote: > Andreas Tobler wrote: >> On 27.02.10 22:28, Alexander Bakst wrote: >>> (Switched my non-work e-mail) >>> >>> Well, I actually am using a fancy apple G5 - I belive it is a power >>> 970fx, not sure though. I'm not even sure how to check the current >>> clock >>> frequency of my cpu. To be honest, it would be fantastic if it weren't >>> running at the highest speed, since I would like to save power. I don't >>> know if the kernel will tell the cpu to snooze/nap. >> >> Hm, it is a 970FX @ 2000.36 MHz. >> I'm confused that there is no smu? >> Maybe this one lacks the smu. According to the docs I have, the 7,3 >> behaves similar to the 7,2. And the 7,2/3 do not have an smu. The cpu >> speed is controlled via freq and volt. And some nasty gpio interrupts >> @ Nathan :) This bites me currently! >> >> Can you boot this machine into OS-X and see what it tells you about >> the CPU speed? >> >> Hopefully I'm wrong :) > The CPU speed is only low if you break into OF at boot. If you just > let it autoboot on PowerMac 7,2 and 7,3 (and RackMac 3,1), it has the > correct value. Unfortunately, Andreas is right that your machine is > SMU-free, and so there is no fan control at the moment. I believe he > is working on fixing that, and, if you are feeling ambitious, you > could try working together. It should be fairly straightforward, and > your other options, unfortunately, are waiting or falling back to Debian. > -Nathan