https://bugzilla.kernel.org/show_bug.cgi?id=42725
--- Comment #29 from Alex Shi <alex....@intel.com> 2012-06-15 00:39:48 --- (In reply to comment #28) > The first kernel I compiled in the bisect process just panics on boot, is this > to be expected or did I do something wrong? I am not surprised. :) Some code is not qualified even on Linus' tree. So, follow the man page of 'git bisect', you can skip that commit. But if the next commit is still unbootable -- that often happen until the serial commit out, you can assume the commit is 'good' or 'bad', and continue your bisection. If your assumption is incorrect, go back and change a direction. You can save what's you did by 'git bisect log &> abc' etc. That command introduce in 'man git bisect' Oh, BTW, you'd better try the latest kernel 3.5-rc2 to make sure the bug still is there. Go ahead! Waiting for your finding! -- 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
