From: "René Rebe" <rene@exactcode.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4932] Preliminary PPC64/Linux host support
Date: Sat, 26 Jul 2008 21:32:18 +0200 [thread overview]
Message-ID: <488B7BC2.3020100@exactcode.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0807252212390.2131@linmac.oyster.ru>
Hi,
malc wrote:
> On Fri, 25 Jul 2008, Ren? Rebe wrote:
>
>> malc wrote:
>>> On Thu, 24 Jul 2008, Ren Rebe wrote:
>>>
>
> [..snip..]
>
>> I gave it a spin yesterday, it built and managed to boot a decent
>> linux-2.6
>> system until the first user-space programs after init where running and
>> segfaulted thereafter.
>
> 'Decent linux-2.6 system'? Recent perhaps? In any case that is strange
> since linux-test image does work here as does ls after booting it (not
> much, i know)
Yes, recent (2.6.2x), of course :-)
>> I'm abroad the next days, but I'll definetly will help (or try to,
>> I'm no
>> yet that into TCG, yet :-) to hunt those segfaults :-)
>
> Thanks, in the meantime can You tell what is that you have unsuccessfully
> tried to boot?
Well it's my standard T2 SDE (http://t2-project.org) test image. Actually it
boots, and quite some user-space is running (statically linked early
userspace of
the initrd for u/dev & co) and then the system init and even mounting the
virtual/pseudo filesystems. It "only" segfaults somewhere soonish after init
is already running and executed the first tasks. So on my side actually
"quite a lot" already worked.
However, I just checked with the qemu:HEAD and the qemu segfault
booting my system is already gone - though it's booting quite slowly :-(
Great work so far!
René
--
René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
http://exactcode.de | http://t2-project.org | http://rene.rebe.name
next prev parent reply other threads:[~2008-07-26 19:33 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 19:17 [Qemu-devel] [4932] Preliminary PPC64/Linux host support malc
2008-07-24 6:01 ` René Rebe
2008-07-24 17:41 ` malc
2008-07-24 18:42 ` Andreas Färber
2008-07-25 8:41 ` René Rebe
2008-07-25 18:15 ` malc
2008-07-26 19:32 ` René Rebe [this message]
2008-07-27 18:17 ` malc
[not found] ` <1964D914-95C1-4A3E-AE40-2DE082D40C24@hotmail.com>
2008-07-24 23:33 ` C.W. Betts
2008-07-25 18:18 ` malc
2008-07-26 13:08 ` Andreas Färber
[not found] ` <F41A287D-66CA-42E4-A191-CD5381987301@hotmail.com>
2008-07-26 17:36 ` C.W. Betts
2008-07-26 18:00 ` Andreas Färber
2008-07-26 18:54 ` malc
2008-07-26 20:42 ` Andreas Färber
2008-07-27 18:14 ` malc
2008-07-29 16:28 ` [Qemu-devel] Mac OS X PPC host support (was: [4932] Preliminary PPC64/Linux host support) Andreas Färber
2008-07-29 20:23 ` malc
2008-07-30 18:45 ` Blue Swirl
2008-07-31 17:15 ` malc
2008-07-31 18:57 ` malc
2008-07-31 21:50 ` Andreas Färber
2008-08-01 18:52 ` malc
2008-08-02 21:29 ` Andreas Färber
2008-08-03 18:56 ` malc
2008-08-02 16:35 ` Andreas Färber
[not found] ` <E3E8B39E-1924-465D-AA4A-9250D835C932@hotmail.com>
2008-08-02 19:43 ` C.W. Betts
2008-07-26 13:39 ` [Qemu-devel] [4932] Preliminary PPC64/Linux host support Andreas Färber
[not found] ` <1D9DD99A-96CE-4570-B8EE-428CDBAE5FE3@hotmail.com>
2008-07-26 17:13 ` C.W. Betts
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=488B7BC2.3020100@exactcode.de \
--to=rene@exactcode.de \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).