From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (unknown [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8D09B1388E3 for ; Tue, 7 Oct 2014 15:52:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0845DE0BE2; Tue, 7 Oct 2014 15:51:37 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7D698E0BB0 for ; Tue, 7 Oct 2014 15:51:35 +0000 (UTC) Received: from localhost ([84.133.144.248]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MVvi4-1XiFB72DcW-00X2hI for ; Tue, 07 Oct 2014 17:51:33 +0200 Date: Tue, 7 Oct 2014 17:51:32 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Cohorent pool size too small... Message-ID: <20141007155132.GA3826@solfire> References: <20141005135221.GC3856@solfire> <20141005145415.GE3856@solfire> <20141005174403.GF3856@solfire> <20141006084357.GC12584@TranscendTheRubicon.zedat.fu-berlin.de> <20141006163406.GB3826@solfire> <20141007072846.GA19166@TranscendTheRubicon.alshain.ring0> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20141007072846.GA19166@TranscendTheRubicon.alshain.ring0> User-Agent: mutt-ng/devel-r804 (Linux) X-Provags-ID: V03:K0:cRS+MuZvVtJuq8gJyg7duSzmGB02i2yrkicZohyC66bdZYXf0Ne LQGn0x/j492+nORvB1kYNBYMlgmefFLXYc2j/AZnZLpDxmFf+bmNEEmt4b2rYuiQUrZZyYl sV4s1i2fmUNJfKGUEA7W3FC1AuApKVUHmCkGbPciyvTzzA0R8Ql80rBMuxLywbgBqqJ2ITL NquoqL9p5+1rPf7wGkY7Q== X-UI-Out-Filterresults: notjunk:1; X-Archives-Salt: 2c1c93f0-bfd4-4e4a-9532-834159c6bae9 X-Archives-Hash: 975877a8cdbb50b2dca9251f9e7f9618 Hinnerk van Bruinehsen [14-10-07 17:23]: > On Mon, Oct 06, 2014 at 06:34:06PM +0200, meino.cramer@gmx.de wrote: > > >=20 > > Moin Hinnerk,=20 > > (hopefully have guessed this greet correctly...I am from that > > part of Germany ;) > >=20 > > I have the source of the driver exclusivly compiled for 3.8.13 > > as for 3.14.something (cant remember).=20 > > 3.14.x has some other problems (on that embedded platform) like > > not powering off when shutdown, random reboots and such. > > So decided to go back to 3.8.13. > > Yesterday I started updateing (eix-sync and emerge) that Gentoo > > and it ends up in an endless loop (bash update) of configureing > > (damn slow on that mini iron) and compiling - as it looks - > > of a single file. > > After more than 10 hours I CTRL-C that, reupated and now I am > > ...updateing the bash again. > > Sigh. > > Currently "fun" is something else... > >=20 > > Is the 3.15.10++ branch free of things like random reboot and > > not powering off? >=20 > Moin Meino, >=20 > (you've hit dead on spot: is there another "valid" greeting except that o= ne? > ;-) ) >=20 > Right now I don't have a beaglebone black so sadly I can't provide any fi= rst > hand experience. > A 10 hour configure loop definitely sounds fishy to me. I'm running > a (hardened) Gentoo on a Raspberry Pi right now and I do compiling native= ly > most of the time (as it's not a that critical machine). As it's an even m= ore > mini iron I know that it can be time consuming (maybe interesting: bash: = 25 > minutes, 57 seconds for 29 merges). > My rpi runs on a 3.16.3 kernel and my experience is that newer kernels he= lp > immensely if available (that is if the hardware is either supported upstr= eam or > there is a vendor branch testing new kernels). Especially for arm there i= s much > better support lately. > I find for less used platforms (read: "not-x86/amd64) the newer kernels a= re > often more stable than "stable" ones because the latter often doesn't > experience much testing. >=20 > So in the end there aren't many more options than just try it out (kernel > builds are quick luckily because - as you stated in your other reply - ke= rnel > builds are very easily cross-compilable). >=20 > Good luck/Viel Erfolg, >=20 > Hinnerk Moin Hinnerk, (yes, exactly what you have said: "Moin" is the way to go!!! :)) 8))))) The problem with the kernel sources here on the beagle bone side of the street arises not from the kernel sources themselve -- so to speak the Torvaldic parts of Kernaltica -- but more from the parts which were implemented and designed to speak to the hardware itsself. 3.8.x has good "cape" support ("cape": additonal pluggable PCBs)but less good USB and ethernet. 3.14.x has better ethernet and USB but does not switch off the board if shutdown (aka "battery eater") and does random reboots. The GPIOs for the "capes" have to be configured more or less manually with 3.14.x. Now I am experimenting with 3.15.x...we will see. The whole process from "I want" to "I have" is time consuming, because each time a lot of sources are downloaded and my DSL is=20 "old school" ;) Thanks a lot for your help! Viele Dank f=FCr Deine Hilfe! :) Meino