From: "Jan Sommer" <jan.sommer@s2008.tu-chemnitz.de>
To: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Preempt-rt on 3.2.23 raspberry pi kernel
Date: Sun, 29 Jul 2012 22:32:08 +0200 [thread overview]
Message-ID: <op.wh75zuz8k9j7wf@soja-mo> (raw)
In-Reply-To: <op.wh75q4qvk9j7wf@soja-mo>
Hello,
This probably is related to the this thread
http://comments.gmane.org/gmane.linux.rt.user/8424 but I don't know how to
answer to it as I have just subscribed to the mailinglist.
As Tom I used the 3.2.23 branch for the raspberry pi from bootc
(http://www.bootc.net/projects/raspberry-pi-kernel/) and applied the
rt-patch. Because Tom told about problems with the USB-driver I set up my
system to mount the rootfs via NFS.
The patched kernel boots up fine when using the voluntary, low latency and
basic preempt option but fails to boot after compiling it with the
preempt_full option.
You can find a screenshot (literally ;-) ) of the last kernel
output here: http://imageshack.us/photo/my-images/140/rpikernellog.jpg/
It complains about a certain part of the code within rtmutex.c.
As I'm fairly new to building kernel related things, does anyone has a
suggestion what to do? The problem occurs in both versions of the patch
(rt36 and rt37) and it does not matter if I want to mount the rootfs via
sd-card or NFS (probably because the error appears even before).
At the moment I don't have the chance to hook up a serial cable to the
serial port as I don't have level converters.
Best regards,
Jan
next parent reply other threads:[~2012-07-29 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.wh4l2os2k9j7wf@soja-mo>
[not found] ` <op.wh75q4qvk9j7wf@soja-mo>
2012-07-29 20:32 ` Jan Sommer [this message]
2012-07-30 5:37 ` Preempt-rt on 3.2.23 raspberry pi kernel Nick Lott
2012-10-28 10:44 ` Thomas Gleixner
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=op.wh75zuz8k9j7wf@soja-mo \
--to=jan.sommer@s2008.tu-chemnitz.de \
--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