Interrupt storm detected (was: Re: hang after after update:
"adX: FAILURE - already active DMA on this device" (ICH5 system))
grover at ceribus.net
Wed Jun 9 20:13:07 GMT 2004
Im getting interupt storms myself from just having the printer turned on
while booting using todays current.
FreeBSD 5.2-CURRENT (DOMINATION) #0: Wed Jun 9 12:42:55 PDT 2004
ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <Parallel port bus> on ppc0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
orm0: <Option ROMs> at iomem 0xc8000-0xcffff,0xc0000-0xc7fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 1194923742 Hz quality 800
Timecounters tick every 10.000 msec
ad0: 9732MB <SAMSUNG SV1022D> [19773/16/63] at ata0-master UDMA66
ad1: 117800MB <IC35L120AVVA07-0> [239340/16/63] at ata1-master UDMA100
ad2: 117800MB <IC35L120AVVA07-0> [239340/16/63] at ata1-slave UDMA100
Mounting root from ufs:/dev/ad0s1a
Interrupt storm detected on "irq7: lpt0"; throttling interrupt source
I dunno if this is on the same topic but if anyone cared theres my error.
> -----Original Message-----
> From: owner-freebsd-current at freebsd.org [mailto:owner-freebsd-
> current at freebsd.org] On Behalf Of Bruce Evans
> Sent: Wednesday, June 09, 2004 12:20 PM
> To: Alexander Leidinger
> Cc: Johan Pettersson; current at FreeBSD.org; sos at FreeBSD.org
> Subject: Re: Interrupt storm detected (was: Re: hang after after update:
> "adX: FAILURE - already active DMA on this device" (ICH5 system))
> On Wed, 9 Jun 2004, Alexander Leidinger wrote:
> > On Tue, 8 Jun 2004 18:36:25 +0200
> > Johan Pettersson <manlix at demonized.net> wrote:
> > > Todays -CURRENT works just fint. It even works as it should with HTT
> > > enabled now. Wee! :) Can it be the recent ACPI-changes that fixed it?
> > Confirmed.
> > BTW.: I get "Interrupt storm detected on "irq18: uhci2+"; throttling
> > interrupt source", is anybody interested in a dmesg of a system?
> I fixed interrupt storm handling to actually work in more cases.
> However, if you get the "Interrupt strorm detected" message, then you
> also get low performance for devices on that interrupt, especially
> after my changes.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current