Interrupt storm and Intel DQ67SW
In case anyone else runs into this problem, here it is for the archives. FreeBSD 8.3, AMD64 (Actually, RELENG_8 as of March 2012) I upgraded my home server to an Intel DQ67SW motherboard (hardware version AAG12527-309). I used a bge PCI-E nic in the 1x slot which caused an interrupt storm issue with the usb. Trying an old PCI fxp card showed the same problem. Even with just 2Mb of pppoe traffic crossing the bge or fxp, I would see storm issues. Running top, showed 10% of the system was spending its time servicing interrupts. vmstat -i showed a rate of close to 10k on irq16. I upgraded the BIOS to SWQ6710H.86A.0061.2012.0210.1130 from the Nov 2011 version and all is fine now. Everything about the box 'feels' more responsive and throughput on my wan connection is normal again. # vmstat -i interrupt total rate irq16: bge0 ehci0+ 40439 3 irq20: fwohci0 2 0 irq23: ehci1 22177 2 cpu0: timer 22062162 2000 irq256: em014825 1 irq257: ahci04874088441 cpu3: timer 22054239 1999 cpu1: timer 22054150 1999 cpu2: timer 22054168 1999 Total 93176250 8446 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz (2793.67-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x179ae3bfSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,TSCDLT,AESNI,XSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 17179869184 (16384 MB) avail memory = 16434216960 (15672 MB) ACPI APIC Table: INTEL DQ67SW FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ichwd module loaded cryptosoft0: software crypto on motherboard aesni0: AES-CBC,AES-XTS on motherboard acpi0: INTEL DQ67SW on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 850 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 vgapci0: VGA-compatible display port 0xf000-0xf03f mem 0xfb40-0xfb7f,0xc000-0xcfff irq 16 at device 2.0 on pci0 pci0: simple comms at device 22.0 (no driver attached) atapci0: Intel ATA controller port 0xf130-0xf137,0xf120-0xf123,0xf110-0xf117,0xf100-0xf103,0xf0f0-0xf0ff irq 18 at device 22.2 on pci0 atapci0: [ITHREAD] ata2: ATA channel at channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel at channel 1 on atapci0 ata3: [ITHREAD] uart2: Non-standard ns8250 class UART with FIFOs port 0xf0e0-0xf0e7 mem 0xfbc29000-0xfbc29fff irq 17 at device 22.3 on pci0 uart2: [FILTER] em0: Intel(R) PRO/1000 Network Connection 7.3.2 port 0xf080-0xf09f mem 0xfbc0-0xfbc1,0xfbc28000-0xfbc28fff irq 20 at device 25.0 on pci0 em0: Using an MSI interrupt em0: [FILTER] em0: Ethernet address: 00:22:4d:52:5c:34 ehci0: EHCI (generic) USB 2.0 controller mem 0xfbc27000-0xfbc273ff irq 16 at device 26.0 on pci0 ehci0: [ITHREAD] usbus0: EHCI version 1.0 usbus0: EHCI (generic) USB 2.0 controller on ehci0 pci0: multimedia, HDA at device 27.0 (no driver attached) pcib2: ACPI PCI-PCI bridge irq 17 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: HPQ 10/100/1000 Copper Based Gigabit Adapter, ASIC rev. 0x004001 mem 0xfbb1-0xfbb1 irq 16 at device 0.0 on pci2 bge0: CHIP ID 0x4001; ASIC REV 0x04; CHIP REV 0x40; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5750 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: 00:10:18:14:15:43 bge0: [ITHREAD] pcib3: ACPI PCI-PCI bridge irq 17 at device 28.4 on pci0 pci3: ACPI PCI bus on pcib3 3ware device driver for 9000 series storage controllers, version: 3.80.06.003 twa0: 3ware 9000 series Storage Controller port 0xe000-0xe0ff mem 0xd000-0xd1ff,0xfba2-0xfba20fff irq 16 at device 0.0 on pci3 twa0: [ITHREAD] twa0: INFO: (0x15: 0x1300): Controller details:: Model 9650SE-2LP, 2 ports, Firmware FE9X 4.08.00.006, BIOS BE9X 4.08.00.001 pcib4: ACPI PCI-PCI bridge irq 18 at device 28.6 on pci0
9.0-STABLE custom kernel interrupt storm irq10
Hi all, After updating the sources to 9.0-STABLE and building a custom kernel I get a interrupt storm on irq10, from messages I get that different devices use irq10. It starts after loading ums0 and wlan0 and ath0 times out then. Rebuilding the GENERIC kernel en booting does not give this interrupt storm. In the messages from GENERIC I see that the devices sing irq10 with the custom kernel use different irq,s What device or option did I comment out in the custom kernel that triggers this? In /etc/make.conf I have MODULES_OVERRIDE= cd9660 cd9660_iconv msdosfs msdosfs_iconv linux linprocfs so only the modules I (might) use are being build. The uname -a without this problem $ uname -a FreeBSD mpw 9.0-STABLE FreeBSD 9.0-STABLE #0: Sat Jan 7 12:41:51 CET 2012 root@mpw:/usr/obj/usr/src/sys/GENERIC i386 $ vmstat -i interrupt total rate irq1: atkbd01793 2 irq9: acpi021373 27 irq14: ata010404 13 irq18: ath0 uhci2 17219 22 irq19: uhci1 10129 13 irq20: hpet0 cbb0 156521202 irq23: uhci0 ehci0 2 0 irq256: hdac0 2020 2 Total 219461283 This is with the GENERIC kernel, nothing is using irq10. Below you find output of pciconf, the custom kernel config and output of messages. Thanks in advance $ pciconf -lv hostb0@pci0:0:0:0: class=0x06 card=0x01101025 chip=0x27a08086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub' class = bridge subclass = HOST-PCI vgapci0@pci0:0:2:0: class=0x03 card=0x01101025 chip=0x27a28086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller' class = display subclass = VGA vgapci1@pci0:0:2:1: class=0x038000 card=0x01101025 chip=0x27a68086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller' class = display hdac0@pci0:0:27:0: class=0x040300 card=0x01101025 chip=0x27d88086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family High Definition Audio Controller' class = multimedia subclass = HDA pcib1@pci0:0:28:0: class=0x060400 card=0x01101025 chip=0x27d08086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family PCI Express Port 1' class = bridge subclass = PCI-PCI pcib2@pci0:0:28:1: class=0x060400 card=0x01101025 chip=0x27d28086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family PCI Express Port 2' class = bridge subclass = PCI-PCI pcib3@pci0:0:28:2: class=0x060400 card=0x01101025 chip=0x27d48086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family PCI Express Port 3' class = bridge subclass = PCI-PCI uhci0@pci0:0:29:0: class=0x0c0300 card=0x01101025 chip=0x27c88086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB uhci1@pci0:0:29:1: class=0x0c0300 card=0x01101025 chip=0x27c98086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB uhci2@pci0:0:29:2: class=0x0c0300 card=0x01101025 chip=0x27ca8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB uhci3@pci0:0:29:3: class=0x0c0300 card=0x01101025 chip=0x27cb8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB UHCI Controller' class = serial bus subclass = USB ehci0@pci0:0:29:7: class=0x0c0320 card=0x01101025 chip=0x27cc8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = 'N10/ICH 7 Family USB2 EHCI Controller' class = serial bus subclass = USB pcib4@pci0:0:30:0: class=0x060401 card=0x01101025 chip=0x24488086 rev=0xe2 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Mobile PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:0:31:0: class=0x060100 card=0x01101025 chip=0x27b98086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801GBM (ICH7-M) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:0:31:1:class=0x01018a card=0x01101025 chip=0x27df8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) IDE Controller' class = mass storage subclass = ATA
Re: 9.0-STABLE custom kernel interrupt storm irq10
On Sat, 7 Jan 2012 13:17:01 +0100 Bas Smeelen b.smee...@ose.nl wrote: Hi all, After updating the sources to 9.0-STABLE and building a custom kernel I get a interrupt storm on irq10, from messages I get that different devices use irq10. It starts after loading ums0 and wlan0 and ath0 times out then. I guess device apic is mandatory Disclaimer: http://www.ose.nl/email ___ 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
interrupt storm detected
Hello All, I have a server running FreeBSD 8.2-RC1 with a 3ware 9650 24ports controller. Every now and then I am seeing the interrupt storm message. I have increased the following according to the list: hw.intr_storm_threshold=4000 but it still happens. Any advice? interrupt storm detected on irq16:; throttling interrupt source interrupt storm detected on irq16:; throttling interrupt source fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 1133 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 12087 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 1386 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 13771 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 1578 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 20487 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 571 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 20407 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). interrupt storm detected on irq16:; throttling interrupt source fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 2331 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 27599 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 2681 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 20055 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). fsync: giving up on dirty 0xff0007c7e000: tag devfs, type VCHR usecount 1, writecount 0, refcount 2690 mountedhere 0xff00079f9000 flags () v_object 0xff0007be40d8 ref 0 pages 19631 lock type devfs: EXCL by thread 0xff0007504000 (pid 7) dev da0.journal GEOM_JOURNAL: Cannot suspend file system /mnt/backups (error=35). interrupt storm detected on irq16:; throttling interrupt source Thanks! Steph ___ 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: Interrupt storm detected on irq10:; throttling interrupt source
I'm having the same issue. It's FreeBSD on a Nokia530 Firewall. The message that keeps repeating over and over is interrupt storm detected on irq12:; throttling interrupt source. Here's the vmstat -i interrupt total rate irq0: clk 31362 98 irq4: sio0 21362 67 irq6: cbb1 dc1 dc2 1 0 irq8: rtc 40020126 irq11: dc4 dc7+1 0 irq12: cbb0 dc528456 89 irq14: ata032073101 Total 153275483 I have no idea what the + means next to IRQ11. I know of a couple of people that have this problem as well. Let me know if you need any other information. Thanks, Kurt Nunke nazir-2 wrote: Hi, I'm getting these on my HP-DL165 AMD Quad Qore interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source # uname -a FreeBSD intra.umt 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 # sysctl hw.model hw.model: Quad-Core AMD Opteron(tm) Processor 2352 please advise ...TQ ___ 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 -- View this message in context: http://www.nabble.com/Interrupt-storm-detected-on-%22irq10%3A%22--throttling-interrupt-source-tp20005328p25243620.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
interrupt storm on irq 10
I purchased a NetGear WPN511 cardbus wireless adapter (atheros chipset) yesterday. The card uses irq 10, as does the firewire port and ethernet port (fxp0) on my Dell Inspiron 8100. The laptop is running FreeBSD 7.2 Release (generic kernel). When I bootup the laptop with the wireless adapter in the cardbus slot, I see messages regarding interrupt storm detected throttling interrupt source. This did not occur prior to adding the wireless adapter. If I insert the wireless adapter after bootup, I don't see the messages on the console or as dmesg output. Otherwise, the adapter works fine. Are interrupt storms a problem? Do I need to worry about them? If so, is there anything I can do about them? Thanks, Andrew ___ 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: interrupt storm on irq 10
On Wed, May 27, 2009 at 12:51:45PM -0500, Andrew Gould wrote: [...] Are interrupt storms a problem? Do I need to worry about them? If so, is there anything I can do about them? Have run across interrupt storms for the first time myself last night. Am thinking they are from interrupt sources that interrupt handlers do not fully support. So the interrupt is not being serviced and is repeatedly being invoked. Probably PCI doesn't behave the same as much simpler embedded hardware that I am used to, but the above is what an interrupt storm looks like on simple embedded hardware. My source of interrupt storms was caused by a bad SATA cable. Installed a new VIA 6421-based SATA card (selected because it was only $15) and two new hard drives for the purpose of copying files off two older drives. New drives were detected but ad4 did not work when ad6 did. Swapped drives and the other drive on ad6 worked. Thought the card was bad but decided to try swapping cables which fixed ad4 and broke ad6. Ergo, bad cable. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ 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: interrupt storm on irq 10
My source of interrupt storms was caused by a bad SATA cable. Installed a new VIA 6421-based SATA card (selected because it was only $15) and two new hard drives for the purpose of copying files off two older drives. New drives were detected but ad4 did not work when ad6 did. Swapped drives and the other drive on ad6 worked. Thought the card was bad but decided to try swapping cables which fixed ad4 and broke ad6. Ergo, bad cable. anyway very strange controller reaction to that case. i can hardly believe the way cable have to be broken to produce interrupt storm. maybe this way: controller sends message to drive, bad cable causes CRC errors, hard drive reacts with some message for that, interrupt is generated, driver in case of detected transmission problem instantly resends last commands, situation repeats. But it's contrary to what you said that interrupt storm are lots of interrupts that are not serviced by any driver. I'm not telling that you are wrong that cable produced this, but i can't find any explanation for that. any idea? ___ 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: interrupt storm on irq 10
On Wed, May 27, 2009 at 09:30:19PM +0200, Wojciech Puchar wrote: I'm not telling that you are wrong that cable produced this, but i can't find any explanation for that. One two-port controller card, two drives, two cables. Interrupt storms move from one port to the other with the suspect cable no matter which drive is connected to that cable, no matter which port it is connected to. Two supposedly identical SATA cables purchased together. Will purchase new cables to try tonight. -- David Kelly N4HHE, dke...@hiwaay.net Whom computers would destroy, they must first drive mad. ___ 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 got2get.net...@agora.rdrop.com 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
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
On 5/9/09, per...@pluto.rain.com per...@pluto.rain.com wrote: Paul B. Mahol one...@gmail.com wrote: On 5/8/09, per...@pluto.rain.com 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=51READY,DSC,ERROR error=4ABORTED 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 one...@gmail.com wrote: On 5/9/09, per...@pluto.rain.com per...@pluto.rain.com wrote: Paul B. Mahol one...@gmail.com wrote: On 5/8/09, per...@pluto.rain.com 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=51READY,DSC,ERROR error=4ABORTED 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 per...@pluto.rain.com wrote: Paul B. Mahol one...@gmail.com wrote: On 5/9/09, per...@pluto.rain.com per...@pluto.rain.com wrote: Paul B. Mahol one...@gmail.com wrote: On 5/8/09, per...@pluto.rain.com 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=51READY,DSC,ERROR error=4ABORTED 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 one...@gmail.com wrote: On 5/10/09, per...@pluto.rain.com 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=51READY,DSC,ERROR error=4ABORTED 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
On 5/8/09, per...@pluto.rain.com 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=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 67100672 (63 MB) avail memory = 51662848 (49 MB) ... atapci1: VIA 6421 SATA150 controller port 0x1800-0x180f,0x14f0-0x14ff,0x14e0-0x14ef,0x14d0-0x14df,0x14a0-0x14bf,0x1000-0x10ff irq 9 at device 16.0 on pci0 atapci1: [ITHREAD] ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ata4: ATA channel 2 on atapci1 ata4: [ITHREAD] ... ad6: FAILURE - SET_MULTI status=51READY,DSC,ERROR error=4ABORTED ad6: 61136MB PATRIOT MEMORY 64GB SSD 02.10104 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=51READY,DSC,ERROR error=4ABORTED 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=51READY,DSC,ERROR error=4ABORTED 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 one...@gmail.com wrote: On 5/8/09, per...@pluto.rain.com 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=51READY,DSC,ERROR error=4ABORTED 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
how to fix interrupt storm
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=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 67100672 (63 MB) avail memory = 51662848 (49 MB) ... atapci1: VIA 6421 SATA150 controller port 0x1800-0x180f,0x14f0-0x14ff,0x14e0-0x14ef,0x14d0-0x14df,0x14a0-0x14bf,0x1000-0x10ff irq 9 at device 16.0 on pci0 atapci1: [ITHREAD] ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ata4: ATA channel 2 on atapci1 ata4: [ITHREAD] ... ad6: FAILURE - SET_MULTI status=51READY,DSC,ERROR error=4ABORTED ad6: 61136MB PATRIOT MEMORY 64GB SSD 02.10104 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=51READY,DSC,ERROR error=4ABORTED 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=51READY,DSC,ERROR error=4ABORTED 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
Re: Interrupt storm detected on irq10:; throttling interrupt source
On Thu, Oct 16, 2008 at 12:20 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote: --- On Wed, 10/15/08, nazir [EMAIL PROTECTED] wrote: From: nazir [EMAIL PROTECTED] Subject: Interrupt storm detected on irq10:; throttling interrupt source To: freebsd-questions@freebsd.org Date: Wednesday, October 15, 2008, 8:44 PM Hi, I'm getting these on my HP-DL165 AMD Quad Qore interrupt storm detected on irq10:; throttling interrupt source What is on IRQ 10? You can determine this via the command: `dmesg |grep irq` then look for the line for IRQ 10 which specifies what device is there. It could be a driver problem, or it could be that the hardware there is bunk. - mdh vmstat -i output would also come in handy here. # vmstat -i interrupt total rate irq1: atkbd0 30 0 irq10: ohci0 ohci+ 8265418989 irq33: mpt049348 5 irq40: bge075482 9 cpu0: timer 16431874 1968 cpu2: timer 16424530 1967 cpu3: timer 16424557 1967 cpu1: timer 16424557 1967 cpu4: timer 16424556 1967 cpu6: timer 16424540 1967 cpu7: timer 16424521 1967 cpu5: timer 16424556 1967 Total 139793969 16743 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm detected on irq10:; throttling interrupt source
On Thu, Oct 16, 2008 at 03:23:33PM +0800, nazir wrote: On Thu, Oct 16, 2008 at 12:20 PM, Jeremy Chadwick [EMAIL PROTECTED] wrote: On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote: --- On Wed, 10/15/08, nazir [EMAIL PROTECTED] wrote: From: nazir [EMAIL PROTECTED] Subject: Interrupt storm detected on irq10:; throttling interrupt source To: freebsd-questions@freebsd.org Date: Wednesday, October 15, 2008, 8:44 PM Hi, I'm getting these on my HP-DL165 AMD Quad Qore interrupt storm detected on irq10:; throttling interrupt source What is on IRQ 10? You can determine this via the command: `dmesg |grep irq` then look for the line for IRQ 10 which specifies what device is there. It could be a driver problem, or it could be that the hardware there is bunk. - mdh vmstat -i output would also come in handy here. # vmstat -i interrupt total rate irq1: atkbd0 30 0 irq10: ohci0 ohci+ 8265418989 irq33: mpt049348 5 irq40: bge075482 9 cpu0: timer 16431874 1968 cpu2: timer 16424530 1967 cpu3: timer 16424557 1967 cpu1: timer 16424557 1967 cpu4: timer 16424556 1967 cpu6: timer 16424540 1967 cpu7: timer 16424521 1967 cpu5: timer 16424556 1967 Total 139793969 16743 Can you provide full output of dmesg? It appears you have an OCHI USB controller that is going crazy with interrupts, but there may be more devices attached to IRQ 10 which could be responsible (I think that's what the + indicates). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm detected on irq10:; throttling interrupt source
Hi, I'm getting these on my HP-DL165 AMD Quad Qore interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source # uname -a FreeBSD intra.umt 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 10:35:36 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 # sysctl hw.model hw.model: Quad-Core AMD Opteron(tm) Processor 2352 please advise ...TQ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm detected on irq10:; throttling interrupt source
--- On Wed, 10/15/08, nazir [EMAIL PROTECTED] wrote: From: nazir [EMAIL PROTECTED] Subject: Interrupt storm detected on irq10:; throttling interrupt source To: freebsd-questions@freebsd.org Date: Wednesday, October 15, 2008, 8:44 PM Hi, I'm getting these on my HP-DL165 AMD Quad Qore interrupt storm detected on irq10:; throttling interrupt source What is on IRQ 10? You can determine this via the command: `dmesg |grep irq` then look for the line for IRQ 10 which specifies what device is there. It could be a driver problem, or it could be that the hardware there is bunk. - mdh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm detected on irq10:; throttling interrupt source
On Wed, Oct 15, 2008 at 06:17:56PM -0700, mdh wrote: --- On Wed, 10/15/08, nazir [EMAIL PROTECTED] wrote: From: nazir [EMAIL PROTECTED] Subject: Interrupt storm detected on irq10:; throttling interrupt source To: freebsd-questions@freebsd.org Date: Wednesday, October 15, 2008, 8:44 PM Hi, I'm getting these on my HP-DL165 AMD Quad Qore interrupt storm detected on irq10:; throttling interrupt source What is on IRQ 10? You can determine this via the command: `dmesg |grep irq` then look for the line for IRQ 10 which specifies what device is there. It could be a driver problem, or it could be that the hardware there is bunk. - mdh vmstat -i output would also come in handy here. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: irq19 interrupt storm?
On Wednesday 17 September 2008 05:17:27 pm John Baldwin wrote: On Wednesday 17 September 2008 11:00:24 am Scott Gasch wrote: You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a dumb question: how do I fix it? I tried setting plug and play OS in the BIOS and then using device.hints to push different devices to different irqs. But every time I tried a new hint it seemed to be ignored. I was trying stuff like: set hint.atapci.1.irq=20 set hint ata.4.irq=20 (ata4 is a channel on atapci1) set hint fwhco.0.irq=20 etc... I also tried to move the dc driver to a new irq as a test. This was also seemingly ignored. I then tried turning plug and play OS off in the BIOS but I don't see anywhere to set the IRQs of the onboard SATA controllers via the menus. I'm looking for a BIOS upgrade now... any other advice? Unfortunately you can't really move PCI IRQs around. You can read about more of the gritty details here: http://people.freebsd.org/~jhb/papers/bsdcan/2007/ You might be able to shuffle some IRQs around using 'hw.pciX.Y.INTA.irq' tunables. Gah, wrong tunables. These devices are on PCI link devices, so you'd need to do something like 'hw.pci.LNKA.irq' (where LNKA is the name of the link device in the ACPI namespace). Verbose boot messages (boot -v) can tell you which link device you PCI devices are using. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: irq19 interrupt storm?
You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a dumb question: how do I fix it? I tried setting plug and play OS in the BIOS and then using device.hints to push different devices to different irqs. But every time I tried a new hint it seemed to be ignored. I was trying stuff like: set hint.atapci.1.irq=20 set hint ata.4.irq=20 (ata4 is a channel on atapci1) set hint fwhco.0.irq=20 etc... I also tried to move the dc driver to a new irq as a test. This was also seemingly ignored. I then tried turning plug and play OS off in the BIOS but I don't see anywhere to set the IRQs of the onboard SATA controllers via the menus. I'm looking for a BIOS upgrade now... any other advice? Thx, Scott On Tue, Sep 16, 2008 at 7:12 AM, Gary Jennejohn [EMAIL PROTECTED]wrote: On Mon, 15 Sep 2008 22:57:38 -0700 Scott Gasch [EMAIL PROTECTED] wrote: Hi, I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of 1 cpu is constantly being used handling irq19: uhci4 interrupts. This seems to happen both with and without any USB devices plugged in: vmstat -i interrupt total rate irq1: atkbd0 5 0 irq6: fdc0 1 0 irq17: mskc0 dc0 1180547 18 irq18: skc0 uhci2* 163250699 2512 irq19: uhci4++ 3187989508 49072 I think the ++ here indicates that two or more devices are sharing this interrupt. Try doing grep irq.*19 /var/run/dmesg.boot to see which ones. One of these devices could be the culprit. --- Gary Jennejohn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: irq19 interrupt storm?
On Wednesday 17 September 2008 11:00:24 am Scott Gasch wrote: You're right: atapci1, atapci2, fwohci0 and uhci4 are all sharing the same irq (19) while irqs 20, 21, 22 at least seem completely unused. Here's a dumb question: how do I fix it? I tried setting plug and play OS in the BIOS and then using device.hints to push different devices to different irqs. But every time I tried a new hint it seemed to be ignored. I was trying stuff like: set hint.atapci.1.irq=20 set hint ata.4.irq=20 (ata4 is a channel on atapci1) set hint fwhco.0.irq=20 etc... I also tried to move the dc driver to a new irq as a test. This was also seemingly ignored. I then tried turning plug and play OS off in the BIOS but I don't see anywhere to set the IRQs of the onboard SATA controllers via the menus. I'm looking for a BIOS upgrade now... any other advice? Unfortunately you can't really move PCI IRQs around. You can read about more of the gritty details here: http://people.freebsd.org/~jhb/papers/bsdcan/2007/ You might be able to shuffle some IRQs around using 'hw.pciX.Y.INTA.irq' tunables. Probably you have a device driver whose interrupt handler isn't handling some condition. I would suspect ata as it's interrupt handler is rather simplistic with no chipset-specific hooks, and I've seen several reports of interrupt storms with ata(4) recently. Thx, Scott On Tue, Sep 16, 2008 at 7:12 AM, Gary Jennejohn [EMAIL PROTECTED]wrote: On Mon, 15 Sep 2008 22:57:38 -0700 Scott Gasch [EMAIL PROTECTED] wrote: Hi, I'm running freebsd 7.0-RELEASE-p4 on a 4-core amd64 box. Nearly 100% of 1 cpu is constantly being used handling irq19: uhci4 interrupts. This seems to happen both with and without any USB devices plugged in: vmstat -i interrupt total rate irq1: atkbd0 5 0 irq6: fdc0 1 0 irq17: mskc0 dc0 1180547 18 irq18: skc0 uhci2* 163250699 2512 irq19: uhci4++ 3187989508 49072 I think the ++ here indicates that two or more devices are sharing this interrupt. Try doing grep irq.*19 /var/run/dmesg.boot to see which ones. One of these devices could be the culprit. --- Gary Jennejohn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 To unsubscribe, send any mail to [EMAIL PROTECTED] -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
interrupt storm detected
I'm getting, interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source interrupt storm detected on irq10:; throttling interrupt source Slowly filling up my console. I've seen previous threads about this from Googling, but no resolution or discussion of whether it is performance impacting or just an annoyance. So, is there a resolution? If not, is it going to impact performance or is it just an annoyance? I'm getting these on a Soekris net5501. IRQ 10 is owned by a ath(4) NIC, ath0: Atheros 5212 mem 0xa001-0xa001 irq 10 at device 14.0 on pci0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:1d:6a:36:49:ca ath0: mac 7.9 phy 4.5 radio 5.6 The OS is, uname -a FreeBSD net5501.pumpky.net 7.0-STABLE FreeBSD 7.0-STABLE #3: Tue Jun 24 12:48:46 PDT 2008 [EMAIL PROTECTED]:/home/cjc/obj/usr/src/sys/NET5501 i386 Here's the dmesg.boot (note the message about glxsb0 using IRQ 10 is bogus; I get the interrupt storm messages when that device is not built into the kernel), Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #3: Tue Jun 24 12:48:46 PDT 2008 [EMAIL PROTECTED]:/home/cjc/obj/usr/src/sys/NET5501 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Geode(TM) Integrated Processor by AMD PCS (499.90-MHz 586-class CPU) Origin = AuthenticAMD Id = 0x5a2 Stepping = 2 Features=0x88a93dFPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CLFLUSH,MMX AMD Features=0xc040MMX+,3DNow!+,3DNow! real memory = 536870912 (512 MB) avail memory = 515977216 (492 MB) K6-family MTRR support enabled (2 registers) ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cryptosoft0: software crypto on motherboard cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 Geode LX: Soekris net5501 comBIOS ver. 1.33b 20080501 Copyright (C) 2000-2008 MFGPT bar: f0016200 glxsb0: AMD Geode LX Security Block (AES-128-CBC,RNG) mem 0xa000-0xa0003fff irq 10 at device 1.2 on pci0 glxsb0: [ITHREAD] vr0: VIA VT6105M Rhine III 10/100BaseTX port 0xe100-0xe1ff mem 0xa0004000-0xa00040ff irq 11 at device 6.0 on pci0 vr0: Quirks: 0x6 vr0: Revision: 0x96 miibus0: MII bus on vr0 ukphy0: Generic IEEE 802.3u media interface PHY 1 on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:00:24:ca:91:b4 vr0: [ITHREAD] vr1: VIA VT6105M Rhine III 10/100BaseTX port 0xe200-0xe2ff mem 0xa0004100-0xa00041ff irq 5 at device 7.0 on pci0 vr1: Quirks: 0x6 vr1: Revision: 0x96 miibus1: MII bus on vr1 ukphy1: Generic IEEE 802.3u media interface PHY 1 on miibus1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr1: Ethernet address: 00:00:24:ca:91:b5 vr1: [ITHREAD] vr2: VIA VT6105M Rhine III 10/100BaseTX port 0xe300-0xe3ff mem 0xa0004200-0xa00042ff irq 9 at device 8.0 on pci0 vr2: Quirks: 0x6 vr2: Revision: 0x96 miibus2: MII bus on vr2 ukphy2: Generic IEEE 802.3u media interface PHY 1 on miibus2 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr2: Ethernet address: 00:00:24:ca:91:b6 vr2: [ITHREAD] vr3: VIA VT6105M Rhine III 10/100BaseTX port 0xe400-0xe4ff mem 0xa0004300-0xa00043ff irq 12 at device 9.0 on pci0 vr3: Quirks: 0x6 vr3: Revision: 0x96 miibus3: MII bus on vr3 ukphy3: Generic IEEE 802.3u media interface PHY 1 on miibus3 ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr3: Ethernet address: 00:00:24:ca:91:b7 vr3: [ITHREAD] ath0: Atheros 5212 mem 0xa001-0xa001 irq 10 at device 14.0 on pci0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:1d:6a:36:49:ca ath0: mac 7.9 phy 4.5 radio 5.6 isab0: PCI-ISA bridge at device 20.0 on pci0 isa0: ISA bus on isab0 atapci0: AMD CS5536 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 20.2 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] ohci0: OHCI (generic) USB controller mem 0xa002-0xa0020fff irq 15 at device 21.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 uhub0: 4 ports with 4 removable, self powered ehci0: EHCI (generic) USB 2.0 controller mem 0xa0021000-0xa0021fff irq 15 at device 21.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: EHCI (generic) USB 2.0 controller on ehci0 usb1: USB revision 2.0 uhub1: AMD EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 on usb1 uhub1: 4 ports with 4 removable, self powered orm0: ISA Option ROM at iomem 0xc8000
Re: Re[4]: Fwd: twe0 interrupt storm
Dear Daniel, I have moved two disks to motherboard controller, cvsuped sources to 7.0-STABLE and recompiled kernel and world. gmirrored disks (RAID-1). Server worked good for about 6 hours, and than again, interrupt storm detected on irq22:; throttling interrupt source gans# vmstat -i interrupt total rate irq1: atkbd0 3 0 irq9: acpi01 0 irq16: ohci0 1 0 irq17: ohci1 ohci3 1 0 irq18: ohci2 ohci4 1 0 irq22: atapci01195017654 55266 cpu0: timer 43244319 1999 cpu1: timer 43244059 1999 Total 1281506039 59265 last pid: 75968; load averages: 2.54, 2.57, 2.60up 0+06:01:20 20:20:15 292 processes: 1 running, 290 sleeping, 1 zombie CPU: 21.8% user, 0.0% nice, 12.9% system, 0.6% interrupt, 64.7% idle Mem: 1033M Active, 435M Inact, 379M Wired, 51M Cache, 210M Buf, 37M Free Swap: 4128M Total, 296M Used, 3832M Free, 7% Inuse Maybe there is a way not to move from hetzner? No additional devices are attached to motherboard. I remember that server worked on 6.2-STABLE without these storms, but there were not so much processes. Best Regards, Stanislav 2008/6/15 Daniel Gerzo [EMAIL PROTECTED]: Hello Stanislav, Sunday, June 15, 2008, 12:40:57 PM, you wrote: Dear Daniel, Please tell me you had this storms only with 3ware 8006-2LP? Actually, I do have them on the boxes which do not have the raid controller. I have several boxes in hetzner. The ones that does not have any additional devices attached to the motherboard seem like not having the problem. However most of my machines have at least additional NIC device. Please note that my machines does not crash even when there is an interrupt storm. On the other hand, they suffer from some performance problems :/ The funny thing is that after reboot there's some silent period of time, when the interrupts are OK. After the systems becomes to be loaded more, the interrupt rate increases unless it reaches around 350k interrupt rate... I have tried to play with the BIOS settings, nothing really helped. Because as I remember on MSI motherboard controller, I have no problems with FreeBSD 6.2, but when I upgraded to FreeBSD 7.0 that storms appeared, but not so often as with 3ware. P.S. Maybe I have to ask them to update BIOS? I am so happy with their network and service, don't want to move to another server... I have tried to ask them to update the BIOS in the past, AFAIR they replied that the BIOS update is up to me... -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re[2]: Fwd: twe0 interrupt storm
Dear Daniel, Please tell me you had this storms only with 3ware 8006-2LP? Because as I remember on MSI motherboard controller, I have no problems with FreeBSD 6.2, but when I upgraded to FreeBSD 7.0 that storms appeared, but not so often as with 3ware. P.S. Maybe I have to ask them to update BIOS? I am so happy with their network and service, don't want to move to another server... Kind Regards 2008/6/15 Daniel Gerzo [EMAIL PROTECTED]: Hello FreeBSD, Saturday, June 14, 2008, 4:38:10 PM, you wrote: Be careful with hetzner.de hosting, here is their answer: The controller is compatible with the mainboard. With linux there are no problems. FreeBSD is also not officially supported by us (only Debian/Ubuntu/Suse). Yea, I know they do not officialy support FreeBSD, unluckily :-( These interrupt storms are the only problem I have with hetzner.de... -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[4]: Fwd: twe0 interrupt storm
Hello Stanislav, Sunday, June 15, 2008, 12:40:57 PM, you wrote: Dear Daniel, Please tell me you had this storms only with 3ware 8006-2LP? Actually, I do have them on the boxes which do not have the raid controller. I have several boxes in hetzner. The ones that does not have any additional devices attached to the motherboard seem like not having the problem. However most of my machines have at least additional NIC device. Please note that my machines does not crash even when there is an interrupt storm. On the other hand, they suffer from some performance problems :/ The funny thing is that after reboot there's some silent period of time, when the interrupts are OK. After the systems becomes to be loaded more, the interrupt rate increases unless it reaches around 350k interrupt rate... I have tried to play with the BIOS settings, nothing really helped. Because as I remember on MSI motherboard controller, I have no problems with FreeBSD 6.2, but when I upgraded to FreeBSD 7.0 that storms appeared, but not so often as with 3ware. P.S. Maybe I have to ask them to update BIOS? I am so happy with their network and service, don't want to move to another server... I have tried to ask them to update the BIOS in the past, AFAIR they replied that the BIOS update is up to me... -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: twe0 interrupt storm
Hello Stanislav, Thursday, June 12, 2008, 3:45:36 PM, you wrote: Hi, I have problem on FreeBSD 6.2, 7.0 with 3ware 8006-2LP RAID-1 controller: Is it MSI mobo by any cnance? I am seeing these interrupt storms on a few boxes (irq21 too, twe(4) or fxp(4) attached to these) with an Base Board Information Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD Product Name: MS-7368 Version: 1.0 I was unable so far to fix this problem...seems like some hardware issue -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: twe0 interrupt storm
Dear Daniel, Yes, you're right: Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD Product Name: MS-7368 Version: 1.0 Serial Number: To Be Filled By O.E.M. UUID: Not Present Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Thank you very much! Kind Regards 2008/6/14 Daniel Gerzo [EMAIL PROTECTED]: Hello Stanislav, Thursday, June 12, 2008, 3:45:36 PM, you wrote: Hi, I have problem on FreeBSD 6.2, 7.0 with 3ware 8006-2LP RAID-1 controller: Is it MSI mobo by any cnance? I am seeing these interrupt storms on a few boxes (irq21 too, twe(4) or fxp(4) attached to these) with an Base Board Information Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD Product Name: MS-7368 Version: 1.0 I was unable so far to fix this problem...seems like some hardware issue -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: twe0 interrupt storm
Be careful with hetzner.de hosting, here is their answer: The controller is compatible with the mainboard. With linux there are no problems. FreeBSD is also not officially supported by us (only Debian/Ubuntu/Suse). Sorry, but it is not possible to buy a new model only for a few customers. 2008/6/14 Stanislav [EMAIL PROTECTED]: Dear Daniel, Yes, you're right: Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD Product Name: MS-7368 Version: 1.0 Serial Number: To Be Filled By O.E.M. UUID: Not Present Wake-up Type: Power Switch SKU Number: To Be Filled By O.E.M. Family: To Be Filled By O.E.M. Thank you very much! Kind Regards 2008/6/14 Daniel Gerzo [EMAIL PROTECTED]: Hello Stanislav, Thursday, June 12, 2008, 3:45:36 PM, you wrote: Hi, I have problem on FreeBSD 6.2, 7.0 with 3ware 8006-2LP RAID-1 controller: Is it MSI mobo by any cnance? I am seeing these interrupt storms on a few boxes (irq21 too, twe(4) or fxp(4) attached to these) with an Base Board Information Manufacturer: MICRO-STAR INTERANTIONAL CO.,LTD Product Name: MS-7368 Version: 1.0 I was unable so far to fix this problem...seems like some hardware issue -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re[2]: Fwd: twe0 interrupt storm
Hello FreeBSD, Saturday, June 14, 2008, 4:38:10 PM, you wrote: Be careful with hetzner.de hosting, here is their answer: The controller is compatible with the mainboard. With linux there are no problems. FreeBSD is also not officially supported by us (only Debian/Ubuntu/Suse). Yea, I know they do not officialy support FreeBSD, unluckily :-( These interrupt storms are the only problem I have with hetzner.de... -- Best regards, Danielmailto:[EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: twe0 interrupt storm
Hi, I have problem on FreeBSD 6.2, 7.0 with 3ware 8006-2LP RAID-1 controller: Model 8006-2LP Serial # L018501C7271467 Firmware FE8S 1.05.00.068 Driver1.50.01.002 BIOS BE7X 1.08.00.048 Monitor ME7X 1.01.00.040 Memory Installed 512 kB # of Ports2 # of Drives 2 # of Units1 Jun 11 21:38:00 gans kernel: twe0: 3ware Storage Controller. Driver version 1.50.01.002 port 0xe800-0xe80f mem 0xfebffc00-0xfebffc0f,0xfe00-0xfe7f irq 20 at device 2.0 on pci3 Jun 11 21:38:00 gans kernel: twe0: [GIANT-LOCKED] Jun 11 21:38:00 gans kernel: twe0: [ITHREAD] Jun 11 21:38:00 gans kernel: twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 /var/log/messages Jun 10 14:51:36 gans kernel: interrupt storm detected on irq21:; throttling interrupt source Jun 10 14:52:07 gans last message repeated 31 times Jun 10 14:54:08 gans last message repeated 121 times Jun 10 15:04:09 gans last message repeated 598 times Jun 10 15:14:10 gans last message repeated 599 times Jun 10 15:24:11 gans last message repeated 600 times Jun 10 15:34:12 gans last message repeated 598 times Jun 10 15:44:13 gans last message repeated 598 times Jun 10 15:54:14 gans last message repeated 600 times Jun 10 16:04:15 gans last message repeated 600 times Jun 10 16:14:16 gans last message repeated 599 times Jun 10 16:24:17 gans last message repeated 598 times [EMAIL PROTECTED] /home/sg]# vmstat -w 5 procs memory page disk faults cpu r b w avmfre flt re pi pofr sr tw0 in sy cs us sy id 8 3 0 5389M 220M 1410 23 5 3 809 1762 0 11200 1377 3451 26 15 59 7 5 0 5505M 139M 16909 188 1 0 11025 0 81 565387 182791 30440 68 18 14 1 6 0 5468M 158M 19244 35 1 0 19469 0 42 563246 217685 7941 75 22 3 6 3 0 5276M 235M 23078 7 1 0 27426 0 135 555198 118844 73807 33 20 47 0 0 0 5177M 283M 9636 3 1 0 20972 0 108 564052 144113 6643 29 14 57 5 0 0 5176M 284M 8968 7 0 0 8607 0 22 567849 143837 6767 27 12 60 9 1 0 5199M 268M 14417 0 0 0 25905 0 31 567551 249480 6951 48 22 29 1 3 0 5341M 201M 8095 16 25 0 5087 0 112 565233 63826 6777 28 8 63 1 4 0 5356M 184M 30195 11 2 0 38720 0 95 560968 137901 52156 71 22 7 1 3 0 5266M 225M 13461 2 1 0 15518 0 46 564340 101664 9105 33 13 54 [EMAIL PROTECTED] /home/sg]# vmstat -i interrupt total rate irq1: atkbd0 4 0 irq16: ohci0 1 0 irq17: ohci1 ohci3 1 0 irq18: ohci2 ohci4 1 0 irq21: twe0 38629583391 101980 cpu0: timer757587412 1999 cpu1: timer757587403 1999 Total40144758213 105980 I have recompiled kernel to 6.2-STABLE, 7.0-RELEASE, 7.0-RELEASE-p1, 7.0-STABLE but error persists. System work good for some time (few days) and than vmstat -i irq20; rate increases from 60-90 to 10+ and than system hangs. After reboot system work good for some time. I have replaced sever, moved disks to another server with same hardware (and controller), and error persists. Kind Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm with 7.0
lysergius2001 wrote: Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and now have a continuous interrupt storm on IRQ17. This is a shared IRQ for ath0 and echi0. Never saw this on 6.3??? Any suggestions? Just another contribution to the collection of interrupt storms maybe related to ath: Whenever I plug in my ath1 on cardbus0, I get exactly one storm: interrupt storm detected on irq10:; throttling interrupt source ath1: Atheros 5212 mem 0xd022-0xd022 irq 10 at device 0.0 on cardbus0 Anyhow, I am not sure, if it is really ath causing this. During boot, I get one storm, too, that is on irq 10, but my ath0 on pci2 is on irq 9: ath0: Atheros 5212 mem 0xd020-0xd020 irq 9 at device 4.0 on pci2 [...] interrupt storm detected on irq10:; throttling interrupt source I do not get interrupt storms on irq 9 and I have already had that storm before I replaced my minipci iwi0 with ath0: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078684.html The reply to that posting was that it is probably related to USB: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078687.html Moreover, I have a bunch of other devices sharing irq 10: vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd800-0xdfff,0xd010-0xd010 irq 10 at device 0.0 on pci1 uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0x1800-0x181f irq 10 at device 29.0 on pci0 uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0x1840-0x185f irq 10 at device 29.2 on pci0 ehci0: Intel 82801DB/L/M (ICH4) USB 2.0 controller mem 0xd000-0xd3ff irq 10 at device 29.7 on pci0 fwohci0: Texas Instruments TSB43AB21/A/AI/A-EP mem 0xd0218000-0xd02187ff,0xd021-0xd0213fff irq 10 at device 7.0 on pci2 pcm0: Intel ICH4 (82801DB) port 0x1c00-0x1cff,0x18c0-0x18ff mem 0xdc00-0xddff,0xd800-0xd8ff irq 10 at device 31.5 on pci0 On our problematic irq, we both have got echi0. Thus, the second storm I get upon attaching ath1 might not be directly caused by ath. No suggestions, just more data. Cheers Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm with 7.0
Subject: Re: Interrupt storm with 7.0 On Sunday 13 April 2008 14:41:51 lysergius2001 wrote: Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and now have a continuous interrupt storm on IRQ17. This is a shared IRQ for ath0 and echi0. Never saw this on 6.3??? Any suggestions? I've seen something similar on an old dell laptop, on 6.3. It would cause an interrupt storm when it got disconnected by the hostap for beacon misses. ath driver as well, not sure what it shared it with. Unfortunately, I never got around to reporting it and the machine has been destroyed by little mongrols, I mean the sweet boys. I know this doesn't help you, but at least you know that there is 'something' with the ath driver that can cause interrupt storms. Had the same problem by upgrading from FBSD-6.3 to FBSD-7.0 right up start. I think it got some thing to do with device cpufreq and shared IRQ ! I had a IRQ-storm on IRQ-10, but my iwi0 need it. well to solved the problem temporally I did compile my kernel without device cpufreq as I had on FBSD-6.3, but the down side is that my 1.8Ghz Laptop will only run very very slow with 0.228Ghz... after that (ONLY on FBSD-7.0) at the end I just removed the other PCMCIA card (a Sierra Wireless) which using IRQ-10 too, but is in no function on FreeBSD any way. after that I compiled the kernel with device cpufreq and I'm up o 1.8GHz without IRQ-storm again. I know this is not a finally solution, but I think we have to wait for FBSD-7.1 or higher to brush out all this little faults. I had a similarly problem when I was updating from FBSD-5.4 to FBSD-6.0 with the iwi0 driver, lots of IRQ-storms, had some thing to do with device cpufreq and ACPI that time too ! hope this will go away in future. --- Hanno signature.asc Description: PGP signature
Re: Interrupt storm with 7.0
On Monday 14 April 2008 11:36:43 Jan Henrik Sylvester wrote: lysergius2001 wrote: Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and now have a continuous interrupt storm on IRQ17. This is a shared IRQ for ath0 and echi0. Never saw this on 6.3??? Any suggestions? Just another contribution to the collection of interrupt storms maybe related to ath: Whenever I plug in my ath1 on cardbus0, I get exactly one storm: interrupt storm detected on irq10:; throttling interrupt source ath1: Atheros 5212 mem 0xd022-0xd022 irq 10 at device 0.0 on cardbus0 Anyhow, I am not sure, if it is really ath causing this. During boot, I get one storm, too, that is on irq 10, but my ath0 on pci2 is on irq 9: ath0: Atheros 5212 mem 0xd020-0xd020 irq 9 at device 4.0 on pci2 [...] interrupt storm detected on irq10:; throttling interrupt source I do not get interrupt storms on irq 9 and I have already had that storm before I replaced my minipci iwi0 with ath0: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078684.html The reply to that posting was that it is probably related to USB: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078687.html Moreover, I have a bunch of other devices sharing irq 10: vgapci0: VGA-compatible display port 0x3000-0x30ff mem 0xd800-0xdfff,0xd010-0xd010 irq 10 at device 0.0 on pci1 uhci0: Intel 82801DB (ICH4) USB controller USB-A port 0x1800-0x181f irq 10 at device 29.0 on pci0 uhci2: Intel 82801DB (ICH4) USB controller USB-C port 0x1840-0x185f irq 10 at device 29.2 on pci0 ehci0: Intel 82801DB/L/M (ICH4) USB 2.0 controller mem 0xd000-0xd3ff irq 10 at device 29.7 on pci0 fwohci0: Texas Instruments TSB43AB21/A/AI/A-EP mem 0xd0218000-0xd02187ff,0xd021-0xd0213fff irq 10 at device 7.0 on pci2 pcm0: Intel ICH4 (82801DB) port 0x1c00-0x1cff,0x18c0-0x18ff mem 0xdc00-0xddff,0xd800-0xd8ff irq 10 at device 31.5 on pci0 On our problematic irq, we both have got echi0. Thus, the second storm I get upon attaching ath1 might not be directly caused by ath. No suggestions, just more data. I dug through daily security runs and \o/ the machine got rebooted one time, so I got a dmesg: +uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xdce0-0xdcff irq 11 at device 7.2 on pci0 +uhci0: [GIANT-LOCKED] +ath0: Atheros 5212 mem 0x8800-0x8800 irq 11 at device 0.0 on cardbus0 +ath0: Ethernet address: 00:11:95:69:1d:eb +ath0: mac 7.9 phy 4.5 radio 5.6 Not ehci, but uhci. Still... I can't find if it had cpufreq. The kernel config I still have and it had it compiled in, but it doesn't show in the dmesg. Only power/sleep button, lid switch and thermal zone. A typical storm session looks like this: +ath0: link state changed to DOWN +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +interrupt storm detected on irq11:; throttling interrupt source +ath0: link state changed to UP -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm with 7.0
Hi Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and now have a continuous interrupt storm on IRQ17. This is a shared IRQ for ath0 and echi0. Never saw this on 6.3??? Any suggestions? Cheers -- Lysergius says Stay light and trust gravity ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm with 7.0
On Sunday 13 April 2008 14:41:51 lysergius2001 wrote: Recently installed 7.0-RELEASE on an i386 as upgrade from 6.3-RELEASE and now have a continuous interrupt storm on IRQ17. This is a shared IRQ for ath0 and echi0. Never saw this on 6.3??? Any suggestions? I've seen something similar on an old dell laptop, on 6.3. It would cause an interrupt storm when it got disconnected by the hostap for beacon misses. ath driver as well, not sure what it shared it with. Unfortunately, I never got around to reporting it and the machine has been destroyed by little mongrols, I mean the sweet boys. I know this doesn't help you, but at least you know that there is 'something' with the ath driver that can cause interrupt storms. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
SMP kernel and interrupt storm
Building 6.3-RELEASE on dual Xeon boxes, SMP kernel builds fine, all 4 CPUs launch on reboot. options SMP device apic But I get a TON of interrupts from acpi0 -- about 68,000 per second according to vmstat -i. With system at idle with almost no services running, here is output of top -S: last pid: 1026; load averages: 0.94, 0.96, 0.91 63 processes: 6 running, 42 sleeping, 15 waiting CPU states: 0.0% user, 0.0% nice, 0.0% system, 45.3% interrupt, 54.7% idle Mem: 9296K Active, 13M Inact, 28M Wired, 16K Cache, 17M Buf, 3843M Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 13 root 1 171 52 0K 8K RUN0 42:54 99.02% idle: cpu0 21 root 1 -52 -171 0K 8K CPU2 2 32:26 85.25% irq9: acpi0 11 root 1 171 52 0K 8K RUN2 10:33 12.74% idle: cpu2 Notice high load (0.94, often higher) and 45% interrupt. If turn off ACPI (set hint.apic.0.disabled=1 in loader.conf), the interrupt 'storm' ceases, but then I'm only running on one CPU. Help? -- John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI and interrupt storm--7.0 and 6.2
Hope this is the right place to post this...please correct me if this is not the case. I'm building 7.0 BETA3 (though same problem appears in 6.2-STABLE) on 2- and 4-CPU Xeon boxes. Generic SMP and custom kernel configs build fine and all CPUs launch on reboot. However, I get a lot of interrupts from ACPI. Load only settles down to around 0.4 at complete idle with almost no services running. If I turn off ACPI, obviously the interrupt 'storm' ceases, but then I lose the multiple CPUs. I don't have access to the machine(s) at the moment, but my recollection is around 75000 ACPI interrupts per second (per vmstat -i). Any suggestions? pointers? would be much appreciated. Thanks John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
kernel: interrupt storm detected on irq11:; throttling interrupt source
Hi, I bought recently wireless PCMCIA card with atheros chip. When it`s not connected to my access point (ap down, or I just brought the card up and didn`t tell it to which SSID to connect) I often see kernel: interrupt storm detected on irq11:; throttling interrupt source and my system freezes for some seconds. Is there some way I can avoid this? -- PGP KeyID: 0x3118168B Keyserver: pgp.mit.edu Key fingerprint BB50 2983 0714 36DC D02E 158A E03D 56DA 3118 168B signature.asc Description: This is a digitally signed message part.
Interrupt storm on an MS-1029 (AMD64)
I posted this question some month ago, got no replies. I recently repeated the installation with FreeBSD 6.2 and got the same results. -Robert Johnson, [EMAIL PROTECTED] STATEMENT OF PROBLEM FreeBSD 6.1 runs very slowly out of the box on my MS-1029 AMD Turion notebook computer. The first line from the output of 'ps -aux' tells that interrupt 19, in use by the ohci and cardbus systems, is consuming 80% of the CPU time: USERPID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 21 79.1 0.0 016 ?? LL 11:52AM 25:48.51 [irq19: cbb0 ohci ATTEMPTED RESOLUTIONS = I attempted to disable the affected devices in the boot configuration file /boot/device.hints. In all cases my 'hints' were ignored and the device drivers were loaded as normal. I also tried to do the equivalent with sysctls, also to no avail (though I might be doing the Wrong Thing): hint.ohci.0.disabled=1 hint.usb.0.disabled=1 hint.cardbus.0.disabled=1 hint.pccard.0.disabled=1 Booting in safe mode and with ACPI disabled did not help. I rebuilt the kernel with the cardbus driver disabled. This caused the cardbus to disappear from the problem interrupt but the ohci driver was still using irq19 and was having an interrupt storm. In the compromised state of my computer it takes 48 hours to compile a kernel, I don't have access to another computer and anyways I need USB support, so I don't want to recompile again without USB support. I installed FreeBSD 6.0 and the problem was the same. I installed FreeBSD 5.3 and there was no problem (except that I needed to disable ACPI), nor was there a problem with NetBSD 3.0, nor Linux 2.4 or 2.6. OpenBSD 3.9 also appears to suffer from an interrupt problem. DETAILED INFORMATION The computer is a Microstar MS-1029 with an AMD MT-37 Turion processor running at 2.0ghz. The Motherboard uses an ATI Radeon Xpress 200P Chipset (North Bridge RX480M, South Bridge SB400). The Graphics Card is an ATI Mobility Radeon X700 with 128 MB of dedicated RAM. The system has 1024 MB of memory. The BIOS is A1029AMS v2.70 I used the minimal installation from 6.1-RELEASE-amd64-disc1.iso # uname -a FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:04:14 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 see below for dmesg output. Windows XP reports the following information regarding IRQ 19: IRQ 19 Standard OpenHCD USB Host ControllerOK IRQ 19 Standard OpenHCD USB Host ControllerOK IRQ 19 Standard Enhanced PCI to USB Host ControllerOK IRQ 19 Ricoh R/RL/5C476(II) or Compatible CardBus Controller OK The results of running other operating systems on the computer: FreeBSD 6.1 -! ohci (USB) and cardbus interrupt storm on IRQ 19 FreeBSD 6.2 -! identical problem FreeBSD 6.0 -! identical problem FreeBSD 5.3 -- ACPI crashes on boot. No interrupt storm when booted w/o ACPI, kernel ignores spurious interrupt on IRQ 7 NetBSD 3.0 -- no problem OpenBSD 3.9 -! Apparently the same problem as with the FreeBSD 6 kernels... interrupts use 80+% of the cpu; the individual interrupts are not listed by ps... I don't know much about OpenBSD so I can't say more. Slackware 9.1 with Linux 2.4 kernel -- no interrupt problem (but disk access is slow, probably an old ATA driver) Slackware 11 with Linux 2.6 kernel -- no problem WindowsXP Professional with SP2 -- occasional spurious 'data' returned by ACPI hardware, runs fine otherwise. When I first installed FreeBSD 6.1, the install program ran fine, and at the end of the install process I checked the state of the processes using the holographic shell; there was no interrupt storm. When I tried booting my system using the install disk as a rescue disk, the system suffered from the same interrupt storm (perhaps there is a significant difference between the install configuration and the rescue configuration)? I noticed in the boot process that the computer appears to run fine through the initial boot, but at around the point that it begins processing the rc files it slows down. The slowdown appears to begin between module_register_init: MOD_LOAD (amr_linux, 0x806205d0, 0) error 6 and Entropy Harvesting:; in particular, the slowdown first appears noticeable when the ATA devices were probed (but this may just be due to waiting for devices to respond). Following up on this observation, I disabled entropy harvesting of interrupts but this did not help. Windows reports this about the IDE/ATA system: NameStandard Dual Channel PCI IDE Controller Manufacturer(Standard IDE ATA/ATAPI controllers) Status OK PNP Device ID PCI\VEN_1002DEV_4376SUBSYS_02911462REV_00\3267A616A0A1 I/O Port0xFF00-0xFF0F Driver c:\windows\system32\drivers\pciide.sys (5.1.2600.0
Interrupt storm on an MS-1029 (AMD Turion 64)
Is anyone aware of problems with FreeBSD on the MS-1029 notebook or is this a bona fide bug? -Robert Johnson, [EMAIL PROTECTED] STATEMENT OF PROBLEM FreeBSD 6.1 runs very slowly out of the box on my MS-1029 AMD Turion notebook computer. The first line from the output of 'ps -aux' tells that interrupt 19, in use by the ohci and cardbus systems, is consuming 80% of the CPU time: USERPID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 21 79.1 0.0 016 ?? LL 11:52AM 25:48.51 [irq19: cbb0 ohci ATTEMPTED RESOLUTIONS = I attempted to disable the affected devices in the boot configuration file /boot/device.hints. In all cases my 'hints' were ignored and the device drivers were loaded as normal. I also tried to do the equivalent with sysctls, also to no avail (though I might be doing the Wrong Thing): hint.ohci.0.disabled=1 hint.usb.0.disabled=1 hint.cardbus.0.disabled=1 hint.pccard.0.disabled=1 Booting in safe mode and with ACPI disabled did not help. I rebuilt the kernel with the cardbus driver disabled. This caused the cardbus to disappear from the problem process in 'ps' but the ohci driver was still using irq19 and was having an interrupt storm. In the compromised state of my computer it takes 48 hours to compile a kernel, I don't have access to another computer and I want to run with USB support, so I don't want to recompile again without USB support. I installed FreeBSD 6.0 and the problem was the same. I installed FreeBSD 5.3 and there was no problem (except that I needed to disable ACPI), nor was there a problem with NetBSD 3.0, nor Linux 2.4 or 2.6. OpenBSD 3.9 also appears to suffer from an interrupt problem. DETAILED INFORMATION The computer is a Microstar MS-1029 with an AMD MT-37 Turion processor running at 2.0ghz. The Motherboard uses an ATI Radeon Xpress 200P Chipset (North Bridge RX480M, South Bridge SB400). The Graphics Card is an ATI Mobility Radeon X700 with 128 MB of dedicated RAM. The system has 1024 MB of memory. The BIOS is A1029AMS v2.70 I used the minimal installation from 6.1-RELEASE-amd64-disc1.iso # uname -a FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:04:14 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Windows XP reports the following information regarding IRQ 19: IRQ 19 Standard OpenHCD USB Host ControllerOK IRQ 19 Standard OpenHCD USB Host ControllerOK IRQ 19 Standard Enhanced PCI to USB Host ControllerOK IRQ 19 Ricoh R/RL/5C476(II) or Compatible CardBus Controller OK The results of running other operating systems on the computer: FreeBSD 6.1 -! ohci (USB) and cardbus interrupt storm on IRQ 19 FreeBSD 6.0 -! identical problem FreeBSD 5.3 -- ACPI crashes on boot. No interrupt storm when booted without ACPI, kernel ignores spurious interrupt on IRQ 7 NetBSD 3.0 -- no problem OpenBSD 3.9 -! Apparently the same problem as with the FreeBSD 6 kernels... interrupts use 80+% of the cpu; the individual interrupts are not listed by ps... I don't know much about OpenBSD so I can't say more. Slackware 9.1 with Linux 2.4 kernel -- no interrupt problem (but disk access is slow, probably an old ATA driver) Slackware 11 with Linux 2.6 kernel -- no problem WindowsXP Professional with SP2 -- occasional spurious 'data' returned by ACPI hardware, runs fine otherwise. When I first installed FreeBSD 6.1, the install program ran fine, and at the end of the install process I checked the state of the processes using the holographic shell; there was no interrupt storm. I noticed in the boot process that the computer appears to run fine through the initial boot, but at around the point that it begins processing the rc files it slows down. # dmesg -a Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Sun May 7 04:04:14 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Turion(tm) 64 Mobile Technology MT-37 (1989.82-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f42 Stepping = 2 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow+,3DNow AMD Features2=0x1LAHF real memory = 536084480 (511 MB) avail memory = 505630720 (482 MB) ACPI APIC Table: MSIOEMAPIC ioapic0: Changing APIC ID to 1 ioapic0 Version 2.1 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: MSI 1029 on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21 acpi0: Power Button (fixed) acpi_ec0: Embedded Controller: GPE 0x6 port 0x62,0x66 on acpi0 Timecounter ACPI-fast frequency 3579545 Hz
Best Practices - interrupt storm
Hi, FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet I've found quite a bit of information about how to deal with: Interrupt storm detected in irq7:; throttling interrupt source Problem is, it's a little confusing. From what I've gathered, the options are: Use the BIOS to set the printer port to ECP, Use lptcontrol to set the port to polled mode, Use device.hints to do both IIRC, in the past, I have used lptcontrol to set polled mode, but that resulted in: too many stray irq7's, not logging any more Can anyone suggest a method to make both interrupt storm and too many stray irq7's go away? -- Thanks, Charles http://bubbabbq.homeunix.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best Practices - interrupt storm
Charles Howse [EMAIL PROTECTED] wrote: FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet I've found quite a bit of information about how to deal with: Interrupt storm detected in irq7:; throttling interrupt source Problem is, it's a little confusing. From what I've gathered, the options are: Use the BIOS to set the printer port to ECP, Use lptcontrol to set the port to polled mode, Use device.hints to do both IIRC, in the past, I have used lptcontrol to set polled mode, but that resulted in: too many stray irq7's, not logging any more Can anyone suggest a method to make both interrupt storm and too many stray irq7's go away? hw.intr_storm_threshold changes the meaning of storm, I don't know how/if it influences stray irq messages though. Fabian -- http://www.fabiankeil.de/ signature.asc Description: PGP signature
RE: Best Practices - interrupt storm
Stray irq 7 messages The FBSD FAQ entry says 5.24. What does ``stray IRQ'' mean? Stray IRQs are indications of hardware IRQ glitches, mostly from hardware that removes its interrupt request in the middle of the interrupt request acknowledge cycle. One has three options for dealing with this: 1. Live with the warnings. All except the first 5 per IRQ are suppressed anyway. 2. Break the warnings by changing 5 to 0 in isa_strayintr() so that all the warnings are suppressed. 3. Break the warnings by installing parallel port hardware that uses IRQ 7 and the PPP driver for it (this happens on most systems), and install an IDE drive or other hardware that uses IRQ 15 and a suitable driver for it. ** End of FAQ # 5.24 * The number 3 item above is false, the ATA IDE standard is the primary IDE channel master and slave devices use IRQ 14 and the secondary IDE channel master and slave devices use IRQ 15. IRQ 15 is also used by many NIC cards. A printer attached to the parallel port uses IRQ 7, and the annoying bogus stray IRQ 7 messages still gets issued. So you are left with two options, learn to deal with it, or hack the code to make it go away. To stop the annoying bogus stray IRQ 7 messages you can hack the source where these messages originate from and change the counter value 5 to 0 so the messages will no longer be issued. isa_strayintr lives in /usr/src/sys/i386/isa/intr_machdep.c cd /usr/src/sys/i386/i386/ cp intr_machdep.c intr_machdep.c.org # make backup of original ee intr_machdep.c Find isa_strayintr to locate the start of the stray IRQ 7 logic change this if (intrcnt[1 + intr] = 5) To this if (intrcnt[1 + intr] = 0) Recompile your kernel source and those stray IRQ 7 messages are gone. Document this some place for yourself just in case you reinstall from CDROM. Remember that if you cvsup update your source to upgrade to next stable release, your 'stray IRQ 7 hack' will be stepped on and return back to the official FBSD version. You will have to reapply this hack. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Charles Howse Sent: Tuesday, May 23, 2006 10:14 AM To: FreeBSD Questions Subject: Best Practices - interrupt storm Hi, FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet I've found quite a bit of information about how to deal with: Interrupt storm detected in irq7:; throttling interrupt source Problem is, it's a little confusing. From what I've gathered, the options are: Use the BIOS to set the printer port to ECP, Use lptcontrol to set the port to polled mode, Use device.hints to do both IIRC, in the past, I have used lptcontrol to set polled mode, but that resulted in: too many stray irq7's, not logging any more Can anyone suggest a method to make both interrupt storm and too many stray irq7's go away? -- Thanks, Charles http://bubbabbq.homeunix.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best Practices - interrupt storm
Charles Howse [EMAIL PROTECTED] wrote: FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet I've found quite a bit of information about how to deal with: Interrupt storm detected in irq7:; throttling interrupt source Problem is, it's a little confusing. From what I've gathered, the options are: Use the BIOS to set the printer port to ECP, Use lptcontrol to set the port to polled mode, Use device.hints to do both IIRC, in the past, I have used lptcontrol to set polled mode, but that resulted in: too many stray irq7's, not logging any more Can anyone suggest a method to make both interrupt storm and too many stray irq7's go away? I always set to EPP in BIOS and device.hints to 0x24 (used to compile into kernel pre 5.X). (I suspect one or the other would do, and ECP would do instead of EPP, or 0x28 instead of 0x24). Haven't had an interrupt storm or stray interrupt since. man ppc for the flags to use and get into practice converting hex to binary and vice versa :-) Never used lptcontrol. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Best Practices - interrupt storm
Thanks very much, I'll also make a note to check the FAQ before posting. On May 23, 2006, at 10:45 AM, fbsd wrote: Stray irq 7 messages The FBSD FAQ entry says 5.24. What does ``stray IRQ'' mean? Stray IRQs are indications of hardware IRQ glitches, mostly from hardware that removes its interrupt request in the middle of the interrupt request acknowledge cycle. One has three options for dealing with this: 1. Live with the warnings. All except the first 5 per IRQ are suppressed anyway. 2. Break the warnings by changing 5 to 0 in isa_strayintr() so that all the warnings are suppressed. 3. Break the warnings by installing parallel port hardware that uses IRQ 7 and the PPP driver for it (this happens on most systems), and install an IDE drive or other hardware that uses IRQ 15 and a suitable driver for it. ** End of FAQ # 5.24 * The number 3 item above is false, the ATA IDE standard is the primary IDE channel master and slave devices use IRQ 14 and the secondary IDE channel master and slave devices use IRQ 15. IRQ 15 is also used by many NIC cards. A printer attached to the parallel port uses IRQ 7, and the annoying bogus stray IRQ 7 messages still gets issued. So you are left with two options, learn to deal with it, or hack the code to make it go away. To stop the annoying bogus stray IRQ 7 messages you can hack the source where these messages originate from and change the counter value 5 to 0 so the messages will no longer be issued. isa_strayintr lives in /usr/src/sys/i386/isa/intr_machdep.c cd /usr/src/sys/i386/i386/ cp intr_machdep.c intr_machdep.c.org # make backup of original ee intr_machdep.c Find isa_strayintr to locate the start of the stray IRQ 7 logic change this if (intrcnt[1 + intr] = 5) To this if (intrcnt[1 + intr] = 0) Recompile your kernel source and those stray IRQ 7 messages are gone. Document this some place for yourself just in case you reinstall from CDROM. Remember that if you cvsup update your source to upgrade to next stable release, your 'stray IRQ 7 hack' will be stepped on and return back to the official FBSD version. You will have to reapply this hack. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Charles Howse Sent: Tuesday, May 23, 2006 10:14 AM To: FreeBSD Questions Subject: Best Practices - interrupt storm Hi, FreeBSD 6.1-RELEASE, cups-1.1.23.0_1, HP 1100 LaserJet I've found quite a bit of information about how to deal with: Interrupt storm detected in irq7:; throttling interrupt source Problem is, it's a little confusing. From what I've gathered, the options are: Use the BIOS to set the printer port to ECP, Use lptcontrol to set the port to polled mode, Use device.hints to do both IIRC, in the past, I have used lptcontrol to set polled mode, but that resulted in: too many stray irq7's, not logging any more Can anyone suggest a method to make both interrupt storm and too many stray irq7's go away? -- Thanks, Charles http://bubbabbq.homeunix.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- How I make Great Barbecue - http://bubbabbq.homeunix.net/bbq.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interrupt storm
Mark Busby wrote: Checking /var/log/messages after loading snd_emu10k1, I see the following. muz kernel: pcm1: Creative EMU10K1 port 0xd800-0xd81f irq 4 at device 9.0 on pci0 muz kernel: Interrupt storm detected on irq4: atapci0; throttling interrupt source muz kernel: pcm1: SigmaTel STAC9708/11 AC97 Codec muz kernel: emujoy0: detached Upon. muz# vmstat -i interrupt total rate irq0: clk 933473998 irq4: pcm0 atapci0 1213 1 irq7: ppc0 1 0 irq8: rtc 119494127 irq11: dc0 1001 1 irq13: npx01 0 irq14: ata0 46 0 Total1055229 1128 [...] I have added to /boot/device.hints the following lines to try to force pcm to another IRQ but no joy hint.pcm.0.at=isa hint.pcm.0.irq=5 hint.pcm.0.drq=1 hint.pcm.0.flags=0x0 Is there a way to move the sound to another irq? or the atapci? and HOW? Try to place the soundcard on another PCI-Slot. This will help you most probably. HTH, Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
interrupt storm
Checking /var/log/messages after loading snd_emu10k1, I see the following. muz kernel: pcm1: Creative EMU10K1 port 0xd800-0xd81f irq 4 at device 9.0 on pci0 muz kernel: Interrupt storm detected on irq4: atapci0; throttling interrupt source muz kernel: pcm1: SigmaTel STAC9708/11 AC97 Codec muz kernel: emujoy0: detached Upon. muz# vmstat -i interrupt total rate irq0: clk 933473998 irq4: pcm0 atapci0 1213 1 irq7: ppc0 1 0 irq8: rtc 119494127 irq11: dc0 1001 1 irq13: npx01 0 irq14: ata0 46 0 Total1055229 1128 ### muz# pciconf -lv [EMAIL PROTECTED]:0:0: class=0x06 card=0x154110b9 chip=0x154110b9 rev=0x04 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M1541 Aladdin V/V+ AGP System Controller' class= bridge subclass = HOST-PCI [EMAIL PROTECTED]:1:0: class=0x060400 card=0x00e0 chip=0x524310b9 rev=0x04 hdr=0x01 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M1541 PCI to AGP Bridge' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:2:0: class=0x0c0310 card=0x chip=0x523710b9 rev=0x03 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M5237 OpenHCI 1.1 USB Controller' class= serial bus subclass = USB [EMAIL PROTECTED]:3:0: class=0x068000 card=0x710110b9 chip=0x710110b9 rev=0x00 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M7101 Power Management Controller' class= bridge [EMAIL PROTECTED]:7:0: class=0x060100 card=0x chip=0x153310b9 rev=0xc3 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'ALI M1533 Aladdin IV ISA Bridge' class= bridge subclass = PCI-ISA [EMAIL PROTECTED]:9:0: class=0x040100 card=0x100a1102 chip=0x00021102 rev=0x0a hdr=0x00 vendor = 'Creative Labs' device = 'EMU1 Sound Blaster Live! (Also Live! 5.1) - OEM from DELL - CT4780' class= multimedia subclass = audio [EMAIL PROTECTED]:9:1: class=0x098000 card=0x00201102 chip=0x70021102 rev=0x0a hdr=0x00 vendor = 'Creative Labs' device = 'EMU1 Game Port' class= input device [EMAIL PROTECTED]:10:0:class=0x03 card=0x chip=0x88115333 rev=0x44 hdr=0x00 vendor = 'S3 Graphics Co., Ltd.' device = '86C732 Trio32, 86C764 Trio64, 86C765 Trio64V+ Rev 01' class= display subclass = VGA [EMAIL PROTECTED]:12:0: class=0x02 card=0xf0041385 chip=0x000211ad rev=0x21 hdr=0x00 vendor = 'Lite-On Communications Inc' device = 'NGMC169B 10/100 Ethernet (NetGear FA310TX)' class= network subclass = ethernet [EMAIL PROTECTED]:13:0: class=0x018000 card=0x4d33105a chip=0x4d30105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20267 FastTrack100 EIDE Controller' class= mass storage [EMAIL PROTECTED]:15:0: class=0x01018a card=0x chip=0x522910b9 rev=0xc1 hdr=0x00 vendor = 'Acer Labs Incorporated (ALi)' device = 'M1543 Southbridge EIDE Controller' class= mass storage subclass = ATA I have added to /boot/device.hints the following lines to try to force pcm to another IRQ but no joy hint.pcm.0.at=isa hint.pcm.0.irq=5 hint.pcm.0.drq=1 hint.pcm.0.flags=0x0 Is there a way to move the sound to another irq? or the atapci? and HOW? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm?!
Seems like the issue was in part to partially failing hardware between the drive and the controller card or a bad SCSI cable. Amusing. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm?!
This is a new error I've seen from FreeBSD. Was displayed on ttyv0 right after I started playing some music on the a remote machine from the disk shared via NFS: Interrupt storm detected on irq11: ahc0; throttling interrupt source ahc0: PCI error Interrupt at seqaddr = 0x9 ach0: Data Parity Error Detected during address or write data phase Any ideas what this means? ahc0 is the dev name for my adaptec scsi card. I also had some issues just a little earlier with RAM and the slot on the motherboard I was using (turns out the slot is bad and not the RAM), but this is sure a weird error. Thanks! -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm?!
Garrett Cooper wrote: [ ... ] Interrupt storm detected on irq11: ahc0; throttling interrupt source ahc0: PCI error Interrupt at seqaddr = 0x9 ach0: Data Parity Error Detected during address or write data phase Any ideas what this means? ahc0 is the dev name for my adaptec scsi card. I also had some issues just a little earlier with RAM and the slot on the motherboard I was using (turns out the slot is bad and not the RAM), but this is sure a weird error. Taking a look at vmstat -i, and trying to avoid interrupt sharing with other devices if possible might help. (If you can, try turning off the USB controller in your BIOS, since that commonly shares an IRQ with other devices.) If you're seeing a RAM slot going bad, it's also quite possible that your motherboard is simply corrupting data and needs to be replaced. Check cooling, check power supply... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
sound in 5.4-RELEASE snd_ich.ko Interrupt storm
Hello, after loading 'sound.ko' and 'snd_ich.ko' in my i386 notebook with 5.4-RELEASE, GENERIC kernel and the following modules: # kldstat Id Refs AddressSize Name 1 15 0xc040 5dde24 kernel 21 0xc09de000 47e4 if_tap.ko 31 0xc09e3000 d164 kqemu.ko 4 14 0xc09f1000 56270acpi.ko 51 0xc2784000 1c000ipl.ko 61 0xc2867000 17000linux.ko 72 0xc2ad2000 18000sound.ko 91 0xc2b49000 17000radeon.ko 101 0xc2af1000 5000 snd_ich.ko I detected that the box was running very slow and with high percentage of interrupts; this is aparently caused by the 'snd_ich.ko' somehow because during unload it says: # kldunload snd_ich Interrupt storm detected on irq11: cbb1 pcm0+++; throttling interrupt source pcm0: detached # kldload snd_ich pcm0: SiS 7012 port 0x1800-0x187f,0x1c00-0x1cff irq 11 at device 2.7 on pci0 pcm0: Cirrus Logic CS4299 AC97 Codec After 'kldunload snd_ich' and 'kldload snd_ich' sound works a while but the Interrupt storm comes back after some time. This problem looks similar to: http://www.freebsd.org/cgi/query-pr.cgi?pr=80114 Is there some fix available? Matthias -- Matthias Apitz / Sisis Informationssysteme GmbH Gruenwalder Weg 28g / D-82041 Oberhaching Fon: ++49 89 / 61308-351, Fax: -399, Mobile ++49 170 4527211 http://www.sisis.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
Nicklas B. Westerlund wrote: Alex Zbyslaw wrote: But if you do that, then I believe you will not be able to use the DRAC as a remote console because your virtual keyboard won't work. (not without changing to the ukbd0 from your real keyboard, which pretty much defeats the point of the virtual keyboard i.e. using it automatically from miles away). Which I'd have to prove wrong, as it works great on my end here. Or atleast it did when I tried the DRAC console, after everything was in order.. Ofcourse, I might be wrong. although I doubt it. What version of FreeBSD? AFAIU, FreeBSD only supports one console keyboard, so if you plug in ukbd1 and make it the console, the DRAC on ukbd0 shouldn't work. I'm sure I tried this and that it didn't work, but I'd be happy to be wrong. Are you sure that both your DRAC and USB work at the same time? --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
Alex Zbyslaw wrote: What version of FreeBSD? AFAIU, FreeBSD only supports one console keyboard, so if you plug in ukbd1 and make it the console, the DRAC on ukbd0 shouldn't work. I'm sure I tried this and that it didn't work, but I'd be happy to be wrong. Are you sure that both your DRAC and USB work at the same time? Alex, On those machines we're running releng_5_4. But, as I said, I might be wrong. After all, it is quite some time since I tried this. I never tried using both at the same time, but I do know that I set ukbd to 1, to be able to use the console. Then, when I was done and put the machine into pre-production I used the DRAC. (Again, this is what I remember - so I'm not going to argue points before I get a chance to try it again). The question we should ask ourselves though is why anyone would have to use a 'normal' console keyboard, when there's the DRAC console. Nick. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
This may be getting a bit Off Topic, but I always find it annoying when archive thread peter out without any conclusion... Nicklas B. Westerlund wrote: Alex Zbyslaw wrote: What version of FreeBSD? AFAIU, FreeBSD only supports one console keyboard, so if you plug in ukbd1 and make it the console, the DRAC on ukbd0 shouldn't work. I'm sure I tried this and that it didn't work, but I'd be happy to be wrong. Are you sure that both your DRAC and USB work at the same time? Alex, On those machines we're running releng_5_4. But, as I said, I might be wrong. After all, it is quite some time since I tried this. I never tried using both at the same time, but I do know that I set ukbd to 1, to be able to use the console. Then, when I was done and put the machine into pre-production I used the DRAC. (Again, this is what I remember - so I'm not going to argue points before I get a chance to try it again). The question we should ask ourselves though is why anyone would have to use a 'normal' console keyboard, when there's the DRAC console. I may have a chance to test this again, sometime, but the machine is installed remotely now and I don't know if they have a USB keyboard or not :-( If you made ukdb1 the console from the command line, then this would have gone away when the machine was rebooted. Why would you want to do this? 2 reasons I can think of: 1) There actually are sometimes staff at the remote location, and having a keyboard next to the machine makes it easier to use the console at the same time as doing hardware things like inserting CDs. (Note that you can use a local keyboard if you are fiddling with the BIOS, since it's just FreeBSD which forces one keyboard). The same issue affects PS/2 keyboards as well as USB ones, btw. 2) The DRAC keyboard through the Java app is a bit funny. Below is a quick message I wrote (not to this list) summarising my difficulties. The lack of a \ is a pain as there is rarely one on-screen to cut-and-paste. # less difficult since it's usually in some file which has other comments in it already. Neither of those *require* you to use a local keyboard, though. --Alex Here is my experienced behaviour using the Java console applet. Sometimes, when the applet starts you get these key mappings: \ - # | - ~ ALT` - | # - f ~ - F nothing produces \ If you change the mouse acceleration mode you get these instead: \ - \ | - | @ - - @ # - f ~ - F nothing produces # However, BEWARE of changing the mode when in the BIOS, as it seems to make the keyboard stop working. When in FreeBSD with a mouse, you can copy some text with the white cursor, and that seems to make the keyboard work again. That option not available in the BIOS. --Alex PS No way to paste text as yet. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
You sir, are a genius. Fixed John On Aug 27, 2005, at 6:42 AM, Nicklas B. Westerlund wrote: John Straiton wrote: Hello, I am attempting to install 5.4R on a brand new Dell PowerEdge 1850 machine. The installation goes perfectly however after the reboot, I am unable to log into the machine (or in this case, create the entropy salt) John, Let me take a quick guess.. You've got the DRAC4 card installed? If you do, that's why the keyboard doesn't work, as it defaults to the DRAC4 one (Although it's only a virtual keyboard). If that's the case, just go to singleuser, and change devd.conf and change ukbd0 to ukbd1. Nick. John Straiton [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
Nicklas B. Westerlund wrote: John Straiton wrote: Hello, I am attempting to install 5.4R on a brand new Dell PowerEdge 1850 machine. The installation goes perfectly however after the reboot, I am unable to log into the machine (or in this case, create the entropy salt) John, Let me take a quick guess.. You've got the DRAC4 card installed? If you do, that's why the keyboard doesn't work, as it defaults to the DRAC4 one (Although it's only a virtual keyboard). If that's the case, just go to singleuser, and change devd.conf and change ukbd0 to ukbd1. But if you do that, then I believe you will not be able to use the DRAC as a remote console because your virtual keyboard won't work. (not without changing to the ukbd0 from your real keyboard, which pretty much defeats the point of the virtual keyboard i.e. using it automatically from miles away). My advice is to use the DRAC as your console. You can still use a PS/2 kbd for the BIOS or from the install CD (as long as you don't pick option 8(?) boot with USB kbd). --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
Alex Zbyslaw wrote: But if you do that, then I believe you will not be able to use the DRAC as a remote console because your virtual keyboard won't work. (not without changing to the ukbd0 from your real keyboard, which pretty much defeats the point of the virtual keyboard i.e. using it automatically from miles away). Which I'd have to prove wrong, as it works great on my end here. Or atleast it did when I tried the DRAC console, after everything was in order.. Ofcourse, I might be wrong. although I doubt it. Nick. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
John Straiton wrote: Hello, I am attempting to install 5.4R on a brand new Dell PowerEdge 1850 machine. The installation goes perfectly however after the reboot, I am unable to log into the machine (or in this case, create the entropy salt) John, Let me take a quick guess.. You've got the DRAC4 card installed? If you do, that's why the keyboard doesn't work, as it defaults to the DRAC4 one (Although it's only a virtual keyboard). If that's the case, just go to singleuser, and change devd.conf and change ukbd0 to ukbd1. Nick. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt Storm Dell PowerEdge 1850
Hello, I am attempting to install 5.4R on a brand new Dell PowerEdge 1850 machine. The installation goes perfectly however after the reboot, I am unable to log into the machine (or in this case, create the entropy salt) I have noticed 2 quirky behaviors with this machine. 1) I get to just about the local package time of boot when I start seeing Interrupt storm detected on irq18: uhci; throttling interrupt source While not a solution, I got this to go away by disabling the USB ports on the system in the BIOS. I only mention it because it's the only other new behaviour I'm seeing on this machine versus the other boxes I maintain. 2) The keyboard works until the devd detects a PS2 keyboard and installs the device for it. As in, I can pick which way I'd like to boot FreeBSD from the menu and can hit keys during the probing but as soon as I see the message that it's set up the keyboard, bam..nonresponsive. As a test, I installed 4.11R on the machine tonight and it works flawlessly. The only problem is that the machine this was intending to replace is already running 5.2+ so I'll need to get this one into the 5.X arena somehow. Thoughts? John Straiton j k s @clickcom.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
* John Straiton [EMAIL PROTECTED] [2005-08-26 15:25:40 -0400]: While not a solution, I got this to go away by disabling the USB ports on the system in the BIOS. I only mention it because it's the only other new behaviour I'm seeing on this machine versus the other boxes I maintain. Bad mobo perhaps? (I'm presuming the USB is intergrated into it. Under 4.11, can you use the USB ports successfully? Thomas -- N.J. Thomas [EMAIL PROTECTED] Etiamsi occiderit me, in ipso sperabo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt Storm Dell PowerEdge 1850
John Straiton [EMAIL PROTECTED] [2005-08-26 15:25:40 -0400]: While not a solution, I got this to go away by disabling the USB ports on the system in the BIOS. I only mention it because it's the only other new behaviour I'm seeing on this machine versus the other boxes I maintain. Bad mobo perhaps? (I'm presuming the USB is intergrated into it. Under 4.11, can you use the USB ports successfully? Thomas Come to think of it, no. I tried using a USB keyboard in 4.11 and although I got a message on console to the effect of it seeing the keyboard I had just added, I was not able to log in until I swapped to a PS2 one. I think I'm going to just load a WinServer image on it long enough to see what errors pop up in that realm and try to gather a more extensive list of behaviours. Thanks for answering, 'till later.. John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
'Interrupt storm' results non-stopable noise
Hi, In some cases, when two audio events coincide (usually in gaim), I get the following message: Interrupt storm detected on irq9: pcm0 uhci2; throttling interrupt source and then there is a continuous noise that I can not stop in anyway. Does anybody knows how to resolve this (*stop* the noise)? Thanks. (please cc: me any replies) -- ___ Kostas Blekos http://a.physics.upatras.gr/~mplekos --- pgp6ycOHcOZ1E.pgp Description: PGP signature
Re: 'Interrupt storm' results non-stopable noise
Kostas Blekos wrote: Hi, In some cases, when two audio events coincide (usually in gaim), I get the following message: Interrupt storm detected on irq9: pcm0 uhci2; throttling interrupt source and then there is a continuous noise that I can not stop in anyway. Does anybody knows how to resolve this (*stop* the noise)? Thanks. (please cc: me any replies) Hello. I had a similar problem with interrupt storms when I was setting up my printer. The fix for this involved me modifying /boot/device.hints . To see what I did and if it can help you or not, please read the entire thread entitled Very slow printing with stock FreeBSD5.3 + CUPS + Gimp-Print + HPDeskJet612C from the archives shown http://lists.freebsd.org/mailman/htdig/freebsd-questions/2005-April/thread.html#84195 I hope this helps. -Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm in Compaq Presario Laptop
Dear fellows, I have a Compaq presario 1230 laptop here! FreeBSD 4.11 Installs fine but: a) USB port doesn't work b) touchpad doesn't work c) /dev/psm0 cannot be found in /dev FreeBSD 5.4 and 5.3 --- Installs fine but: a) USB port works fine b) touchpad doesn't work c) /dev/psm0 cannot be found in /dev d) time passes too quickly! 1 minute in FreeBSD 5.4 and 5.3 passes every 10 seconds. Below I attached the output of ls /dev more /etc/rc.conf dmesg Any ideas how can I fix those problems? Thanks in advance! This is my dev directory acd0 acd0t01 ad0 ad0s1 ad0s1a ad0s1b ad0s1c ad0s1d ad0s1e ad0s1f ata atkbd0 console consolectl ctty cuaa0 cuaia0 cuala0 devctl devstat fd fd0 fido geom.ctl io kbd0 klog kmem log mdctl mem net net1 net2 network nfs4 null pci ptyp0 ptyp1 ptyp2 random stderr stdin stdout sysmouse ttyd0 ttyid0 ttyld0 ttyp0 ttyp1 ttyp2 ttyv0 ttyv1 ttyv2 ttyv3 ttyv4 ttyv5 ttyv6 ttyv7 ttyv8 ttyv9 ttyva ttyvb ttyvc ttyvd ttyve ttyvf ums0 urandom usb usb0 xpt0 zero This is my /etc/rc.conf --- # -- sysinstall generated deltas -- # Sat May 21 12:34:39 2005 # Created: Sat May 21 12:34:38 2005 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. defaultrouter=195.251.194.200 hostname=nevra.materials.uoi.gr ifconfig_ed1=inet 195.251.194.137 netmask 255.255.255.128 linux_enable=YES moused_enable=NO moused_port=/dev/cuaa3 moused_type=auto sshd_enable=YES usbd_enable=YES This is my dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Cyrix GXm (24.45-MHz 586-class CPU) Origin = CyrixInstead Id = 0x540 DIR=0x3544 Stepping=3 Revision=5 real memory = 100663296 (96 MB) avail memory = 88838144 (84 MB) pnpbios: Bad PnP BIOS data checksum npx0: math processor on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 5 Entries on motherboard pci0: PCI bus on pcib0 cbb0: TI1221 PCI-CardBus Bridge at device 17.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb1: TI1221 PCI-CardBus Bridge at device 17.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 isab0: PCI-ISA bridge port 0x5000-0x500f,0x4000-0x401f,0x3000-0x307f mem 0x4001-0x40010fff at device 18.0 on pci0 isa0: ISA bus on isab0 ohci0: OHCI (generic) USB controller mem 0xfedfe000-0xfedfefff irq 9 at device 19.0 on pci0 usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x0e11) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: display, VGA at device 20.0 (no driver attached) orm0: ISA Option ROM at iomem 0xc-0xc9fff on isa0 pmtimer0 on isa0 ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 uhub1: Atmel product 0x3311, class 9/0, rev 1.00/3.00, addr 2 uhub1: 4 ports with 4 removable, self powered Timecounter TSC frequency 24447264 Hz quality 800 Timecounters tick every 10.000 msec ad0: 3100MB FUJITSU MHA2032AT/8211 [6300/16/63] at ata0-master PIO4 acd0: CDROM TOSHIBA CD-ROM XM-1702BC/1261 at ata1-master PIO4 ed1: PCMCIA Ethernet Card at port 0x300-0x31f irq 9 function 0 config 32 on pccard0 ed1: Ethernet address: 00:a0:0c:12:74:2e ed1: if_start running deferred for Giant ed1: type NE2000 (16 bit) Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted /usr: mount pending error: blocks 12 files 1 WARNING: /var was not properly dismounted /var: mount pending error: blocks 8 files 2 ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 3, iclass 3/1 ums0: 5 buttons and Z dir. uhub1: illegal enable change, port 1 Discover Yahoo!
Re: 5.3 interrupt storm (atapicam) and I/O error
Daniel I wonder if you can mount a CD with a GENERIC kernel? I also wonder if you can avoid the interrupt storm with your custom kernel but by disabling atapi dma? (hw.ata.atapi_dma=0 in /boot/loader.conf) If this kernel boots, can you mount a CD? If you get some free time and feel like messing around with it, I'd be curious what you find. Regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt [EMAIL PROTECTED] wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:38:14 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error oops, did forget the tixt file ...brbrDaniel S. Haischt schrieb:br I don't know whether this is related to your issue,br but on one of my boxes I am also getting an interruptbr storm with atapicam enabled.br br On FreeBSD 5.2.1 I did not experience any interruptbr storm issues, even if using the same hardware configuration.br br Have a look at the attached text file for a detailedbr description ...br br Olivier Certner schrieb:br br Hi,brbr Could you give a look at my post dated 04/01/2005 entitled Freeze br with CAM (using KsCD)? Maybe we have fallen on the same kind of bug br concerning atapicam.brbr If you have KDE, maybe you should try to reproduce the problem I had. br I've no time to test your scenario (the one with the EIDE drive, I br don't have SCSI) now, but I'll try to reproduce it at the beginning of br next week, in order to see if the freeze happens also on my computer.brbr Hope this will help us to progress on our issues.brbr Regards,brbr Olivierbr ___br freebsd-questions@freebsd.org mailing listbr http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbr To unsubscribe, send any mail to br [EMAIL PROTECTED]br br brbr-- brMit freundlichen Gruessen / With kind regardsbrDAn.I.El S. HaischtbrbrWant a complete signature??? Type at a shell prompt:br$ finger -l [EMAIL PROTECTED]brHello,brbrrecently I updated one of my FreeBSD boxes tobrv 5.3. This box got a builtin Promise PDC20269brUDMA133 controller. Actually it's a controllerbrwith two IDE channels.brbrSo far if using the GENERIC kernel that comesbrwith FreeBSD, I do not experience any problems.brbrIf using my own customized kernel I am gettingbrthe following error message while booting thebrsystem:brbr8 88---8-8-brInterrupt storm detected on irq10: atapci1;brthrotteling interrupt source:br888---8-8-brbrAfter some trail-and-error based investigations,brI did figure out that if I don't plugin any devicebrinto IDE channel two, the just described errorbrdoes not occur.brbrSo it has something to do with IDE channel two.brbrAs an additional note - The controller worksbrunder Linux, FreeBSD 5.3 (GENERIC) and FreeBSDbr5.2.1 (custom kernel).brbrAny hints on how to solve this issue would bebrgreatly appreciated. ___brfreebsd-questions@freebsd.org mailing listbrhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrTo unsubscribe, send any mail to [EMAIL PROTECTED]br ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
On Saturday 29 January 2005 05:30, ad5gb wrote: Greetings, Not sure what to think about this yet but it definitely has something to do with having my ATAPI CD connected to the 2nd channel of my Promise Ultra 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the kernel will boot with atapicam enabled. I don't seem to be able to use my motherboard's embedded EIDE controller with the Promise adapter installed. I don't see any obvious I/O or interrupt conflicts, but I also don't have too much control over it with this old SuperMicro mainboard. Seems odd to me though, since this all worked on 5.2.1. Open for suggestions, but for now I'm going to try to track down the SCSI I/O error problem so I can get some CD burning done (critical system backups) and then I'll see if I can try to figure out if this is an EIDE driver issue or a atapicam issue. If anyone comes up with anything in the meantime... please YELL! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt [EMAIL PROTECTED] wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:37:21 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error I don't know whether this is related to your issue,brbut on one of my boxes I am also getting an interruptbrstorm with atapicam enabled.brbrOn FreeBSD 5.2.1 I did not experience any interruptbrstorm issues, even if using the same hardware configuration.brbrHave a look at the attached text file for a detailedbrdescription ...brbrOlivier Certner schrieb:br Hi,br br Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM br (using KsCD)? Maybe we have fallen on the same kind of bug concerning br atapicam.br br If you have KDE, maybe you should try to reproduce the problem I had. I've no br time to test your scenario (the one with the EIDE drive, I don't have SCSI) br now, but I'll try to reproduce it at the beginning of next week, in order to br see if the freeze happens also on my computer.br br Hope this will help us to progress on our issues.br br Regards,br br Olivierbr ___ br I am also having a shitload of problems on my newly installed 5.3 box (which was a happy camper under 4.x. I have a promise tx2 100 board. there are a pair of disks with a geom stripe over them, Under heavy i/o the system either freezes or crashes. I will have some time later next week to investigate but I am really inclined to use the time to revert to 4.11. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
Hello, attached you will find a copy of my custom kernel config which did work without any issue under FreeBSD 5.2.1. As outlined earlier if using this config on FreeBSD 5.3-RELEASE I am getting an interrupt storm while booting the system. The following hardware configuration *won't* cause an interrupt storm on FreeBSD 5.3 if using the Promise PDC20269 controller: * harddrive attached to IDE channel #1 * no device attached to channel #2 The following hardware configuration *will* cause an interrupt storm on FreeBSD 5.3 if using the Promise PDC20269 controller: Config #1: * harddrive attached to IDE channel #1 * CDROM or CDRW attached to channel #2 Config #2: * CDROM or CDRW attached to channel #1 * harddrive attached to IDE channel #2 Jason Henson schrieb: On 01/28/05 08:38:14, Daniel S. Haischt wrote: oops, did forget the tixt file ... Daniel S. Haischt schrieb: I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM (using KsCD)? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 888---8-8- Interrupt storm detected on irq10: atapci1; throtteling interrupt source: 888---8-8- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. How about a copy of your custom changes to the kernel? Also did you get a response from Søren Schmidt [EMAIL PROTECTED], he wrote and maintains the ata stuff iirc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.369.2.2 2002/12/31 05:35:45 scottl Exp $ machine i386 #cpuI486_CPU cpu I586_CPU #cpuI686_CPU ident ABYSSONE maxusers512 #To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints #Default places to look for devices. #makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options NETATALK#AppleTalk
Re: 5.3 interrupt storm (atapicam)
Greetings, I seem to have made a little progress with the atapicam driver. It seems if I force PIO mode (hw.ata.atapi_dma=0 in /boot/loader.conf) a kernel with the atapicam device will boot. I still cannot access a disk in the drive however either via the acdx device or the new cdx device provided by the atapicam driver. Perhaps you could try adding that line in your /boot/loader.conf and see if it cures your problem -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner [EMAIL PROTECTED] wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi,brbr Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM br(using KsCD)? Maybe we have fallen on the same kind of bug concerning bratapicam.brbr If you have KDE, maybe you should try to reproduce the problem I had. I've no brtime to test your scenario (the one with the EIDE drive, I don't have SCSI) brnow, but I'll try to reproduce it at the beginning of next week, in order to brsee if the freeze happens also on my computer.brbr Hope this will help us to progress on our issues.brbr Regards,brbr Olivierbr___brfreebsd-questions@freebsd.org mailing listbrhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrTo unsubscribe, send any mail to [EMAIL PROTECTED]br ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
On 01/28/05 08:38:14, Daniel S. Haischt wrote: oops, did forget the tixt file ... Daniel S. Haischt schrieb: I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM (using KsCD)? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 888---8-8- Interrupt storm detected on irq10: atapci1; throtteling interrupt source: 888---8-8- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. How about a copy of your custom changes to the kernel? Also did you get a response from Søren Schmidt [EMAIL PROTECTED], he wrote and maintains the ata stuff iirc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter @@ -251,22 +272,22 @@ device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #deviceudbp# USB Double Bulk Pipe devices -device ugen# Generic -device uhid# Human Interface Devices -device ukbd# Keyboard -device ulpt# Printer -device umass # Disks/Mass storage - Requires scbus and da -device ums # Mouse -device urio# Diamond Rio 500 MP3 player -device uscanner# Scanners +#deviceugen# Generic +#deviceuhid# Human Interface Devices +#deviceukbd# Keyboard +#deviceulpt# Printer +#deviceumass # Disks/Mass storage - Requires scbus and da +#deviceums # Mouse +#deviceurio# Diamond Rio 500 MP3 player +#deviceuscanner# Scanners # USB Ethernet, requires mii -device aue # ADMtek USB Ethernet -device axe # ASIX Electronics USB Ethernet -device cue # CATC USB Ethernet -device kue # Kawasaki LSI USB Ethernet -device rue # RealTek RTL8150 USB Ethernet +#deviceaue # ADMtek USB Ethernet +#deviceaxe # ASIX Electronics USB Ethernet +#devicecue # CATC USB Ethernet +#devicekue # Kawasaki LSI USB Ethernet +#devicerue # RealTek RTL8150 USB Ethernet # FireWire support -device firewire# FireWire bus code -device sbp # SCSI over FireWire (Requires scbus and da) -device fwe # Ethernet over FireWire (non-standard!) +#devicefirewire# FireWire bus code +#devicesbp # SCSI over FireWire (Requires scbus and da) +#devicefwe # Ethernet over FireWire (non-standard!) -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Sat 01/29, Jason Henson [EMAIL PROTECTED] wrote: From: Jason Henson [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Sun, 30 Jan 2005 04:58:31 + Subject: Re: 5.3 interrupt storm (atapicam) and I/O error On 01/28/05 08:38:14, Daniel S. Haischt wrote:br oops, did forget the tixt file ...br br Daniel S. Haischt schrieb:br I don't know whether this is related to your issue,br but on one of my boxes I am also getting an interruptbr storm with atapicam enabled.br br On FreeBSD 5.2.1 I did not experience any interruptbr storm issues, even if using the same hardware configuration.br br Have a look at the attached text file for a detailedbr description ...br br Olivier Certner schrieb:br br Hi,br br Could you give a look at my post dated 04/01/2005 entitled Freeze br with CAM (using KsCD)? Maybe we have fallen on the same kind of br bug concerning atapicam.br br If you have KDE, maybe you should try to reproduce the problem I br had. I've no time to test your scenario (the one with the EIDE br drive, I don't have SCSI) now, but I'll try to reproduce it at the br beginn ing of next week, in order to see if the freeze happens also br on my computer.br br Hope this will help us to progress on our issues.br br Regards,br br Olivierbr ___br freebsd-questions@freebsd.org mailing listbr http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbr To unsubscribe, send any mail to freebsd-questions- br [EMAIL PROTECTED]br brbr br-- br Mit freundlichen Gruessen / With kind regardsbr DAn.I.El S. Haischtbr br Want a complete signature??? Type at a shell prompt:br $ finger -l [EMAIL PROTECTED]brbrbr Hello,br br recently I updated one of my FreeBSD boxes tobr v 5.3. This box got a builtin Promise PDC20269br UDMA133 controller. Actually it's a controllerbr with two IDE channels.br br So far if using the GENERIC kernel that comesbr with FreeBSD, I do not experi ence any problems.br br If using my own customized kernel I am gettingbr the following error message while booting thebr system:br br 888---8-8-br Interrupt storm detected on irq10: atapci1;br throtteling interrupt source:br 888---8-8-br br After some trail-and-error based investigations,br I did figure out that if I don't plugin any devicebr into IDE channel two, the just described errorbr does not occur.br br So it has something to do with IDE channel two.br br As an additional note - The controller worksbr under Linux, FreeBSD 5.3
Re: 5.3 interrupt storm (atapicam) and I/O error
Hi, Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM (using KsCD)? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM (using KsCD)? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
oops, did forget the tixt file ... Daniel S. Haischt schrieb: I don't know whether this is related to your issue, but on one of my boxes I am also getting an interrupt storm with atapicam enabled. On FreeBSD 5.2.1 I did not experience any interrupt storm issues, even if using the same hardware configuration. Have a look at the attached text file for a detailed description ... Olivier Certner schrieb: Hi, Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM (using KsCD)? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Mit freundlichen Gruessen / With kind regards DAn.I.El S. Haischt Want a complete signature??? Type at a shell prompt: $ finger -l [EMAIL PROTECTED] Hello, recently I updated one of my FreeBSD boxes to v 5.3. This box got a builtin Promise PDC20269 UDMA133 controller. Actually it's a controller with two IDE channels. So far if using the GENERIC kernel that comes with FreeBSD, I do not experience any problems. If using my own customized kernel I am getting the following error message while booting the system: 888---8-8- Interrupt storm detected on irq10: atapci1; throtteling interrupt source: 888---8-8- After some trail-and-error based investigations, I did figure out that if I don't plugin any device into IDE channel two, the just described error does not occur. So it has something to do with IDE channel two. As an additional note - The controller works under Linux, FreeBSD 5.3 (GENERIC) and FreeBSD 5.2.1 (custom kernel). Any hints on how to solve this issue would be greatly appreciated. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
Greetings, My problem might be slightly different than yours. My system hangs during the boot process whenever I boot a kernel with atapicam enabled. A can't do anything but reboot the box at that point. Maybe this is a good time to learn to use the kernel debugger. When I get home this evening I'll try a few more things. This problem didn't happen in 5.2.1. Thanks! -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Olivier Certner [EMAIL PROTECTED] wrote: From: Olivier Certner [mailto: [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 10:05:30 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error Hi,brbr Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM br(using KsCD)? Maybe we have fallen on the same kind of bug concerning bratapicam.brbr If you have KDE, maybe you should try to reproduce the problem I had. I've no brtime to test your scenario (the one with the EIDE drive, I don't have SCSI) brnow, but I'll try to reproduce it at the beginning of next week, in order to brsee if the freeze happens also on my computer.brbr Hope this will help us to progress on our issues.brbr Regards,brbr Olivierbr___brfreebsd-questions@freebsd.org mailing listbrhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrTo unsubscribe, send any mail to [EMAIL PROTECTED]br ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
Greetings, Not sure what to think about this yet but it definitely has something to do with having my ATAPI CD connected to the 2nd channel of my Promise Ultra 133 TX2 adapter (PDC20269). If I disconnect the cable from channel 2 the kernel will boot with atapicam enabled. I don't seem to be able to use my motherboard's embedded EIDE controller with the Promise adapter installed. I don't see any obvious I/O or interrupt conflicts, but I also don't have too much control over it with this old SuperMicro mainboard. Seems odd to me though, since this all worked on 5.2.1. Open for suggestions, but for now I'm going to try to track down the SCSI I/O error problem so I can get some CD burning done (critical system backups) and then I'll see if I can try to figure out if this is an EIDE driver issue or a atapicam issue. If anyone comes up with anything in the meantime... please YELL! Kind regards -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve --- On Fri 01/28, Daniel S. Haischt [EMAIL PROTECTED] wrote: From: Daniel S. Haischt [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org Date: Fri, 28 Jan 2005 14:37:21 +0100 Subject: Re: 5.3 interrupt storm (atapicam) and I/O error I don't know whether this is related to your issue,brbut on one of my boxes I am also getting an interruptbrstorm with atapicam enabled.brbrOn FreeBSD 5.2.1 I did not experience any interruptbrstorm issues, even if using the same hardware configuration.brbrHave a look at the attached text file for a detailedbrdescription ...brbrOlivier Certner schrieb:br Hi,br br Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM br (using KsCD)? Maybe we have fallen on the same kind of bug concerning br atapicam.br br If you have KDE, maybe you should try to reproduce the problem I had. I've no br time to test your scenario (the one with the EIDE drive, I don't have SCSI) br now, but I'll try to reproduce it at the beginning of next week, in order to br see if the freeze happens also on my computer.br br Hope this will help us to progress on our issues.br br Regards,br br Olivierbr ___ br freebsd-questions@freebsd.org mailing listbr http://lists.freebsd.org/mailman/listinfo/freebsd-questionsbr To unsubscribe, send any mail to [EMAIL PROTECTED]brbr-- brMit freundlichen Gruessen / With kind regardsbrDAn.I.El S. HaischtbrbrWant a complete signature??? Type at a shell prompt:br$ finger -l [EMAIL PROTECTED]br___brfreebsd-questions@freebsd.org mailing listbrhttp://lists.freebsd.org/mailman/listinfo/freebsd-questionsbrTo unsubscribe, send any mail to [EMAIL PROTECTED]br ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 interrupt storm (atapicam) and I/O error
Greetings, I've recently returned to FreeBSD (x86) after my Ultra 30 died. I've had good results with the 5.2* and 5.3 releases until I tried to copy an audio cd with cdda2wav. I'm a bit 'out-of-touch' with the changes to FBSD over the last 4 years or so and am hoping someone can point me straight. First... I tried cdda2wav on the disk in my SCSI CD drive attached to a 2940 controller. Got a boatload of messages like the following which eventually resulted in a hung process. cmd finished after 0.175s timeout 300s 1/ 1/ 1/ 51495 54573%cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: retryable error CDB: 28 00 00 02 36 4F 00 00 1A 00 status: 0x0 (GOOD STATUS) resid: 53248 cmd finished after 0.174s timeout 300s 1/ 1/ 1/ 51496 54573%cdda2wav: Input/output error. ReadStandard10: scsi sendcmd: retryable error CDB: 28 00 00 02 36 68 00 00 0C 00 status: 0x0 (GOOD STATUS) resid: 24576 So I thought I'd try enabling atapicam and trying to use my EIDE CD drive but the system hangs on boot with a message about an interrupt storm (throttling input). I tried to disable the 'atapicd' device but it didn't seem to help. Hoping someone has the magic potion for this.. Many thanks! -- Randall D. DuCharme (Radio AD5GB) Powered by FreeBSD! The Power to Serve ___ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm detected on irq20: acpi0; throttling interrupt source ???
dmesg output: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE-p5 #0: Tue Jan 25 06:15:15 EET 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKERN ACPI APIC Table: ASUS P2B-DS Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium III/Pentium III Xeon/Celeron (451.02-MHz 686-class CPU) Origin = GenuineIntel Id = 0x672 Stepping = 2 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE, MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 268423168 (255 MB) avail memory = 257204224 (245 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0 Version 1.1 irqs 0-23 on motherboard npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P2B-DS on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 20 acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xe400-0xe7ff at device 0.0 on pci0 pcib1: PCI-PCI bridge at device 1.0 on pci0 pci1: PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 4.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xd400-0xd41f irq 19 at device 4.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 4.3 (no driver attached) ahc0: Adaptec aic7890/91 Ultra2 SCSI adapter port 0xd000-0xd0ff mem 0xdf80-0xdf800fff irq 19 at device 6.0 on pci0 ahc0: [GIANT-LOCKED] aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs fxp0: Intel 82559 Pro/100 Ethernet port 0xb800-0xb83f mem 0xde80-0xde8f,0xdf00-0xdf000fff irq 18 at device 10.0 on pci0 miibus0: MII bus on fxp0 inphy0: i82555 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:d0:b7:53:a2:be fdc0: floppy drive controller port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: ECP parallel printer port port 0x778-0x77b,0x378-0x37b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: Parallel port bus on ppc0 sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: 16550A-compatible COM port port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: ISA Option ROMs at iomem 0xd4000-0xd57ff,0xc-0xca7ff 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 0xa-0xb on isa0 Timecounters tick every 10.000 msec Interrupt storm detected on irq20: acpi0; throttling interrupt source acd0: CDRW ASUS CRW-5224A/1.40 at ata1-slave UDMA33 Waiting 5 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 1 lun 0 da0: IBM DNES-318350W SA30 Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) Mounting root from ufs:/dev/da0s1a Interrupt storm detected on irq20: acpi0; throttling interrupt source Is this tell me that motherboard have any problem? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3 interrupt storm
I have read a few tips on this - but looking for something that works. I have DISABLED USB support in the bios on my IBM 305 servers. It seems FreeBSD still 'sees' USB. I copied the GENERIC kernel to TEST kernel I removed -all- USB support from the new kernel. I then rebooted and I still see this: ohci0: OHCI (generic) USB controller at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ... Interrupt storm detected on irq11: ohci0; throttling interrupt source What can I do to get rid of ALL USB support on this 5.3 system as I dont use it and dont want these 'storms' of interrupts! thanks in advance! -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 AIM:lonebanditusa // MSN:[EMAIL PROTECTED] // Yahoo:lonebanditusa ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm
On 01/20/05 19:47:12, J.D. Bronson wrote: I have read a few tips on this - but looking for something that works. I have DISABLED USB support in the bios on my IBM 305 servers. It seems FreeBSD still 'sees' USB. I copied the GENERIC kernel to TEST kernel I removed -all- USB support from the new kernel. I then rebooted and I still see this: ohci0: OHCI (generic) USB controller at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: OHCI (generic) USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ... Interrupt storm detected on irq11: ohci0; throttling interrupt source What can I do to get rid of ALL USB support on this 5.3 system as I dont use it and dont want these 'storms' of interrupts! thanks in advance! If it is not in the kernel see if the module is being loaded. Use kldstat. Did you comment out the usbd in /etc/rc.conf? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm on FreeBSD 5.3
Hello, I tried the following at the boot prompt: # unload # load /boot/kernel/kernel (- my custom kernel) # set hint.ohci.0.irq=15 The command 'show' at the boot loader prompt shows that the above device hint was set appropriatly. I did this because I set the OHCI device in the computer's bios to IRQ 15. I additionally included the above device hint in the file /boot/device.hints. Tho - During the boot process I am still getting: ohci0: SiS 5571 USB controller mem 0xe400-0xe4000fff irq 11 at device 1.2 on pci0 Which finally leads to the same interrupt storm on irq11: ohci+ Why is the device hint not recognized during the boot process? Is it because I did enable DEVICE_POLLING in my kernel configuration file? But I thought this option only belongs to network cards ... Daniel S. Haischt schrieb: Hello, Lowell Gilbert schrieb: Daniel S. Haischt [EMAIL PROTECTED] writes: I am getting the following error message during the boot process after having compiled a custom kernel for FreeBSD 5.3-RELEASE-p1. 888---8-8- Interrupt storm detected on irq11: ohci+; throtteling interrupt source 888---8-8- Are you using OHCI? Disable it if you're not. The problem here is, if disabling USB (OHCI) in the bios, the interrupt storm appears in conjuction with the device atkbd ... ... so the interrupt storm remains - no matter what I am doing. Mounting root from ufs:/dev/ad4s2a warning: KLD '/boot/kernel.save/ipfw.ko' is newer than the linker.hints file ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled Accounting enabled warning: KLD '/boot/kernel.save/linux.ko' is newer than the linker.hints file Looks like you haven't really updated everything... ___ That message is a result of booting using the old GENERIC kernel (actually it is called kernel.save/kernel). If I am using the new kernel I am not getting these error messages. But then, unfortunatly, I am getting the interrupt storm message :( -- Mit freundlichen Gruessen / With kind regards Daniel S. Haischt | phone:+49 -7032-992909 Grabenstrasse 11| +49 -700-DHAISCHT | fax: +49 -7032-992910 D-71083 Herrenberg | fax2mail: +49 -7032-7999738 GERMANY | cell: +49 -172-7668936 SIP: sip:[EMAIL PROTECTED]:5060 email: [EMAIL PROTECTED] web: http://www.daniel.stefan.haischt.name/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm on FreeBSD 5.3
Daniel S. Haischt [EMAIL PROTECTED] writes: I am getting the following error message during the boot process after having compiled a custom kernel for FreeBSD 5.3-RELEASE-p1. 888---8-8- Interrupt storm detected on irq11: ohci+; throtteling interrupt source 888---8-8- Are you using OHCI? Disable it if you're not. In the past I did use the same kernel configuration file on FreeBSD 5.2.1 which did work perfectly. A great many things changed between 5.2.1 and 5.3. Tho - If using the GENERIC kernel that comes with FreeBSD 5.3 I do not run into any problems. Can you give any hints how to solve the problem? Attached you will find the output of dmesg. Tell me if you need any additional information. Take the GENERIC kernel and your old kernel config, and use binary search to narrow down which of the differences between them causes your problem. Mounting root from ufs:/dev/ad4s2a warning: KLD '/boot/kernel.save/ipfw.ko' is newer than the linker.hints file ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled Accounting enabled warning: KLD '/boot/kernel.save/linux.ko' is newer than the linker.hints file Looks like you haven't really updated everything... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Interrupt storm on FreeBSD 5.3
Hello, Lowell Gilbert schrieb: Daniel S. Haischt [EMAIL PROTECTED] writes: I am getting the following error message during the boot process after having compiled a custom kernel for FreeBSD 5.3-RELEASE-p1. 888---8-8- Interrupt storm detected on irq11: ohci+; throtteling interrupt source 888---8-8- Are you using OHCI? Disable it if you're not. The problem here is, if disabling USB (OHCI) in the bios, the interrupt storm appears in conjuction with the device atkbd ... ... so the interrupt storm remains - no matter what I am doing. Mounting root from ufs:/dev/ad4s2a warning: KLD '/boot/kernel.save/ipfw.ko' is newer than the linker.hints file ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled Accounting enabled warning: KLD '/boot/kernel.save/linux.ko' is newer than the linker.hints file Looks like you haven't really updated everything... ___ That message is a result of booting using the old GENERIC kernel (actually it is called kernel.save/kernel). If I am using the new kernel I am not getting these error messages. But then, unfortunatly, I am getting the interrupt storm message :( -- Mit freundlichen Gruessen / With kind regards Daniel S. Haischt | phone:+49 -7032-992909 Grabenstrasse 11| +49 -700-DHAISCHT | fax: +49 -7032-992910 D-71083 Herrenberg | fax2mail: +49 -7032-7999738 GERMANY | cell: +49 -172-7668936 SIP: sip:[EMAIL PROTECTED]:5060 email: [EMAIL PROTECTED] web: http://www.daniel.stefan.haischt.name/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm on FreeBSD 5.3
Hello, I am getting the following error message during the boot process after having compiled a custom kernel for FreeBSD 5.3-RELEASE-p1. 888---8-8- Interrupt storm detected on irq11: ohci+; throtteling interrupt source 888---8-8- In the past I did use the same kernel configuration file on FreeBSD 5.2.1 which did work perfectly. Tho - If using the GENERIC kernel that comes with FreeBSD 5.3 I do not run into any problems. Can you give any hints how to solve the problem? Attached you will find the output of dmesg. Tell me if you need any additional information. -- Mit freundlichen Gruessen / With kind regards Daniel S. Haischt | phone:+49 -7032-992909 Grabenstrasse 11| +49 -700-DHAISCHT | fax: +49 -7032-992910 D-71083 Herrenberg | fax2mail: +49 -7032-7999738 GERMANY | cell: +49 -172-7668936 email: [EMAIL PROTECTED] web: http://www.daniel.stefan.haischt.name/ Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-RELEASE #0: Fri Nov 5 04:19:18 UTC 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Pentium/P55C (233.03-MHz 586-class CPU) Origin = GenuineIntel Id = 0x543 Stepping = 3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 268435456 (256 MB) avail memory = 253014016 (241 MB) Intel Pentium detected, installing workaround for F00F bug npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge pcibus 0 on motherboard pir0: PCI Interrupt Routing Table: 6 Entries on motherboard pci0: PCI bus on pcib0 isab0: PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 5513 UDMA33 controller port 0xd000-0xd00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 11 at device 1.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: SiS 5571 USB controller mem 0xe400-0xe4000fff irq 11 at device 1.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SiS 5571 USB controller on ohci0 usb0: USB revision 1.0 uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Atmel Standard USB Hub, class 9/0, rev 1.10/3.00, addr 2 uhub1: 4 ports with 4 removable, self powered ugen0: Cambridge Silicon Radio Ltd. Bluetooth USB dongle, rev 1.10/5.25, addr 3 xl0: 3Com 3c905C-TX Fast Etherlink XL port 0xb800-0xb87f mem 0xe380-0xe380007f irq 4 at device 9.0 on pci0 miibus0: MII bus on xl0 xlphy0: 3c905C 10/100 internal PHY on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:10:22:fd:f2:7d sis0: NatSemi DP8381[56] 10/100BaseTX port 0xb400-0xb4ff mem 0xe300-0xe3000fff irq 9 at device 10.0 on pci0 sis0: Silicon Revision: DP83815D miibus1: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:40:f4:5f:91:ed pci0: display, VGA at device 11.0 (no driver attached) atapci1: Promise PDC20269 UDMA133 controller port 0x9800-0x980f,0xa000-0xa003,0xa400-0xa407,0xa800-0xa803,0xb000-0xb007 mem 0xe280-0xe2803fff irq 11 at device 12.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 cpu0 on motherboard orm0: ISA Option ROMs at iomem 0xcc000-0xce7ff,0xc8000-0xc87ff,0xc-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x64,0x60 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: Enhanced floppy controller at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 ppc0: parallel port not found. sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ppc1: parallel port not found. unknown: PNP0700 can't assign resources (port) unknown: PNP0f13 can't assign resources (irq) unknown: PNP0303 can't assign resources (port) Timecounter TSC frequency 233030328 Hz quality 800 Timecounters tick every 10.000 msec ad0: 1919MB NEC Corporation DSE2010A/VVK0333 [3900/16/63] at ata0-master WDMA2 ad4: 78533MB IC35L080AVVA07-0/VA4OA52A [170197/15/63] at ata2-master UDMA100 acd0: CDRW PLEXTOR CD-R PREMIUM/1.05 at ata3-master UDMA33 acd1: DVDROM PLEXTOR DVD-ROM PX-116A2 0100/1.00 at ata3-slave UDMA66 Mounting root from ufs:/dev/ad4s2a warning: KLD
Interrupt storm detected on irq7
Hello, i'm running FreeBSD 5.3 BETA-7 from October 13, everytime i try to print something through my LPT printer i get the next message: Interrupt storm detected on irq 7: lpt0; throttling interrupt source and the printer gets extremely slow. I've googled a bit and have found it's not a strange problem, some people suggest to add SMP option to the kernel (it's a one processor machine) or increasing the number of simultaneous interruptions at sysctl. I don't think any of them are a good choice, but Anyone of you has had this problem? and if so, how did you solve? Thanks in advance pgptRbUoTlAkj.pgp Description: PGP signature
Re: Interrupt storm detected on irq7
Enrique Ayesta Perojo wrote: Anyone of you has had this problem? and if so, how did you solve? i had the same problem with my printer, switching to polled mode did help in my case: lptcontrol -e lpt0 philipp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
interrupt storm on irq 7
Hi, I keep receiving messages about interrupt storm on irq 7 and my device being throttled down on my -CURRENT machine. The result is very slow printout. Does anybody else see this, or is there a workaround for it? Regards, Uli. P.S.I am using cups - perhaps this causes the problem? +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Interrupt storm detected on irq7: lpt0
Hi! My last cvsup of -CURRENT on monday seems to have messed up printing somehow. When I try to print (I am using cups) I receive this message: Interrupt storm detected on irq7: lpt0; throttling interrupt source Result is: Printing becomes very slow (about one minute for a simple text file, longer for some OpenOffice document). What can be done? Regards, Uli. +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
