All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Boot issues with custom 64-bit kernel v3.19
Date: Sun, 21 May 2017 17:15:34 +0200	[thread overview]
Message-ID: <20170521151534.GA7016@kroah.com> (raw)
In-Reply-To: <CAPn5F5zx59TNChAbhUMxqepHZxXL4yyRu4JCCesCxeBOOwcMQQ@mail.gmail.com>

On Fri, May 05, 2017 at 04:58:27PM -0400, Aditya Basu wrote:
> I am trying to compile and boot Linux Kernel v3.19 (64-bit version) using -
> 
> make defconfig
> make kvmconfig
> make -j8
> 
> The compilation works out without any errors but it doesn't boot
> inside qemu or my host machine.
> I use the following command line parameters to linux: "debug
> earlyprintk loglevel=7"
> 
> # The boot hangs at the point -
> ####################################
> Booting from ROM...
> early console in setup code
> early console in decompress_kernel
> 
> Decompressing Linux... Parking ELF... done.
> Booting the kernel .
> ####################################
> 
> # Things I have tried so far:
> - Interestingly if I uncheck the 64-bit build in config (from make
> menuconfig), the resulting 32-bit kernel boots correctly.
> 
> - Have tried running qemu with different cpus (host) + with & without kvm.
> 
> sudo qemu-system-x86_64 -m 4G -append 'debug earlyprintk loglevel=7'
> -kernel arch/x86/boot/bzImage -cpu host -enable-kvm
> 
> I know the kernel will panic because of no root filesystem, but it
> happens later in the boot process. I am basing this from booting the
> 32 bit version of the kernel which prints out a lot of stuff and then
> panics due to no vfs_root.
> 
> - The 64-bit versions of kernel v4.2 and above don't have this issue -
> meaning they boot correctly.

Great!  Stick with newer kernels, 3.19 is really old, as is 4.2, lots
and lots of things have been fixed since then, you aren't going to be
able to get any help from anyone in the community if you use old kernels
like that, sorry.

> 
> Any pointers to what the mistake is?
> 
> *Linux Kernel Repo used*
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

That has all kernel releases _ever_, you need to be a bit more specific
as to the branch you are using :)

good luck!

greg k-h

  reply	other threads:[~2017-05-21 15:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05 21:33 Boot issues with custom 64-bit kernel v3.19 Aditya Basu
2017-05-21 15:15 ` Greg KH [this message]
2017-05-22 15:29   ` Aditya Basu
2017-05-22 15:43     ` Greg KH
2017-05-22 16:23       ` Aditya Basu

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=20170521151534.GA7016@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.