From: Guenter Roeck <linux@roeck-us.net>
To: Xuetao Guan <gxt@pku.edu.cn>
Cc: linux-kernel@vger.kernel.org, Guan Xuetao <gxt@mprc.pku.edu.cn>,
Chen Gang <gang.chen.5i5j@gmail.com>,
Grant Likely <grant.likely@linaro.org>
Subject: Re: 回复： Re: 回复： Re: 回复： Status of 'unicore32' architecture in Linux kernel
Date: Thu, 04 Sep 2014 22:52:39 -0700 [thread overview]
Message-ID: <54094FA7.6000809@roeck-us.net> (raw)
In-Reply-To: <926403536.39754.1409733179383.JavaMail.root@bj-mail03.pku.edu.cn>
On 09/03/2014 01:32 AM, Xuetao Guan wrote:
>
[ ... ]
>> Please try the following patch. That seems to do it.
>> I am sure it can be improved, but it is a start.
>>
>> Thanks,
>> Guenter
>
> Thanks. I'll test it.
> BTW, Qemu codestyle is different, and tab should be replaced with blanks.
>
Here is where I am. User space code (busybox) was compiled
using the unicore toolchain available on the web.
...
serio: i8042 KBD port at 0x6eb00060,0x6eb00064 irq 22
mousedev: PS/2 mouse device common for all mice
Enable UniCore-F64 support.
Warning: unable to open an initial console.
Freeing unused kernel memory: 1156K (c0408000 - c0529000)
Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
The kernel tries to execute the init program, which fails with SIGSEGV.
I confirmed that the init program is loaded and starts to execute.
Any idea what might cause such a problem ?
Thanks,
Guenter
next prev parent reply other threads:[~2014-09-05 6:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 23:51 Status of 'unicore32' architecture in Linux kernel Guenter Roeck
2014-09-01 4:00 ` Chen Gang
2014-09-02 14:03 ` 回复： " Xuetao Guan
2014-09-02 15:58 ` Guenter Roeck
2014-09-03 0:09 ` 回复： " Xuetao Guan
2014-09-03 1:52 ` Guenter Roeck
2014-09-03 3:58 ` Guenter Roeck
2014-09-03 8:32 ` 回复： " Xuetao Guan
2014-09-05 5:52 ` Guenter Roeck [this message]
2014-09-05 6:13 ` 回复： " Xuetao Guan
2014-09-06 17:25 ` Guenter Roeck
2014-09-08 12:57 ` 回复： " Xuetao Guan
2014-09-08 13:35 ` Guenter Roeck
2014-09-09 0:58 ` 回复： " Xuetao Guan
2014-09-09 2:06 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54094FA7.6000809@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gang.chen.5i5j@gmail.com \
--cc=grant.likely@linaro.org \
--cc=gxt@mprc.pku.edu.cn \
--cc=gxt@pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.