From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Cohorent pool size too small...
Date: Tue, 7 Oct 2014 09:28:46 +0200 [thread overview]
Message-ID: <20141007072846.GA19166@TranscendTheRubicon.alshain.ring0> (raw)
In-Reply-To: <20141006163406.GB3826@solfire>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
On Mon, Oct 06, 2014 at 06:34:06PM +0200, meino.cramer@gmx.de wrote:
<SNIP>
>
> Moin Hinnerk,
> (hopefully have guessed this greet correctly...I am from that
> part of Germany ;)
>
> I have the source of the driver exclusivly compiled for 3.8.13
> as for 3.14.something (cant remember).
> 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...
>
> Is the 3.15.10++ branch free of things like random reboot and
> not powering off?
Moin Meino,
(you've hit dead on spot: is there another "valid" greeting except that one?
;-) )
Right now I don't have a beaglebone black so sadly I can't provide any first
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 natively
most of the time (as it's not a that critical machine). As it's an even more
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 help
immensely if available (that is if the hardware is either supported upstream or
there is a vendor branch testing new kernels). Especially for arm there is much
better support lately.
I find for less used platforms (read: "not-x86/amd64) the newer kernels are
often more stable than "stable" ones because the latter often doesn't
experience much testing.
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 - kernel
builds are very easily cross-compilable).
Good luck/Viel Erfolg,
Hinnerk
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-07 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 13:52 [gentoo-user] Cohorent pool size too small meino.cramer
2014-10-05 14:12 ` [gentoo-user] " walt
2014-10-05 14:54 ` meino.cramer
2014-10-05 17:31 ` walt
2014-10-05 17:44 ` meino.cramer
2014-10-06 8:43 ` Hinnerk van Bruinehsen
2014-10-06 16:34 ` meino.cramer
2014-10-06 18:47 ` thegeezer
2014-10-06 22:30 ` meino.cramer
2014-10-07 7:28 ` Hinnerk van Bruinehsen [this message]
2014-10-07 15:51 ` meino.cramer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141007072846.GA19166@TranscendTheRubicon.alshain.ring0 \
--to=h.v.bruinehsen@fu-berlin.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox