Messages in this thread | | | Date | Fri, 29 Oct 2004 18:26:22 +0200 | From | Ingo Molnar <> | Subject | Re: [patch] Real-Time Preemption, -RT-2.6.9-mm1-V0.5.2 |
| |
* Mark_H_Johnson@raytheon.com <Mark_H_Johnson@raytheon.com> wrote:
> The critical section nesting was "unique" and looks like > > | preempt count: 00010005 ] > | 5-level deep critical section nesting: > ---------------------------------------- > .. [<c03257cf>] .... _spin_lock+0x1f/0x70 > .....[<c01e217a>] .. ( <= __up_write+0x26a/0x2a0) > .. [<c03257cf>] .... _spin_lock+0x1f/0x70 > .....[<c01e1f65>] .. ( <= __up_write+0x55/0x2a0) > .. [<c0325817>] .... _spin_lock+0x67/0x70 > .....[<c011b54d>] .. ( <= task_rq_lock+0x3d/0x70) > .. [<c03257cf>] .... _spin_lock+0x1f/0x70 > .....[<c0115f47>] .. ( <= nmi_watchdog_tick+0x127/0x140) > .. [<c013d5bd>] .... print_traces+0x1d/0x60 > .....[<c0105bec>] .. ( <= show_regs+0x14c/0x174)
this might as well have been the NMI watchdog interacting. Could you turn off the NMI watchdog to see whether that stabilizes things?
> The script then exits with preempt count of 3 and an atomic counter > underflow BUG message. This is followed right after with > > BUG: Unable to handle kernel NULL pointer dereference at virtual address > 00000 > 020
these are then probably just followup-errors. Will take a look at the logs.
Ingo - 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/
| |