From owner-freebsd-questions@FreeBSD.ORG Thu Sep 16 21:18:45 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D48916A4D0 for ; Thu, 16 Sep 2004 21:18:45 +0000 (GMT) Received: from mail.cableone.net (scanmail3.cableone.net [24.116.0.123]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEE5F43D1F for ; Thu, 16 Sep 2004 21:18:44 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.62.13]) by smail3.cableone.net (SurgeMail 1.9b) with ESMTP id 36615202 for multiple; Thu, 16 Sep 2004 14:01:39 -0700 Date: Thu, 16 Sep 2004 16:18:02 -0500 From: Vulpes Velox To: Andriy Gapon Message-ID: <20040916161802.0ee13060@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <414975AF.7080208@icyb.net.ua> References: <414975AF.7080208@icyb.net.ua> X-Mailer: Sylpheed-Claws 0.9.12a (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com cc: freebsd-questions@freebsd.org Subject: Re: nforce2 vs. apic X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Sep 2004 21:18:45 -0000 On Thu, 16 Sep 2004 14:14:55 +0300 Andriy Gapon wrote: > > I have nforce2-based motherboard Abit NF7 and run 5.2.1-RELEASE on > that system. I have tried to enable APIC by compiling kernel with > 'device apic' (both with and without SMP option, although this is a > UP system), but system just freezes during boot with it. Everything > works pretty well without APIC, I was just curious about getting it > to work. > > I found this discussion: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-May/027316.html > > and I have also found numerous reports on nforce2+APIC lockup > problem in Linux and some patches that were reported to help with > it. > > So, I want to find out if anything changed with respect to this in > FreeBSD, maybe some patches/workarounds, or success stories about > FreeBSD+nforce2+APIC. > > Also some notes about my lockup. It happens at this point (exerpt > for non-verbose non-APIC dmesg): > > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > pmtimer0 on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > isa0 Timecounter "TSC" frequency 1830012912 Hz quality 800 > Timecounters tick every 10.000 msec > ipfw2 initialized, divert disabled, rule-based forwarding enabled, > default to accept, logging limited to 100 packets/entry by default > <<< In APIC case system freezes here >>> > GEOM: create disk ad0 dp=0xc6e15e60 > ad0: 76319MB [155061/16/63] at ata0-master > UDMA100 acd0: CDRW at ata1-master UDMA33 > > Also, when system freezes keyboard LEDs still work properly and > cursor disappears when I press Scroll Lock, but arrow and > PgUp/PgDown do not work; if I try Alt-F system speacker emits > monotonic sound that can not be turned off (except by reset, of > course). > > I am ready to provide any additional information. Unfortunately I am > not able to use serial console, so I can't give much info for > APIC-enabled case. I own a Abit NF7 Yeah... I remember this. A bit... I remember having to tweak it a bit to get it to play nicely. IIRC 5.2.1 does not have apic in by defualt? I may just haved removed it... I forget now, but any ways. Before trying apic, make sure your kernel has it. If your kernel does not, go into the setup screen and turn it off. I never had any ACPI problems with it and that has all ways worked well, minus a warning about a odd character or the like in it at startup. I also ran into another problem of my board not liking two ram sticks in dual channel mode... would cause a lock up around booting... iirc it would nearly finish and then lock up and KB LEDs would work a bit. So far my only complaint with it has been the onboard vr ethernet chip appears to suck compared to the dc pci card I have been using. Not taken the time to sort that out yet. Appears some what slow under heavy load. Think that has to do with a problem with device polling for that chipset.