[GoFlex Home] Kernel panic - Attempted to kill init!

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

[GoFlex Home] Kernel panic - Attempted to kill init!

Postby ava1ar » Fri Jan 22, 2016 6:39 am

Hi,

Faced a very strange problem with my Seagate GoFlex today - getting kernel panic on reboot/shutdown. Here is a log message:
$this->bbcode_second_pass_code('', '[ 46.685855] zram: Removed device: zram0
[ 49.245466] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[ 49.274808] systemd-journald[129]: Received SIGTERM from PID 1 (systemd-shutdow).
[ 49.305793] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[ 49.338850] systemd-shutdown[1]: Hardware watchdog 'Orion Watchdog', version 0
[ 49.347468] systemd-shutdown[1]: Unmounting file systems.
[ 49.353849] systemd-shutdown[1]: Remounting '/' read-only with options 'data=ordered'.
[ 49.403510] EXT4-fs (sda1): re-mounted. Opts: data=ordered
[ 49.419181] systemd-shutdown[1]: Remounting '/' read-only with options 'data=ordered'.
[ 49.427591] EXT4-fs (sda1): re-mounted. Opts: data=ordered
[ 49.433189] systemd-shutdown[1]: All filesystems unmounted.
[ 49.438982] systemd-shutdown[1]: Deactivating swaps.
[ 49.444291] systemd-shutdown[1]: All swaps deactivated.
[ 49.449778] systemd-shutdown[1]: Detaching loop devices.
[ 49.464717] systemd-shutdown[1]: All loop devices detached.
[ 49.470413] systemd-shutdown[1]: Detaching DM devices.
[ 49.476260] systemd-shutdown[1]: All DM devices detached.
[ 49.494312] systemd-shutdown[1]: Successfully changed into root pivot.
[ 49.501078] systemd-shutdown[1]: Returning to initrd...
[ 49.525007] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 49.525007]
[ 49.534244] CPU: 0 PID: 1 Comm: shutdown Tainted: G O 4.3.3-2-ARCH #1
[ 49.541874] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[ 49.548237] [<c00106c8>] (unwind_backtrace) from [<c000db0c>] (show_stack+0x10/0x14)
[ 49.556074] [<c000db0c>] (show_stack) from [<c00c7c2c>] (panic+0x88/0x200)
[ 49.563024] [<c00c7c2c>] (panic) from [<c0021d74>] (do_exit+0xa74/0xab8)
[ 49.569793] [<c0021d74>] (do_exit) from [<c0021e1c>] (do_group_exit+0x38/0xf0)
[ 49.577098] [<c0021e1c>] (do_group_exit) from [<c0021ee4>] (__wake_up_parent+0x0/0x18)
[ 49.585083] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 49.585083]')
Last time I updated the system somewhere around first week on January and reboot was working fine and today after all the updates I faced the above issue.
Here is the version of kernel\uboot I have:
$this->bbcode_second_pass_code('', 'core/linux-kirkwood-dt 4.3.3-2
alarm/uboot-goflexhome 2015.10-1
alarm/uboot-tools 2016.01-1')
my uEnv.txt is
$this->bbcode_second_pass_code('', 'optargs=rootfstype=ext4 ipv6.disable=1 elevator=noop panic=-1
rdfile=none')
This is what I tried to do in order to resolve the issue:
$this->bbcode_list('1')
  • checked the ext4 root partition (I am using usb flash drive for system)
  • downgraded the kernel to 4.3.2 and 4.3.1
  • downgraded the uboot-tools 2015.10-1
  • tried booting without initrd (with rdfile=none in uEnv.txt) and with initrd enabled

  • As a temporary workaround I added panic=-1 to the kernel parameters to be able to reboot the machine without the physically resetting it, but I want to find the root cause of the issue.

    Is there any ideas what should I try to do in order to resolve this.
    Thanks in advance for any suggestions!
    ava1ar
     
    Posts: 16
    Joined: Sun Oct 25, 2015 3:26 pm
    Location: Guttenberg, NJ, USA

    Return to Marvell Kirkwood

    Who is online

    Users browsing this forum: No registered users and 13 guests