From: Kim Christensen <kingudk@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: Config_preempt_rt patch for 2.6.34 or newer kernels
Date: Thu, 10 Jun 2010 22:19:30 +0200 [thread overview]
Message-ID: <AANLkTin4hTyfOLsdxZcT8GVFA4UvozJ9RaG4YSoddgEj@mail.gmail.com> (raw)
Hi
I'm attempting to get a CONFIG_PREEMPT_RT patched kernel to run with
the Embest Devkit8000 board. It seems that the 2.6.34 kernel series
(and later) vanilla kernels have support for the board and compiles
quite fine.
However the latest CONFIG_PREEMPT_RT patch available is for the 2.6.33 series.
I have found a 2.6.33-rc8 kernel (
http://gitorious.org/devkit8000/linux-omap-devkit8000/commits/4.3inch
) which supports the hardware, the patch for 2.6.33-rc8-rt2 applies
mostly without problems (patch complains about that it has already
been applied to one file). The kernel however panics when it is
configured with CONFIG_PREEMPT_RT=y, it boots fine otherwise.
Before the kernel panics the kernel complains about a null pointer
deref. And the kernel panics on a missing rootfilesystem, which seems
to be caused because it falls back from booting from a MMC card to
using NFS (if I'm not mistaken). Somehow I think that the deref and
the changed device for the rootfs is related, I just don't know how to
approach the issue.
So I was hoping that there would be a patch for the 2.6.34 series or
perhaps one for the one of the early 2.6.35-rcX kernels.
Is anyone able to tell me when or if such patches is available?
Alternatively is there anyone who is able to provide pointers to solve
the problems with the 2.6.33-rc8 kernel?
Any help will be greatly appreciated.
The best regards
Kim Christensen
reply other threads:[~2010-06-10 20:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTin4hTyfOLsdxZcT8GVFA4UvozJ9RaG4YSoddgEj@mail.gmail.com \
--to=kingudk@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).