Re: Interrupt storm

From: Dan Cojocar (dan.cojocar_at_gmail.com)
Date: 03/30/05

  • Next message: Jeremie Le Hen: "strcspn(3) complexity improvement" 
    Date: Wed, 30 Mar 2005 10:13:07 +0300
To: freebsd-current@freebsd.org

    On Tue, 29 Mar 2005 15:46:52 -0500 (EST), Andre Guibert de Bruet
    <andy@siliconlandmark.com> wrote:
    >
    > On Tue, 29 Mar 2005, Dan Cojocar wrote:
    > > On Tue, 29 Mar 2005 14:33:44 -0500, Mike Tancsa <mike@sentex.net> wrote:
    > >> At 02:29 PM 29/03/2005, Dan Cojocar wrote:
    > >>> I have enabled in BIOS and loaded audio driver and USB and i get
    > >>> the following storm:
    > >>> Interrupt storm detected on "irq11: pcm0 rl1+"; throttling interrupt source
    > >>> Interrupt storm detected on "irq5: rl0"; throttling interrupt source
    > >>
    > >> Any different if you comment out
    > >> device apic # I/O APIC
    > >>
    > > I don't have device apic in my kernel.
    > >
    > > I updated my BIOS, as Jung-uk Kim suggested, and now i have 3
    > > interrupt stroms :)
    > >
    > > Interrupt storm detected on "irq10: rl0 ohci1"; throttling interrupt source
    > > Interrupt storm detected on "irq11: rl1 ehci0"; throttling interrupt source
    > > Interrupt storm detected on "irq5: ohci0"; throttling interrupt source
    >
    > Have you tried booting this machine using GENERIC with ACPI turned off?
    >

    I tried running GENERIC and i get the following lor and watchdog
    timeout, no interrupt storms:

    lock order reversal
     1st 0xc09fc7a0 ifnet (ifnet) @ /usr/src/sys/net/if.c:1091
     2nd 0xc23c0700 rl0 (network driver) @
    /usr/src/sys/modules/rl/../../pci/if_rl.c:1688
    KDB: stack backtrace:
    kdb_backtrace(c08eb4f7,c23c0700,c24055c0,c0b27e4c,c0b27ddd) at
    kdb_backtrace+0x2e
    witness_checkorder(c23c0700,9,c0b27ddd,698,c09fc7a0) at witness_checkorder+0x6b3
    _mtx_lock_flags(c23c0700,0,c0b27ddd,698,c23c0000) at _mtx_lock_flags+0x8a
    rl_watchdog(c23c0000,0,c08f0f38,443,c09adfe0) at rl_watchdog+0x3a
    if_slowtimo(0,0,c08e8914,107,c06eea90) at if_slowtimo+0x59
    softclock(0,0,c08e51fb,256,c09adfa0) at softclock+0x249
    ithread_loop(c2300500,e35f1d48,c08e4fe6,30e,c2300500) at ithread_loop+0x162
    fork_exit(c065dd00,c2300500,e35f1d48) at fork_exit+0xc6
    fork_trampoline() at fork_trampoline+0x8
    --- trap 0x1, eip = 0, esp = 0xe35f1d7c, ebp = 0 ---
    rl0: watchdog timeout
    rl1: watchdog timeout
    rl0: watchdog timeout
    rl1: watchdog timeout
    rl1: watchdog timeout
    rl1: watchdog timeout
    rl1: watchdog timeout

       Here is the full dmesg: http://cs.ubbcluj.ro/~dan/dmesg.txt.generic
       I tried also my kernel with apic, i don't get interrupt storms but
    i get watchdog timeout message just like with GENERIC.
    Here is the full dmesg: http://cs.ubbcluj.ro/~dan/dmesg.txt.apic
       And finally i tried my kernel without apic and without acpi, it's
    running just fine, no interrupt storms, no watchdog timeout, but i
    don't have acpi :(, here is the final
    dmesg: http://cs.ubbcluj.ro/~dan/dmesg.txt.noacpi.
       Thanks,
       Dan
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Jeremie Le Hen: "strcspn(3) complexity improvement"

    Relevant Pages

    • Re: Interrupt storm
      ... >rl0: watchdog timeout ... >rl1: watchdog timeout ... To unsubscribe, ...
      (freebsd-current)
    • Re: rl watchdog timeout
      ... The only thing in the dmesg output is ... use dhcp to get it's address which it does just fine when rl1 isn't in the ... both the nics enabled rl1 gives me watchdog timeout errors and rl0 does not ...
      (comp.unix.bsd.freebsd.misc)
    • Re: em watchdog timeout on Intel 82541 and 82546EB
      ... PCI-X bus. ... After I load the new kernel, kernel said: em2 watchdog timeout and could ... I switch the line to the em0, ...
      (freebsd-current)
    • em watchdog timeout on Intel 82541 and 82546EB
      ... After I load the new kernel, kernel said: em2 watchdog timeout and could not send any ... I switch the line to the em0, ...
      (freebsd-current)
    • Re: interrupt storm and watchdog timeout with 5.3 Release
      ... I actually did mean acpi because some of the mailing list archive entries mentioned the ... connection between watchdog timeout and acpi. ...
      (comp.unix.bsd.freebsd.misc)