Re:

From: Bill Davidsen
Date: Sat Oct 11 2008 - 11:12:26 EST


Yudha Harimantoro T wrote:
Date: Fri, 10 Oct 2008 16:41:36 -0400
From: Bill Davidsen


Yudha Harimantoro T wrote:
Hi all,
Yesterday I build kernel 2.6.26.6 and it's run well. Today I got
2.6.27 patch and try to build it.

I build with `make oldconfig` and answer any question with default answer, I just press [enter].
I build with `make`. No error and all compiled.
Then I install with `make modules_install` and `make install`.


I realize that this is a low-probability thought, but did you:
- apply the patch against 2.6.26 NOT 2.6.26.6
Yup, I've did it.
- run make clean before applying the patch
I still need this for a pure 2.6.26? I'll try this.

After reboot the system I got 'kernel panic'.
This is the error picture :
http://www.ryht.co.cc/wordpress/wp-content/uploads/2008/10/pa101358.jpg
Is it a bugs?

http://www.ryht.co.cc/wordpress/wp-content/uploads/2008/10/pa101353.jpg [2.6.26.6 run well]

I keep configs in a separate place. I would first copy a 2.6.26 tree to a new directory (cp -rl linux-2.6.26 linux2.6.27) then be sure I had a clean copy with "make distclean" (or "make mrproper") and then apply the 2.6.27 patch. Then I would copy the 2.6.26 (or maybe 2.6.26.6) config to .config, and make the oldconfig.
None of that is magic, it just keeps me from making common mistakes, lets me start with a clean 2.6.27, etc, etc.
You mentioned oldconfig, but not starting back with a clean 2.6.26, which made me think of this.
Hm, I `cp /boot/config .config` in new kernel tree [2.6.27] for the
config. Do I make mistakes?

No, I was just noting that I try to start oldconfig with a known working config, to reduce the number of choices and possible errors. I wasn't sure if you did that, so I mentioned it.

--
Bill Davidsen <davidsen@xxxxxxx>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/