El Fri, 23 Oct 2015 17:45:57 +0800
Rui Xiang escribió:
> Hi，list
>
> I encounter a panic about init process.
>
> Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0007
>
> Pid: 1, comm: init Tainted: G RO 3.4.24.19-0.11-default #1
> Call Trace:
> [] panic+0xc1/0x1e2
[Xishi Qiu]
> Hi Petter,
Hi.
> You mean init will be killed at boot time when there is no memory,
> right?
The linux kernel "out of memory" killer will kill fairly random
processes (the last one asking for more memory, if I recall correctly)
when the machine run out of memory. Earlier it could
On 2015/10/24 14:54, Petter Reinholdtsen wrote:
> [Rui Xiang]
>> Hi，list
>
> Hi.
>
>> It seems that reboot or force reboot through *sysvinit* have the problem.
>> Furthermore, using reboot -f in *systemd* should also have this
>> problem, right?
>>
>> And is that a bug for current reboot process
On 2015/10/23 17:45, Rui Xiang wrote:
> Hi，list
>
> I encounter a panic about init process.
>
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0007
>
> Pid: 1, comm: init Tainted: G RO 3.4.24.19-0.11-default #1
> Call Trace:
> [] panic+0xc1/0x1e2
> [] do_exit+0x7d
[Rui Xiang]
> Hi，list
Hi.
> It seems that reboot or force reboot through *sysvinit* have the problem.
> Furthermore, using reboot -f in *systemd* should also have this
> problem, right?
>
> And is that a bug for current reboot process in sysvinit or systemd?
>
> All comments are welcome, thanks.
Unsubscribe
Sent from my iPhone
> On Oct 23, 2015, at 2:45 AM, Rui Xiang wrote:
>
> Hi，list
>
> I encounter a panic about init process.
>
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0007
>
> Pid: 1, comm: init Tainted: G RO 3.4.24.19-0.11-default #1
> Call
Hi，list
I encounter a panic about init process.
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0007
Pid: 1, comm: init Tainted: G RO 3.4.24.19-0.11-default #1
Call Trace:
[] panic+0xc1/0x1e2
[] do_exit+0x7db/0x8d0
[] do_group_exit+0x3a/0xa0
[] get_signal_to_deliv
