lkml.org 
[lkml]   [2004]   [Nov]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm2-V0.7.29-0
    From
    Date
    I'm getting a bug print (really a warning) from enable_irq spawned from
    the e100 driver. The reason is that enable_irq is being called because
    the irq depth is zero.

    Looking into this, it is because the e100 uses a shared interrupt. On
    setup (see drivers/net/e100.c: e100_up) it disables the irq that it will
    use, and then calls request_irq which calls setup_irq which zeros out
    the depth of the irq if it is not shared. So if the e100 is the first
    to be loaded, then you get this message.

    I know that for now this doesn't hurt anything, but besides annoying me
    in my print outs (I can't stop panicking when I see it ;-), is this
    really a bug and thus a design flaw of the e100? How else can a shared
    irq initialize without turning off the irq before setting itself up?

    Should it enable the irq before it requests it, and thus open the race
    of a spurious interrupt, or just disable all interrupts?

    Thanks,

    --
    Steven Rostedt
    Senior Engineer
    Kihon Technologies
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:08    [W:4.062 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site