From owner-freebsd-current@FreeBSD.ORG Wed Dec 31 07:04:10 2003 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 4A21716A4CE for ; Wed, 31 Dec 2003 07:04:10 -0800 (PST) Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by mx1.FreeBSD.org (Postfix) with SMTP id D3DA343D31 for ; Wed, 31 Dec 2003 07:04:08 -0800 (PST) (envelope-from q_dolan@yahoo.com.au) Received: from unknown (HELO ?192.168.100.140?) (q?dolan@203.144.21.67 with plain) by smtp013.mail.yahoo.com with SMTP; 31 Dec 2003 15:04:08 -0000 From: Q To: current@freebsd.org Message-Id: <1072882939.17946.47.camel@boxster.onthenet.com.au> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 01 Jan 2004 01:02:20 +1000 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Losing Interrupts with 5.2RC & ACPI 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: Wed, 31 Dec 2003 15:04:10 -0000 I have a fairly new AMD nforce2 based machine running 5.2RC (updated from RELENG_5_1 to RELENG_5_2 a couple of days ago) that has been working perfectly with ACPI enabled, although there are a couple of ACPI related error messages on bootup.The machine has been running for a month or so using the internal nv0 ethernet but has also had an fxp0 interface sitting unused. So today I decided to setup a DMZ on the fxp card and ran into immediate problems with interrupts. Both interfaces share the same interrupt, and work fine without ACPI enabled, but if ACPI is enabled they will both start issuing watchdog timeouts within about 30sec of completing bootup, during which time vmstat -i shows no new interrupts at all on the shared irq. If I down the fxp0 interface during this the nv0 interface seems to recover after the watchdog timer expires (I didn't try up'ing the fxp0 interface again). Any suggestions on where to start looking or options to turn on to try and track down what's going on? -- Seeya...Q -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- _____ / Quinton Dolan q_dolan@yahoo.com.au __ __/ / / __/ / / / __ / _/ / / Gold Coast, QLD, Australia __/ __/ __/ ____/ / - / Ph: +61 419 729 806 _______ / _\