The culprit here may be co-related to the so called
'hacker' kernels (2.1.x). These 'hacker' kernels are
a kind of pre-alpha, alpha and beta releases and not
designed for production use. As far as I know, the
Linux naming scheme for

     version.release.modification

is that if release is an odd number, it's a 'hacker'
kernel, while the 'user' kernels have an even number
in the release (the high modification level is also
another indication for a 'hacker' kernel). This
applies to all Linux distributions with not a single
exception (at least to my knowledge). Although a
Linux distribution will always contain a regular
kernel, there is also a hacker kernel as well and the
re-compilation of an individual kernel is also not
too uncommon in this world.
Perhaps it's also a good idea to look in the Linux
lists and newsgroups, maybe there will be a fix of
this problem available sooner than expected.

So it might be a workaround to talk with the people
running these 'hacker' kernels to re-boot and use a
'regular' kernel for ADSM tasks.

However, what does ADSM development think about the
'fact', that a client can cause server problems. Even
though Linux isn't officially supported, this might
be of public interest ...

Best regards

Andreas Peikert, Systems Programmer
   aMaDEUS Data Processing GmbH
   P.O. Box,   D-85424 Erding,   Germany
   Fon: +49 (0)8122 43-5805
   Fax: +49 (0)8122 43-3260
   email: apeikert AT amadeus DOT net

<* save a megabyte - do you really have to file this note *>