Hello, Simon. On 06/29/2010 09:10 AM, Simon Li wrote: > We observed that all the processes on the blade are totally stuck, > though only one process is actually accessing the disks, other > processes are mostly CPU-consuming applications. Can you please turn on printk timestamp and attach the dmesg output _after_ such failure? I think there are two possibilities. The kernel could be generating too many messages to slow serial console, or the it might as well be that all processes got stuck on IO. It's really difficult to figure out what's going on without more specific information. What does "stuck" mean? Does it mean all of them are in iowait or is the kernel just stuck inside kernel? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
