Re: Real-Time Preemption, -RT-2.6.10-rc2-mm1-V0.7.28-1

From: Jan Engelhardt (jengelh_at_linux01.gwdg.de)
Date: 11/18/04

  • Next message: Stephen C. Tweedie: "Re: Fw: [POSSIBLE-BUG] telldir() broken on ext3 dir_index'd directories just after the first entry."
    Date:	Thu, 18 Nov 2004 16:37:48 +0100 (MET)
    To: Christian Meder <chris@onestepahead.de>
    
    

    >I've got one of those 'my box just locked up'. I can reproduce it with
    >0.7.25-1, 0.7.28-0 and 0.7.28-1 by starting the Jetty servlet container
    >with our inhouse java project under a Blackdown 1.4 jdk. Within a minute
    >the laptop just locks up: no mouse, no ping, console switching sysrq-t

    Sysrq+T itself might work, it's just a matter to get to the console! If you can
    get to a con, I'm sure it does, because hitting the keys generates an interrupt
    which will be delivered to the sysrq code if interrupts are not currently
    disabled. So even if your box appears totally dead, you'd be surprised when you
    hit Sysrq+B.

    To get any data, I'd start a vnc server on it, and all graphical apps in it,
    and let the machine itself stay on tty10 (or wherever kernel output goes), and
    then try hitting Sysrq+T when it hangs.

    Jan Engelhardt

    -- 
    Gesellschaft für Wissenschaftliche Datenverarbeitung
    Am Fassberg, 37077 Göttingen, www.gwdg.de
    -
    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/
    

  • Next message: Stephen C. Tweedie: "Re: Fw: [POSSIBLE-BUG] telldir() broken on ext3 dir_index'd directories just after the first entry."

    Relevant Pages

    • Re: [PATCH] 3c59x: read current link status from phy
      ... there is only one interrupt that for data transmission (both Tx ... The MII registers are not ... Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: is killing zombies possible w/o a reboot?
      ... An interrupt could be received at any time, ... in uninterruptible state because it is uninterruptible ... Processes must never get stuck in D, it's a kernel bug. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.0-test7-mm1
      ... >> handlers happens to start a thread, ... Problem is, things like bus resets happen in interrupt, and while I can ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: amd64 booting panic (really, really early)
      ... Sounds very like what I was hitting. ... > serial driver hasn't a chance to probe.) ... > same config file for 2.6.12-rc4 it goes back to the panic. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: CONFIG_IRQBALANCE for AMD64?
      ... Provide some sort of cache-affinity for network interrupt processing, ... Utilize idle CPUs where possible to shoulder the load. ... I'll confess to not having looked at non-i386 arches. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)