From owner-freebsd-current@FreeBSD.ORG Sun Jun 15 23:40:40 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFB6D37B401 for ; Sun, 15 Jun 2003 23:40:40 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 314ED43F85 for ; Sun, 15 Jun 2003 23:40:40 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h5G6eWM7048102; Sun, 15 Jun 2003 23:40:36 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200306160640.h5G6eWM7048102@gw.catspoiler.org> Date: Sun, 15 Jun 2003 23:40:32 -0700 (PDT) From: Don Lewis To: ths@katjusha.de In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: current@FreeBSD.org Subject: Re: qmail uses 100% cpu after FreeBSD-5.0 to 5.1 upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jun 2003 06:40:41 -0000 On 16 Jun, Thorsten Schroeder wrote: > Hi, > > On Mon, 15 Jun 2003, Chris Shenton wrote: > >> [...] qmail is run under daemontools and all work fine (the configuration >> is 2 years old!), but when I delivery the first mail (localy or remote) >> the qmail-send process fire up to 100% of CPU infinitely >> >> All other mail are right delivery, and the CPU use is the only problem, I >> see in qmail-send.c that select() function, after the first message, >> allways return 1 > > same here too. > I don't know what it could be - perhaps a problem with named pipes > ("lock/trigger")? > > You can find my ktrace output here: http://cs.so36.net/~ths/kdump.txt > > Would be nice if anyone have an idea :) > >> A truss shows me it's running in a tight loop over this code: >> close(9) = 0 (0x0) >> select(0x9,0xbfbffcbc,0xbfbffc3c,0x0,0xbfbffc24) = 1 (0x1) > >> Anyone else seen this or know what in FreeBSD-5.1 might have changed to cause >> this? Any thoughts on how I might go about diagnosing this any better? Which version of fifo_vnops.c? If the problem is present in 5.1-RELEASE, then the problem is likely to be the change made in 1.79 and 1.85. If the problem didn't show up until after the 5.1-RELEASE, then the problem could be the changes in 1.87 or 1.88.