From owner-freebsd-bugs Sat Jan 19 12:50:12 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id AAE8237B400 for ; Sat, 19 Jan 2002 12:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0JKo2057383; Sat, 19 Jan 2002 12:50:02 -0800 (PST) (envelope-from gnats) Date: Sat, 19 Jan 2002 12:50:02 -0800 (PST) Message-Id: <200201192050.g0JKo2057383@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ian Dowse Subject: Re: misc/23364: gethostbyaddr takes longer or locks up and burns cpu when linked to -pthread Reply-To: Ian Dowse Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/23364; it has been noted by GNATS. From: Ian Dowse To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: misc/23364: gethostbyaddr takes longer or locks up and burns cpu when linked to -pthread Date: Sat, 19 Jan 2002 20:42:50 +0000 Adding a reply I had forgotten about to the audit trail: In message <5.1.0.14.2.20011120112559.04ae0bb0@ball>, Chris Pugmire writes: > >At 08:11 AM 11/18/01 -0800, you wrote: >>Synopsis: gethostbyaddr takes longer or locks up and burns cpu when linked >>to -pthread >> >>State-Changed-From-To: open->feedback >>State-Changed-By: iedowse >>State-Changed-When: Sun Nov 18 08:10:21 PST 2001 >>State-Changed-Why: >> >>Does this problem still occur with more recent releases? I can't >>reproduce it with FreeBSD 4.4. >> >>http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23364 > >Hi, sorry I'm unable to reproduce it now, it originally occured on a customers >machine which I no longer have access to, I can't make it occur on our own >system now but I don't know if I ever reproduced it locally, it may be >dependent >in some way on the dns server used I'm not sure. > >Sorry this isn't very helpful, all I can suggest is you check the code that >reads from the dns server to see if it can in any way loop while waiting for >a response, my guess would be if the thread library is somehow stopping a >select >call from working correctly but it must be more subtle than that. > >Thanks for looking into it anyway I appreciate it. It was several months >ago I reported this so sorry if I'm a bit shaky on the facts. > > ChrisP. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message