Re: how to fix "interrupt storm"
On 5/8/09, per...@pluto.rain.com wrote: > What, exactly, is an "interrupt storm", and how do I fix it? > > I have added a 64GB Patriot flash drive to a 7.0 system, but it does > not seem to be working properly. Pertinent parts of dmesg.boot: > > FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 > r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Pentium II/Pentium II Xeon/Celeron (449.85-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > > Features=0x183f9ff > real memory = 67100672 (63 MB) > avail memory = 51662848 (49 MB) > ... > atapci1: port > 0x1800-0x180f,0x14f0-0x14ff,0x14e0-0x14ef,0x14d0-0x14df,0x14a0-0x14bf,0x1000-0x10ff > irq 9 at device 16.0 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ... > ad6: FAILURE - SET_MULTI status=51 error=4 > ad6: 61136MB at ata3-master SATA150 > > At first things look OK, despite the "FAILURE" message: > > $ ls -l /dev/ad6* > crw-r- 1 root operator0, 88 May 3 20:30 /dev/ad6 > $ file -s /dev/ad6 > /dev/ad6: x86 boot sector, Microsoft Windows XP MBR, Serial 0x9e5523de > $ grep -w ad6 /usr/local/etc/mtools.conf > drive f: file="/dev/ad6" > $ mdir f: > init F: non DOS media > Cannot initialize 'F:' > > Now this seems a bit odd: file(1) says it's a Windows disk, but > mdir(1) says it isn't. (Note that there are no slices, else the > initial ls(1) should have shown them, so I suppose the drive has > a single FAT filesystem as one would expect on a floppy disk.) > Then, when I tried to investigate further by examining the contents > of the drive with "od -c /dev/ad6 | more", I got one screenful of > output followed by (on console and in dmesg): > > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > ad6: FAILURE - SET_MULTI status=51 error=4 > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=10712 > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > interrupt storm detected on "irq9:"; throttling interrupt source > ad6: FAILURE - SET_MULTI status=51 error=4 > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 > > etc. etc. until I killed it with ^C. (Just entering "q", to cause > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not > stop the spew of messages.) > > What does this indicate? Hardware problems? Bad configuration? > Something else? > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > Output of "vmstat -i"? -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
"Paul B. Mahol" wrote: > On 5/8/09, per...@pluto.rain.com wrote: > > What, exactly, is an "interrupt storm", and how do I fix it? ... > > interrupt storm detected on "irq9:"; throttling interrupt source > > interrupt storm detected on "irq9:"; throttling interrupt source > > interrupt storm detected on "irq9:"; throttling interrupt source > > interrupt storm detected on "irq9:"; throttling interrupt source > > interrupt storm detected on "irq9:"; throttling interrupt source > > ad6: FAILURE - SET_MULTI status=51 error=4 > > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 > > > > etc. etc. until I killed it with ^C. (Just entering "q", to cause > > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not > > stop the spew of messages.) > > > > What does this indicate? Hardware problems? Bad configuration? > > Something else? > > Output of "vmstat -i"? $ vmstat -i interrupt total rate irq0: clk 497386851 1004 irq1: atkbd02491 0 irq3: xl0 2030 0 irq6: fdc011 0 irq7: ppbus0 ppc0 1 0 irq8: rtc 63654324128 irq9: uhci0+ 166216 0 irq14: ata0 369620 0 irq15: ata1 691 0 Total 561582235 1133 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
On 5/9/09, per...@pluto.rain.com wrote: > "Paul B. Mahol" wrote: >> On 5/8/09, per...@pluto.rain.com wrote: >> > What, exactly, is an "interrupt storm", and how do I fix it? > ... >> > interrupt storm detected on "irq9:"; throttling interrupt source >> > interrupt storm detected on "irq9:"; throttling interrupt source >> > interrupt storm detected on "irq9:"; throttling interrupt source >> > interrupt storm detected on "irq9:"; throttling interrupt source >> > interrupt storm detected on "irq9:"; throttling interrupt source >> > ad6: FAILURE - SET_MULTI status=51 error=4 >> > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 >> > >> > etc. etc. until I killed it with ^C. (Just entering "q", to cause >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not >> > stop the spew of messages.) >> > >> > What does this indicate? Hardware problems? Bad configuration? >> > Something else? >> >> Output of "vmstat -i"? > > $ vmstat -i > interrupt total rate > irq0: clk 497386851 1004 > irq1: atkbd02491 0 > irq3: xl0 2030 0 > irq6: fdc011 0 > irq7: ppbus0 ppc0 1 0 > irq8: rtc 63654324128 > irq9: uhci0+ 166216 0 uhci0 is doing strange things, what usb device are connected? It could be bad configuration, bug or hardware problem. > irq14: ata0 369620 0 > irq15: ata1 691 0 > Total 561582235 1133 > -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
"Paul B. Mahol" wrote: > On 5/9/09, per...@pluto.rain.com wrote: > > "Paul B. Mahol" wrote: > >> On 5/8/09, per...@pluto.rain.com wrote: > >> > What, exactly, is an "interrupt storm", and how do I fix it? > > ... > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> > ad6: FAILURE - SET_MULTI status=51 error=4 > >> > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 > >> > > >> > etc. etc. until I killed it with ^C. (Just entering "q", to cause > >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not > >> > stop the spew of messages.) > >> > > >> > What does this indicate? Hardware problems? Bad configuration? > >> > Something else? > >> > >> Output of "vmstat -i"? > > > > $ vmstat -i > > interrupt total rate > > irq0: clk 497386851 1004 > > irq1: atkbd02491 0 > > irq3: xl0 2030 0 > > irq6: fdc011 0 > > irq7: ppbus0 ppc0 1 0 > > irq8: rtc 63654324128 > > irq9: uhci0+ 166216 0 > > uhci0 is doing strange things, what usb device are connected? There are no USB devices connected. I think those must actually be atapci1 interrupts, since irq9 is where dmesg reported it. > It could be bad configuration, bug or hardware problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
On 5/10/09, per...@pluto.rain.com wrote: > "Paul B. Mahol" wrote: >> On 5/9/09, per...@pluto.rain.com wrote: >> > "Paul B. Mahol" wrote: >> >> On 5/8/09, per...@pluto.rain.com wrote: >> >> > What, exactly, is an "interrupt storm", and how do I fix it? >> > ... >> >> > interrupt storm detected on "irq9:"; throttling interrupt source >> >> > interrupt storm detected on "irq9:"; throttling interrupt source >> >> > interrupt storm detected on "irq9:"; throttling interrupt source >> >> > interrupt storm detected on "irq9:"; throttling interrupt source >> >> > interrupt storm detected on "irq9:"; throttling interrupt source >> >> > ad6: FAILURE - SET_MULTI status=51 >> >> > error=4 >> >> > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 >> >> > >> >> > etc. etc. until I killed it with ^C. (Just entering "q", to cause >> >> > more(1) to exit and presumably stop od(1) with a SIGPIPE, did not >> >> > stop the spew of messages.) >> >> > >> >> > What does this indicate? Hardware problems? Bad configuration? >> >> > Something else? >> >> >> >> Output of "vmstat -i"? >> > >> > $ vmstat -i >> > interrupt total rate >> > irq0: clk 497386851 1004 >> > irq1: atkbd02491 0 >> > irq3: xl0 2030 0 >> > irq6: fdc011 0 >> > irq7: ppbus0 ppc0 1 0 >> > irq8: rtc 63654324128 >> > irq9: uhci0+ 166216 0 >> >> uhci0 is doing strange things, what usb device are connected? > > There are no USB devices connected. I think those must actually > be atapci1 interrupts, since irq9 is where dmesg reported it. Try editing /boot/device.hints lines with irq or adding similar lines ... > >> It could be bad configuration, bug or hardware problem. > -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
"Paul B. Mahol" wrote: > On 5/10/09, per...@pluto.rain.com wrote: ... > >> >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> >> > interrupt storm detected on "irq9:"; throttling interrupt source > >> >> > ad6: FAILURE - SET_MULTI status=51 > >> >> >error=4 > >> >> > ad6: TIMEOUT - READ_DMA retrying (1 retry left) LBA=136936 > >> >> > > >> >> > etc. etc. until I killed it with ^C ... > >> >> > >> >> Output of "vmstat -i"? > >> > > >> > $ vmstat -i > >> > interrupt total rate > >> > irq0: clk 497386851 1004 > >> > irq1: atkbd02491 0 > >> > irq3: xl0 2030 0 > >> > irq6: fdc011 0 > >> > irq7: ppbus0 ppc0 1 0 > >> > irq8: rtc 63654324128 > >> > irq9: uhci0+ 166216 0 > >> > >> uhci0 is doing strange things, what usb device are connected? > > > > There are no USB devices connected. I think those must actually > > be atapci1 interrupts, since irq9 is where dmesg reported it. > > Try editing /boot/device.hints lines with irq or adding similar > lines ... How would I go about figuring out what to add or change? I suppose I want to move either uhci0 or atapci1 to an unused irq, but my recollection is that I don't have unlimited choice in the matter because the IRQ used by a particular PCI device -- or at least the set available for assignment -- is determined by how the motherboard is wired. Granted it's been several years since I was into PCI at this level. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
PerryH-2 wrote: > > There are no USB devices connected. I think those must actually > be atapci1 interrupts, since irq9 is where dmesg reported it. > I think this could be related to previous issues on same topic. I don't recall the thread titles, but the solution is located here: http://confighell.com/FreeBSD#How_to_get_rid_of_interrupt_storm_atapci0_and_others_ I hope it can solve things out for you as well. - Nicolai -- View this message in context: http://www.nabble.com/how-to-fix-%22interrupt-storm%22-tp23450486p23481884.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to fix "interrupt storm"
Nicolais wrote: > PerryH-2 wrote: > > There are no USB devices connected. I think those must actually > > be atapci1 interrupts, since irq9 is where dmesg reported it. > > I think this could be related to previous issues on same topic. > I don't recall the thread titles, but the solution is located here: > > http://confighell.com/FreeBSD#How_to_get_rid_of_interrupt_storm_atapci0_and_others_ > > I hope it can solve things out for you as well. It does not seem to be the solution in this case. (Apologies for the delay; this machine turned out to be a bit under-resourced for kernel building, and meanwhile life got in the way.) So, I am back to asking what changes or additions to make in /boot/device.hints. I suppose I need to move either uhci0 or atapci1 off of the (currently shared) irq9 to an unused irq, but I'm not finding it immediately evident how to do that. For the archives, in case the referenced page goes away in the future, it suggests adding options KDB options KDB_UNATTENDED options DDB to the kernel. This is reported to have caused an interrupt storm, involving an atapci controller on an amd64 system, to go away. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
