From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46373)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1YcGaO-00076a-HD
	for qemu-devel@nongnu.org; Sun, 29 Mar 2015 13:01:21 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1YcGaJ-0004lZ-FS
	for qemu-devel@nongnu.org; Sun, 29 Mar 2015 13:01:20 -0400
Received: from [2a03:4000:1::4e2f:c7ac:d] (port=51370
	helo=v220110690675601.yourvserver.net)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1YcGaJ-0004lS-9K
	for qemu-devel@nongnu.org; Sun, 29 Mar 2015 13:01:15 -0400
Message-ID: <55182FCC.5060206@weilnetz.de>
Date: Sun, 29 Mar 2015 19:01:00 +0200
From: Stefan Weil <sw@weilnetz.de>
MIME-Version: 1.0
References: <20150328160709.GA2551@waldemar-brodkorb.de>	<5516DEDC.8080608@weilnetz.de>	<20150329134706.GA28330@waldemar-brodkorb.de>
	<55181FF4.6040808@weilnetz.de>
In-Reply-To: <55181FF4.6040808@weilnetz.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt
 masking/unmasking
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Waldemar Brodkorb <wbx@openadk.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>, Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org

Am 29.03.2015 um 17:53 schrieb Stefan Weil:
> Am 29.03.2015 um 15:47 schrieb Waldemar Brodkorb:
>> Hi Stefan,
>> Stefan Weil wrote,
>>
>>> You can debug the kernel panic by attaching a cross debugger to the
>>> running kernel.
>>> If you have a kernel image with debug symbols, this is very 
>>> comfortable.
>> How would I do this?
>> Tried to start qemu with -s -S and then attach with my cross-gdb
>> using the kernel with debug symbols. But gdb does not recognize the
>> panic:
>> Command: mdev -s
>> Command: ifconfig lo 127.0.0.1 up
>> Execution Finished, Exiting
>>
>> Sash command shell (version 1.1.1)
>> /> Kernel panic - not syncing: Attempted to kill init!
>> exitcode=0x0000000b
>>
>> ---[ end Kernel panic - not syncing: Attempted to kill init!
>> exitcode=0x0000000b

Is this the kernel panic which you get? I did not have a closer look
on it before, but now I see that it is something quite common:

Your kernel runs an init script (or binary) which terminates
(obviously normally). Then the kernel does not know what to
do, so it throws a kernel panic "Attempted to kill init".

Usually the init process should only terminate at a system shutdown.

Stefan