Hi Conrad,

Thanks for reporting this regression.  I'd like to try to work with you
to narrow down the specific patch which caused this regression.  It will
require doing a git bisect.  This is obviously not something we expect
you to know how to do so I'll try to walk you through it step by step.
A git bisect basically does a binary search of the git revision history
to help narrow down a patch which has caused a regression.  It will
require doing some kernel builds as well which again I'll try to help
you out with.  For general information regarding a git bisect and
building the Ubuntu kernels, refer to:

http://www.kernel.org/doc/local/git-quick.html#bisect
https://help.ubuntu.com/community/Kernel/Compile

First, I'll need you to install a few extra packages:

1) sudo apt-get install linux-kernel-devel fakeroot build-essential
makedumpfile git-core

Next, clone the Ubuntu git kernel tree and change into the ubuntu-
intrepid directory:

2) git clone git://kernel.ubuntu.com/ubuntu/ubuntu-intrepid.git ubuntu-intrepid
3) cd ubuntu-intrepid

Begin the git bisect:
4) git bisect start
5) git bisect bad Ubuntu-2.6.27-10.20
6) git bisect good Ubuntu-2.6.27-8.17

Before building the kernels, I usually like the modify the version name
so the .deb file that will be produced has a unique name:

7) vim debian/changelog

Edit the kernel version in the first line and save the file.  For example 
change it from:
linux (2.6.27-9.18) UNRELEASED; urgency=low
to
linux (2.6.27-9.18~conrad) UNRELEASED; urgency=low

Then build the kernel:

8) AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic

After if finishes building, undo the edits you made to the
debian/changelog file (otherwise you'll run into some issues in the
later steps when you start marking good and bad bisects):

9) vim debian/changelog
Edit the kernel version back to what it was originally and save the file.  For 
example change it back from:
linux (2.6.27-9.18~conrad) UNRELEASED; urgency=low
to
linux (2.6.27-9.18) UNRELEASED; urgency=low

After this finishes building it should have created a .deb file for you
to install one directory level up.  It'll be named something similar to
"linux-image-2.6.27-9-generic_2.6.27-9.18~conrad_i386.deb".  This is the
test kernel you'll want to install.  Then reboot to test if it boots
successfully or not.

10) sudo dpkg -i linux-image-2.6.27-9-generic_2.6.27-9.18~conrad_i386.deb
11) sudo reboot

If the kernel boots successfully then you'll want to mark that bisect as
good:

12a) cd ubuntu-intrepid
12b) git bisect good

Otherwise if the kernel boot fails as you've reported here then you'll
want to mark that bisect as bad:

13a) cd ubuntu-intrepid
13b) git bisect bad

Continue to repeat steps 7 though 12or13 until the bisect has been
narrowed down to a single commit.  Please then post that commit
information here.

We really appreciate you help with this.  Let us know if you have any
questions.  Thanks.

-- 
crc error/Kernel panic
https://bugs.launchpad.net/bugs/302308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to