From owner-freebsd-current@FreeBSD.ORG Wed Jun 16 20:54:26 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 A794D16A4CE for ; Wed, 16 Jun 2004 20:54:26 +0000 (GMT) Received: from out011.verizon.net (out011pub.verizon.net [206.46.170.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EF1543D46 for ; Wed, 16 Jun 2004 20:54:26 +0000 (GMT) (envelope-from david.gurvich@verizon.net) Received: from verizon.net ([68.161.87.134]) by out011.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040616205257.JSVW18566.out011.verizon.net@verizon.net> for ; Wed, 16 Jun 2004 15:52:57 -0500 Date: Wed, 16 Jun 2004 16:52:54 -0400 Mime-Version: 1.0 (Apple Message framework v553) Content-Type: text/plain; charset=US-ASCII; format=flowed From: David Gurvich To: freebsd-current@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <23DDF6A8-BFD7-11D8-BFFD-000393AB07D8@verizon.net> X-Mailer: Apple Mail (2.553) X-Authentication-Info: Submitted using SMTP AUTH at out011.verizon.net from [68.161.87.134] at Wed, 16 Jun 2004 15:52:57 -0500 Subject: Hang on reboot, segmentation fault during compile 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: Wed, 16 Jun 2004 20:54:26 -0000 Dismounts all systems, stops running processes, and proceeds to make siren noises on soft reboot, requires power reboot. Random segmentation faults during building from source. i.e. I will reboot, build and succeed. Generally unstable system. All as of 5/28/2004 -Current. 5.2.1-Current iso image as of 2/22/2004 operates with no problems, as long as apic is disabled. With both ACPI and APIC enabled onboard lan will timeout, usb mouse will be disabled. System consists of asus nforce1 motherboard with onboard lan, usb, and vga. The 'nv driver' is fast and stable, nvidia binary driver is not. Am using the nvnet driver for onboard lan, nv for X11 as nvidia driver crashes too frequently to be useable, and ums for mouse. Noticed "Giant Locked" on both nvnet and nvidia driver. kldunload crashes system when trying to unload nvidia, no problem with if_nv. Then again the nvidia driver doesn't need help to crash system. Was wondering if Giant Lock is what it does to system? Recent cvsup of src confirmed that the problem remains in -Current as of June 16,2004.