From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: dashesy <dashesy@gmail.com>
Cc: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: 2.6.33.9-rt31 boot problem
Date: Wed, 15 Jun 2011 12:28:17 -0700 [thread overview]
Message-ID: <4DF907D1.1040008@localhost> (raw)
In-Reply-To: <BANLkTikywL79BpXj44Ve24SbmwB1Wr1Ckg@mail.gmail.com>
On 06/15/2011 12:18 PM, dashesy wrote:
> On Wed, Jun 15, 2011 at 11:48 AM, Fernando Lopez-Lezcano
> <nando@ccrma.stanford.edu> wrote:
>> 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.
>
> Thanks for the reply,
> Actually oops is much earlier than init, as you can see in the
> attached boot.log I have "init=/bin/sh"
> [ 0.000000] Linux version 2.6.33.9-rt31 (ehsan@ehsan) (gcc version
> 4.6.0 20110530 (Red Hat 4.6.0-9) (GCC) ) #3 SMP PREEMPT RT Wed Jun 8
> 16:16:46 MDT 2011
>
> [ 0.000000] Command line: console=ttyS0 root=/dev/sda rw init=/bin/sh
I see, yes (sorry I did not look at the log before), very very early...
don't know what to make of it, sorry...
-- Fernando
prev parent reply other threads:[~2011-06-15 19:28 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
2011-06-15 19:18 ` dashesy
2011-06-15 19:28 ` Fernando Lopez-Lezcano [this message]
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=4DF907D1.1040008@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).