On 10/24/07, BERTRAND Joël <[EMAIL PROTECTED]> wrote: > Hello, > > Any news about this trouble ? Any idea ? I'm trying to fix it, but I > don't see any specific interaction between raid5 and istd. Does anyone > try to reproduce this bug on another arch than sparc64 ? I only use > sparc32 and 64 servers and I cannot test on other archs. Of course, I > have a laptop, but I cannot create a raid5 array on its internal HD to > test this configuration ;-) >
Can you collect some oprofile data, as Ming suggested, so we can maybe see what md_d0_raid5 and istd1 are fighting about? Hopefully it is as painless to run on sparc as it is on IA: opcontrol --start --vmlinux=/path/to/vmlinux <wait> opcontrol --stop opreport --image-path=/lib/modules/`uname -r` -l -- Dan - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
