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]
Date:   Mon, 1 Oct 2018 19:51:38 +0530
From:   Firoz Khan <firoz.khan@...aro.org>
To:     Tony Luck <tony.luck@...el.com>
Cc:     linux-ia64@...r.kernel.org, Fenghua Yu <fenghua.yu@...el.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Philippe Ombredanne <pombredanne@...b.com>,
        Kate Stewart <kstewart@...uxfoundation.org>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux-Arch <linux-arch@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>,
        Deepa Dinamani <deepa.kernel@...il.com>,
        Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>
Subject: Re: [PATCH v2 0/7] System call table generation support

Hi Tony,

On Fri, 28 Sep 2018 at 23:01, Luck, Tony <tony.luck@...el.com> wrote:
>
> Still does not boot. Last part of console log (nothing unusual
> before the "Kernel panic" line):
>
>
> EFI Variables Facility v0.08 2004-May-17
> sd 5:0:0:0: [sdb] 286749488 512-byte logical blocks: (147 GB/137 GiB)
> sd 5:0:0:0: [sdb] Write Protect is off
> sd 5:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
>  sdb: sdb1 sdb2
> sd 5:0:0:0: [sdb] Attached SCSI disk
> NET: Registered protocol family 17
> console [netcon0] enabled
> netconsole: network logging started
> Freeing unused kernel memory: 960K
> This architecture does not have kernel memory protection.
> Run /init as init process
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
>
> ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
>  ]---
>

Thanks for the update. I'm planning to solve this issue asap.

- Firoz

> -Tony

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ