Hi, I'm afraid, the bug is still there:
Feb 26 12:09:51 alpha1 lwresd[21939]: starting BIND 9.4.2 Feb 26 12:09:51 alpha1 lwresd[21939]: found 1 CPU, using 1 worker thread Feb 26 12:09:51 alpha1 lwresd[21939]: rwlock.c:337: INSIST((rwl->cnt_and_flag & 0x1) != 0) failed Feb 26 12:09:51 alpha1 lwresd[21939]: exiting (due to assertion failure) Feb 26 12:09:55 alpha1 named[21984]: starting BIND 9.4.2 Feb 26 12:09:55 alpha1 named[21984]: found 1 CPU, using 1 worker thread Feb 26 12:09:55 alpha1 named[21984]: rwlock.c:337: INSIST((rwl->cnt_and_flag & 0x1) != 0) failed Feb 26 12:09:55 alpha1 named[21984]: exiting (due to assertion failure) ... as opposed to...: Feb 26 12:36:36 alpha1 named[22199]: starting BIND 9.3.4 Feb 26 12:36:36 alpha1 named[22199]: found 1 CPU, using 1 worker thread Feb 26 12:36:36 alpha1 named[22199]: loading configuration from '/etc/bind/named.conf' Feb 26 12:36:36 alpha1 named[22199]: listening on IPv4 interface lo, 127.0.0.1#53 Feb 26 12:36:36 alpha1 named[22199]: listening on IPv4 interface eth1, 192.168.1.1#53 ... Yours, Andreas. "Debian Bug Tracking System" <[EMAIL PROTECTED]> schrieb: > > This is an automatic notification regarding your Bug report > which was filed against the bind9 package: > > #435194: bind9 9.4.1-1 on alpha dies with assertion failure in rwclock.c > > It has been closed by LaMont Jones <[EMAIL PROTECTED]>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact LaMont Jones > <[EMAIL PROTECTED]> by > replying to this email. > > > -- > 435194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435194 > Debian Bug Tracking System > Contact [EMAIL PROTECTED] with problems >
