At 05:21 AM 7/03/2007, you wrote:

>Hellen,
>
> Thanks for your support. I switched thread because I think the error
>"Lock manager out of room" was a consequence of "SCH_validate" error.
>I apologize and remain in this thread.
>
> You gave me a good hint to solve the problem, as I found the
>SCH_validate error in two different servers I have.
>
>Server A:
>Pentium III - 300 MHz - 256 MBytes
>Fedora Core 2
>Kernel 2.6.5-1.358 #1
>NPTL 0.61
>FirebirdSS-1.5.2.4731-0
>
>Server B:
>Pentium IV - 3.0 GHz - 1 GByte.
>Debian Etch
>Kernel 2.6.18-4-686 #1 SMP
>NPTL 2.3.6
>firebird2-super-server 1.5.3.4870-12
>
> Clearly, the first one is the case you pointed at, so I'll install
>.nptl.rpm packages in Server A
>
> For Server B, I'll ask again the Debian Firebird mantainer if his
>package is NTPL or not.

If it is not, then you can disable NPTL threading
on the machine via a setenv - see the
installation notes for Linux in the release notes
(Fb 1.5.x or Fb 2) for how to do that on
Linux. You'll need to ask whether that's valid for Debian.

> In the case it is not

>¿ Should installing the Classic Server package solves the problem ?

Yes. Classic doesn't thread connections, so it
is neutral about whether it runs in an NPTL or a pthreads environment.

> ¿ Does using a single processor kernel (not
> SMP) to avoid hyperthreading help ?

Superserver should be ok where there are multiple
physical CPUs. It won't use multiple CPUs but
(according to folklore) it shouldn't display the
kind of problems you get on Windows with multiple
CPUs. But, from your specs, it looks as though you have only one CPU.

HT is another thing again: it has been known to
cause problems on Windows-based SS because the
thread-switching doesn't seem to obey CPU
affinity settings *on some hardware*. You need
to ask on the Debian forums whether there is any
such history with Debian and your motherboard model.

To kill HT you need to disable it at motherboard level.

./heLen