On Sun, 17 Feb 2008 21:49:10 +0100
allied internet ag- Stefan Priebe <s.priebe@allied-internet.ag> wrote:

quoted text
>  >> One week ago we upgraded about 300 servers from 2.6.20.20 to
>  >> 2.6.24.2.
>  >
>  > Painfull.
> 
> OK not really - i've tested the new kernel on all models. And it
> works fine... the DN state only comes sometimes - absolutely not
> reproducable. So my tests went OK and then we've done the update.
> I've now seen 5 servers in 7 days having this problem.
> 
>  >> Now we get sometimes dozent of processes in state DN. The system
>  >> is completely idle - but the load is 20 or 90 or whatever. And it
>  >> can only be "repaired" by rebooting the system.
>  >
>  > please post sysrq-t (echo t > /proc/sysrq-trigger) output.
> Sorry what key is sysrq? Can i also do this via SSH Console?

just do the echo above and it'll have the same effect as the key, and yes
you can do this via ssh just fine (I do that all the time)


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
unsubscribe notice
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/