From owner-freebsd-doc@FreeBSD.ORG Thu May 31 21:28:27 2007 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15CA316A421; Thu, 31 May 2007 21:28:27 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.freebsd.org (Postfix) with ESMTP id E658A13C457; Thu, 31 May 2007 21:28:26 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn03.u.washington.edu (hymn03.u.washington.edu [140.142.12.169]) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l4VLSQ05005978 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 31 May 2007 14:28:26 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn03.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4VLSQbr021751; Thu, 31 May 2007 14:28:26 -0700 X-Auth-Received: from [192.55.52.4] by hymn03.u.washington.edu via HTTP; Thu, 31 May 2007 14:28:25 PDT Date: Thu, 31 May 2007 14:28:26 -0700 (PDT) From: youshi10@u.washington.edu To: hackers@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.5.31.140735 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SUPERLONG_LINE 0.05, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: usb@freebsd.org, stable@freebsd.org, doc@freebsd.org, current@freebsd.org Subject: Re: Kernel panicking in 6.2 and 7-CURRENT -- interrupt issues X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 May 2007 21:28:27 -0000 On Tue, 29 May 2007 youshi10@u.washington.edu wrote: > Hello, > I'm trying to install 7-CURRENT on my desktop, locally instead of on a > virtual machine, and I'm running into an issue where the kernel almost always > panics on boot with my motherboard (ASUS P5N-SLI E), due to some sort of > interrupt assignment / probing issues. > > Observations: > 1. 7-CURRENT (built) never properly detects the interrupts on the system. > 2. 7-CURRENT (May ISO snapshot) doesn't properly detect my USB keyboard, > but boots and runs sysinstall. > 3. 6.2 RELEASE panics if I don't boot FreeBSD up into "safe mode", due to > an issue with the ohci driver (I think the error message had something to deal > with device adding / enumeration and not being able to find a memory / > interrupt address). > > First off, if I could get some of the command line arguments to pass to > the kernel to emulate safe-mode, that would be much appreciated. Second off, if > anybody has any ideas on how to debug this issue, I'll go off and try to > determine what the cause is. If it's anything like it was before (clean out > /usr/obj, rebuild), I'll be ok. Otherwise, I'll have to purchase more parts and > build another dedicated FreeBSD system :(.. > > Thanks, > -Garrett Sorry for cross-posting so much, but this information is relevant to all of the mailing lists included. Ok I "solved" my problem, to a certain extent. Basically the ASUS P5N-E SLI motherboard (nVidia chipset) isn't bootable with FreeBSD 6.2 RELEASE without going into SAFE MODE (panics after ohci_add_done looking for a non-existent memory address, if the USB controller is enabled in the BIOS with "Legacy Mode", i.e. USB Keyboard compatible), and isn't compatible with FreeBSD 7 at all (kernel can't map IRQs properly on up-to-date CURRENT and panics in kernel mode during boot). Strangely enough the 7-CURRENT snapshot ISOs work, but then again it doesn't setup the OHCI and USB keyboard stuff properly, and I can't get any sort of input from my keyboard, obviously. The ASUS P5B-DLX motherboard (Intel chipset) is compatible with FreeBSD 6.2 and 7 though, without any hacks. Maybe someone should update some documentation on the release notes page for supported hardware? Thanks, -Garrett PS Please CC me in any communication as I'm not subscribed to doc@, stable@, or usb@.