From: Piotr Majka <charvel@link.pl>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: bind-9.3.1 doesnt work with 2.6.14
Date: Fri, 25 Nov 2005 01:09:51 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.63.0511250100590.19047@link.pl> (raw)
In-Reply-To: <200511251057.06263.kernel@kolivas.org>
After run named on 2.6.14 (I try 2.6.14-rcX too) I got in logfile:
Nov 10 18:24:57 xxx named[1845]: errno2result.c:109: unexpected error:
Nov 10 18:24:57 xxx named[1845]: unable to convert errno to isc_result:
14: Bad address
Nov 10 18:24:57 xxx named[1845]: UDP client handler shutting down due to
fatal receive error: unexpected error
and named dont respond to the query. I switch back to 2.6.13.2 - all
work fine. Once again run 2.6.14 - the same error after few minutes of
working.
# sh /home/linux-2.6.14/scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux xxx 2.6.13.2-grsec #1 Sat Sep 24 18:30:11 CEST 2005 i686
i686 i386 GNU/Linux
Gnu C 4.0.1
Gnu make 3.80
binutils 2.16.91.0.2
util-linux 2.12p
mount 2.12p
module-init-tools 3.1
e2fsprogs 1.38
reiserfsprogs line
reiser4progs line
nfs-utils 1.0.7
Linux C Library 2.3.5
Dynamic linker (ldd) 2.3.5
Procps 3.2.6
Net-tools 1.60
Kbd 1.12
Sh-utils 5.2.1
udev 058
# lsmod
Module Size Used by
#
I try with, and without grsecurity patch - still the same. Seems that its
vanila kernel bug related.
--
Piotr "Charvel" Majka | Uin: 20873695
GCM d- s-:- a- C++ UL++++ P+ L+++ E--- W+ N+++ !o !K w--- !O M V- PS+ PE !Y
PGP+ t--- !5 X R tv- b !DI D+ G++ e h r y++**
next prev parent reply other threads:[~2005-11-25 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 23:57 2.6.14-ck6 Con Kolivas
2005-11-25 0:09 ` Piotr Majka [this message]
2005-11-25 0:16 ` PROBLEM: bind-9.3.1 doesnt work with 2.6.14 Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0511250100590.19047@link.pl \
--to=charvel@link.pl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®