From owner-freebsd-ppc@freebsd.org Mon May 2 13:32:41 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F4E3B297AD for ; Mon, 2 May 2016 13:32:41 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2D8AE1EA1 for ; Mon, 2 May 2016 13:32:41 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u42DWInp065749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Mon, 2 May 2016 13:32:30 GMT (envelope-from swills@FreeBSD.org) To: FreeBSD PowerPC ML From: Steve Wills Subject: wired memory leak at r298785 Message-ID: <572756DF.1010809@FreeBSD.org> Date: Mon, 2 May 2016 09:32:15 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Mon, 02 May 2016 13:32:33 +0000 (UTC) X-Spam-Status: No, score=2.8 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2016 13:32:41 -0000 Hi, Just did my monthly update and r298785 seems to be leaking wired memory rather rapidly. My system has 8gb of RAM and the amount of wired memory just goes up and up continuously. It takes about 12 hours before it exhausts all the RAM and sort of locks up (though shutdown still works). I also made one other change to the system at the same time as updating, which was to add another disk and configure it using ZFS. Perhaps this is a ZFS on PowerPC64 issue? My amd64 box running the same rev of CURRENT doesn't have the issue. Anyone have any ideas on this issue? Thanks, Steve From owner-freebsd-ppc@freebsd.org Mon May 2 18:19:35 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EC81B2AAFD for ; Mon, 2 May 2016 18:19:35 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-155.reflexion.net [208.70.211.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E15341EBC for ; Mon, 2 May 2016 18:19:34 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 8618 invoked from network); 2 May 2016 18:19:56 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 2 May 2016 18:19:56 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.90.3) with SMTP; Mon, 02 May 2016 14:19:27 -0400 (EDT) Received: (qmail 5261 invoked from network); 2 May 2016 18:19:26 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with SMTP; 2 May 2016 18:19:26 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-76-115-7-162.hsd1.or.comcast.net [76.115.7.162]) by iron2.pdx.net (Postfix) with ESMTPSA id E98781C43D6; Mon, 2 May 2016 11:19:23 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: RE: wired memory leak at r298785 [-r298793 comparison, no ZFS use] Message-Id: <3618C937-DBD5-4EAC-8425-D8BD438FE019@dsl-only.net> Date: Mon, 2 May 2016 11:19:26 -0700 To: Steve Wills , FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2016 18:19:35 -0000 I updated a powerpc64 to -r298793 Yesterday (Sunday). It has been up for = a little over 18 hours but sitting idle. No ZFS use, just UFS. 16 GBytes = of RAM. top reports 724M Wired. (Also: 5716K Active, 532M Inact, 215M Buf, 14G Free.) > # uname -apKU > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #33 r298793M: Sun = May 1 07:40:17 PDT 2016 = root@FBSDG5C0:/usr/obj/xtoolchain/powerpc.powerpc64/usr/src/sys/GENERIC64v= tsc-NODEBUG powerpc powerpc64 1100106 1100106 > # uptime > 11:09AM up 18:01, 2 users, load averages: 0.16, 0.17, 0.16 =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Tue May 3 00:56:08 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 418A8B2BC7D; Tue, 3 May 2016 00:56:08 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DDDB11B2; Tue, 3 May 2016 00:56:07 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u430twvQ074316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 3 May 2016 00:56:04 GMT (envelope-from swills@FreeBSD.org) Subject: Re: wired memory leak at r298785 To: FreeBSD PowerPC ML , freebsd-current@freebsd.org References: <572756DF.1010809@FreeBSD.org> From: Steve Wills Cc: scottl@FreeBSD.org, Warner Losh Message-ID: <5727F71E.20101@FreeBSD.org> Date: Mon, 2 May 2016 20:55:58 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <572756DF.1010809@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Tue, 03 May 2016 00:56:04 +0000 (UTC) X-Spam-Status: No, score=2.8 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 00:56:08 -0000 Hi, On 05/ 2/16 09:32 AM, Steve Wills wrote: > Hi, > > Just did my monthly update and r298785 seems to be leaking wired memory > rather rapidly. My system has 8gb of RAM and the amount of wired memory > just goes up and up continuously. It takes about 12 hours before it > exhausts all the RAM and sort of locks up (though shutdown still works). > > I also made one other change to the system at the same time as updating, > which was to add another disk and configure it using ZFS. Perhaps this > is a ZFS on PowerPC64 issue? My amd64 box running the same rev of > CURRENT doesn't have the issue. > I've rebooted the box and started repeatedly logging the output of vmstat -m. It seems to show CAM CCB using a lot of memory and growing rather rapidly. For example, here's a few lines of diff output: - CAM CCB 91418 182836K - 187149 2048 + CAM CCB 447070 894140K - 900292 2048 from two samples that are 60 minutes apart. The box is isn't terribly busy, it's just running the monitoring daemons running (snmpd, collectd), whatever web requests are hitting it (very few if any), this logging process, and my shell, etc. Could this be related to recent changes in CURRENT? Copying Scott and Warner in case they have comments on this since I'm told they have been active in this area recently. Thanks, Steve From owner-freebsd-ppc@freebsd.org Tue May 3 03:24:13 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8087CB2BAB6 for ; Tue, 3 May 2016 03:24:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FB8E1CE4 for ; Tue, 3 May 2016 03:24:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-ig0-x232.google.com with SMTP id u10so103994077igr.1 for ; Mon, 02 May 2016 20:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=pQBnEn1LQpkBztPlW/MyUBfUvX8drJ9PVvfgvpJPoxI=; b=wPNER6xrHaijGyTPbcJeCN9zjrpIJYRinTA5aa25ms9tVXRvSt6Hbfe29FDTfbJiRE 234RK0k0bwBiY7uPATN2oAJe21SZ7NqhmZkBC2YEhod+1+GGSYeiAOuVtC890ErkWcIg yXew21eF7OBSwofQPNBlmsxWXSBZn112Twk/czIK9F7G7DY73py8hhQ/J7JAosbYxT1A XfGcqM50xCw37YqBHtfAPEKzcKRYzGdTW2hmgfCexw7p9Ui36GWvtMMc0MskLV8j7a2N mn3d41yKNTM9MDdXgCWMME4IsGnVQTY/sv+JsONJxfahwYhv2j5hVxBlsTeoro4avUep kK/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=pQBnEn1LQpkBztPlW/MyUBfUvX8drJ9PVvfgvpJPoxI=; b=BYGSp3LGJhuYu9iSD2AizfBqU4YZEawsV0TK5yEE94N/1KGWvoVy5k3ZBSefdf16DI EbfDikK61l2nP4eIkKVwcj3OV7kAtypizlYMftkIgbjgb3JB2cBPyw79ybZALcOardUK PxxRxP96i+4lLaWhqK5mFq3olnhPBPlHYVKIywL4jmyQfxNamGS3pNMwzPJ5uMdG2WFY HEDSumm4ES6pnoN7GW9HfolC8H+7ddbu3IdkaFespmLR2zw3YBp20sCP/5ZwnP4lHuJO /WKOBr6Rh933jbK+8J81NdGuMyQScRwLBTqHuxMjPJt/ZCrLYcgcG5AF8fRah2NyuuTI rQoQ== X-Gm-Message-State: AOPr4FXgyENEv7nddXvMsVqMLsCLMwnYjx22z3+tPhRTKpGqxsB+M5SA2yicECYBlZhRJBfB2fzf6CQfgTGN9A== MIME-Version: 1.0 X-Received: by 10.50.32.102 with SMTP id h6mr23676945igi.16.1462245852205; Mon, 02 May 2016 20:24:12 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.75.68 with HTTP; Mon, 2 May 2016 20:24:12 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <5727F71E.20101@FreeBSD.org> References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> Date: Mon, 2 May 2016 21:24:12 -0600 X-Google-Sender-Auth: l5icnEmHYaEw9yRZzPTHdihg5Jo Message-ID: Subject: Re: wired memory leak at r298785 From: Warner Losh To: Steve Wills Cc: FreeBSD PowerPC ML , FreeBSD Current , Scott Long Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 03:24:13 -0000 On Mon, May 2, 2016 at 6:55 PM, Steve Wills wrote: > Hi, > > On 05/ 2/16 09:32 AM, Steve Wills wrote: > > Hi, > > > > Just did my monthly update and r298785 seems to be leaking wired memory > > rather rapidly. My system has 8gb of RAM and the amount of wired memory > > just goes up and up continuously. It takes about 12 hours before it > > exhausts all the RAM and sort of locks up (though shutdown still works). > > > > I also made one other change to the system at the same time as updating, > > which was to add another disk and configure it using ZFS. Perhaps this > > is a ZFS on PowerPC64 issue? My amd64 box running the same rev of > > CURRENT doesn't have the issue. > > > > I've rebooted the box and started repeatedly logging the output of > vmstat -m. It seems to show CAM CCB using a lot of memory and growing > rather rapidly. For example, here's a few lines of diff output: > > - CAM CCB 91418 182836K - 187149 2048 > + CAM CCB 447070 894140K - 900292 2048 > > from two samples that are 60 minutes apart. > > The box is isn't terribly busy, it's just running the monitoring daemons > running (snmpd, collectd), whatever web requests are hitting it (very > few if any), this logging process, and my shell, etc. > > Could this be related to recent changes in CURRENT? > > Copying Scott and Warner in case they have comments on this since I'm > told they have been active in this area recently. > I've been looking into it. I'm not sure what's up since I don't see it in production. I'll give it a bump in priority though. Warner From owner-freebsd-ppc@freebsd.org Tue May 3 06:03:04 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E2F5B2B737; Tue, 3 May 2016 06:03:04 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EEA881EC9; Tue, 3 May 2016 06:03:03 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u4362oK1093461 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 3 May 2016 06:02:56 GMT (envelope-from swills@FreeBSD.org) Subject: Re: wired memory leak at r298785 To: Warner Losh References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> Cc: FreeBSD PowerPC ML , FreeBSD Current , Scott Long From: Steve Wills Message-ID: <57283F05.80305@FreeBSD.org> Date: Tue, 3 May 2016 02:02:45 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Tue, 03 May 2016 06:02:58 +0000 (UTC) X-Spam-Status: No, score=2.8 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 06:03:04 -0000 On 05/ 2/16 11:24 PM, Warner Losh wrote: > > > On Mon, May 2, 2016 at 6:55 PM, Steve Wills > wrote: > > Hi, > > On 05/ 2/16 09:32 AM, Steve Wills wrote: > > Hi, > > > > Just did my monthly update and r298785 seems to be leaking wired > memory > > rather rapidly. My system has 8gb of RAM and the amount of wired > memory > > just goes up and up continuously. It takes about 12 hours before it > > exhausts all the RAM and sort of locks up (though shutdown still > works). > > > > I also made one other change to the system at the same time as > updating, > > which was to add another disk and configure it using ZFS. Perhaps this > > is a ZFS on PowerPC64 issue? My amd64 box running the same rev of > > CURRENT doesn't have the issue. > > > > I've rebooted the box and started repeatedly logging the output of > vmstat -m. It seems to show CAM CCB using a lot of memory and growing > rather rapidly. For example, here's a few lines of diff output: > > - CAM CCB 91418 182836K - 187149 2048 > + CAM CCB 447070 894140K - 900292 2048 > > from two samples that are 60 minutes apart. > > The box is isn't terribly busy, it's just running the monitoring daemons > running (snmpd, collectd), whatever web requests are hitting it (very > few if any), this logging process, and my shell, etc. > > Could this be related to recent changes in CURRENT? > > Copying Scott and Warner in case they have comments on this since I'm > told they have been active in this area recently. > > > I've been looking into it. I'm not sure what's up since I don't see it > in production. I'll give it a bump in priority though. > Thanks! I did notice that killing bsnmpd drastically slowed the rate of growth, but didn't completely eliminate it. Steve From owner-freebsd-ppc@freebsd.org Tue May 3 06:24:38 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BEB0AB2BD71; Tue, 3 May 2016 06:24:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x244.google.com (mail-pa0-x244.google.com [IPv6:2607:f8b0:400e:c03::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 90E5E1E41; Tue, 3 May 2016 06:24:38 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x244.google.com with SMTP id yl2so678346pac.1; Mon, 02 May 2016 23:24:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=0pEk6l6lOKfFPx4ye2AdzlcGLEQd6UxrBrnMWYYVdmM=; b=D3z5dt4TA8fEqe/hDZ6qBywFMXGwrMfs9cMthuscRpT5iHPa36n8nNVnikVczBwsyv yb3ZLhe7CvZp0qNF/WKS4dYgb1hI8goNrpaRlmNHMnQWeB9KNRvMPCSnlUh1UiT88XZr cnyb8f2uxByxLDJ8fGS8oxuvKdvD/9f5zitQda8rlCYuiZP4raoo7oE3blOcbcZS2N/j bQw00Z1C7xzzTRi9tUf+H15uQHJUGxLFFC0jvs1nGiEREhIjQr+x3cEU7AWdX/qYxeOJ mIKVD+hbzaCerOayV9y0CdZDYED4DLx52CaeWp5HTMNVG6pLWW7425j7QxLEpXNCtRh2 szag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=0pEk6l6lOKfFPx4ye2AdzlcGLEQd6UxrBrnMWYYVdmM=; b=ZTksoRQBbVIIGPKkTty6D5XRYZ/u6CvVulIiN+WrueEideWp8aR6R7JpgVdk1uvUDm 5xTuqlhS/cYscqvAM5ImotLftxr7sEP4iRp1tPl90f8Sd33lWlxkXOUZOWAMkErZ+rKK Z2KTvGCcRFbsPaUcU2BCIcUdVZQSK5B8R4XPsRat0XeUDdAl+8Pa8vI0Dmt3wdHFuaST DcBnz/RZtoJ3sKvXAsw2yjyEfNZC52rIMMRcZrvxcAoHUPJsphLv8Dp0hv9S/ZcKxRDD hWgzTwAMgUOElRhNBcIuxVotmaZ4D2Mz2rvH+qttYrqFugqO5F8YMCFl4HKVPhD1fqH+ zqcQ== X-Gm-Message-State: AOPr4FU7OvijzRgvomq5FPTN+VgaNnJWYDuxMsOAKNFIeIh1GNGRW7ByeHd2NYuBOT2JCA== X-Received: by 10.66.90.136 with SMTP id bw8mr1013807pab.52.1462256678263; Mon, 02 May 2016 23:24:38 -0700 (PDT) Received: from raichu ([2604:4080:1102:0:ca60:ff:fe9d:3963]) by smtp.gmail.com with ESMTPSA id c25sm2531533pfd.67.2016.05.02.23.24.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 May 2016 23:24:37 -0700 (PDT) Sender: Mark Johnston Date: Mon, 2 May 2016 23:20:31 -0700 From: Mark Johnston To: Steve Wills Cc: FreeBSD PowerPC ML , freebsd-current@freebsd.org, scottl@FreeBSD.org, Warner Losh Subject: Re: wired memory leak at r298785 Message-ID: <20160503062031.GA2209@raichu> References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5727F71E.20101@FreeBSD.org> User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 06:24:38 -0000 On Mon, May 02, 2016 at 08:55:58PM -0400, Steve Wills wrote: > Hi, > > On 05/ 2/16 09:32 AM, Steve Wills wrote: > > Hi, > > > > Just did my monthly update and r298785 seems to be leaking wired memory > > rather rapidly. My system has 8gb of RAM and the amount of wired memory > > just goes up and up continuously. It takes about 12 hours before it > > exhausts all the RAM and sort of locks up (though shutdown still works). > > > > I also made one other change to the system at the same time as updating, > > which was to add another disk and configure it using ZFS. Perhaps this > > is a ZFS on PowerPC64 issue? My amd64 box running the same rev of > > CURRENT doesn't have the issue. > > > > I've rebooted the box and started repeatedly logging the output of > vmstat -m. It seems to show CAM CCB using a lot of memory and growing > rather rapidly. For example, here's a few lines of diff output: > > - CAM CCB 91418 182836K - 187149 2048 > + CAM CCB 447070 894140K - 900292 2048 > > from two samples that are 60 minutes apart. > > The box is isn't terribly busy, it's just running the monitoring daemons > running (snmpd, collectd), whatever web requests are hitting it (very > few if any), this logging process, and my shell, etc. This was causing problems on one of my amd64 systems, so it's not specific to powerpc64. It turns out to be due to r298004: the CCB allocated in cam_periph_devctl_notify() never gets freed. The patch below seems to fix it. It's possible to trace CCB allocations/frees using dtrace, which makes many of these sorts of problems trivial to find. Running # dtrace -n 'dtmalloc::CAM_CCB: {printf("%s", execname); stack();}' and examining the output showed that hald was frequently allocating CCBs at cam_periph_error+0x48f, but never freeing them. This corresponds to the allocation in cam_periph_devctl_notify(). diff --git a/sys/cam/cam_periph.c b/sys/cam/cam_periph.c index 85b2ff9..1f7be4f 100644 --- a/sys/cam/cam_periph.c +++ b/sys/cam/cam_periph.c @@ -1876,6 +1876,7 @@ cam_periph_devctl_notify(union ccb *ccb) if (cgd->ccb_h.status == CAM_REQ_CMP) sbuf_bcat(&sb, cgd->serial_num, cgd->serial_num_len); + xpt_free_ccb((union ccb *)cgd); } sbuf_printf(&sb, "\" "); sbuf_printf(&sb, "cam_status=\"0x%x\" ", ccb->ccb_h.status); From owner-freebsd-ppc@freebsd.org Tue May 3 14:33:40 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9AB04B2AEEC for ; Tue, 3 May 2016 14:33:40 +0000 (UTC) (envelope-from scott4long@yahoo.com) Received: from nm7-vm5.bullet.mail.gq1.yahoo.com (nm7-vm5.bullet.mail.gq1.yahoo.com [98.136.218.212]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 670201B08 for ; Tue, 3 May 2016 14:33:40 +0000 (UTC) (envelope-from scott4long@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1462285674; bh=hpQw02F8Rp2eNUp77U0oes0TxrsLqTk3NgAqeON/HPk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject; b=LNDsgRVTxbwjRrgOCG2/OEZ/RCTu/aFJMFQ7vxJOfBgPYDUEtVNZDc4nKqQgCqkUMpTovDUmu0jMiERR6xiyXDkA/HL2eYSDcCyLXJhgnyaaqVOcQRe1+ww12IOmNn9SZm2iGVaEf4q1pO/YXBDJWD9s7E1mei9cSIh498xi0l4ksFloRSAnP69YNYKMr6lH83+ioaPI6DXXjq2Bn+T9dLIH2epgm+QWMKgMbrPePnRq7pT01HG7O3NRLOoalZr3AkEltxAVJgtu/wzXLN7Vj+Icer9M1qYKLBHzmwjQsWduHWslMg+G2vWPq+oip30pkvRPBHhBLjHLUx/v1QMVVQ== Received: from [98.137.12.55] by nm7.bullet.mail.gq1.yahoo.com with NNFMP; 03 May 2016 14:27:54 -0000 Received: from [98.136.164.77] by tm15.bullet.mail.gq1.yahoo.com with NNFMP; 03 May 2016 14:27:54 -0000 Received: from [127.0.0.1] by smtp239.mail.gq1.yahoo.com with NNFMP; 03 May 2016 14:27:54 -0000 X-Yahoo-Newman-Id: 909627.77454.bm@smtp239.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 9WGsZOEVM1lAFTvJu7Bl5wvimwbGTVj4LvA7rZwMC2h4Ikm NASAfpR3xv784xxMw7EZRXNjO6dJVmqu7nOX4pbI0qpbdqd8UA8kFXIwackR MAQVUs6oRNVFRHXoZh5roPicu7PR_anyk1nFgpxZDmDr30A1xuJq5OLTiJQL PXZvdRzQSBY4cvpLKKOxuw6xEDZQY_sD3PZBxK53vixHPnmDCW2rjo.IkMd7 soTcmiVbFhg_WatBfI0YCQ1UNM.l4wCDRJUp9VWpH33M0kYQgVl1._3ESx6f sifIs0DC.PZKn8eHRMUUXJ.zSQX90S7pftWoBWMSZaZbkXiJakrJojWB.OuG HN.DJ0Rf8lExqi.LtZ0J.pjhYIW2sGN1rCrFHfxTwEjgnYk.udb0BSkwtvUG 9THRvFYb8icQ55gAAXOWeaZWjKo8mjy5AbYYLoLbfhhHDsaGQLI.pIP.vvdO 5r_VQyDiwZ1oPTxhZ8HgTRKbIrkcdBs51DSnTefwyLpuKoUWAyR6HPezwxga F8YOdszU2Lgp2JNZoRqSV7SIfGgJc6N_j_IQ1zO4- X-Yahoo-SMTP: clhABp.swBB7fs.LwIJpv3jkWgo2NU8- Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: wired memory leak at r298785 From: Scott Long In-Reply-To: <20160503062031.GA2209@raichu> Date: Tue, 3 May 2016 08:27:52 -0600 Cc: Steve Wills , FreeBSD PowerPC ML , freebsd-current@freebsd.org, scottl@FreeBSD.org, Warner Losh Content-Transfer-Encoding: quoted-printable Message-Id: References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> <20160503062031.GA2209@raichu> To: Mark Johnston X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 14:33:40 -0000 > On May 3, 2016, at 12:20 AM, Mark Johnston wrote: >=20 > On Mon, May 02, 2016 at 08:55:58PM -0400, Steve Wills wrote: >> Hi, >>=20 >> On 05/ 2/16 09:32 AM, Steve Wills wrote: >>> Hi, >>>=20 >>> Just did my monthly update and r298785 seems to be leaking wired = memory >>> rather rapidly. My system has 8gb of RAM and the amount of wired = memory >>> just goes up and up continuously. It takes about 12 hours before it >>> exhausts all the RAM and sort of locks up (though shutdown still = works). >>>=20 >>> I also made one other change to the system at the same time as = updating, >>> which was to add another disk and configure it using ZFS. Perhaps = this >>> is a ZFS on PowerPC64 issue? My amd64 box running the same rev of >>> CURRENT doesn't have the issue. >>>=20 >>=20 >> I've rebooted the box and started repeatedly logging the output of >> vmstat -m. It seems to show CAM CCB using a lot of memory and growing >> rather rapidly. For example, here's a few lines of diff output: >>=20 >> - CAM CCB 91418 182836K - 187149 2048 >> + CAM CCB 447070 894140K - 900292 2048 >>=20 >> from two samples that are 60 minutes apart. >>=20 >> The box is isn't terribly busy, it's just running the monitoring = daemons >> running (snmpd, collectd), whatever web requests are hitting it (very >> few if any), this logging process, and my shell, etc. >=20 > This was causing problems on one of my amd64 systems, so it's not > specific to powerpc64. It turns out to be due to r298004: the CCB > allocated in cam_periph_devctl_notify() never gets freed. The patch > below seems to fix it. Thanks Mark, that looks like the right fix. I=E2=80=99ll put it in = today. Scott From owner-freebsd-ppc@freebsd.org Tue May 3 18:20:55 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43A8FB2A819 for ; Tue, 3 May 2016 18:20:55 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B2B50115C; Tue, 3 May 2016 18:20:54 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id u43IKkIs073121 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 May 2016 20:20:47 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id u43IKkMg073118; Tue, 3 May 2016 20:20:46 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Tue, 3 May 2016 20:20:46 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Scott Long cc: Mark Johnston , Steve Wills , FreeBSD PowerPC ML , freebsd-current@freebsd.org, scottl@FreeBSD.org, Warner Losh Subject: Re: wired memory leak at r298785 In-Reply-To: Message-ID: References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> <20160503062031.GA2209@raichu> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED, AWL autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 18:20:55 -0000 On Tue, 3 May 2016 08:27-0600, Scott Long wrote: > > > On May 3, 2016, at 12:20 AM, Mark Johnston wrote: > > > > On Mon, May 02, 2016 at 08:55:58PM -0400, Steve Wills wrote: > >> Hi, > >> > >> On 05/ 2/16 09:32 AM, Steve Wills wrote: > >>> Hi, > >>> > >>> Just did my monthly update and r298785 seems to be leaking wired memory > >>> rather rapidly. My system has 8gb of RAM and the amount of wired memory > >>> just goes up and up continuously. It takes about 12 hours before it > >>> exhausts all the RAM and sort of locks up (though shutdown still works). > >>> > >>> I also made one other change to the system at the same time as updating, > >>> which was to add another disk and configure it using ZFS. Perhaps this > >>> is a ZFS on PowerPC64 issue? My amd64 box running the same rev of > >>> CURRENT doesn't have the issue. > >>> > >> > >> I've rebooted the box and started repeatedly logging the output of > >> vmstat -m. It seems to show CAM CCB using a lot of memory and growing > >> rather rapidly. For example, here's a few lines of diff output: > >> > >> - CAM CCB 91418 182836K - 187149 2048 > >> + CAM CCB 447070 894140K - 900292 2048 > >> > >> from two samples that are 60 minutes apart. > >> > >> The box is isn't terribly busy, it's just running the monitoring daemons > >> running (snmpd, collectd), whatever web requests are hitting it (very > >> few if any), this logging process, and my shell, etc. > > > > This was causing problems on one of my amd64 systems, so it's not > > specific to powerpc64. It turns out to be due to r298004: the CCB > > allocated in cam_periph_devctl_notify() never gets freed. The patch > > below seems to fix it. > > Thanks Mark, that looks like the right fix. I’ll put it in today. > > Scott A few of my stable/10 systems simple froze due to this bug. Would it be possible for the kernel to detect when it's running low on (kernel) memory, or when it's completely out of (kernel) memory, and call on panic() only to limp away for a day or so before rebooting again? -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-ppc@freebsd.org Tue May 3 21:17:29 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20C26B2CB48 for ; Tue, 3 May 2016 21:17:29 +0000 (UTC) (envelope-from dsharoh@gmail.com) Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com [IPv6:2a00:1450:4010:c07::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9EFAB1686 for ; Tue, 3 May 2016 21:17:28 +0000 (UTC) (envelope-from dsharoh@gmail.com) Received: by mail-lf0-x244.google.com with SMTP id m101so3430947lfi.1 for ; Tue, 03 May 2016 14:17:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=rO7XAwqBXX080jNS+D7PuyROdbNhUSBvO5J7ixTUh1g=; b=RbKnQ3WXZrAISwJvCDg0IZQgDeP+icfyKh9R+NJszppCx6CKRQEbrL45twLQ9TZvIF 9CW+PGeXR65gUmH9RqXGX9otFuDk5ihgGOJAKYmCM+9BhPnBzgcYsSZPhSIqVFUCHbBe qGQ4CmCkc/V2IW5sWTvCPhgJSO/TrBMIufttuaB3O3ph0ebph6vzATXoB30DBYIcpNfm dSc0G2V0yv/8HuLobyoZ3eJP9R209FZZk45u7maVMw8rYbAhwZbu3sRo7LTGZbya9XZN 6RssjhxERcIWO5qV1+ipXcljAYmcm3ll25R8XmAcQQMF8xNed81l/WnVFEcW0fur8NvM SC/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=rO7XAwqBXX080jNS+D7PuyROdbNhUSBvO5J7ixTUh1g=; b=gLpX+PBQY/lLuI4bv9OaV+JQusQgNchHtbLxGWLEh5+fJuZPmnx01zQHWTCdBw7tt8 lC40TNlS+rg9hMdK+mtL8SZV2V765EuDtOHvnRw7xcChm/QKrW23pezfPk8PZUlKc7YG oinN/Q8fB6lRBkFKPOvcDFCGLvH2VVyPVT4TDHHgV05/4CzdN/xJNgLqOIB7M2jDvxue T52sO9+nHGVvUTGf/5sauC6y28TXAOxVxs+aDeNHT1AKIatMjpBoGGHm0D8NWs4uBKnG s6naaBrPJEQvjKbTTpEsz/q9neSn3BW0XvmkJ5xdgbfxulfmsNCLfdwS+4Z48vaUI0qF qdlA== X-Gm-Message-State: AOPr4FVMBcVuYL63sFgejh54c8R3OE+hdljYAIIojHUwxe7rz+HkUGebum+4YcH6O/aJrzUgF5d7ZTYlBt89FA== X-Received: by 10.112.169.105 with SMTP id ad9mr2241641lbc.123.1462310246959; Tue, 03 May 2016 14:17:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.15.230 with HTTP; Tue, 3 May 2016 14:17:07 -0700 (PDT) From: Daniel Sharoh Date: Tue, 3 May 2016 23:17:07 +0200 Message-ID: Subject: Backlight control on iMAC G5 8,1 To: freebsd-ppc@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 21:17:29 -0000 Hi everyone, Sorry if this is the wrong place for my question. Maybe I should ask on IRC instead? I'm new to freeBSD and BSD in general, but am a long time linux user. I have an iMac G5 that I've installed freeBSD 10.2 on, and it's generally working well. This system uses the ATI Radeon 9600 graphics card, and I am using the ati-ums driver with X because the the regular ati driver won't build on my system (it says intel only when I try to build it). One major problem I have with my system is that I cannot control the backlight level. For example 'sysctl dev.backlight.0.level=0' has no effect. 'xset dpms force off' blanks the screen but leaves the backlight on When I query sysctl dev.backlight I get dev.backlight.0.level: 2956 dev.backlight.0.%parent: vgapci0 dev.backlight.0.%pnpinfo: dev.backlight.0.%location: dev.backlight.0.%driver: backlight dev.backlight.0.%desc: PowerBook backlight for nVidia graphics dev.backlight.%parent: Which seems suspicious because I don't have an nVidia graphics card. I see atibl.c in /usr/src/sys/powerpc/powermac/, but that module isn't available in /boot/kernel/ or /usr/src/sys/modules Does anyone have any idea what I could do? I haven't been able to find any information, probably because I'm new to BSD and ask the wrong questions. Another unrelated problem is that I don't have any control over the hardware volume using 'mixer.' Programs like mplayer can use software control, as in this post https://lists.freebsd.org/pipermail/freebsd-ppc/2014-January/006796.html, but it would be nice to have hardware control. Is this currently achievable on the iMac 8,2? Thanks! Dan -- Sent from my teletype From owner-freebsd-ppc@freebsd.org Tue May 3 23:51:51 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06E04B2CE15; Tue, 3 May 2016 23:51:51 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C91FD1196; Tue, 3 May 2016 23:51:50 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pa0-x233.google.com with SMTP id xk12so16626878pac.0; Tue, 03 May 2016 16:51:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=z9iqTq74JjDoS7Mn0Oo/C5o8GndD+qh/Rg05tWKWAtw=; b=txnBi/kzJ3zRReROp97fVX02V01P0kXn9K6Ll6wMB+5P/qrMUpOjzgh8L29QwmotFY Cq7AvO9Y2lyWusm2V1gTe7AANz+VYpwk3D/+PBCh5yHpiFrr/+fIFZqT9vJEJcvy9TLo P4V+iq/3Jzpq7Ye1zSLunCHSMO147M3QkI0RhziD1Vl0yZtVq8USYAcqp14K7v1n7uxB 1EQAUcdDX6L0ELY9Vu/A+JSG6fMBnBDwQG+t2N9vhrd9htP+jlprGpazNuZDuIyiKyJ3 h/aaJ4piixfO4yOIr2jR6iwctbMc+68cShpCfwhsnttOzj8W/8e/Wk3U65iztdmMygjk JNVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=z9iqTq74JjDoS7Mn0Oo/C5o8GndD+qh/Rg05tWKWAtw=; b=kLWrCaCGigbYpVKThM1zfOrWog2rjODbIa5XLL/h5e5TThRGqI4e1ex/oncW1sI2iV zJ37ahNHf+hH1k7IFV6di4Wm3K5kHYrDPPPDUjxp9SAgMrihpAIOpcMjQhM9tQVkdrhI c1gxJSXkHIex7Z5eWyd+rW/sxpuv33D6FkZtUVrAdCUO/qhtbjVGOQM/dYQGD7Yc7Bxn VVtAWMhlL+g+wst4QXBKntFCoLMqFaV8tOXQGM/tJYznKnnXUx5whP8fdFdVFHbI8oc9 tVhmS93SvK1L1wGzViItkP6gWdwxOXimJK7hSBKBcOuw2ipkcL93XBPIlFVNRx4KbzOu Qpvw== X-Gm-Message-State: AOPr4FXL9fvtPzlL306PbU88BvcET2gId5yw6lKvSNu9VLGcyxVmKCH9+6gm3KnbKkjGsA== X-Received: by 10.66.79.197 with SMTP id l5mr7697431pax.61.1462319510207; Tue, 03 May 2016 16:51:50 -0700 (PDT) Received: from wkstn-mjohnston.west.isilon.com (c-76-104-201-218.hsd1.wa.comcast.net. [76.104.201.218]) by smtp.gmail.com with ESMTPSA id u2sm783463pfi.26.2016.05.03.16.51.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 May 2016 16:51:49 -0700 (PDT) Sender: Mark Johnston Date: Tue, 3 May 2016 16:55:29 -0700 From: Mark Johnston To: Trond =?iso-8859-1?Q?Endrest=F8l?= Cc: Scott Long , Steve Wills , FreeBSD PowerPC ML , freebsd-current@freebsd.org, scottl@FreeBSD.org, Warner Losh Subject: Re: wired memory leak at r298785 Message-ID: <20160503235529.GA44671@wkstn-mjohnston.west.isilon.com> References: <572756DF.1010809@FreeBSD.org> <5727F71E.20101@FreeBSD.org> <20160503062031.GA2209@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 23:51:51 -0000 On Tue, May 03, 2016 at 08:20:46PM +0200, Trond Endrestøl wrote: > On Tue, 3 May 2016 08:27-0600, Scott Long wrote: > > > On May 3, 2016, at 12:20 AM, Mark Johnston wrote: > > > This was causing problems on one of my amd64 systems, so it's not > > > specific to powerpc64. It turns out to be due to r298004: the CCB > > > allocated in cam_periph_devctl_notify() never gets freed. The patch > > > below seems to fix it. > > > > Thanks Mark, that looks like the right fix. I’ll put it in today. > > > > Scott > > A few of my stable/10 systems simple froze due to this bug. Would it > be possible for the kernel to detect when it's running low on (kernel) > memory, or when it's completely out of (kernel) memory, and call on > panic() only to limp away for a day or so before rebooting again? I don't know of a mechanism in the kernel that would let you do this. The closest thing I can think of would be a cron job that periodically checks the amount of leaked memory with vmstat -m | awk '/CAM CCB/{print $(NF - 3)}' and triggers a reboot once that value rises above some threshold. From owner-freebsd-ppc@freebsd.org Wed May 4 02:46:23 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6B6FFB2CF95 for ; Wed, 4 May 2016 02:46:23 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4671C1278 for ; Wed, 4 May 2016 02:46:23 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-io0-x231.google.com with SMTP id 190so41748867iow.1 for ; Tue, 03 May 2016 19:46:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=2rUmizf+ALMYzZpMDZ0LOaucgACtLqeo7HTbywepKZE=; b=sX84Mj0YyFzUqi/2dXTSRnlUg03CRcE9XBBxx12mwGIdCyCKORVaK4mZdkj6AVkYmj v0uJpWUbeJE55mZri+NdRE2fH5ObSDx1y7C8o3xSWYyTBLge7/0ll4ijNTWg8TFOzRC0 /eEjVd7IRKUoxSRq5Gm/Qb8SkU6yiRk7Ykh/s9BNFlE8WBdAmaf8vJgeYNx6Pxa8hq4H 0mWE61Sv35j+oyQTIqrN9V/SG1jQG3WIoQ5eA6oH5x7AiizLTu7VYbv48hIz2HtCfYwA oDiEfMdFVTHxvRsoSZ7u+zmsOwqnNUecHJu6i+O8ZSQvTNUrJZhkUuGgKrP3vx41j7hy bVlA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=2rUmizf+ALMYzZpMDZ0LOaucgACtLqeo7HTbywepKZE=; b=b8dfn8zhFgAXWgIAm+o8upf16IYk9RFYAC4Oyh4SH4Su/NKXetC1BLD8qT3QaGaSEK WgkBzOwUKZE290VYfR+rhzXzQqNNVQm79lzM5Yl8bPQ7ccIg+1FmMcqgcwfvLJOCe//L 4HWjklctTaDfP97MkCbpj8DhHpPDKIthJAVTxBJJl0WRYwrxOwZrFM2ajHMrgfTUtJob ZuFwxYNyulaujHpfpowGNisuDVrVhNTXeAFxWZP9c589NctZB/X/iSoBiQZjK6RMdvDC aY2glKOjx6L1jvvv6d7l5xnWHNWFWJkQ0tPswajEQ5C1SFx71gyxgGO3YV/7yDc0C/kc E8AA== X-Gm-Message-State: AOPr4FVYJQy+H77Fu6Ix+ThGKiX/GZnfqwALQkMuL658A3x7bazF1f2xz/6khWueSLN0Mg== X-Received: by 10.107.7.72 with SMTP id 69mr7148108ioh.64.1462329982566; Tue, 03 May 2016 19:46:22 -0700 (PDT) Received: from zhabar.knownspace (c-98-240-160-157.hsd1.mn.comcast.net. [98.240.160.157]) by smtp.gmail.com with ESMTPSA id b9sm852356igv.6.2016.05.03.19.46.21 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 03 May 2016 19:46:22 -0700 (PDT) Date: Tue, 3 May 2016 21:46:20 -0500 From: Justin Hibbits To: Daniel Sharoh Cc: freebsd-ppc@freebsd.org Subject: Re: Backlight control on iMAC G5 8,1 Message-ID: <20160503214620.13191b12@zhabar.knownspace> In-Reply-To: References: X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; powerpc64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2016 02:46:23 -0000 On Tue, 3 May 2016 23:17:07 +0200 Daniel Sharoh wrote: > Hi everyone, > > Sorry if this is the wrong place for my question. Maybe I should ask > on IRC instead? > > I'm new to freeBSD and BSD in general, but am a long time linux user. > I have an iMac G5 that I've installed freeBSD 10.2 on, and it's > generally working well. This system uses the ATI Radeon 9600 graphics > card, and I am using the ati-ums driver with X because the the > regular ati driver won't build on my system (it says intel only when > I try to build it). One major problem I have with my system is that I > cannot control the backlight level. > > For example 'sysctl dev.backlight.0.level=0' has no effect. > 'xset dpms force off' blanks the screen but leaves the backlight on > > When I query sysctl dev.backlight I get > > dev.backlight.0.level: 2956 > dev.backlight.0.%parent: vgapci0 > dev.backlight.0.%pnpinfo: > dev.backlight.0.%location: > dev.backlight.0.%driver: backlight > dev.backlight.0.%desc: PowerBook backlight for nVidia graphics > dev.backlight.%parent: > > Which seems suspicious because I don't have an nVidia graphics card. > > I see atibl.c in /usr/src/sys/powerpc/powermac/, but that module isn't > available in /boot/kernel/ or /usr/src/sys/modules > > Does anyone have any idea what I could do? I haven't been able to > find any information, probably because I'm new to BSD and ask the > wrong questions. > > Another unrelated problem is that I don't have any control over the > hardware volume using 'mixer.' Programs like mplayer can use software > control, as in this post > https://lists.freebsd.org/pipermail/freebsd-ppc/2014-January/006796.html, > but it would be nice to have hardware control. Is this currently > achievable on the iMac 8,2? > > Thanks! > Dan > > Hi Dan, The atibl driver is built into the kernel, I never made it compileable as a module, nor nvbl. There is a bug in stable/10, which I've fixed in head, regarding the backlight drivers. In stable/10, the drivers only check the device type, which I learned later is insufficient, so the drivers now, in head, check the PCI device ID as well, so the driver should work properly for you in head. Regarding the mixer, that driver has not been written yet. Unfortunately most of us who work on powerpc don't have much time lately, or the hardware to test with. I don't know if there's a bug filed for it, but if not, could you file a bug, and also post the output of 'ofwdump -ap' into the bug? - Justin From owner-freebsd-ppc@freebsd.org Wed May 4 03:28:09 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4802DB2CA8C; Wed, 4 May 2016 03:28:09 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E627C10DB; Wed, 4 May 2016 03:28:08 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u443RvcL009185 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 4 May 2016 03:28:04 GMT (envelope-from swills@FreeBSD.org) Subject: Re: svn commit: r413746 - in head: archivers/innoextract archivers/pecl-phk archivers/php55-phar archivers/php56-phar audio/xmms-volnorm benchmarks/smhasher biology/plinkseq chinese/wordpress-zh_CN chi... To: Jan Beich References: <201604211643.u3LGhF6h057956@repo.freebsd.org> <7ffb-9k1q-wny@vfemail.net> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org, "'FreeBSD PowerPC ML'" From: Steve Wills Message-ID: <57296C3D.8090509@FreeBSD.org> Date: Tue, 3 May 2016 23:27:57 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 In-Reply-To: <7ffb-9k1q-wny@vfemail.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Wed, 04 May 2016 03:28:04 +0000 (UTC) X-Spam-Status: No, score=2.8 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2016 03:28:09 -0000 Hi, On 05/ 3/16 12:35 PM, Jan Beich wrote: > > Where I can find error logs? The error logs that this commit was based on are here: http://poudriere.mouf.net/karl/poudriere/data/headpowerpc-default/2016-04-02_20h57m16s/build.html There were a few others that I found were broken after fixing pixman (since it had blocked the attempt to build them), but I think I lost the logs for those with a disk issue so I'll have to wait > Tautological BROKEN messages with stub commit logs do not help > maintainer to analyze, forward upstream or maybe even fix the issue. > This invites bitrot. I'm happy to share the logs, but I didn't want to include the link in the commit message. I welcome any help fixing things. Sorry the messages aren't more specific. > powerpc64 isn't represented on pkg-fallout@. There isn't any cluster hardware currently building this stuff, hopefully we can get some cluster hardware doing this soon. > Can you check r414539 ? Is there a particular port you want me to try to build? If not, I will do the full bulk -a again, but I lost the packages themselves in the previously mentioned disk issue. Luckily I still have the logs. Anyway, last time it took several months for the full build from scratch. That build above was not the full build from scratch, it was an incremental build. And before I do the full bulk build again, I'm going to try to build a few specific things like ruby and gcc6-devel with a different compiler. But if you have specific things you want to test, let me know and I'll try to get them tested, but it will take a little time. Thanks, Steve From owner-freebsd-ppc@freebsd.org Thu May 5 15:38:26 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDE9CB2DDAA for ; Thu, 5 May 2016 15:38:26 +0000 (UTC) (envelope-from andy.silva@snsreports.com) Received: from mailer238.gate85.rs.smtp.com (mailer238.gate85.rs.smtp.com [74.91.85.238]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86F0E16D5 for ; Thu, 5 May 2016 15:38:25 +0000 (UTC) (envelope-from andy.silva@snsreports.com) X-MSFBL: eyJyIjoiZnJlZWJzZC1wcGNAZnJlZWJzZC5vcmciLCJiIjoiNzRfOTFfODVfMjM4 IiwiZyI6IlNuc3RlbGVjb21fZGVkaWNhdGVkX3Bvb2wifQ== Received: from [192.168.80.42] ([192.168.80.42:44491] helo=rs-ord-mta04-2.smtp.com) by rs-ord-mta04-3.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTP id D8/23-13530-8E86B275; Thu, 05 May 2016 15:38:16 +0000 DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1462462696; h=From:Subject:To:Date:MIME-Version:Content-Type; bh=2+9KhEx/aZkFYBWbZR6J+pMHVyqFnvQyfwUKWBlqy0I=; b=SNRk8ODsD1PNduD9N5cO6yxQliRw6U5X5zABpw5ei5fFbh6hwbhs67Zn/gJo91w6 TGAc+e7yy2X3L81o0hAAuPlYQqaEKANULn0kXR6Dr32pxGLqgcI1F+Vb+bbQF/8J qnoX8s7iFiw0LJiyJ8OTL+sdRBwyksuGH6Sw8u750zg=; Received: from [205.250.224.245] ([205.250.224.245:36099] helo=d205-250-224-245.bchsia.telus.net) by rs-ord-mta04-2.smtp.com (envelope-from ) (ecelerity 4.1.0.46749 r(Core:4.1.0.4)) with ESMTPA id 35/D1-22442-8E86B275; Thu, 05 May 2016 15:38:16 +0000 MIME-Version: 1.0 From: "Andy Silva" Reply-To: andy.silva@snsreports.com To: freebsd-ppc@freebsd.org Subject: The Wearable Technology Ecosystem: 2016 - 2030 - Opportunities, Challenges, Strategies, Industry Verticals & Forecasts (Report) X-Mailer: Smart_Send_2_0_138 Date: Thu, 5 May 2016 08:38:06 -0700 Message-ID: <79324288698561164930549@Ankur> X-Report-Abuse: SMTP.com is an email service provider. Our abuse team cares about your feedback. Please contact abuse@smtp.com for further investigation. X-SMTPCOM-Tracking-Number: 7ecf57ba-79dc-401d-862b-af2bbcbee453 X-SMTPCOM-Sender-ID: 6008902 Feedback-ID: 6008902:SMTPCOM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 May 2016 15:38:27 -0000 The Wearable Technology Ecosystem: 2016 - 2030 - Opportunities, Challenges,= Strategies, Industry Verticals and Forecasts Hello=20 Let me offer you the latest SNS Research report to you and your team, " The= Wireless Network Infrastructure Ecosystem: 2016 - 2030 - Macrocell RAN, Sm= all Cells, C-RAN, RRH, DAS, Carrier Wi-Fi, Mobile Core, Backhaul & Fronthau= l " Below is the report highlight and if you like I can send you sample pag= es for your details inside. =20 Our reports are compiled with primary and secondary informations to produce= an overall industry outlook. Report Information: Release Date: May 2016 Number of Pages: 652 Number of Tables and Figures: 219 =20 =20 Report Overview: =20 While wearable technology has been utilized in vertical sectors such as the= military and healthcare for many years, ongoing advances have triggered a = major resurgence of the concept, particularly among the consumer community.= Key enabling technologies including low cost sensors, wireless connectivit= y, active materials and energy have converged to make wearable technology m= ainstream.=20 With the continued miniaturization of enabling technologies, wearable devic= es have hit the mass market in a diverse variety of form factors, ranging f= rom glasses to even jewelry. Driven by the ability to interconnect with key modern trends of healthcare,= fitness, messaging and socialization, the wearable technology ecosystem is= attracting significant levels of interest. Companies as varied as smartph= one OEMs, wireless carriers, health insurers and retailers are circling the= ecosystem alongside tiny startups, all vying for a stake. SNS Research estimates that by 2016, wearable device shipments will surpass= 140 Million and will account for nearly $30 Billion in revenue. The market= is further expected to grow at a CAGR of 30% over the next five years. The "Wearable Technology Ecosystem: 2016 - 2030 - Opportunities, Challenges= , Strategies, Industry Verticals & Forecasts" report presents an in-depth a= ssessment of the wearable technology ecosystem including key market drivers= , challenges, investment potential, consumer & vertical market opportunitie= s, use cases, future roadmap, value chain, case studies, vendor market shar= e and strategies. The report also presents forecasts for wearabledevice shi= pments and revenue from 2015 through to 2030. The forecasts are further seg= mented for 7 device form factor submarkets, 7 vertical markets, 6 regions a= nd 73 countries. The report comes with an associated Excel datasheet suite covering quantita= tive data from all numeric forecasts presented in the report. Key Findings: =20 The report has the following key findings: SNS Research estimates that wearable device shipments will grow at a CAGR o= f 29% between 2016 and 2020. By 2020, wearable devices will represent a mar= ket worth $40 Billion with over 240 Million annual unit shipments. Leading smartphone OEMs, Apple and Samsung, are replicating their success i= n the OS powered smart watch arena with a combined market share of nearly 7= 5%. As wearable device OEMs seek to minimize dependence on hardware sales, new = business models are beginning to emerge, particularly in the enterprise spa= ce. For example, specialist vendors such as Catapult are offering subscript= ion based services to sports teams, which combine wearable sensors, cloud-b= ased software and analytics. SNS Research estimates that wearable devices will help mobile operators dri= ve over $13 Billion in service revenue by the end of 2020, following a CAGR= of nearly 32% between 2016 and 2020. The market is ripe for acquisitions of pure-play wearable technology startu= ps, as competition heats up between consumer and vertical centric OEMs. Topics Covered: =20 The report covers the following topics: Wearable technology ecosystem Market drivers and barriers Enabling technologies and operating systems for wearable devices Standardization and regulation landscape Wearable technology industry roadmap and value chain Assessment of vertical market opportunities and use cases for consumer, hea= lthcare, professional sports, retail & hospitality, military, public safety= and 8 other verticals Case studies of wearable technology deployments Company profiles and strategies of over 440 wearable technology ecosystem p= layers Wearable device vendor market share Prospects of smartphone OEMs and wireless chipset suppliers in the wearable= technology ecosystem Impact of 5G, NB-IoT and LTE Direct on wearable technology Strategic recommendations for enabling technology providers, wearable devic= e OEMs, vertical market players, application developers and mobile operators Market analysis and forecasts from 2016 till 2030 Forecast Segmentation: =20 Market forecasts are provided for each of the following submarkets and the= ir categories: Market forecasts are provided for each of the following submarkets and the= ir categories: Vertical Submarkets Consumer Healthcare Professional Sports Retail & Hospitality Military Public Safety Others Form Factor Submarkets Smart Bands Smart Watches Smart Glasses Smart Clothing Smart Jewelry Heads-up Displays Others Regional Markets Asia Pacific Eastern Europe Latin & Central America Middle East & Africa North America Western Europe Country Markets=20 73 Country level markets: Algeria, Argentina, Australia, Austria, Banglades= h, Belarus, Belgium, Bolivia, Bosnia & Herzegovina, Brazil, Bulgaria, Canad= a, Chile, China, Colombia, Croatia, Czech Republic, Denmark, Ecuador, Egypt= , Finland, France, Germany, Greece, Hong Kong, Hungary, India, Indonesia, I= reland, Israel, Italy, Japan, Kenya, Luxembourg, Malaysia, Mexico, Morocco,= Netherlands, New Zealand, Nigeria, Norway, Pakistan, Paraguay, Peru, Phili= ppines, Poland, Portugal, Qatar, Romania, Russia, Saudi Arabia, Serbia, Sin= gapore, Slovakia, South Africa, South Korea, Spain, Sudan, Sweden, Switzerl= and, Taiwan, Tanzania, Thailand, Tunisia, Turkey, UAE, UK, Ukraine, Uruguay= , USA, Uzbekistan, Venezuela and Vietnam Key Questions Answered: The report provides answers to the following key questions: How big is the wearable technology ecosystem=3F How is the ecosystem evolving by segment and region=3F What will the market size be in 2020 and at what rate will it grow=3F What trends, challenges and barriers are influencing its growth=3F Who are the key wearable device vendors and what are their strategies=3F How much are vertical enterprises investing in wearable devices=3F What opportunities exist for wireless chipset suppliers in the wearable tec= hnology ecosystem=3F How can mobile operators capitalize on the growing popularity of smart watc= hes, fitness bands, smart glasses and other wearable devices=3F Which countries, regions and verticals will see the highest percentage of w= earable device shipments=3F Which sports category will see the highest level of wearable technology int= egration=3F Report Pricing: Single User License: USD 2,500 Company Wide License: USD 3,500 Ordering Process: Please contact Andy Silva on andy.silva@snscommunication.com Provide the following information: 1. Report Title - 2. Report License - (Single User/Company Wide) 3. Name - 4. Email - 5. Job Title - 6. Company - 7. Invoice Address - Please contact me if you have any questions, or wish to purchase a copy. Ta= ble of contents mentioned below for your better inside. I look forward to hearing from you. Kind Regards Andy Silva Marketing Executive Signals and Systems Telecom =20 ___________________________________________________________________________= __________________________________________________________________________ =20 Table of Content =20 Chapter 1 1.1 Executive Summary 1.2 Topics Covered 1.3 Historical Revenue & Forecast Segmentation 1.4 Key Questions Answered 1.5 Key Findings 1.6 Methodology 1.7 Target Audience 1.8 Companies & Organizations Mentioned =20 Chapter 2: An Overview of Wearable Technology 2.1 What is Wearable Technology=3F 2.2 Device Classification 2.2.1 Head-worn Devices 2.2.2 Wrist-worn Devices 2.2.3 Leg and Ankle-worn Devices 2.2.4 Arm, Chest and Neck-worn Devices 2.2.5 Smart Clothing & Jewelry 2.2.6 In-Body Wearables 2.3 Enabling Technologies 2.3.1 MEMS & Sensors 2.3.2 BT-LE (Bluetooth Low Energy) & WiFi 2.3.3 Voice Recognition 2.3.4 Lowed Powered Wireless SoCs 2.3.5 RFID & NFC 2.3.6 GPS & Navigation Technology 2.3.7 Energy Harvesting 2.3.8 Ergonomics & Materials Science 2.3.9 Augmented Reality 2.4 Market Growth Drivers 2.4.1 Proliferation of Smartphones 2.4.2 Advances in Enabling Technologies & Components 2.4.3 Interest from New Market Segments 2.4.4 Human Centric Assistance 2.4.5 Meaningful Analytics & Tracking 2.4.6 Venture Capital, Crowdfunding & Corporate Investments 2.4.7 Endorsement by Major Mobile OEMs 2.5 Market Barriers 2.5.1 High Costs 2.5.2 Power Consumption & Battery Life Issues 2.5.3 Usability & Unusual Styling 2.5.4 Potential Health Issues 2.5.5 Privacy & Security Concerns 2.5.6 Social Acceptance =20 Chapter 3: Vertical Opportunities & Use Cases 3.1 Consumer Markets 3.1.1 Infotainment & Lifestyle 3.1.2 Casual Sports & Fitness 3.1.3 Gaming 3.1.4 Pet Care 3.1.5 Child Care & Entertainment 3.1.6 Helping People with Disabilities 3.1.7 Car Insurance Claims 3.1.8 Accurate & Targeted Marketing 3.2 Healthcare 3.2.1 Remote Patient Monitoring 3.2.2 Assisted Patient Examination 3.2.3 Reducing Healthcare Costs 3.2.4 Optimizing Health Insurance Costs 3.2.5 Enhancing Medical R&D 3.3 Professional Sports 3.3.1 Sports Data Analytics 3.3.2 Enhancing Real-Time Decision Making 3.3.3 Injury Prevention 3.4 Retail & Hospitality 3.4.1 Improving Retail Productivity 3.4.2 Comparing & Contrasting Retail Items 3.4.3 Travel: Personalizing Customer Service 3.4.4 Replacing Hotel Keys and Credit Cards 3.4.5 Augmenting City & Museum Tours 3.5 Military 3.5.1 Enhancing Infantry Tactics: Shooting Without Being Shot 3.5.2 Monitoring Combat Stress & Injuries 3.5.3 Enhancing Situational Awareness in the Battlefield 3.5.4 Enabling Battlefield Mobility 3.5.5 Facilitating Communications with Military Dogs 3.6 Public Safety 3.6.1 Recording Criminal Evidence 3.6.2 Enhancing Situational Awareness & Assets Coordination 3.6.3 Identifying Suspects & Traffic Violators 3.6.4 Monitoring Biophysical Activity for First Responders 3.6.5 Enhancing Fire Fighting Capabilities 3.6.6 Improving Response to Medical Emergencies 3.7 Other Verticals 3.7.1 Construction Industry 3.7.2 Mining Industry 3.7.3 Manufacturing Operations 3.7.4 Logistics & Supply Chain 3.7.5 Financial Services 3.7.6 Security & Authentication 3.7.7 Repair, Inspection & Field Services 3.7.8 Education 3.8 Case Studies 3.8.1 Virgin Atlantic: Improving Airline Customer Services with Wearable Te= chnology 3.8.1.1 Solution & Vendors 3.8.1.2 Applications 3.8.1.3 Feedback from the Field 3.8.2 U.S. Department of Defense: Delivering Tactical Information with Wear= able Technology 3.8.2.1 Solution & Vendors 3.8.2.2 Applications 3.8.2.3 Feedback from the Field 3.8.3 Dubai Police: Catching Speeding Drivers with Google Glass 3.8.3.1 Solution & Vendors 3.8.3.2 Applications 3.8.3.3 Feedback from the Field 3.8.4 Disney: Theme Park Management with Wearable Technology 3.8.4.1 Solution & Vendors 3.8.4.2 Applications 3.8.4.3 Feedback from the Field 3.8.5 AT&T: Connected Healthcare Monitoring for the Elderly 3.8.5.1 Solution & Vendors 3.8.5.2 Applications 3.8.5.3 Feedback from the Field =20 Chapter 4: Industry Roadmap & Value Chain 4.1 Wearable Technology Industry Roadmap 4.1.1 2013 =96 2014: Initial Hype & the Revival of Smart Watches 4.1.2 2015 =96 2016: Convergence of Wrist Worn Wearables 4.1.3 2017 =96 2020 & Beyond: The Augmented Reality & Smart Glasses Era 4.2 The Wearable Technology Value Chain 4.2.1 Wearable Device OEM Ecosystem 4.2.1.1 Vertical Centric OEMs 4.2.1.2 Smartphone, Tablet & Consumer Electronics OEMs 4.2.1.3 Fashion & Watch OEMs 4.2.2 Consumers & Vertical Enterprises 4.2.3 Wireless Carriers & the Connectivity Ecosystem 4.2.4 Applications Ecosystem =20 Chapter 5: Market Analysis & Forecasts 5.1 Global Outlook of Wearable Technology 5.2 Form Factor Segmentation 5.3 Smart Bands 5.4 Smart Watches 5.5 Smart Glasses 5.6 Smart Clothing 5.7 Smart Jewelry 5.8 Heads-up Display Systems 5.9 Others 5.10 Vertical Market Segmentation 5.11 Consumer Wearable Devices 5.12 Healthcare Wearable Devices 5.13 Professional Sports Wearable Devices 5.14 Retail & Hospitality Wearable Devices 5.15 Military Wearable Devices 5.16 Public Safety Wearable Devices 5.17 Wearable Devices in Other Verticals 5.18 Regional Market Segmentation 5.19 Asia Pacific 5.20 North America 5.20.1 Canada 5.20.2 USA 5.21 Western Europe 5.22 Eastern Europe 5.23 Middle East & Africa 5.24 Latin & Central America =20 Chapter 6: Key Market Players 6.1 270 Vision 6.2 3L Labs 6.3 4DForce 6.4 4iii Innovations 6.5 9Solutions 6.6 Abbot Laboratories 6.7 Active Mind Technology 6.8 AcousticSheep 6.9 Adidas 6.10 AirType 6.11 Amazon 6.12 Ambit Networks 6.13 AMD (Advanced Micro Devices) 6.14 Amiigo 6.15 Amulyte 6.16 Apple 6.17 ARA (Applied Research Associates) 6.18 Archos 6.19 ARM Holdings 6.20 ASUS (ASUSTeK Computer) 6.21 Atellani 6.22 Atheer Labs 6.23 Atlas Wearables 6.24 Augmendix 6.25 Avegant 6.26 AVG 6.27 Baidu 6.28 BAE Systems 6.29 Basis Science 6.30 Beddit 6.31 Behavioral Technology Group 6.32 BIA Sport 6.33 Bionym 6.34 Biosensics 6.35 BIT (Blue Infusion Technologies) 6.36 Bitbanger Labs 6.37 BI (GEO Group) 6.38 Blocks Wearables 6.39 bOMDIC 6.40 Bondara (Nagook) 6.41 Boston Scientific Corporation 6.42 BRAGI 6.43 Brilliantservice 6.44 Broadcom 6.45 Breitling 6.46 Brother Industries 6.47 BSX Atheletics 6.48 BTS Bioengineering 6.49 Buhel 6.50 Cambridge Temperature Concepts 6.51 Carre Technologies 6.52 Casio 6.53 Catapult Sports 6.54 Citizen 6.55 Cityzen Sciences 6.56 Codoon 6.57 CommandWear 6.58 CompeGPS 6.59 ConnecteDevice 6.60 Connect America 6.61 Control VR 6.62 Cool Shirt Systems 6.63 Creoir 6.64 CSR 6.65 Cuff 6.66 Cyberdyne 6.67 DAQRI 6.68 Dell 6.69 DK Tek Innovations 6.70 DorsaVi (ASX) 6.71 Dreamtrap Commercials 6.72 EB Sport Group 6.73 EdanSafe 6.74 Ekso Bionics 6.75 Electric Foxy 6.76 Emotiv Systems 6.77 Enjoy S.R.L 6.78 Epson (Seiko Epson Corporation) 6.79 Everfind 6.80 EuroTech 6.81 Evena Medical 6.82 Exelis 6.83 EyeTap 6.84 FashionTEQ 6.85 Fat Shark 6.86 Fatigue Science 6.87 Filip Technologies 6.88 Finis 6.89 FitBark 6.90 Fitbit 6.91 Fitbug 6.92 FitLinxx 6.93 Flyfit 6.94 Flextronics 6.95 Force Impact Technologies 6.96 Fossil 6.97 Foxtel 6.98 Freescale Semiconductor 6.99 Free Wavz 6.100 Fujitsu 6.101 Garmin 6.102 GEAK (Shanda Group) 6.103 Gemalto 6.104 General Dynamics Mission Systems 6.105 GestureLogic 6.106 Geopalz 6.107 Ginger.io 6.108 GlassUp 6.109 Glofaster 6.110 GN Store Nord 6.111 GoPro 6.112 Google 6.113 GOQii 6.114 Gucci 6.115 Guess 6.116 HealBe 6.117 HereO 6.118 Hollywog 6.119 Honeywell International 6.120 Hovding 6.121 House of Horology 6.122 HP 6.123 HTC 6.124 Huawei 6.125 i4C Innovations 6.126 i.am+ 6.127 ICEdot 6.128 ICON Health and Fitness 6.129 iHealth Lab 6.130 iLOC Technologies 6.131 i=92m SpA 6.132 Imagination Technologies 6.133 Imec 6.134 Immerz 6.135 Ineda Systems 6.136 Innovega 6.137 InfinitEye 6.138 Intel Corporation 6.139 InteraXon 6.140 InvenSense 6.141 Iotera 6.142 iRhythm 6.143 Instabeat 6.144 Iron Will Innovations 6.145 Jawbone 6.146 Jaybird 6.147 Johnson & Johnson 6.148 Kairos Watches 6.149 Kapture 6.150 Ki Performance 6.151 Kiwi Wearable Technologies 6.152 KMS Solutions 6.153 KoruLab 6.154 Kreyos 6.155 Kronoz 6.156 L-3 Communications 6.157 Lark Technologies 6.158 Laster Technologies 6.159 LeapFrog Enterprises 6.160 Lechal 6.161 LG Electronics 6.162 LifeBEAM 6.163 LifeLogger Technologies Corporation 6.164 Limmex 6.165 Liquid Image 6.166 Lockheed Martin 6.167 LogBar 6.168 LOSTnFOUND 6.169 Lumafit 6.170 Lumo BodyTech 6.171 Lumus 6.172 Luxottica 6.173 Mad Apparel 6.174 Magellan (MiTAC Digital Corporation) 6.175 Martian Watches 6.176 Matilde 6.177 MC10 6.178 McLear 6.179 MediaTek 6.180 Medtronic 6.181 Melon 6.182 META 6.183 Meta Watch 6.184 Microsoft 6.185 MindStream 6.186 Mio Global 6.187 Misfit Wearables 6.188 Moff 6.189 MonDevices 6.190 Moov 6.191 Moticon 6.192 Motion Fitness 6.193 Motorola Mobility/Lenovo 6.194 Motorola Solutions 6.195 Movable 6.196 Mozilla Corporation 6.197 Mutalink 6.198 Mutewatch 6.199 Myontec 6.200 Narrative 6.201 Neptune 6.202 Netatmo 6.203 NeuroPro 6.204 NeuroSky 6.205 New Balance 6.206 Nike 6.207 Nintendo 6.208 Nissan 6.209 Nixie Labs 6.210 Nixon 6.211 Nod 6.212 Notch Interfaces 6.213 NTT DoCoMo 6.214 Nuance 6.215 Nuubo 6.216 NVIDIA 6.217 NZN Labs 6.218 O-Synce 6.219 Oculus VR (Facebook) 6.220 ODG (Osterhout Design Group) 6.221 Olive Labs 6.222 Omate 6.223 OMG Life 6.224 Omron 6.225 OMsignal 6.226 Opening Ceremony 6.227 Optalert 6.228 Optinvent 6.229 OrCam Technologies 6.230 OriginGPS 6.231 Orion Labs (OnBeep) 6.232 Orpyx Medical Technologies 6.233 Owlet Baby Care 6.234 Panasonic 6.235 Pebble 6.236 Perceptive Devices 6.237 Performance Sports Group 6.238 Perpetua Power Source Technologies 6.239 PFO Tech 6.240 PHTL (PH Technical Labs) 6.241 Pivothead 6.242 Pixie Scientific 6.243 Phyode 6.244 Plantronics 6.245 Playtabase 6.246 PNI Sensor Corporation 6.247 Polar Electro 6.248 Pragmasystems 6.249 Preventice 6.250 Proteus Digital Health 6.251 PUSH Design Solutions 6.252 Qardio 6.253 Qualcomm 6.254 Ralph Lauren Corporation 6.255 Raytheon 6.256 Razer 6.257 Recon Instruments 6.258 Reebok International 6.259 Rest Devices 6.260 Revolutionary Tracker 6.261 RHLvision Technologies 6.262 Ringblingz 6.263 Ringly 6.264 RSL Steeper Group 6.265 Rufus Labs 6.266 S3 ID 6.267 Salesforce.com 6.268 Salutron 6.269 Samsung Electronics 6.270 Sarvint Technologies 6.271 Secret Labs 6.272 Seiko 6.273 SenseCore 6.274 Sensegiz Technologies 6.275 Sensible Baby 6.276 Sensoplex 6.277 Sensoria 6.278 Senso Solutions 6.279 Sentimoto 6.280 Seraphim Sense 6.281 Shimmer 6.282 ShotTracker 6.283 Si14 6.284 Sigmo 6.285 Skully Systems 6.286 Smart Device (SmartQ) 6.287 Smarty Destination Technology 6.288 Smarty Ring 6.289 SMI (SensoMotoric Instruments) 6.290 SMS Audio 6.291 Snaptracs 6.292 Somaxis 6.293 Sonitus Medical 6.294 Sonostar 6.295 Sony Mobile Communications 6.296 Sotera Wireless 6.297 Soundbrenner 6.298 SparkPeople 6.299 Spire 6.300 Sports Beat 6.301 SpotNSave 6.302 Spree Wearables 6.303 Sproutling 6.304 Sqord 6.305 Stalker Radar (Applied Concepts) 6.306 STATSports 6.307 Striiv 6.308 STMicroelectronics 6.309 SunFriend Corporation 6.310 Suunto 6.311 sWaP 6.312 Swatch Group 6.313 T.Ware 6.314 Tag Heuer 6.315 Tarsier 6.316 TASER International 6.317 TCL Communication 6.318 Technical Illusions 6.319 Thalmic Labs 6.320 Theatro 6.321 TI (Texas Instruments) 6.322 Timex Group 6.323 TLink Golf 6.324 TN Games 6.325 Tobii Technology 6.326 TomTom 6.327 Tomoon Technology 6.328 Touch Bionics 6.329 TrackingPoint 6.330 Two Tin Cans 6.331 U-blox 6.332 Under Armour 6.333 Uno 6.334 Valencell 6.335 Validic (Motivation Science) 6.336 Vancive Medical Technologies (Avery Dennison) 6.337 Vergence Labs 6.338 Victoria=92s Secret 6.339 Vigo 6.340 VSN Mobil 6.341 Vuzix 6.342 Wahoo Fitness 6.343 Wather Enterprises 6.344 We:eX (Wearable Experiments) 6.345 Wearable Intelligence 6.346 Weartrons Labs 6.347 Wellograph 6.348 Whistle 6.349 Withings 6.350 WTS (Wonder Technology Solutions) 6.351 X-Doria (Doria International) 6.352 Xensr 6.353 Xiaomi 6.354 XO Eye Technologies 6.355 XOWi 6.356 Xybermind 6.357 Yingqu Technology 6.358 Zackees 6.359 Zeiss (Carl Zeiss AG) 6.360 Zephyr Technology (Covidien) 6.361 Zepp Labs 6.362 Zinc Software 6.363 Zoll Medical Corporation 6.364 ZTE =20 Chapter 7: Conclusion & Strategic Recommendations 7.1 Wearable Technology Operating Systems: Is there a Dominant Market Leade= r=3F 7.2 LTE Direct & its Impact on Wearable Technology 7.3 How is Wearable Technology Affecting the Wireless Chipsets Ecosystem=3F 7.4 How Big is the Wearable Applications Ecosystem=3F 7.5 Prospects of Standardization & Regulation 7.6 Prospects of Smartphone OEMs in the Wearable Technology Ecosystem 7.7 Wireless Carriers: The Wearable Service Revenue Opportunity 7.8 Vendor Share: Who Leads the Market=3F 7.9 The Rise of Wearable Startups 7.10 Combining Fashion with Technology 7.11 Prospects of Fitness & Sports Centric Wearables 7.12 Recommendations 7.12.1 Enabling Technology Providers 7.12.2 Wearable Device OEMs & Vertical Players 7.12.3 Wearable Application Developers 7.12.4 Wireless Carriers =20 Thank you once again and looking forward to hearing from you. =20 Kind Regards =20 Andy Silva Marketing Executive Signals and Systems Telecom andy.silva@snscommunication.com =20 =20 =20 To unsubscribe send an email with unsubscribe in the subject line to: remov= e@snsreports.com From owner-freebsd-ppc@freebsd.org Fri May 6 11:11:49 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F141B30F65 for ; Fri, 6 May 2016 11:11:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 602D61F6C for ; Fri, 6 May 2016 11:11:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u46BBne2054610 for ; Fri, 6 May 2016 11:11:49 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 209274] No hardware mixer control in PPC Date: Fri, 06 May 2016 11:11:49 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ppc@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 11:11:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D209274 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-ppc@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-ppc@freebsd.org Fri May 6 14:33:27 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0531B31D06 for ; Fri, 6 May 2016 14:33:27 +0000 (UTC) (envelope-from jessie@saleguru.biz) Received: from smtp104.biz.mail.bf1.yahoo.com (smtp104.biz.mail.bf1.yahoo.com [98.139.221.63]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7DD6011BB for ; Fri, 6 May 2016 14:33:26 +0000 (UTC) (envelope-from jessie@saleguru.biz) Received: (qmail 66955 invoked from network); 6 May 2016 14:33:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1462545199; bh=d8vkv2V/fY/hS6Z22woSusSKkiSA0eBNOYbB5KFrCUA=; h=From:To:Subject:Date:Message-ID:MIME-Version:Content-Type; b=eccBKXOnoz8dbp3BL3KXKh/Uq3VkbQdwShWsMnB5P6mtSQdcKuO0No++j2iD0LEWisO/kvUIcNQpiyX9iWn6ahIFAfq/v2YtN0ldgKm/U0NoSMsf9YRte4dnk992pvsse1M/UoZY5SaJvz3f2NOLOqLLoxmYop7LrsIo6b50b4o= X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: lhbXRJwVM1n5u_SF_KSRczC7nHeO3ktcWWlXIUT5x960wQe GwUa_njDmE0jH1Ji5PUNY83apdH.8ymVUxsUUGWN6FwL7kAYDrMP0HsmbHjl Ud5J6lQDrspQd9pH2JsGjG9lBf1uMhsPc.NqjyqSRGq5ZFZryu2XaN6Nzr.c vBHCy5wbRS.Dun9gp6HfrMWl_VnF2SVvB_4a8X_QN_8zYXiUaHwcfWYOeUHY ZHaJsVVdflLjN2q28KHeBweTjqyUYYUNK8V6IPBWHHHbmkx6sHetOkbApZUy Scc4YcWDhVmaSaFy8y7j3ZJiWb.IZ8FiWAOovWx7pK4zdUTEsCJdbjTBm4ja AB6hNYzTh9XAbwfAYqUCDezy2pdCi.X.xRgtSI26LzcNFG9aWWI8IcIlOZJg cqvc2kYwLURvZa60YGidCiEoqJxA4Mqkn2vAEfB7HEC4.zMmz2i6y8C_VwoK n9_Guw8YOLA7XcXmwK9OFpl1YEXY73B2rUxZ5w1Q665SYLyB.LYd.9.yF3z5 20UQk6sydDHPQb8dCY4Ul17Zii4cQTfM4TD_8uJ7R X-Yahoo-SMTP: ANmUFYeswBBG9p9oru6nijCoorcizi8Vj9ALgkNk_BG7528r3k51kEnJsl1q From: "Jessie Richards" To: Subject: Business Proposal Date: Fri, 6 May 2016 20:03:23 +0530 Message-ID: <4e2501d1a7a4$40e09430$c2a1bc90$@saleguru.biz> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 16.0 Thread-Index: AdGnoZrra7xYzqebSvuX+FFLhCFJag== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2016 14:33:27 -0000 Greetings for the day! Hope you are doing great! My name is Jessie Richards and I am a Website Consultant. I found your email account online and would like to discuss some business opportunities with you, which you may find beneficial for your business. In today's Web World, a website plays a vital role in gaining credibility & revenue for your business. We will help you develop an effective website for your business or will redesign your existing business website efficiently to ensure that your website converts more visitors into leads and to get it placed higher in the organic search for a few of the select terms. This is NOT like one of those foreign emails you probably get in your inbox every day. Just to be upfront, we have experienced and skilled SEO and Web Design/Development team, they are committed to perform White Hat SEO activities to bring organic traffic providing business oriented creative design to our client's website. I would just need to know which (if not both) services you're open to checking out information about, either SEO or Web Design/Development. Would you be open to seeing more brief info / quote for what I would like to accomplish? Warm Regards, Jessie Richards Website Consultant Ph: +1 (424) 625-4981 Disclaimer: Thank you for reading this. In the event that you do not wish me to contact you again, simply send an email with unsubscribe as a subject line.