From owner-freebsd-current@FreeBSD.ORG Sat Feb 28 14:15:05 2004 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 57A0816A4CE; Sat, 28 Feb 2004 14:15:05 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F405D43D31; Sat, 28 Feb 2004 14:15:04 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i1SME3DL034550; Sat, 28 Feb 2004 17:14:03 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i1SME2dH034547; Sat, 28 Feb 2004 17:14:02 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sat, 28 Feb 2004 17:14:02 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Vincent Poy In-Reply-To: <20040228115347.K8264-100000@oahu.WURLDLINK.NET> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: alc@freebsd.org cc: current@freebsd.org cc: Kris Kennaway Subject: Re: HEADSUP: Sleep queues added to kernel, so be careful. 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: Sat, 28 Feb 2004 22:15:05 -0000 On Sat, 28 Feb 2004, Vincent Poy wrote: > > > > Switch the sleep/wakeup and condition variable implementations to use the > > > > sleep queue interface: > > > > > > There should be little user-visible effect from this change. > > > > Except for the kernel breakage, perhaps ;-) I guess John is away until > > Monday though. > > What kind of kernel breakage? I think Kris is referring to the tinderbox messages -- the midway driver appears to be having problems compiling because it relied on the cv_waitq_empty() primitive, which is no longer present following the sleep queue change. > What seems to happen for me is that I was originally on a September 23, > 2003 -CURRENT and then applied all /etc updates and then according to > src/UPDATING - I did a make buildworld, followed by a make buildkernel, > make installkernel and rebooted and things were still working. Then I > did a make installworld and then recvsupped with the latest tree which > had src/sbin/savecore/savecore.c 1.68 as the latest thing, then repeated > the make buildworld, make buildkernel, make installkernel, make > installworld but this time as soon as I rebooted, the network seems to > not work at all. I can't get past the machine. Is this something > broken with ipfw since I can't ping the public IP but I can ping the > local 192.168.0.1 address but not anything beyond that and is connected > at 100Mbps Full Duplex. Tried switching both NIC cards and cables just > in case they decided to fail but no go either. Could you confirm that your userspace and userland are really 100% in sync? If you run without IPFW, do things work properly? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research