* Bad Commit for Current Lockups
@ 2014-12-11 14:37 nick
2014-12-11 15:01 ` Chris Lee
2014-12-11 15:08 ` Valdis.Kletnieks at vt.edu
0 siblings, 2 replies; 3+ messages in thread
From: nick @ 2014-12-11 14:37 UTC (permalink / raw)
To: kernelnewbies
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Bad Commit for Current Lockups
2014-12-11 14:37 Bad Commit for Current Lockups nick
@ 2014-12-11 15:01 ` Chris Lee
2014-12-11 15:08 ` Valdis.Kletnieks at vt.edu
1 sibling, 0 replies; 3+ messages in thread
From: Chris Lee @ 2014-12-11 15:01 UTC (permalink / raw)
To: kernelnewbies
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 at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
^ permalink raw reply [flat|nested] 3+ messages in thread
* Bad Commit for Current Lockups
2014-12-11 14:37 Bad Commit for Current Lockups nick
2014-12-11 15:01 ` Chris Lee
@ 2014-12-11 15:08 ` Valdis.Kletnieks at vt.edu
1 sibling, 0 replies; 3+ messages in thread
From: Valdis.Kletnieks at vt.edu @ 2014-12-11 15:08 UTC (permalink / raw)
To: 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....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141211/914a7e60/attachment-0001.bin
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-12-11 15:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-11 14:37 Bad Commit for Current Lockups nick
2014-12-11 15:01 ` Chris Lee
2014-12-11 15:08 ` Valdis.Kletnieks at vt.edu
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.