lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090619134446.GI24573@n2100.arm.linux.org.uk>
Date:	Fri, 19 Jun 2009 14:44:46 +0100
From:	Russell King - ARM Linux <linux@....linux.org.uk>
To:	Sudeep K N <sudeepholla.maillist@...il.com>
Cc:	linux-arm-kernel@...ts.arm.linux.org.uk, drzeus-mmc@...eus.cx,
	linux-kernel@...r.kernel.org
Subject: Re: Rootfs in eMMC: Kernel panic ...Attempted to kill init!

On Thu, Jun 18, 2009 at 02:48:10PM +0530, Sudeep K N wrote:
> After mounting the rootfs in eMMC, it panics.
> Panic log as below.  When I traced, I observed it fails while its
> execution "run_init_process"
> I have tried with different init process,i.e. init=/linuxrc,
> init=/bin/busybox, init=/sbin/init
> Even I tried initramfs and the switch_root/pivot_root to rootfs on
> eMMC partition.
> In all the cases, I got the same panic.
> Can anybody help me in understanding the exact reason for this panic?

Enable CONFIG_DEBUG_USER and pass user_debug=31 - that should get
more detail on the problem that's killing init.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ