On Sat, 8 Sep 2012, Sedat Dilek wrote: > I have reported the breakage of Linux-Next (next-20120906) > independently on AMD64 [1], but seem to be ignored in this thread. Not on AMD64, so I did not see anything until Tony's post. > Dis you test SLAB-only? > Can you please test next time also with a SLUB config? Tested all 3 allocators here before the release and I did not notice anything wrong. AFAICT multiple other testers also saw no problem. > The next day you removed "slab/common-for-cgroups" from slab/next, why? I do not handle that tree. > You knew that it was broken (before Tony reported IA64 boot problems)? > On linux-mm/linux-next/LKML MLs I have not read any hints/reports > before the one of Tony. Tony's report was the first report that I got on this issue. There were 2 others issues for which I also submitted patches this week. > Can you please inform people in time? I usually post too early rather than too late. There was no delay on this one either. Emails reflected my real time knowledge and fixes available. > I know linux-next is highly experimental, but I use all my > daily-builds on my system here. > Not virtual machine - on real bare metal! That is quite good. Thanks for your efforts. > Feel free to add as it fixes the reported issue: > > Reported-by: Sedat Dilek <sedat.dilek@xxxxxxxxx> > Tested-by: Sedat Dilek <sedat.dilek@xxxxxxxxx> Thanks for testing. My daughter has been in the ICU since Thursday and I had to guess that this was the right solution based on what I was able to glean on from experiences of others with the issue. Never was able to truly test the fix or even do a kernel build while the crisis was going on here. She just was moved out of the ICU an hour ago so I will be able to do more next week. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
