-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
chas williams - CONTRACTOR schrieb:
| try building with SMP and PREEMPT (or !SMP and !PREEMPT).
Strike, that was it. Now it works without these error codes, but not really fast
:-| (see other post I made).
So I have to optimize more here.
First move the
try building with SMP and PREEMPT (or !SMP and !PREEMPT).
In message <[EMAIL PROTECTED]>,Lars Schimmer writes:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA1
>
>Hiho!
>
>chas williams - CONTRACTOR schrieb:
>| tell me a little about your kernel. is it smp? is it preempt?
>
>Uhhh. It was built on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hiho!
chas williams - CONTRACTOR schrieb:
| tell me a little about your kernel. is it smp? is it preempt?
Uhhh. It was built on my own, preempt, yes, smp, noo. Single AMD Sempron 1900+
CPU on ASUS board with via 333 chips.
It was the 2.6.10 kernel sou
On Fri, 2005-03-11 at 13:40 +0100, Lars Schimmer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Lars Schimmer schrieb:
> | Hi!
> |
> | I setup a filserver on debian sarge on 2.6.10 and 1.3.79 and I wanted to
> | try out
> | the memcache option.
> | But after a reboot syslog pronts ou
tell me a little about your kernel. is it smp? is it preempt?
In message <[EMAIL PROTECTED]>,Lars Schimmer writes:
>Mar 11 13:05:30 atlas kernel: <1>Unable to handle kernel NULL pointer
>dereference at virtual address 00c4
>Mar 11 13:05:30 atlas kernel: printing eip:
>Mar 11 13:05:30 atlas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lars Schimmer schrieb:
| Hi!
|
| I setup a filserver on debian sarge on 2.6.10 and 1.3.79 and I wanted to
| try out
| the memcache option.
| But after a reboot syslog pronts out:
| allocation failed: out of vmalloc space - use vmalloc= to increase
| siz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I setup a filserver on debian sarge on 2.6.10 and 1.3.79 and I wanted to try out
the memcache option.
But after a reboot syslog pronts out:
allocation failed: out of vmalloc space - use vmalloc= to increase size.
Mar 11 11:37:21 localhost last messa
