From: Tomas Kalibera <kalibera@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Kernel crash with Xenomai (caused by fork?)
Date: Mon, 31 Mar 2008 00:04:46 -0400 [thread overview]
Message-ID: <47F062DE.5000709@domain.hid> (raw)
In-Reply-To: <18415.63399.305120.344817@domain.hid>
Crashed on the very same line as before
Tomas
[ 189.558776] ------------[ cut here ]------------
[ 189.563377] kernel BUG at arch/x86/mm/highmem_32.c:43!
[ 189.568491] invalid opcode: 0000 [#1] PREEMPT SMP
[ 189.573285] Modules linked in: rfcomm l2cap bluetooth ppdev sbp2 parport_pc lp parport sr_mod cdrom pcspkr iTCO_wdt iTCO_v
endor_support shpchp pci_hotplug ipv6 evdev ext3 jbd mbcache sg sd_mod ata_piix usbhid hid floppy ata_generic ahci ohci1394 l
ibata scsi_mod ieee1394 ehci_hcd tg3 uhci_hcd usbcore fuse
[ 189.600440]
[ 189.601924] Pid: 4960, comm: ovmtask Not tainted (2.6.24.3xenomaip1 #1)
[ 189.608508] EIP: 0060:[<c011a908>] EFLAGS: 00010286 CPU: 0
[ 189.613971] EIP is at kmap_atomic_prot+0xb8/0xc0
[ 189.618566] EAX: d91a8163 EBX: c2b23500 ECX: fffff000 EDX: c044fecc
[ 189.624804] ESI: 00000007 EDI: 00000163 EBP: 08003875 ESP: df673ea0
[ 189.631043] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
[ 189.636416] Process ovmtask (pid: 4960, ti=df672000 task=df4d29e0 task.ti=df672000)<0>
[ 189.643865] I-pipe domain Linux
[ 189.647257] Stack: fffb2000 00000000 c2b2350c c01a96aa fffb7000 fffb6000 df66d278 dfb7a580
[ 189.655648] dfb7ae40 df846084 df9b7084 08615000 08400000 08615000 f7c3d740 c2b23520
[ 189.664039] 00000000 00000000 c2b2350c c2be8aac fffb3000 08614fff 00000000 00000000
[ 189.672430] Call Trace:
[ 189.675045] [<c01a96aa>] copy_page_range+0x13a/0x560
[ 189.680086] [<c01224ef>] copy_process+0x8df/0x1250
[ 189.684951] [<c012309c>] do_fork+0x4c/0x200
[ 189.689211] [<c01022d2>] sys_clone+0x32/0x40
[ 189.693556] [<c01043a1>] sysenter_past_esp+0x6e/0x72
[ 189.698595] =======================
[ 189.702150] Code: 0c c1 fb 05 29 c1 c1 e3 0c 89 c8 09 fb 89 1a 5b 5e 5f c3 89 e0 25 00 e0 ff ff f7 40 14 ff ff ff ef 0f 85
69 ff ff ff 0f 0b eb fe <0f> 0b eb fe 8d 74 26 00 8b 0d f4 b1 45 c0 e9 35 ff ff ff 90 8d
[ 189.721467] EIP: [<c011a908>] kmap_atomic_prot+0xb8/0xc0 SS:ESP 0068:df673ea0
[ 189.728669] ---[ end trace 7363976c5f0598cc ]---
[ 189.733269] note: ovmtask[4960] exited with preempt_count 1
Gilles Chanteperdrix wrote:
> Tomas Kalibera wrote:
> > Hi Gilles,
> >
> > thanks for looking at it. Your analysis is correct, I don't indeed have
> > CONFIG_PREEMPT_RT kernel, but only CONFIG_PREEMPT, sorry for the confusion.
> >
> > I've put the kernel config, sources, and binary on the web, so that you
> > can be sure you're really looking on the kernel that is crashing,
> > http://www.cs.purdue.edu/homes/tkaliber/crash
>
> After looking at the sources, it appears that kmap_atomic disables
> preemption and kunmap_atomic reenables it. In short, the bug should
> never happen. What could happen is that the preemption count is garbled,
> or that a call to kmap_atomic is not paired with a kunmap_atomic.
>
> To check if the problem comes from the preemption count, could you apply
> the following patch ?
>
>
next prev parent reply other threads:[~2008-03-31 4:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 21:06 [Xenomai-core] Kernel crash with Xenomai (caused by fork?) Tomas Kalibera
2008-03-28 23:25 ` Gilles Chanteperdrix
2008-03-29 0:08 ` Gilles Chanteperdrix
2008-03-29 1:36 ` Tomas Kalibera
2008-03-29 20:17 ` Gilles Chanteperdrix
2008-03-30 20:27 ` Gilles Chanteperdrix
2008-03-31 4:04 ` Tomas Kalibera [this message]
2008-03-31 20:21 ` Gilles Chanteperdrix
2008-03-31 20:30 ` Gilles Chanteperdrix
2008-04-01 0:00 ` Tomas Kalibera
2008-04-01 5:52 ` Gilles Chanteperdrix
2008-04-01 7:59 ` Gilles Chanteperdrix
2008-04-01 13:54 ` Tomas Kalibera
2008-04-01 14:03 ` Gilles Chanteperdrix
2008-04-01 15:45 ` Tomas Kalibera
2008-04-01 15:58 ` Gilles Chanteperdrix
2008-04-01 21:23 ` Tomas Kalibera
2008-04-02 8:42 ` Gilles Chanteperdrix
2008-04-02 15:02 ` Tomas Kalibera
2008-04-02 15:07 ` Gilles Chanteperdrix
2008-04-02 18:14 ` Tomas Kalibera
2008-04-02 19:38 ` Tomas Kalibera
2008-04-02 19:42 ` Bill Gatliff
2008-04-02 19:44 ` Gilles Chanteperdrix
2008-04-02 21:45 ` Tomas Kalibera
2008-04-02 22:34 ` Gilles Chanteperdrix
2008-04-02 22:53 ` Gilles Chanteperdrix
2008-04-03 17:31 ` Tomas Kalibera
2008-04-05 4:32 ` Tomas Kalibera
2008-04-05 9:10 ` Jan Kiszka
2008-04-02 23:46 ` Tomas Kalibera
2008-04-03 9:04 ` Gilles Chanteperdrix
2008-04-02 19:52 ` Gilles Chanteperdrix
2008-04-02 21:37 ` Tomas Kalibera
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=47F062DE.5000709@domain.hid \
--to=kalibera@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@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.