Re: Why is "Memory split" Kconfig option only for EMBEDDED?

2006-12-14 Thread Norbert Kiesel
On Thu, 2006-12-14 at 14:47 +, Pavel Machek wrote: > Hi! > > > So far all first-hand experiences I heard of were positive (i.e. I did > > not get an emaail from anyone saying: It had a negative effect for me), > > so I propose to apply the patch from Con Kolivas. The wording in the > > descrip

Re: Why is "Memory split" Kconfig option only for EMBEDDED?

2006-12-09 Thread Norbert Kiesel
On Sat, 2006-12-09 at 13:27 +0100, Alejandro Riveira Fernández wrote: > El Wed, 6 Dec 2006 14:10:03 +0100 > Adrian Bunk <[EMAIL PROTECTED]> escribió: > > > On Wed, Dec 06, 2006 at 01:19:08PM +0100, Norbert Kiesel wrote: > > > On Wed, 2006-12-06 at 12:58 +0100, Arja

Re: Why is "Memory split" Kconfig option only for EMBEDDED?

2006-12-06 Thread Norbert Kiesel
On Wed, 2006-12-06 at 13:45 +0100, Arjan van de Ven wrote: > On Wed, 2006-12-06 at 13:19 +0100, Norbert Kiesel wrote: > > On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote: > > > On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote: > > > > Hi, > >

Re: Why is "Memory split" Kconfig option only for EMBEDDED?

2006-12-06 Thread Norbert Kiesel
On Wed, 2006-12-06 at 12:58 +0100, Arjan van de Ven wrote: > On Wed, 2006-12-06 at 12:42 +0100, Norbert Kiesel wrote: > > Hi, > > > > I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would > > be optimal for a machine with exactly 1GB memory (like my c

Why is "Memory split" Kconfig option only for EMBEDDED?

2006-12-06 Thread Norbert Kiesel
Hi, I remember reading on LKML some time ago that using VMSPLIT_3G_OPT would be optimal for a machine with exactly 1GB memory (like my current desktop). Why is that option only prompted for after selecting EMBEDDED (which I normally don't select for desktop machines)? Best, Norbert - To unsub

2.6.13 locks my machine within 1h, 2.6.12.5 works fine (PREEMPT?)

2005-09-04 Thread Norbert Kiesel
Hi, I had 2.6.13 lock my machine three times within a hour each after upgrading to 2.6.13 (last time within 5 minutes). The machine was running 2.6.12.5 (and earlier releases) without any problems, so I'd suspect it's not a hardware issue. Problem is that I don't find any trace of this lockup an