public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Harald Arnesen <skogtun.linux@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Panic with latest git kernel
Date: Sun, 26 Jan 2014 16:00:16 +0100	[thread overview]
Message-ID: <52E52300.7020008@nod.at> (raw)
In-Reply-To: <52E51FEE.4020403@gmail.com>

Am 26.01.2014 15:47, schrieb Harald Arnesen:
> Richard Weinberger [2014-01-26 14:36]:
> 
>>> $ cpio --list </boot/initrd.img-3.13.0-03477-gdf32e43
>>> kernel
>>> kernel/x86
>>> kernel/x86/microcode
>>> kernel/x86/microcode/GenuineIntel.bin
>>> 50 blocks
>>> $
> 
>> Looks very strange.
>> Add rdinit=/bin/sh to your commandline such that you get a shell within
>> the initrd...
> 
> Okay, I did. On the non-working kernel/initrd, the working ditto, and
> the Debian-provided files. And ls shows contents that seem sane.
> 
> None of the initrds have a switch_root in them, neither in /sbin or
> anywhere else. They all have a /bin/pivot_root, which may be the same?

Your image shows that the kernel looses the init process because /init seems
to be unable to exec switch_root.
Find out what is going on in your initrd.

So far it has zero to do with the kernel itself.

Thanks,
//richard

  reply	other threads:[~2014-01-26 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26 12:50 Panic with latest git kernel Harald Arnesen
2014-01-26 13:01 ` Madper Xie
2014-01-26 13:03 ` Richard Weinberger
     [not found]   ` <52E50ED7.9070808@gmail.com>
2014-01-26 13:36     ` Richard Weinberger
2014-01-26 13:41       ` Harald Arnesen
2014-01-26 14:47       ` Harald Arnesen
2014-01-26 15:00         ` Richard Weinberger [this message]
2014-01-26 19:57           ` Harald Arnesen
2014-01-26 20:42             ` Sebastian Steinhuber

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=52E52300.7020008@nod.at \
    --to=richard@nod.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skogtun.linux@gmail.com \
    /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