lkml.org 
[lkml]   [2007]   [Feb]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    SubjectRe: 2.6.20-git13 kernel BUG at /mnt/md0/devel/linux-git/kernel/time/tick-sched.c:168
    From
    Date
    On Sat, 2007-02-17 at 15:47 +0100, Alex Riesen wrote:
    > > > 164 if (need_resched())
    > > > 165 goto end;
    > > > 166
    > > > 167 cpu = smp_processor_id();
    > > > 168 BUG_ON(local_softirq_pending());
    > >
    > > Hmm, the BUG_ON is inside of an interrupt disabled region, so we should
    > > have bailed out early in the need_resched() check above (because we are
    > > in the idle task context according to the stack trace).
    > >
    > > Is this reproducible ?
    >
    > Seen this too (Ubuntu, P4/ht-SMT, SATA, typed from screen):

    Can you please apply the patch below, so we can at least see, which
    softirq is pending. This should trigger independently of hrtimers and
    dynticks. You can keep it compiled in and disable it at the kernel
    commandline with "nohz=off" and / or "highres=off"

    tglx

    diff --git a/arch/i386/kernel/process.c b/arch/i386/kernel/process.c
    index bea304d..deeb90e 100644
    --- a/arch/i386/kernel/process.c
    +++ b/arch/i386/kernel/process.c
    @@ -236,6 +236,11 @@ void cpu_idle(void)
    * Otherwise, idle callbacks can misfire.
    */
    local_irq_disable();
    + if (local_softirq_pending() && !need_resched())
    + printk(KERN_ERR
    + "Idle: local softirq pending: %04x",
    + local_softirq_pending());
    +
    enter_idle();
    idle();
    __exit_idle();
    diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
    index 95e41f7..91d459f 100644
    --- a/kernel/time/tick-sched.c
    +++ b/kernel/time/tick-sched.c
    @@ -165,7 +165,6 @@ void tick_nohz_stop_sched_tick(void)
    goto end;

    cpu = smp_processor_id();
    - BUG_ON(local_softirq_pending());

    now = ktime_get();
    /*

    -
    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: 2007-02-17 16:13    [W:0.022 / U:1.156 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site