From owner-freebsd-bugs@FreeBSD.ORG Thu May 7 18:20:05 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 833861065695 for ; Thu, 7 May 2009 18:20:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 705B58FC1F for ; Thu, 7 May 2009 18:20:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n47IK57v021674 for ; Thu, 7 May 2009 18:20:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n47IK576021673; Thu, 7 May 2009 18:20:05 GMT (envelope-from gnats) Date: Thu, 7 May 2009 18:20:05 GMT Message-Id: <200905071820.n47IK576021673@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Alexander Motin Cc: Subject: Re: kern/131796: [ata] Introducing new USB or eSATA disks results in atapci1+ irq storm until reboot X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Motin List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2009 18:20:06 -0000 The following reply was made to PR kern/131796; it has been noted by GNATS. From: Alexander Motin To: bug-followup@FreeBSD.org, cfaber@gmail.com Cc: Subject: Re: kern/131796: [ata] Introducing new USB or eSATA disks results in atapci1+ irq storm until reboot Date: Thu, 07 May 2009 21:17:33 +0300 This may be not an ATA related problem. Notation "atapci1+" means that several devices sharing some interrupt and atapci1 is only the first of them. Could you dig you boot messages looking fore devices using that IRQ and somehow resolve the IRQ conflict? I just don't see here relations between attaching USB drive and ATA subsystem. If it won't help, provide additional information about your ATA controller and verbose boot messages and messages any verbose when problem appears. -- Alexander Motin