Your message dated Sat, 13 Oct 2018 16:13:41 +0100
with message-id <[email protected]>
and subject line Re: Bug#896878: Info received (Bug#896878: Failed to execute
/init (error -2) Kernel panic)
has caused the Debian Bug report #896878,
regarding Failed to execute /init (error -2) Kernel panic
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
896878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896878
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sysvinit-core
Version: 2.88dsf-59.9
Hello!
New linux-image-4.9.0-6-amd64 4.9.82-1+deb9u3 and old
linux-image-3.2.0-4-amd64 3.2.96-2 does not want boot with
sysvinit-core. After installation systemd-sysv 232-25+deb9u2 all working
fine.
[ 0.228833] DMAR-IR: Failed to copy IR table for dmar1 from previous
kernel
[ 2.4575631 Failed to execute /init (error -2)
[ 2.4573031 Kernel panic - not syncing: No working init found. Try
passing i
nit= option to kernel. See Linux Documentation/init.txt for guidance.
[ 2.4580131 CPU: 25 PID: 1 Comm: swapper/0 Mot tainted 4.3.0-6-amd64 #1
Debia
n 4.9.82-l+deb9u3
[ 2.458113] Hardware name: Dell Inc. PowerEdge R730xd/0UCJNT, BIOS 2.4.3
01/1
7/2017
[ 2.4582051 0000000000000000 ffffffffa352e074 ffffffffa3803eO0
ffffa9478000f
f 40
[ 2.4585951 ffffffffa337cfbd O0O0000O00000O08 ffffa9478O0Off50
ffffa9478000f
ee8
[ 2.4589841 5080bfd4a466255c 5080bfd4a466255c OOOOOOOOOOOOOOOO
ffff96ccc26cl
000
[ 2.4593711 Call Trace:
[ 2.4594601 Kffffffffa352e0?4>1 ? dump_stack+0x5c/0x78
[ 2.4595521 1<ffffffffa3803e00>1 ? rest_init+0x4O/Ox80
[ 2.4596431 Kffffffffa337cfbd> 1 ? panic+0xe4/0x23f
[ 2.4597321 Kffffffffa3803e4O>1 ? rest_init+0x80/0x80
[ 2.4598211 Kffffffffa3803f21>1 ? kernel_init+0xel/OxlO0
[ 2.4599101 Kffffffffa3811537> 1 ? ret_from_fork+Ox57/Ox70
[ 2.4601031 Kernel Offset: 0x22200000 from Oxffffffff81000000
(relocation ran
ge: Oxffffffff80000O0O-0xffffffffbfffffff)
[ 2.4682561 Rebooting in 1 seconds..
--- End Message ---
--- Begin Message ---
On Fri, 27 Apr 2018 13:23:46 +0300 =?UTF-
8?B?0JDQvdC00YDQtdC5INCS0LDRgdC40LvQuNGI0LjQvQ==?=
<[email protected]> wrote:
> I don't know what helped out of this.
>
> # apt-get install --reinstall linux-image-4.9.0-6-amd64
> linux-image-amd64 sysvinit-core
>
> # upgrade-from-grub-legacy
>
> But now kernel 4.9.82-1+deb9u3 loading normally
"Failed to execute /init" means the initramfs was somehow broken. The
kernel reinstall will have regenerated the initramfs.
This could possibly have been caused by an unclean shutdown shortly
after an earlier update to the initramfses.
In general, you should fully upgrade from one stable release to the
next (including a reboot) before upgrading again.
Ben.
--
Ben Hutchings
All the simple programs have been written, and all the good names taken
signature.asc
Description: This is a digitally signed message part
--- End Message ---
_______________________________________________
Pkg-sysvinit-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
