https://bugzilla.novell.com/show_bug.cgi?id=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c46 Suresh Siddha <suresh.b.siddha@intel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suresh.b.siddha@intel.com --- Comment #46 from Suresh Siddha <suresh.b.siddha@intel.com> 2011-02-01 20:07:03 UTC --- (In reply to comment #44)
I've tried git bisect once more. Due to the early hard lock, I've decided to give
make i386_defconfig make isoimage
a chance. This does not result in a bootable system, so I cannot do something like dmsg. But it reduces the code to compile. And I've started with bad v2.6.32 and good v2.6.31 after tried both kernels. So I needed much less time to compile and reboot while reducing the probability of compiling problems.
I needed three days and about 15 build-reboot cycles but the result is:
d0af9eed5aa91b6b7b5049cae69e5ea956fd85c3 is the first bad commit
This sounded like an issue that is fixed with the upstream commit: commit 68f202e4e87cfab4439568bf397fcc5c7cf8d729 Author: Suresh Siddha <suresh.b.siddha@intel.com> Date: Fri Jul 30 11:46:42 2010 -0700 But few things: a) The above patch is in 2.6.36 onwards and the previous comments seem to say kernels above 2.6.36 also has the same problem. is that correct? b) this MTRR rendezvous patch should affect only the systems which have multiple logical cpus (and the fix is addressed by 68f202e4e87cfab4439568bf397fcc5c7cf8d729) and your system seem to have only one logical cpu. Correct? If "a" and "b" are both true, then I am missing something subtle. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.