Re: [Qemu-devel] [PATCH v2] qemu-m68k: add support for interrupt masking/unmasking

[Stefan Weil <sw@weilnetz.de>]

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