Re: [Bluez-devel] the effect of linux 2.6.18 to the bluez

Martin Röhricht
2006-10-19T19:03:57Z

Am Donnerstag, den 19.10.2006, 16:07 +0800 schrieb Mingfan.Lu:

> I don't know whether the config make it happen or there is something
> wrong with it?
> So, Martin, How about you make config when you building your new
> kernel?

I build the kernels the "debian way" cause I use Ubuntu as well. So
basically:
(1) tar xjf linux-2.6.18.x.tar.bz2
(2) cd linux-2.6.18.x
(3) patch -p1 < ../patch-2.6.18-mh6
(4) cp /boot/config-2.6.15-26-686 .config
(5) make oldconfig
[edit some config options manually if necessary]
(6) fakeroot make-kpkg kernel_image modules_image --initrd --revision
mh6 binary
(7) cd ..
(8) dpkg -i kernel-image-2.6.18.xmh6_i386.deb

Edit /boot/grub/menu.lst if necessary and that's it.
Your problems are really strange. How do you measure the time? I don't
think it has anything to do with the config file per se. But I know of
some pretty neat and improved debugging facilities -- maybe you want to
check out that there is nothing in action that slows down the machine
just for the purpose of deadlock detections.

I'm sorry about it, but it seems extremely hard to me locating such a
problem that never affects one of my machines. :-/

Good luck,
Martin