https://bugzilla.kernel.org/show_bug.cgi?id=42725
--- Comment #40 from Alex Shi <alex....@intel.com> 2012-06-21 00:36:08 --- (In reply to comment #39) > Here's the output of git bisect log > https://dl.dropbox.com/u/2231399/log.tar.gz Oh, you do narrowed the scope. found the last good : 9ea2c4... and last bad: 31dfbc... If the bug is in drivers/cpufreq, you can redo the bisection just on the directory: drivers/cpufreq drivers/acpi with your last good and last bad. You also can list all suspicious patches by following command before bisection. $git log 9ea2c4be978d597076ddc6c..31dfbc93923c0aa drivers/cpufreq/ drivers/acpi drivers/cpuidle but if the bug is not there, you can try just bisect on other source directories, like kernel, arch/x86, mm/ in the git bisection man page, you can find how to narrow the source directory.here is a example: $git bisect start -- arch/i386 include/asm-i386 I think you are near the bug! :) -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are watching the assignee of the bug. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
