All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maksym Veremeyenko <verem@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] mem usage and other application
Date: Thu, 15 Mar 2007 04:55:59 +0200	[thread overview]
Message-ID: <45F8B5BF.6070403@domain.hid> (raw)
In-Reply-To: <17912.37052.725635.483595@domain.hid>

Gilles Chanteperdrix пишет:

> Well, it really looks like an FPU bug. Could you try to:
> - upgrade your trunk to latest revision, then test
> - then apply the attached patch to your up-to-date trunk, then test
>   again ?
> 

I used configuration 2.6.17.14, xenomai-r2299

Before patching xenomai result was the same and more faulty after 
decreasing RAM size down to 256M.

After applying patch situation become worth, i got "Bad pte" messages, 
sometimes "Soft lockup detected", and kernel dump:

Mar 15 04:08:21 dev-3 kernel: Bad pte = 42a5fef8, process = ???, 
vm_flags = 100073, vaddr = 42f60000
Mar 15 04:08:21 dev-3 kernel:  <c0102f70> show_trace+0x12/0x14 
<c0103474> dump_stack+0x1c/0x1e
Mar 15 04:08:21 dev-3 kernel:  <c015c460> print_bad_pte+0x4f/0x5a 
<c015c4b1> vm_normal_page+0x46/0x5c
Mar 15 04:08:21 dev-3 kernel:  <c015c9d4> unmap_vmas+0x162/0x3e4 
<c015f059> exit_mmap+0x55/0xc1
Mar 15 04:08:21 dev-3 kernel:  <c010feb8> mmput+0x5a/0xb0  <c0113161> 
exit_mm+0xe8/0xee
Mar 15 04:08:21 dev-3 kernel:  <c011459f> do_exit+0x1a2/0x719 
<c010d21f> do_page_fault+0x4bf/0x542
Mar 15 04:08:21 dev-3 kernel:  <c010b1da> 
__ipipe_handle_exception+0x89/0xbf  <c0102988> error_code+0x54/0x64

Mar 15 04:08:21 dev-3 kernel: Bad pte = 42a5fef8, process = ???, 
vm_flags = 75, vaddr = 42f62000
Mar 15 04:08:21 dev-3 kernel:  <c0102f70> show_trace+0x12/0x14 
<c0103474> dump_stack+0x1c/0x1e
Mar 15 04:08:21 dev-3 kernel:  <c015c460> print_bad_pte+0x4f/0x5a 
<c015c4b1> vm_normal_page+0x46/0x5c
Mar 15 04:08:21 dev-3 kernel:  <c015c9d4> unmap_vmas+0x162/0x3e4 
<c015f059> exit_mmap+0x55/0xc1
Mar 15 04:08:21 dev-3 kernel:  <c010feb8> mmput+0x5a/0xb0  <c0113161> 
exit_mm+0xe8/0xee
Mar 15 04:08:21 dev-3 kernel:  <c011459f> do_exit+0x1a2/0x719 
<c010d21f> do_page_fault+0x4bf/0x542
Mar 15 04:08:21 dev-3 kernel:  <c010b1da> 
__ipipe_handle_exception+0x89/0xbf  <c0102988> error_code+0x54/0x64

Mar 15 04:08:23 dev-3 kernel: ------------[ cut here ]------------
Mar 15 04:08:23 dev-3 kernel: kernel BUG at mm/rmap.c:560!
Mar 15 04:08:23 dev-3 kernel: invalid opcode: 0000 [#1]
Mar 15 04:08:23 dev-3 kernel: Modules linked in: xeno_16550A
Mar 15 04:08:23 dev-3 kernel: CPU:    0
Mar 15 04:08:23 dev-3 kernel: EIP:    0060:[<c01619f0>]    Not tainted VLI
Mar 15 04:08:23 dev-3 kernel: EFLAGS: 00010286 
(2.6.17.14-xenomai-r2299-min-debug #3)
Mar 15 04:08:23 dev-3 kernel: EIP is at page_remove_rmap+0x1b/0x32
Mar 15 04:08:23 dev-3 kernel: eax: ffffffff   ebx: c1000000   ecx: 
c04d2aec   edx: c1000000
Mar 15 04:08:23 dev-3 kernel: esi: b7f79000   edi: d36f1de4   ebp: 
d351dce4   esp: d351dce4
Mar 15 04:08:23 dev-3 kernel: ds: 007b   es: 007b   ss: 0068
Mar 15 04:08:23 dev-3 kernel: Process bash (pid: 2698, 
threadinfo=d351c000 task=d500c030)
Mar 15 04:08:23 dev-3 kernel: Stack: d351dd3c c015caa6 00000000 d341f6fc 
d351dd54 00000000 00000001 b7fb3000
Mar 15 04:08:23 dev-3 kernel:        d3a5eb7c d55faa1c c04d2aec 00000000 
ffffffff d55faa6c d3a5eb7c 00000019
Mar 15 04:08:23 dev-3 kernel:        003a4c2b b7fb3000 00000000 d351dd54 
d3a08e04 d55faa1c d351dd64 c015f059
Mar 15 04:08:23 dev-3 kernel: Call Trace:
Mar 15 04:08:23 dev-3 kernel:  <c0102f26> show_stack_log_lvl+0x8a/0x94 
<c01030ba> show_registers+0x148/0x1b4
Mar 15 04:08:23 dev-3 kernel:  <c010328a> die+0x164/0x262  <c0103409> 
do_trap+0x81/0x9b
Mar 15 04:08:23 dev-3 kernel:  <c0103b5e> do_invalid_op+0x8e/0x98 
<c010b1da> __ipipe_handle_exception+0x89/0xbf
Mar 15 04:08:23 dev-3 kernel:  <c0102988> error_code+0x54/0x64 
<c015caa6> unmap_vmas+0x234/0x3e4
Mar 15 04:08:23 dev-3 kernel:  <c015f059> exit_mmap+0x55/0xc1 
<c010feb8> mmput+0x5a/0xb0
Mar 15 04:08:23 dev-3 kernel:  <c0175321> flush_old_exec+0x599/0x7c6 
<c01904ad> load_elf_binary+0x4bf/0x1478
Mar 15 04:08:23 dev-3 kernel:  <c0174718> 
search_binary_handler+0x76/0x181  <c018f8e7> load_script+0x1b7/0x1cc
Mar 15 04:08:23 dev-3 kernel:  <c0174718> 
search_binary_handler+0x76/0x181  <c01760f5> do_execve+0x13f/0x1ac
Mar 15 04:08:23 dev-3 kernel:  <c010142b> sys_execve+0x2f/0x76 
<c010269e> sysenter_past_esp+0x63/0x67
Mar 15 04:08:23 dev-3 kernel: Code: e8 7a 4b 13 00 8b 45 d0 83 c4 24 5b 
5e 5f c9 c3 55 89 e5 e8 33 98 fa ff 89 c2 83 40 08 f
Mar 15 04:08:23 dev-3 kernel: EIP: [<c01619f0>] 
page_remove_rmap+0x1b/0x32 SS:ESP 0068:d351dce4

With latest trunk and 256MB i get stable errors even with "perl 
Makefile.PL" for  XML-DOM-1.44 then any RT application used Native skin 
running.


-- 
________________________________________
Maksym Veremeyenko


  reply	other threads:[~2007-03-15  2:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 21:07 [Xenomai-help] mem usage and other application Maksym Veremeyenko
2007-03-14 21:26 ` Gilles Chanteperdrix
2007-03-14 22:38   ` Maksym Veremeyenko
2007-03-14 22:49     ` Gilles Chanteperdrix
2007-03-14 23:02       ` Maksym Veremeyenko
2007-03-14 23:05         ` Gilles Chanteperdrix
2007-03-14 23:27           ` Maksym Veremeyenko
2007-03-14 23:33             ` Gilles Chanteperdrix
2007-03-14 23:59               ` Maksym Veremeyenko
2007-03-15  0:18                 ` Gilles Chanteperdrix
2007-03-15  2:55                   ` Maksym Veremeyenko [this message]
     [not found] <17913.899.384216.185459@domain.hid>
2007-03-15  9:11 ` Gilles Chanteperdrix
2007-03-15 16:34   ` Maksym Veremeyenko
2007-03-18 17:18     ` Gilles Chanteperdrix
2007-03-18 17:35       ` Maksym Veremeyenko
2007-03-18 18:23         ` Gilles Chanteperdrix
2007-03-19 15:17           ` Maksym Veremeyenko

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=45F8B5BF.6070403@domain.hid \
    --to=verem@domain.hid \
    --cc=Xenomai-help@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.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 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.