From owner-freebsd-stable@FreeBSD.ORG Wed Jan 5 11:46:21 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DF9716A4CE for ; Wed, 5 Jan 2005 11:46:21 +0000 (GMT) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.178.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E2AD43D3F for ; Wed, 5 Jan 2005 11:46:20 +0000 (GMT) (envelope-from ohartman@uni-mainz.de) Received: from [134.93.183.16] (edda.Geo.Uni-Mainz.DE [134.93.183.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate1.zdv.Uni-Mainz.DE (Postfix) with ESMTP id 9BB833000662 for ; Wed, 5 Jan 2005 12:46:19 +0100 (CET) Message-ID: <41DBD394.5010108@uni-mainz.de> Date: Wed, 05 Jan 2005 12:46:28 +0100 From: "O. Hartmann" Organization: Institut =?ISO-8859-15?Q?f=FCr_Geophysik?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-AT; rv:1.7.5) Gecko/20050102 X-Accept-Language: de-de, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at uni-mainz.de Subject: RELENG_3: SMP/ACPI on ASUS CUR-DLS possible? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2005 11:46:21 -0000 Dear Sirs. I use FreeBSD 5.3-STABLE, most recently updated and built-world today. I realised strange behaviour with the used ASUS CUR-DLS mainboard and FreeBSD 5.3-{RELEASE|STABLE}. SMP is impossible on this mainboard with FreeBSD 5.3. With or without ACPI enabled, the machine crashes after a while (this 'while' is in the range of several minutes up to a whole day). The crash with SMP enabled is as follows. The system gets stuck, I can move windows around, but I can't open new xterms or other applications, network is dead then. The, after a while, the system reboots or gets completely stuck without any error. In some rare cases I 'suspect' the machine's crashing and I'm able to switch to console and see some debugger messages, most time they are heavily truncated. Also common on this machine (either in UP or SMP) is a not working single user mode. Doing a make installworld dies with a stuck console, typing Ctrl-T reports in nearly 100% of all cases process_foo [biowrd] or something similar. Starting single user kernel from loader without SMP and without APIC seems to solve problem, but compiling a kernel without apic remains the machine in a weird unuseable state (hanging X11/mouse etc.). Another strange thing is enabling/disabling USB, SIO ports and in what slot to put a 64 Bit PCI 1GBit NIC (intel 1000/Pro). Disabling both sio-ports makes the kernel stuck after initialising the SCSI controller all the way. Swapping NIC from on to the other 64 Bit slot decides wheter I can use a further 32 Bit add-on card (audio board) or not! This seems to be a IRQ routing problem which is well known to me since I utilize a TYAN Thunder 2500 mainboard with FreeBSD (without ACPI). I did several PR-reports in the past and i was told my problems were hardware related but I think this is not the truth since in UP the machine is stable (except single user mode) and I get weird behaviour with APIC off (stable, useable single user mode, non working multiuser mode). I also get a stable single user mode when inserting another VGA (PCI type) video board: single user mode is stable, not getting stuck, but machine dies immedieately and reboots when booting the FreeBSD kernel in every variation (with/without apic/acpi/up/smp). Before reporting again masses of faulty bug reports or nonsense not suitable for gurus or developers, I would ask you whether someone out here utilizing the ASUS CUR-DLS mainboard and using FreeBSD 5.3-XXX has the same problems or not. Many thanks in advance. Oliver