Greetings, I send Dave, what I feel is the bad commit for the current lockups found in kernel 3.18 r4. The bad commit I believe is 4995ab9cf512e9a6cc07dfd6b1d4e2fc48ce7fef as it does touch the TLB code in the function that is most likely causing issues. Nick
Did you test this theory or just do a simple search and make an assumption? Did you test before and after reverting the patch? You cant just make a statement without backing it up. Chris On Thu, Dec 11, 2014 at 7:37 AM, nick <xerofoify@gmail.com> wrote:
Greetings, I send Dave, what I feel is the bad commit for the current lockups found in kernel 3.18 r4. The bad commit I believe is 4995ab9cf512e9a6cc07dfd6b1d4e2fc48ce7fef as it does touch the TLB code in the function that is most likely causing issues. Nick
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Thu, 11 Dec 2014 09:37:26 -0500, nick said:
I send Dave, what I feel is the bad commit for the current lockups found in kernel 3.18 r4. The bad commit I believe is 4995ab9cf512e9a6cc07dfd6b1d4e2fc48ce7fef as it does touch the TLB code in the function that is most likely causing issues.
Have you actually confirmed this with a git bisect, and/or tested with this commit reverted on a system that easily locks up, or have a good explanation why the TLB code is at fault, or what function you think is most likely causing issues, and why? Bonus points for explaining *why* the code refactoring in that commit is wrong. /me makes popcorn. This should be interesting....
participants (3)
-
Chris Lee -
nick -
Valdis.Kletnieks＠vt.edu