Am Monday 27 October 2008 18:15:19 schrieb Eric Sandeen:
> Martin Steigerwald wrote:
> > A colleague did a kernel update on the inactive backend 1 server from
> > 2.6.21 to 2.6.26 kernel from backports.org, tommorow backend 2 will
> > follow. Let's see whether that solves the issue.
> > Anyway it seems to be a hard to trigger bug and before bugging you with
> > something in kernel 2.6.21, we at least update to the latest
> > backports.org kernel.
> Honestly, I'd try a 2.6.27 kernel if you can, a few more problems were
> fixed there.
Thanks for the hint. backports.org doesn't contain a 2.6.26 and AFAIK lenny
will ship with 2.6.26 as well, thus I'd like to try that one before doing a
backport of 2.6.27 from sid myself. Thus I hope the issue that is triggered
on those servers is fixed with 2.6.26 or some prior kernel since 2.6.21
already. If not, we will consider backporting 2.6.27.
At least on my notebook I didn't have any issues so far with any kernel since
188.8.131.52. But even with TuxOnIce it doesn't have uptimes of 100 days or more,
since I compile a new kernel for it once in a while.
Martin Steigerwald - team(ix) GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90