kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen-sQDSfeB7uhw@public.gmane.org>
To: Yudha Harimantoro T
	<public-yudha.ht-Re5JQEeQqe8AvxtiuMwx3w-z5DuStaUktnZ+VzJOa5vwg@public.gmane.org>
Cc: public-kernel-testers-u79uwXL29TY76Z2rM5mHXA-z5DuStaUktnZ+VzJOa5vwg@public.gmane.org,
	public-linux-kernel-u79uwXL29TY76Z2rM5mHXA-z5DuStaUktnZ+VzJOa5vwg@public.gmane.org
Subject: Re: Error : Linux-2.6.27
Date: Fri, 10 Oct 2008 16:41:36 -0400	[thread overview]
Message-ID: <48EFBE00.8030609@tmr.com> (raw)
In-Reply-To: <264b990a0810100126l1029f734x7204f8c42ae21609-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>



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
- run make clean before applying the patch

> 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.

-- 
Bill Davidsen <davidsen-sQDSfeB7uhw@public.gmane.org>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

  parent reply	other threads:[~2008-10-10 20:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10  8:26 Error : Linux-2.6.27 Yudha Harimantoro T
     [not found] ` <264b990a0810100126l1029f734x7204f8c42ae21609-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-10 11:53   ` Alexey Dobriyan
     [not found]     ` <20081010115342.GB25982-2ev+ksY9ol182hYKe6nXyg@public.gmane.org>
2008-10-10 12:36       ` Alan Jenkins
2008-10-10 20:41   ` Bill Davidsen [this message]
     [not found] <6966154.1481223935318911.JavaMail.root@zimbra>
2008-10-13 22:03 ` Zaharov D.A.
2008-10-14 17:09   ` Aioanei Rares
     [not found]     ` <48F4D24A.5070400-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-10-14 19:45       ` Alan Jenkins
     [not found]         ` <48F4F6CA.9040103-cCz0Lq7MMjm9FHfhHBbuYA@public.gmane.org>
2008-10-15  5:59           ` rajeev kumar
     [not found]             ` <df3f2abe0810142259m75c7f3a1ue8d8f9c1ed171ed5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-16  6:16               ` Yudha Harimantoro T

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48EFBE00.8030609@tmr.com \
    --to=davidsen-sqdsfeb7uhw@public.gmane.org \
    --cc=public-kernel-testers-u79uwXL29TY76Z2rM5mHXA-z5DuStaUktnZ+VzJOa5vwg@public.gmane.org \
    --cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA-z5DuStaUktnZ+VzJOa5vwg@public.gmane.org \
    --cc=public-yudha.ht-Re5JQEeQqe8AvxtiuMwx3w-z5DuStaUktnZ+VzJOa5vwg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).