Claudio Martins <[EMAIL PROTECTED]> wrote: > > While stress testing 2.6.12-rc2 on an HP DL145 I get processes stuck in D > state after some time. > This machine is a dual Opteron 248 with 2GB (ECC) on one node (the other > node has no RAM modules plugged in, since this board works only with pairs). > > I was using stress (http://weather.ou.edu/~apw/projects/stress/) with the > following command line: > > stress -v -c 20 -i 12 -m 10 -d 20 > > This causes a constant load avg. of around 70, makes the machine go into > swap a little, and writes up to about 20GB of random data to disk while > eating up all CPU. After about half and hour random processes like top, df, > etc get stuck in D state. Half of the 60 or so stress processes are also in > D > state. The machine keeps being responsive for maybe some 15 minutes but then > the shells just hang and sshd stops responding to connections, though the > machine replies to pings (I don't have console acess till tomorrow). > > The system is using ext3 with md software Raid1. > > I'm interested in knowing if anyone out there with dual Opterons can > reproduce this or not. I also have access to an HP DL360 Dual Xeon, so I > will > try to find out if this is AMD64 specific as soon as possible. Please let me > know if you want me to run some other tests or give some more info to help > solve this one.
Can you capture the output from alt-sysrq-T? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
