Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 21460 invoked by uid 6000); 15 Nov 1999 20:33:02 -0000 Received: (qmail 21428 invoked from network); 15 Nov 1999 20:32:55 -0000 Received: from mail.plc.com (HELO prologic.com) (208.218.20.4) by taz.hyperreal.org with SMTP; 15 Nov 1999 20:32:55 -0000 Received: from cos.crosstor.com(192.168.1.75) by prologic.crosstor.com via smap (V2.1) id xma021793; Mon, 15 Nov 99 15:32:15 -0500 Received: from mechanist.plc.com by cos.crosstor.com (SMI-8.6/SMI-SVR4) id NAA11256; Mon, 15 Nov 1999 13:32:38 -0700 Received: from crosstor.com (localhost [127.0.0.1]) by mechanist.plc.com (8.9.1b+Sun/8.9.1) with ESMTP id NAA11994 for ; Mon, 15 Nov 1999 13:34:54 -0700 (MST) Message-ID: <38306E6D.A38D917F@crosstor.com> Date: Mon, 15 Nov 1999 13:34:53 -0700 From: Tom Harrington Organization: CrosStor Software, Inc. X-Mailer: Mozilla 4.61 [en] (X11; U; SunOS 5.7 i86pc) X-Accept-Language: en Mime-Version: 1.0 To: new-httpd@apache.org Subject: Re: recent linux kernels broken? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Marc Slemko wrote: > > I seem to see a lot of people submitting bug reports over the past few > weeks, using a fairly recent 2.2 kernel, about Apache just hanging after > some time on their systems. > > Any known kernel bugs that could be causing this? It seems odd that this > pops up all of a sudden, all with very similar linux kernel versions... I don't know where known kernel bugs would be tracked online. But I have noticed one case of apparently-buggy networking behavior with 2.2.x kernels. The test case I saw was a pair of programs that implemented UDP send/receive, the sort of thing used in an introductory network programming class. In _some_ cases, a call to "recvfrom", with no incoming data would not block, but would instead return an error. I don't recall the error code right now, but it was unexpected behavior that didn't match documentation. This happened on 2.2.6 on a PowerPC system and 2.2.12-20smp on some recent x86-series clone. It did not happen on 2.0.36 on Pentium, or (as a sanity check) on any version of Solaris I could get hold of. Apache shouldn't encounter this specific bug, but it's possible that what I saw was a manifestation of a deeper problem that would affect Apache. -- Tom Harrington CrosStor Software, Inc. tph@crosstor.com