> We upgraded one of our servers (single Opteron, running 64-bit kernel but
> 32-bit userland) from 2.6.11.9 to 2.6.14 (with the additional NFS patches,
> but that shouldn't really matter) today, and now BIND seems to hang every few
> hours. (Everything on the machine except for the kernel is Debian sarge, so
> we're using BIND 9.2.4 and glibc 2.3.2, with NPTL.) I'm unsure what's really
> happening, but it doesn't respond to any requests at all, a plain strace on
> the process gives nothing, ltrace gives nothing, and it doesn't use any CPU.
It seems a not unreasonable assumption that 2.6.13 works okay, or
there would have been reports of unhappiness (though that is a pure
assumption). Since it only takes a few hours to get the problem to
occur, is it feasible to try to bisect the problem space by testing
some snapshots between 2.6.13 and 2.6.14?
Ray
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
