http://bugzilla.novell.com/show_bug.cgi?id=462368
User trenn@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=462368#c17
Thomas Renninger changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
Info Provider| |desdiv@gmail.com
--- Comment #17 from Thomas Renninger 2009-07-20 02:51:42 MDT ---
Seems as if this one is fixed in mainline kernels then?
As we have no clue where the bug could be sitting, only idea where chances are
high to already identify a fix is to do a git bisect.
If you want to do that, here some hints:
- get the latest mainline kernel git repository:
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
2.6_mainline kernel
- copy your current kernel config into it and start compiling:
cd 2.6_mainline kernel
Better check out a stable version:
git checkout v2.6.30
zcat /proc/config.gz >.config
make -j5
make install modules_install # not sure whether modules_install is needed
mkinitrd # not sure whether mkinitrd is needed
check /boot/grub/menu.lst, reboot and boot the new kernel
Does it work?
Then the bug got fixed somewhere between 2.6.30 and 2.6.27.
Do:
git checkout v2.6.27
make -j5
make install modules_install # not sure whether modules_install is needed
mkinitrd # not sure whether mkinitrd is needed
check /boot/grub/menu.lst, to make sure your kernel gets booted, reboot and
boot the new kernel.
Next is to find the fix via git bisect. Because you search a fix and not a
regression you have to exchange good and bad!
git bisect start
git bisect bad v2.6.30
git bisect good v2.6.27
If the kernel works, do:
git bisect bad
if it does not:
git bisect good
Exactly the other way around. Never mix that up!
In the end you get a git commit id what patch fixed the problem which, if not
too intrusive, could be added to 11.1 kernel.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.