https://bugzilla.kernel.org/show_bug.cgi?id=42725
--- Comment #27 from Alex Shi <alex....@intel.com> 2012-06-14 03:24:01 --- (In reply to comment #26) > (In reply to comment #25) > > (In reply to comment #24) > > > (In reply to comment #23) > > > > That workaround does not work for me. My CPU still gets stuck at > > > > 800mhz even > > > > after suspending. I've also attempted the SATA fixes etc. Nothing seems > > > > to fix > > > > it. > > > > > > > > The kernel simply needs to be fixed. This is a clear regression bug. > > > > > > Do you mean your laptop had worked on some old kernel? > > > If so, could you like to do a bisect for this bug? > > > Actually, I like to take a look, but I can not get this laptop. > > > > Yes I think this is a regression, my Asus N51Vn with an Intel Core 2 Duo > > T9400 > > cpu does work properly on Ubuntu 10.10 with the 2.6.35 kernel with ACPI > > enabled. However, any of the newer kernels in an ubuntu distribution show > > the > > aforementioned undesired behaviour when ACPI is not disabled. > > > > I would love to help you, but I don't quite know what a bisect is or how to > > do > > it, could you point me in the direction of some documentation I could use or > > otherwise assist me in the process? > > Oh, It is not difficult. Bisection can find the bug patch in kernel source > code. > > First, to get a linux kernel git repository. > $git clone git://github.com/torvalds/linux.git > > Second. study 'git bisect' command > $man git bisect > or read tutorial online, like > http://www.kernel.org/pub/software/scm/git/docs/v1.5.6/git-bisect.html > > Third, to do bisection under your local git repository: > -- > #go to kernel code repository > $cd linux > #start and set good point at 2.6.35 > --- > $git bisect start > $git bisect good v3.6.35 > > #set bad point at 2.6.38 > $git bisect bad v2.6.38 > > #copy your kernel configuration from /boot/config-x.x.x to your repository. > #and then compile and installed bisection kernel > --- > $cp /boot/config-xxx .config > #you can compile all modules in default config, or just installed modules > $make localmodconfig > $make -j 4 && sudo make install may you needs more precise command: make -j 4 && make modules -j 4 && sudo make modules_install install > > # reboot to just compile kernel, I don't what your grub version, grub 1.0 or > grub 2.0. If it is grub 1.0, change the /etc/grub.conf to boot your kernel. if > grub2.0, it is already changed to new kernel, but if it fails check some > online > tutorial, write a /boot/grub/constom.cfg is a kind of workable way. > > # now, you can check if the new kernel has this bug, if yes, > $git bisect bad > #or no this bug > $git bisect good > > #then continue compile and reboot to new kernel. make sure your is using your > new kernel by checking with "uname -a" and "ls -lrt /boot/vmlinuz*". usually, > only teens recompile/reboot can find out the trigger commit, using 'git bisect > skip' command for uncompilable/unbootable kernel. > > Enjoy bisection!, You will become a real kernel developer after done this! :) > > > > In any case, some of the people in this launchpad thread > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/793437 started a bisect > > back when this regression appeared, I however don't think they actually > > finished it. -- 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
