On Tue, 31 Mar 2009, Kadlecsik Jozsef wrote: > I'll restore the kernel on a not so critical node and will try to find out > how to trigger the bug without mailman. If that succeeds then I'll remove > the patch in question and re-run the test. It'll need a few days, surely, > but I'll report the results. I had been unsuccesful to find a reliable way to trigger the freeze without mailman. So I created a backup mailman directory by which I can test the system. The following has been verified so far: - Removed commit 17968b0fe87829edff1af7fa9ffbbc92540159fb (Remove splice_read file op for jdata files) and commit 4787e11dc7831f42228b89ba7726fd6f6901a1e3 (gfs-kmod: workaround for potential deadlock. Prefault user pages), the system freezes. - Removed commit 5e83cdb08b423478a0b6cc8f6de396ab8328d47a (gfs-kernel: Bug 466645 - reproduceable gfs (dlm) hanger with simple stresstest), the system freezes. (Please note, the volumes are mounted with noatime). If you have any idea what to do next, please write it. Best regards, Jozsef -- E-mail : kadlec@xxxxxxxxxxxx, kadlec@xxxxxxxxxxxxxxxxx PGP key: http://www.kfki.hu/~kadlec/pgp_public_key.txt Address: KFKI Research Institute for Particle and Nuclear Physics H-1525 Budapest 114, POB. 49, Hungary -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
