IRQ 15 is typically an interrupt for the second IDE controller. You may be using SCSI and have disabled the wdc on a mobo that doesn't like that too much. The network traffic blockage could be attributed to the PIC not being reset before the requests were handled. IRQs 8-15 are handled by IRQ 2, mid you, so they are higher priority if your netcard is on PIC1. --cokane Mike Smith had the audacity to say: > > A mission-critical production machine of ours seems to be > > having issues with stray irqs. > > > > This is in the dmesg: > > ----------------------------- > > stray irq 15 > > stray irq 15 > > stray irq 15 > > stray irq 15 > > stray irq 15 > > too many stray irq 15's; not logging any more > > ---------------------------- > > > > It seems as if the ethernet traffic stops for about a minute > > when it posts that message. > > > > I've searched back in the mailing lists to find that this > > may be caused by the BIOS grabbing the IRQ -- and was just > > wondering if anyone else has seen this problem lately? > > No; this is typically caused by having hardware in the system that's > generating interrupts but isn't handled by a driver. It may be > symptomatic of faulty hardware or a system misconfiguration. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
