Prasad Koya: > >>> So your kernel is vanilla v3.4.43 and aufs is plain 3.4-20130325, right? > We have few custom patches on top of vanilla kernel and some backports > from 3.18.
So your kernel has these components, - vanilla v3.4.43 - your patches - aufs3.4-20130325 I don't know what your bug is yet, but there are all chances that every component can be the origin of the bug. Also all of their combinations. - vanilla v3.4.43 x your patches - vanilla v3.4.43 x aufs3.4-20130325 - your patches x aufs3.4-20130325 - vanilla v3.4.43 x your patches x aufs3.4-20130325 Optimistically assuming the first component "vanilla v3.4.43" doesn't have this problem, you may be able to exclude it. As you might know, aufs3.4-20130325 is for vanilla v3.4.0. It means that "vanilla v3.4.43 x aufs3.4-20130325" can be interpreted as "changes between v3.4.0--v3.4.43 x aufs3.4-20130325". If the problem is brand new which means you are the first who has met it, then there is no fix in any git-log. But if the problem is already known and there is a fix for it somewhere, the you will be able to find it in some git-log. Such theory can reduce the area for you to investigate I hope. This will unchange even if your base version is upgraded to v3.18. J. R. Okajima ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
