Losing Interrupts with 5.2RC & ACPI
From: Q (q_dolan_at_yahoo.com.au)
Date: 12/31/03
- Previous message: Hajimu UMEMOTO: "Re: kern.osreldate and EAI_NODATA deprecation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: current@freebsd.org Date: Thu, 01 Jan 2004 01:02:20 +1000
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
_______ /
_\
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Hajimu UMEMOTO: "Re: kern.osreldate and EAI_NODATA deprecation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
