From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: dashesy <dashesy@gmail.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.33.9-rt31 boot problem
Date: Wed, 15 Jun 2011 10:48:10 -0700 [thread overview]
Message-ID: <4DF8F05A.6050203@localhost> (raw)
In-Reply-To: <BANLkTiknsZhD2XHYoW4x2M8RfDku8righg@mail.gmail.com>
On 06/12/2011 09:21 AM, dashesy wrote:
> First, sorry for double post, I did not know if my email went through
> first time (maybe for large config file attached)
>
> Same machine 2.6.33.7.2-rt30 boots fine with Ubuntu and no problem at
> all, today I tried the new version with Fedora 15 but it crashes early
> in the boot process.
A workaround in Fedora 15 (posted in another message to another list so
you may not have seen it) is to use upstart instead of systemd for
startup (systemd requires features only found on newer kernels).
In the kernel boot line add "init=/sbin/upstart" and of course make sure
you have the upstart package installed.
BTW, thanks for the patch!
-- Fernando
> I have attached boot log I get from Qemu which is
> the same (apart from the CPU number for example). I also have attached
> the patch needed for successful build; V4l example in the
> documentation was removed (did not compile with new API), also some
> gcc4.6 related issues with anonymous union and superfluous warnings
> during build was resolved. The patch is just to have the build so it
> is not fully documented.
> Please let me know if any further information is needed, if I should
> submit the crash to another mailing list, or if I should enable some
> option in the config file for more elaborate crash log. Since crash is
> very early I could not get a crashdump.
>
> I will be happy to look into the source code too (I am learning), if
> you can give me some hint, thanks
>
> dashesy
next prev parent reply other threads:[~2011-06-15 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 16:21 2.6.33.9-rt31 boot problem dashesy
2011-06-15 17:48 ` Fernando Lopez-Lezcano [this message]
2011-06-15 19:18 ` dashesy
2011-06-15 19:28 ` Fernando Lopez-Lezcano
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=4DF8F05A.6050203@localhost \
--to=nando@ccrma.stanford.edu \
--cc=dashesy@gmail.com \
--cc=linux-rt-users@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 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).