All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Gilles DOFFE <g.doffe@domain.hid>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [Vortx86DX] What's wrong with kernels upper than 2.6.30.10 ?
Date: Fri, 16 Apr 2010 09:27:54 +0200	[thread overview]
Message-ID: <1271402874.2365.715.camel@domain.hid> (raw)
In-Reply-To: <t2w95dbcd241004151500ne05d5991q4a8f6463f2b37ba1@domain.hid>

On Fri, 2010-04-16 at 00:00 +0200, Gilles DOFFE wrote:
> Hello,
> 
> I try to install a real-time Linux kernel on a Roboard based on a
> Vortex86DX (a x486 with TSC).
> 
> All works fine with :
> Linux Kernel 2.6.30.10
> Xenomai 2.5.1
> Adeos patch adeos-ipipe-2.6.30.8-x86-2.4-09.patch
> 
> But, for all kernels upper or equal to 2.6.31, I always get a double
> fault when testing WP bit. I have this double fault just after that :
> 
> Checking if this processor honours the WP bit even in supervisor
> mode...
> 
> I traced with some simple printk that the problem occurs in this
> function, at the end or after the call of fix_to_virt  :
> 
> static noinline int do_test_wp_bit(void)
> {
>         char tmp_reg;
>         int flag;
> 
>         __asm__ __volatile__(
>                 "       movb %0, %1     \n"
>                 "1:     movb %1, %0     \n"
>                 "       xorl %2, %2     \n"
>                 "2:                     \n"
>                 _ASM_EXTABLE(1b,2b)
>                 :"=m" (*(char *)fix_to_virt(FIX_WP_TEST)),
>                  "=q" (tmp_reg),
>                  "=r" (flag)
>                 :"2" (1)
>                 :"memory");
> 
>         return flag;
> }
> 
> I'm (quasi) sure that the problem is not that function, due to it
> works when the kernel is not patched.
> But where should I search ?

Try backporting these two 2.6.32 patches to your kernel; this should be
straightforward:
http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=576f57f82dfd6c3ac285b0af76e5e0ce617679ba
http://git.denx.de/?p=ipipe-2.6.git;a=commit;h=a250e984a76fd327a0d8cfada5290b27e99f1e4d


> 
> Can you give me some indications ?
> 
> Thanks,
> Gilles 
> _______________________________________________
> Adeos-main mailing list
> Adeos-main@domain.hid
> https://mail.gna.org/listinfo/adeos-main


-- 
Philippe.




  parent reply	other threads:[~2010-04-16  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-15 22:00 [Adeos-main] [Vortx86DX] What's wrong with kernels upper than 2.6.30.10 ? Gilles DOFFE
2010-04-15 22:18 ` Jan Kiszka
2010-04-15 22:24   ` Jan Kiszka
2010-04-16  7:27 ` Philippe Gerum [this message]
2010-04-16 13:23   ` Gilles DOFFE

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=1271402874.2365.715.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=adeos-main@gna.org \
    --cc=g.doffe@domain.hid \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.