Hi Shaohua, >If you could rebuild kernel and apply this debug patch It would be my pleasure to do this. Thank you for your reply! Do you have a decent reference site where I could read through and do this from? I've been to a ton of pages in the past, but none that are concise enough to follow a rebuild and apply a patch like you ask? If not, no worries, I'll just do a bit of digging and reading. I am working from home today though, so if I could bang this one out, it would be amazing! >please capture the /sys/kernel/debug/tracing/trace output and send to me. No problem, once I do this I will send that right over. On Tue, Sep 13, 2016 at 1:43 PM, Shaohua Li <shli@xxxxxxxxxx> wrote: > On Tue, Sep 13, 2016 at 11:22:17AM -0400, Francisco Parada wrote: >> Hi all, >> >> I've tried the suggestions mentioned and also tried booting into an >> older version of Ubuntu (14.04.5 instead of my current 16.04.1), which >> has an older kernel per a private suggestion, but that too was >> unsuccessful. Just wanted to give a quick update that all of the >> mentioned workarounds were unfruitful. > > If you could rebuild kernel and apply this debug patch, I'd like to check what > happens. When the cpu is in 100% usage and reshape stalls, please capture the > /sys/kernel/debug/tracing/trace output and send to me. > > Thanks, > Shaohua > > diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c > index 5883ef0..db484ca 100644 > --- a/drivers/md/raid5.c > +++ b/drivers/md/raid5.c > @@ -62,6 +62,9 @@ > #include "raid0.h" > #include "bitmap.h" > > +#undef pr_debug > +#define pr_debug trace_printk > + > #define cpu_to_group(cpu) cpu_to_node(cpu) > #define ANY_GROUP NUMA_NO_NODE > -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
