| 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
| ||
|
Date: Mon, 22 Jun 2009 16:43:08 +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 Mon, Jun 22, 2009 at 07:43:40PM +0530, Sudeep K N wrote: > Hi Russell, > > Thanks for the suggestion. > With the logs it is clear that crash is in the userspace. > I am getting one of the 2 logs(below) randomly. > >From trial#2, > pgd = c60bc000 > [00000000] *pgd=061ee031, *pte=00000000, *ppte=00000000 > I could understand that the page tables are not proper. > I am not able understand how to proceed. > > Trial#1: > VFS: Mounted root (ext2 filesystem). > Freeing init memory: 108K > linuxrc (1): undefined instruction: pc=40008100 > Code: e08e3003 eb002842 e2801008 e58c217c (e0812103) Your processor is misbehaving; none of the above hex codes are undefined instructions, so you shouldn't be taking an undefined instruction trap. That, coupled with the random nature of these crashes leads me to believe that it's a case of noisy power supply to the SoC. Suggest you get your hardware people to check your board. -- 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