From owner-freebsd-current@FreeBSD.ORG Tue Jan 25 10:57:17 2005 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 1CB7916A4CE for ; Tue, 25 Jan 2005 10:57:17 +0000 (GMT) Received: from hobbit.neveragain.de (neveragain.de [217.69.76.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34ACA43D1D for ; Tue, 25 Jan 2005 10:57:14 +0000 (GMT) (envelope-from amf@hobbit.neveragain.de) Received: from hobbit.neveragain.de (amf@localhost [127.0.0.1]) j0PAvCqB011830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 25 Jan 2005 11:57:12 +0100 Received: (from amf@localhost) by hobbit.neveragain.de (8.13.2/8.13.2/Submit) id j0PAvCEN011829 for freebsd-current@freebsd.org; Tue, 25 Jan 2005 11:57:12 +0100 Date: Tue, 25 Jan 2005 11:57:12 +0100 From: Dennis Koegel To: freebsd-current@freebsd.org Message-ID: <20050125105712.GB10373@neveragain.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-KeyID: 0D73E19A User-Agent: Mutt/1.5.6+20040907i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (hobbit.neveragain.de [127.0.0.1]); Tue, 25 Jan 2005 11:57:12 +0100 (CET) Subject: Enabling atapicam -> Interrupt storm during boot 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: Tue, 25 Jan 2005 10:57:17 -0000 Hi, if I enable "device atapicam", the kernel hangs during bootup, right after probing the ATA devices. The last message to be seen is: Interrupt storm detected on device "irq20: atapci0" [...] (or similar, don't have the machine next to me right now). After this, the machine seems to be dead, only reset helps. I tried the same thing with a GENERIC kernel and adding just atapicam. Same results. This was with a recent RELENG_5 kernel. Using a kernel built from -CURRENT sources (CTM from few days ago) the interrupt storm message does not appear, but the system deadlocks at the same point. System is an amd64, Via KT800 chipset, disk and CDR on SATA. I don't have experience in debugging these things, but I'm happily ready to do any debugging that may help or test patches. The machine isn't really being used right now ;-) TIA! - D. P.S.: Seems like there are related PRs: kern/74272 and 73675.