Date: Sun, 30 Oct 2005 03:35:57 +0100
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: BIND hangs with 2.6.14
Message-ID: <20051030023557.GA7798@uio.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.5.11
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1359
Lines: 29

[Please Cc me on any replies, I'm not subscribed]

Hi,

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.

gdb shows four threads, one of them in sigsuspend, another in select, a third
in __JCR_LIST__ and the fourth just showing garbage. I'm sorry I can't be
more specific here -- I can't find a reliable way to provoke it into this
hanging behaviour, but I've got an strace running now to at least have _some_
tracking information when it goes awry.

Does anybody have a clue as of what might break it in this way? I've skimmed
the changelogs, but couldn't find anything obvious.

/* Steinar */
-- 
Homepage: http://www.sesse.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/