lkml.org 
[lkml]   [2005]   [Apr]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: BUGs in 2.6.12-rc2-RT-V0.7.45-01
    On Fri, 15 Apr 2005, Ingo Molnar wrote:

    > * William Weston <weston@sysex.net> wrote:
    >
    > > On Wed, 13 Apr 2005, Ingo Molnar wrote:
    > >
    > > > what are you using kprobes for? Do you get lockups even if you disable
    > > > kprobes?
    > >
    > > Various processes will lockup on the P4/HT system, usually while under
    > > some load. The processes cannot be killed. X will lockup once or
    > > twice a day (which means my console, and thus sysrq, are toast), but I
    > > can still ssh in. Nothing is logged by the kernel. Are there any
    > > post-lockup forensics that can be performed before I reboot?
    >
    > could you try the -44-03 patch:
    >
    > http://redhat.com/~mingo/realtime-preempt/older/realtime-preempt-2.6.12-rc2-V0.7.44-03
    >
    > this doesnt have the plist changes yet. Is this one more stable?

    With 2.6.12-rc2-V0.7.44-03, the P4/HT box has been stable all day. I'm
    seeing another BUG on boot, not kprobes related this time:

    Freeing unused kernel memory: 192k freed
    logips2pp: Detected unknown logitech mouse model 86
    input: ImExPS/2 Logitech Explorer Mouse on isa0060/serio1
    BUG: kstopmachine:1054 RT task yield()-ing!
    [<c0103dba>] dump_stack+0x23/0x25 (20)
    [<c030ff1f>] yield+0x67/0x69 (20)
    [<c0142a44>] stop_machine+0xa4/0x15e (40)
    [<c0142b2d>] do_stop+0x15/0x77 (20)
    [<c0132c5b>] kthread+0xab/0xd3 (48)
    [<c0100fe9>] kernel_thread_helper+0x5/0xb (563617812)
    ---------------------------
    | preempt count: 00000001 ]
    | 1-level deep critical section nesting:
    ----------------------------------------
    .. [<c013bca6>] .... print_traces+0x1b/0x52
    .....[<c0103dba>] .. ( <= dump_stack+0x23/0x25)

    ns83820.c: National Semiconductor DP83820 10/100/1000 driver.
    eth0: ns83820.c: 0x22c: 49001186, subsystem: 1186:4900
    eth0: ns83820 v0.20: DP83820 v1.2: 00:50:ba:37:d4:bc io=0xff8ff000 irq=18 f=sg


    I'm also seeing an unlikely wakeup time:

    ( X-3581 |#1): new 2533412143 us maximum-latency wakeup.


    Otherwise, this on seems very stable.


    Best Regards,
    --William Weston


    --
    /* William Weston <weston@sysex.net> */
    -
    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-04-16 03:29    [W:0.021 / U:1.108 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site