From owner-freebsd-current Tue Dec 19 14:10:20 2000 From owner-freebsd-current@FreeBSD.ORG Tue Dec 19 14:10:17 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from freebsd.netcom.com (freebsd.netcom.com [198.211.79.3]) by hub.freebsd.org (Postfix) with ESMTP id 8E59137B402 for ; Tue, 19 Dec 2000 14:10:16 -0800 (PST) Received: (from bugs@localhost) by freebsd.netcom.com (8.8.8+Sun/8.8.8) id QAA28118 for freebsd-current@freebsd.org; Tue, 19 Dec 2000 16:10:11 -0600 (CST) From: Mark Hittinger Message-Id: <200012192210.QAA28118@freebsd.netcom.com> Subject: -current "almost" hanging after boot To: freebsd-current@freebsd.org Date: Tue, 19 Dec 2000 16:10:11 -0600 (CST) X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had a problem with -current for a couple weeks that appeared to be a boot hang at first glace. I compiled the kernel with ddb and was able to break into the debugger when things appeared to hang. After the kernel starts up /sbin/init the OS will pause for a second and then begin spewing the microuptime() went backwards stuff. The kernel isn't really hanging it is just being really slow about some things. A few months ago we had a problem with the XL driver where an UNLOCK had been mistakenly coded as a LOCK. The problem feels very simlar to that. Does anyone have any hints for what to look at when I break in to the debugger? Is anyone else seeing this behavior? Later Mark Hittinger Earthlink bugs@freebsd.netcom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message