From: Philippe Reynes <philippe.reynes@isismpp.fr>
To: linux-rt-users@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Announce] 2.6.29-rt1
Date: Fri, 27 Mar 2009 11:10:53 +0000 (UTC) [thread overview]
Message-ID: <gqic7t$c27$1@ger.gmane.org> (raw)
In-Reply-To: gqi6oc$1s3$1@ger.gmane.org
Hi all
I've tried to remove the mlockall(MCL_CURRENT|MCL_FUTURE)
and now, the kernel don't crash. But a data corruption
appear in the data saved by the application. Such corruption
never occurs with other kernel (2.6.28 and 2.6.29). I'll
investigate if it could be an application bug.
Philippe
Le Fri, 27 Mar 2009 09:37:17 +0000, Philippe Reynes a écrit :
> Hi
>
>
> I've got crashes when I run an app with thread with RT priority. This
> crash could happen on any comman, here some log of crashes :
>
>
> First one :
>
> server calling Oops: Exception in kernel mode, sig: 5 [#1] PREEMPT
> MPC837x RR605
> Modules linked in:
> NIP: c0075b08 LR: c0075a50 CTR: c00d7d90 REGS: dbb6dcb0 TRAP: 0700 Not
> tainted (2.6.29-rt1) MSR: 00029032 <EE,ME,CE,IR,DR> CR: 24002488 XER:
> 00000000 TASK = dddea1e0[1769] 'vsftpd' THREAD: dbb6c000 GPR00: 00000001
> dbb6dd60 dddea1e0 df803e24 df803e10 df803e08 00000000 ddc72020
> GPR08: 00000000 0000001b dddea1e0 df803e24 24000482 100bf094 00000000
> c04aa6fc
> GPR16: 00200200 00100100 c04e5958 c04e595c dbb6dd68 c04e0000 c04e0000
> c04aa6bc
> GPR24: 00000020 dbb6ddd8 00000010 df80ae00 00000000 dbb6de38 df816800
> df803e00
> NIP [c0075b08] cache_alloc_refill+0x180/0x62c LR [c0075a50]
> cache_alloc_refill+0xc8/0x62c Call Trace:
> [dbb6dd60] [c038878c] preempt_schedule_irq+0x5c/0x80 (unreliable)
> [dbb6ddd0] [c00761a0] kmem_cache_alloc+0x6c/0x140 [dbb6de00] [c002ddb4]
> __sigqueue_do_alloc+0xa0/0xec [dbb6de10] [c002e2f8]
> send_signal+0xa4/0x224 [dbb6de30] [c002f680]
> do_notify_parent+0x1a8/0x1d4 [dbb6ded0] [c0025608] do_exit+0x584/0x69c
> [dbb6df10] [c00257a0] do_group_exit+0x80/0xac [dbb6df30] [c00257e0]
> sys_exit_group+0x14/0x28 [dbb6df40] [c00117f4] ret_from_syscall+0x0/0x38
> --- Exception: c01 at 0xfef463c
> LR = 0xffa5884
> Instruction dump:
> 7f87f800 40be0018 80ff0010 38000001 901f0048 7f872000 419e00e8 80070010
> 813b001c 7c090010 38000000 7c000114 <0f000000> 381a0001 38c7001c
> 7c0903a6 ---[ end trace 99200bd45c29aa91 ]---
> Fixing recursive fault but reboot is needed!
>
>
> Second one :
> I've run my app, and after just run a simple "ifconfig"
>
>
> -sh-2.05b# ifconfig
> eth0 Link eOops: Exception in kernel mode, sig: 5 [#1] PREEMPT
> MPC837x RR605
> Modules linked in:
> NIP: c0075b08 LR: c0075a50 CTR: c02cf170 REGS: dab41cb0 TRAP: 0700 Not
> tainted (2.6.29-rt1) MSR: 00029032 <EE,ME,CE,IR,DR> CR: 24002488 XER:
> 00000000 TASK = df8be100[1756] 'ifconfig' THREAD: dab40000 GPR00:
> 00000001 dab41d60 df8be100 df803e24 df803e10 df803e08 00000000 dddcc000
> GPR08: 00000000 0000001b df8be100 df803e24 24000482 10023370 00000000
> c04aa6fc
> GPR16: 00200200 00100100 c04e5958 c04e595c dab41d68 c04e0000 c04e0000
> c04aa6bc
> GPR24: 00000020 dab41dd8 00000010 df80ae00 00000000 dab41e38 df816800
> df803e00
> NIP [c0075b08] cache_alloc_refill+0x180/0x62c LR [c0075a50]
> cache_alloc_refill+0xc8/0x62c Call Trace:
> [dab41d60] [00000001] 0x1 (unreliable) [dab41dd0] [c00761a0]
> kmem_cache_alloc+0x6c/0x140 [dab41e00] [c002ddb4]
> __sigqueue_do_alloc+0xa0/0xec [dab41e10] [c002e2f8]
> send_signal+0xa4/0x224 [dab41e30] [c002f680]
> do_notify_parent+0x1a8/0x1d4 [dab41ed0] [c0025608] do_exit+0x584/0x69c
> [dab41f10] [c00257a0] do_group_exit+0x80/0xac [dab41f30] [c00257e0]
> sys_exit_group+0x14/0x28 [dab41f40] [c00117f4] ret_from_syscall+0x0/0x38
> --- Exception: c01 at 0xff3b63c
> LR = 0xffec884
> Instruction dump:
> 7f87f800 40be0018 80ff0010 38000001 901f0048 7f872000 419e00e8 80070010
> 813b001c 7c090010 38000000 7c000114 <0f000000> 381a0001 38c7001c
> 7c0903a6 ---[ end trace f43c24570097662c ]---
> Fixing recursive fault but reboot is needed!
>
>
>
> The kernel is a 2.6.29-rt1 compiled with ltib for powerpc (mpc8377E).
>
> Philippe
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-27 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 10:54 [Announce] 2.6.29-rt1 GeunSik Lim
2009-03-27 9:37 ` Philippe Reynes
2009-03-27 11:10 ` Philippe Reynes [this message]
2009-03-27 12:04 ` Thomas Gleixner
2009-03-27 13:50 ` Philippe Reynes
2009-03-27 14:34 ` Philippe Reynes
-- strict thread matches above, loose matches on Subject: below --
2009-02-11 22:43 [Announce] 2.6.29-rc4-rt1 Thomas Gleixner
2009-02-12 22:56 ` [Announce] 2.6.29-rc4-rt2 Thomas Gleixner
2009-02-23 19:44 ` [Announce] 2.6.29-rc6-rt2 Thomas Gleixner
2009-02-24 17:51 ` Thomas Gleixner
2009-02-24 17:57 ` [Announce] 2.6.29-rc6-rt3 Thomas Gleixner
2009-03-12 19:17 ` [Announce] 2.6.29-rc7-rt1 Thomas Gleixner
2009-03-20 0:31 ` [Announce] 2.6.29-rc78rt1 Thomas Gleixner
2009-03-20 17:45 ` [Announce] 2.6.29-rc8-rt2 Thomas Gleixner
2009-03-23 16:26 ` [Announce] 2.6.29-rc8-rt3 Thomas Gleixner
2009-03-25 20:59 ` [Announce] 2.6.29-rt1 Thomas Gleixner
2009-03-25 21:05 ` Jaswinder Singh Rajput
2009-03-25 21:09 ` Thomas Gleixner
2009-03-26 7:52 ` GeunSik Lim
2009-03-26 8:02 ` GeunSik Lim
2009-03-25 21:16 ` Grammostola Rosea
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='gqic7t$c27$1@ger.gmane.org' \
--to=philippe.reynes@isismpp.fr \
--cc=linux-kernel@vger.kernel.org \
--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).