IRQ 7 Dump vs Oops event

Version 1



    With the release of GOS 5 we have new information in the syslog that may appear to be familiar.   When certain events occur, the system will dump the memory registers used by a particular process to the syslog.  This may appear at first glance to be an Oops or kernel panic event, however unless the dump specifically contains those descriptors it may simply be a driver or a process crash.


    If you run across this situation please escalate the issue with the description of the problem in the summary.  The below log information is not an Oops but rather a software bus bug.  This issue can cause different symptoms including apparent drive failure, NIC communications issues etc.


    kernel: irq 7: nobody cared (try booting with the "irqpoll" option)
    kernel:  [<78132224>] __report_bad_irq+0x24/0x80
    kernel:  [<7813231b>] note_interrupt+0x9b/0x210
    kernel:  [<b8a0843e>] tg3_interrupt_tagged+0xce/0xf0 [tg3]
    kernel:  [<78131d43>] handle_IRQ_event+0x33/0x60
    kernel:  [<78131e25>] __do_IRQ+0xb5/0xc0
    kernel:  [<781046fa>] do_IRQ+0x3a/0x70
    kernel:  [<78102caa>] common_interrupt+0x1a/0x20
    kernel:  [<7814cf99>] kmem_cache_free+0x29/0x50
    kernel:  [<b8a0a52d>] tg3_poll+0xdd/0x710 [tg3]
    kernel:  [<7831cde0>] net_rx_action+0x60/0x160
    kernel:  [<78117ca2>] __do_softirq+0x42/0x90
    kernel:  [<78117d17>] do_softirq+0x27/0x30
    kernel:  [<781046ff>] do_IRQ+0x3f/0x70
    kernel:  [<781046ff>] do_IRQ+0x3f/0x70
    kernel:  [<78102caa>] common_interrupt+0x1a/0x20
    kernel:  [<78101bec>] default_idle+0x2c/0x60
    kernel:  [<78101c3c>] cpu_idle+0x1c/0x60
    kernel:  [<78478777>] start_kernel+0x2f7/0x370
    kernel:  [<78478210>] unknown_bootoption+0x0/0x270
    kernel: handlers:
    kernel: [<b8a08370>] (tg3_interrupt_tagged+0x0/0xf0 [tg3])
    kernel: Disabling IRQ #7


    This issue is only known to be present in GOS 5.0.133 and is resolved by upgrading to GOS 5.1.046 or later.