From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 13 03:00:03 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 C8AE7106566B for ; Tue, 13 Jan 2009 03:00:03 +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 94A768FC13 for ; Tue, 13 Jan 2009 03:00:03 +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 n0D303HC021549 for ; Tue, 13 Jan 2009 03:00:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0D3039V021548; Tue, 13 Jan 2009 03:00:03 GMT (envelope-from gnats) Date: Tue, 13 Jan 2009 03:00:03 GMT Message-Id: <200901130300.n0D3039V021548@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Jason Chambers Cc: Subject: Re: kern/126709: [ata] Regression of SATA/PATA support with 6.3 and 7.0 (x86/amd64) -- Nvidia nForce4 chipset [regression] X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jason Chambers List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2009 03:00:04 -0000 The following reply was made to PR kern/126709; it has been noted by GNATS. From: Jason Chambers To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/126709: [ata] Regression of SATA/PATA support with 6.3 and 7.0 (x86/amd64) -- Nvidia nForce4 chipset [regression] Date: Mon, 12 Jan 2009 18:53:00 -0800 Whatever changes made it into 7.1-RELEASE appear to have mostly fixed the problem. With 7.1 the system runs fine except for the problem described below. After about 7 hours of uptime the system fails due to an interrupt storm between what looks like the nVidia controller, network interface, and USB controller. Changing the em0 interface status to down stops the interrupt storm however it returns as soon as the interface is enabled again. Let me know if you need more data. Thanks, --Jason dmesg log: ============ 16:02:44 -- Starts generating interrupt errors: "interrupt storm detected on "irq21:"; throttling interrupt source" 16:02:45 -- em0: watchdog timeout -- resetting 16:02:45 -- interrupt storm detected.... 16:02:45 -- em0: link state changed to DOWN (...) 16:02:49 -- em0: link state changed to UP The above repeats regularly but is partially squelched by "last message repeated x times" messages. vmstat -i shows: ====================== interrupt total rate irq1: atkbd0 138 0 irq14: ata0 91 0 irq18: fwohci0 3 0 irq19: em0 150708 5 irq21: ohci0+ 853571283 31349 irq22: ehci0+ 267 0 cpu0: timer 54455483 1999 cpu0: timer 54446087 1999 Total 962624060 35354 Checking the dmesg boot log - bzcat /var/log/messages.0.bz2 | grep "irq 21" ================================================ ohci0: mem 0xdfffb000-0xdfffbfff irq 21 at device 11.0 on pci0 atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf mem 0xdfffd000-0xdfffdfff irq 21 at device 16.0 on pci0 Network card boot message: ============================ em0: port 0xdcc0-0xdcff mem 0xdcec0000-0xdcedffff,0xdcee0000-0xdcefffff irq 19 at device 3.0 on pci3