public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: sam@ravnborg.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kexec@lists.infradead.org,
	torvalds <torvalds@linux-foundation.org>
Subject: Re: kexec: Cannot determine the file type of arch/x86/boot/bzImage
Date: Tue, 16 Oct 2007 14:45:44 -0700	[thread overview]
Message-ID: <20071016144544.bad9ff3c.randy.dunlap@oracle.com> (raw)
In-Reply-To: <47152FE6.3050204@m3y3r.de>

On Tue, 16 Oct 2007 23:40:54 +0200 Thomas Meyer wrote:

> Randy Dunlap schrieb:
> > On Tue, 16 Oct 2007 21:51:13 +0200 Thomas Meyer wrote:
> >
> > [adding kexec mailing list]
> >
> >   
> >> Look at this:
> >>
> >> $ file arch/x86/boot/bzImage (tree 821f3eff7cdb9d6c7076effabd46c96c322daed1)
> >> arch/x86/boot/bzImage: Linux kernel x86 boot executable zImage, version
> >> 2.6.23 (thomas@hotzenplotz) #39, RO-rootFS, root_dev 0x803, swap_dev
> >> 0x1, Prompt for Videomode
> >>
> >> $ file /boot/bzImage-2.6.23
> >> /boot/bzImage-2.6.23: Linux kernel x86 boot executable RO-rootFS,
> >> root_dev 0x803, swap_dev 0x1, Normal VGA
> >>
> >> and this:
> >>
> >> # kexec -l arch/x86/boot/bzImage
> >> Cannot determine the file type of arch/x86/boot/bzImage
> >>
> >> How to solve this error?
> >>     
> $ git bisect good
> f77bf01425b11947eeb3b5b54685212c302741b8 is first bad commit
> commit f77bf01425b11947eeb3b5b54685212c302741b8
> Author: Sam Ravnborg <sam@neptun.(none)>
> Date:   Mon Oct 15 22:25:06 2007 +0200
> 
>     kbuild: introduce ccflags-y, asflags-y and ldflags-y
> 
>     Introduce ccflags-y, asflags-y and ldflags-y so we soon can
>     deprecate use of EXTRA_CFLAGS, EXTRA_AFLAGS and EXTRA_LDFLAGS.
>     This patch does not touch any in-tree users - thats next round.
>     Lets get this committed first and then fix the users of the
>     soon to be deprecated variants next.
> 
>     The rationale behind this change is to introduce support for
>     makefile fragments like:
> 
>     ccflags-$(CONFIG_WHATEVER_DEBUG) := -DDEBUG
> 
>     As a replacement for the uglier:
>     ifeq ($(CONFIG_WHATEVER_DEBUG),y)
>             EXTRA_CFLAGS := -DDEBUG
>     endif
> 
>     Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
> 
> :040000 040000 03915c7c738eefa31f2327521130df23b7dfe95e
> e2a1677df3709813ff793fdfa77d80fff9b838a7 M      Documentation
> :040000 040000 ff4ad149975df39509a18782341f1f8f6a32f07a
> 663bce3c08a0f2e107cecb0b29edc4fe9d5735a0 M      scripts


This makes 2 big problems with this patch in the last 1 hour.

Probably time to revert it...

---
~Randy

  reply	other threads:[~2007-10-16 21:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16 19:51 kexec: Cannot determine the file type of arch/x86/boot/bzImage Thomas Meyer
2007-10-16 20:06 ` Randy Dunlap
2007-10-16 21:00   ` yhlu
2007-10-16 21:40   ` Thomas Meyer
2007-10-16 21:45     ` Randy Dunlap [this message]
2007-10-16 22:06     ` Sam Ravnborg
2007-10-16 21:43 ` Luca Tettamanti
2007-10-16 23:27 ` Eric W. Biederman

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=20071016144544.bad9ff3c.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=thomas@m3y3r.de \
    --cc=torvalds@linux-foundation.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