* Re: [Xenomai-help] Oops on PPC405EP
@ 2006-08-21 13:31 Dirk Eibach
2006-08-21 13:50 ` Heikki Lindholm
2006-08-21 13:53 ` Gilles Chanteperdrix
0 siblings, 2 replies; 11+ messages in thread
From: Dirk Eibach @ 2006-08-21 13:31 UTC (permalink / raw)
Cc: xenomai
rpm@xenomai.org wrote:
> On Mon, 2006-08-21 at 14:15 +0200, Dirk Eibach wrote:
>> Oops: Exception in kernel mode, sig: 4 [#1]
>> NIP: C016772C LR: C003C7B0 SP: C1A19E50 REGS: c1a19da0 TRAP: 0700
>> Not tainted
>> MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
>> TASK = c1a10b60[500] 'sampling-497' THREAD: c1a18000
>> Last syscall: 50332203
>> GPR00: C1A10D48 C1A19E50 C1A10B60 C1A10D48 C0005940 0002B030 0007C45F
>> C1A10B5F
>> GPR08: 00000001 00400000 00000001 C0260040 00000000 10020184 01FEF400
>> 00000000
>> GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A19F50
>> C021C420
>> GPR24: 0000000E C0250000 C0260000 00000000 00000018 C0261350 C0362768
>> C0261380
>> Call trace: [c00421fc] [c0042668] [c0043530] [c0035708] [c000b418]
>> [c0002bf4]
>>
>
> Oops indeed. Could you objdump the kernel, and locate the symbols close
> to the addresses 0xC016772C and 0xC003C7B0? TIA,
>
Just compiled symbols into the kernel. Now it should be human readable ;)
Oops: Exception in kernel mode, sig: 4 [#1]
NIP: C016892C LR: C003D8CC SP: C1A39E50 REGS: c1a39da0 TRAP: 0700 Not
tainted
MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
TASK = c1a2fb40[501] 'sampling-498' THREAD: c1a38000
Last syscall: 50332203
GPR00: C1A2FD28 C1A39E50 C1A2FB40 C1A2FD28 C0005960 0002B030 000634DF
C1A2FB3F
GPR08: 00000001 00400000 00000001 C027E040 00000000 10020184 01FEF400
00000000
GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A39F50
C021D4A0
GPR24: 0000000E C0270000 C0280000 00000000 00000018 C027F350 C0382768
C027F380
NIP [c016892c] rthal_restore_fpu+0x10/0xe4
LR [c003d8cc] xnpod_switch_fpu+0x94/0x12c
Call trace:
[c0043318] xnshadow_harden+0xd0/0xfc
[c0043784] xnshadow_wait_barrier+0x100/0x114
[c004464c] losyscall_event+0xc0/0x194
[c0036824] __ipipe_dispatch_event+0x88/0x148
[c000b488] __ipipe_syscall_root+0x50/0xd0
[c0002c14] DoSyscall+0x24/0x6c
Cheers.
--
Dirk Eibach <eibach@domain.hid>
Guntermann & Drunck Systementwicklung GmbH
F & E
Dortmunder Str. 4a, D-57234 Wilnsdorf
Tel.: +49 (0) 2739 8901 100, Fax.: +49 (0) 2739 8901 120
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 13:31 [Xenomai-help] Oops on PPC405EP Dirk Eibach
@ 2006-08-21 13:50 ` Heikki Lindholm
2006-08-21 14:06 ` Dirk Eibach
2006-08-21 14:26 ` Gilles Chanteperdrix
2006-08-21 13:53 ` Gilles Chanteperdrix
1 sibling, 2 replies; 11+ messages in thread
From: Heikki Lindholm @ 2006-08-21 13:50 UTC (permalink / raw)
To: Dirk Eibach; +Cc: xenomai
Dirk Eibach kirjoitti:
> rpm@xenomai.org wrote:
>
>> On Mon, 2006-08-21 at 14:15 +0200, Dirk Eibach wrote:
>>
>>> Oops: Exception in kernel mode, sig: 4 [#1]
>>> NIP: C016772C LR: C003C7B0 SP: C1A19E50 REGS: c1a19da0 TRAP: 0700
>>> Not tainted
>>> MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
>>> TASK = c1a10b60[500] 'sampling-497' THREAD: c1a18000
>>> Last syscall: 50332203
>>> GPR00: C1A10D48 C1A19E50 C1A10B60 C1A10D48 C0005940 0002B030 0007C45F
>>> C1A10B5F
>>> GPR08: 00000001 00400000 00000001 C0260040 00000000 10020184 01FEF400
>>> 00000000
>>> GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A19F50
>>> C021C420
>>> GPR24: 0000000E C0250000 C0260000 00000000 00000018 C0261350 C0362768
>>> C0261380
>>> Call trace: [c00421fc] [c0042668] [c0043530] [c0035708] [c000b418]
>>> [c0002bf4]
>>>
>>
>> Oops indeed. Could you objdump the kernel, and locate the symbols close
>> to the addresses 0xC016772C and 0xC003C7B0? TIA,
>>
>
> Just compiled symbols into the kernel. Now it should be human readable ;)
>
> Oops: Exception in kernel mode, sig: 4 [#1]
> NIP: C016892C LR: C003D8CC SP: C1A39E50 REGS: c1a39da0 TRAP: 0700 Not
> tainted
> MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
> TASK = c1a2fb40[501] 'sampling-498' THREAD: c1a38000
> Last syscall: 50332203
> GPR00: C1A2FD28 C1A39E50 C1A2FB40 C1A2FD28 C0005960 0002B030 000634DF
> C1A2FB3F
> GPR08: 00000001 00400000 00000001 C027E040 00000000 10020184 01FEF400
> 00000000
> GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A39F50
> C021D4A0
> GPR24: 0000000E C0270000 C0280000 00000000 00000018 C027F350 C0382768
> C027F380
> NIP [c016892c] rthal_restore_fpu+0x10/0xe4
> LR [c003d8cc] xnpod_switch_fpu+0x94/0x12c
> Call trace:
> [c0043318] xnshadow_harden+0xd0/0xfc
> [c0043784] xnshadow_wait_barrier+0x100/0x114
> [c004464c] losyscall_event+0xc0/0x194
> [c0036824] __ipipe_dispatch_event+0x88/0x148
> [c000b488] __ipipe_syscall_root+0x50/0xd0
> [c0002c14] DoSyscall+0x24/0x6c
Since your hardware AFAIK does not have an FPU, shouldn't you be
compiling Xenomai without hardware FPU support?
-- Heikki Lindholm
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 13:50 ` Heikki Lindholm
@ 2006-08-21 14:06 ` Dirk Eibach
2006-08-21 14:26 ` Gilles Chanteperdrix
1 sibling, 0 replies; 11+ messages in thread
From: Dirk Eibach @ 2006-08-21 14:06 UTC (permalink / raw)
To: holindho; +Cc: xenomai
holindho@domain.hid wrote:
> Dirk Eibach kirjoitti:
>> rpm@xenomai.org wrote:
>>
>>> On Mon, 2006-08-21 at 14:15 +0200, Dirk Eibach wrote:
>>>
>>>> Oops: Exception in kernel mode, sig: 4 [#1]
>>>> NIP: C016772C LR: C003C7B0 SP: C1A19E50 REGS: c1a19da0 TRAP: 0700
>>>> Not tainted
>>>> MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
>>>> TASK = c1a10b60[500] 'sampling-497' THREAD: c1a18000
>>>> Last syscall: 50332203
>>>> GPR00: C1A10D48 C1A19E50 C1A10B60 C1A10D48 C0005940 0002B030 0007C45F
>>>> C1A10B5F
>>>> GPR08: 00000001 00400000 00000001 C0260040 00000000 10020184 01FEF400
>>>> 00000000
>>>> GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A19F50
>>>> C021C420
>>>> GPR24: 0000000E C0250000 C0260000 00000000 00000018 C0261350 C0362768
>>>> C0261380
>>>> Call trace: [c00421fc] [c0042668] [c0043530] [c0035708] [c000b418]
>>>> [c0002bf4]
>>>>
>>> Oops indeed. Could you objdump the kernel, and locate the symbols close
>>> to the addresses 0xC016772C and 0xC003C7B0? TIA,
>>>
>> Just compiled symbols into the kernel. Now it should be human readable ;)
>>
>> Oops: Exception in kernel mode, sig: 4 [#1]
>> NIP: C016892C LR: C003D8CC SP: C1A39E50 REGS: c1a39da0 TRAP: 0700 Not
>> tainted
>> MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
>> TASK = c1a2fb40[501] 'sampling-498' THREAD: c1a38000
>> Last syscall: 50332203
>> GPR00: C1A2FD28 C1A39E50 C1A2FB40 C1A2FD28 C0005960 0002B030 000634DF
>> C1A2FB3F
>> GPR08: 00000001 00400000 00000001 C027E040 00000000 10020184 01FEF400
>> 00000000
>> GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A39F50
>> C021D4A0
>> GPR24: 0000000E C0270000 C0280000 00000000 00000018 C027F350 C0382768
>> C027F380
>> NIP [c016892c] rthal_restore_fpu+0x10/0xe4
>> LR [c003d8cc] xnpod_switch_fpu+0x94/0x12c
>> Call trace:
>> [c0043318] xnshadow_harden+0xd0/0xfc
>> [c0043784] xnshadow_wait_barrier+0x100/0x114
>> [c004464c] losyscall_event+0xc0/0x194
>> [c0036824] __ipipe_dispatch_event+0x88/0x148
>> [c000b488] __ipipe_syscall_root+0x50/0xd0
>> [c0002c14] DoSyscall+0x24/0x6c
>
> Since your hardware AFAIK does not have an FPU, shouldn't you be
> compiling Xenomai without hardware FPU support?
>
> -- Heikki Lindholm
>
>
> To: eibach@domain.hid
> Cc: xenomai@xenomai.org
You are certainly right, PPC 405EP does not have an FPU. I just did not
realize I had to turn it off in Real-time sub-system. Sorry.
Now the first test is running :)
Cheers.
--
Dirk Eibach <eibach@domain.hid>
Guntermann & Drunck Systementwicklung GmbH
F & E
Dortmunder Str. 4a, D-57234 Wilnsdorf
Tel.: +49 (0) 2739 8901 100, Fax.: +49 (0) 2739 8901 120
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 13:50 ` Heikki Lindholm
2006-08-21 14:06 ` Dirk Eibach
@ 2006-08-21 14:26 ` Gilles Chanteperdrix
2006-08-21 14:37 ` Jan Kiszka
2006-08-21 14:38 ` Philippe Gerum
1 sibling, 2 replies; 11+ messages in thread
From: Gilles Chanteperdrix @ 2006-08-21 14:26 UTC (permalink / raw)
To: Heikki Lindholm; +Cc: xenomai
[-- Attachment #1: message body and .signature --]
[-- Type: text/plain, Size: 231 bytes --]
Heikki Lindholm wrote:
> Since your hardware AFAIK does not have an FPU, shouldn't you be
> compiling Xenomai without hardware FPU support?
Maybe we could prevent this mistake in Kconfig ?
--
Gilles Chanteperdrix.
[-- Attachment #2: xeno-hw-fpu-depends-on-ppc-fpu.patch --]
[-- Type: text/plain, Size: 358 bytes --]
Index: ksrc/arch/powerpc/Kconfig
===================================================================
--- ksrc/arch/powerpc/Kconfig (revision 1484)
+++ ksrc/arch/powerpc/Kconfig (working copy)
@@ -6,6 +6,7 @@
config XENO_HW_FPU
bool "Enable FPU support"
+ depends on PPC_FPU
default y
help
The FPU executes instructions from the processor's normal
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 14:26 ` Gilles Chanteperdrix
@ 2006-08-21 14:37 ` Jan Kiszka
2006-08-21 16:46 ` Philippe Gerum
2006-08-21 14:38 ` Philippe Gerum
1 sibling, 1 reply; 11+ messages in thread
From: Jan Kiszka @ 2006-08-21 14:37 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
Gilles Chanteperdrix wrote:
> Heikki Lindholm wrote:
> > Since your hardware AFAIK does not have an FPU, shouldn't you be
> > compiling Xenomai without hardware FPU support?
>
> Maybe we could prevent this mistake in Kconfig ?
>
I already wanted to ask the same.
Do we have such a dependency on other archs as well?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 14:37 ` Jan Kiszka
@ 2006-08-21 16:46 ` Philippe Gerum
2006-08-21 16:50 ` Philippe Gerum
0 siblings, 1 reply; 11+ messages in thread
From: Philippe Gerum @ 2006-08-21 16:46 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
On Mon, 2006-08-21 at 16:37 +0200, Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Heikki Lindholm wrote:
> > > Since your hardware AFAIK does not have an FPU, shouldn't you be
> > > compiling Xenomai without hardware FPU support?
> >
> > Maybe we could prevent this mistake in Kconfig ?
> >
>
> I already wanted to ask the same.
>
> Do we have such a dependency on other archs as well?
Yep, ARM.
>
> Jan
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 16:46 ` Philippe Gerum
@ 2006-08-21 16:50 ` Philippe Gerum
0 siblings, 0 replies; 11+ messages in thread
From: Philippe Gerum @ 2006-08-21 16:50 UTC (permalink / raw)
To: Jan Kiszka; +Cc: xenomai
On Mon, 2006-08-21 at 18:46 +0200, Philippe Gerum wrote:
> On Mon, 2006-08-21 at 16:37 +0200, Jan Kiszka wrote:
> > Gilles Chanteperdrix wrote:
> > > Heikki Lindholm wrote:
> > > > Since your hardware AFAIK does not have an FPU, shouldn't you be
> > > > compiling Xenomai without hardware FPU support?
> > >
> > > Maybe we could prevent this mistake in Kconfig ?
> > >
> >
> > I already wanted to ask the same.
> >
> > Do we have such a dependency on other archs as well?
>
> Yep, ARM.
>
This said, we don't support hw FP for this arch, so this should not be
an issue.
> >
> > Jan
> >
> > _______________________________________________
> > Xenomai-help mailing list
> > Xenomai-help@domain.hid
> > https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 14:26 ` Gilles Chanteperdrix
2006-08-21 14:37 ` Jan Kiszka
@ 2006-08-21 14:38 ` Philippe Gerum
1 sibling, 0 replies; 11+ messages in thread
From: Philippe Gerum @ 2006-08-21 14:38 UTC (permalink / raw)
To: Gilles Chanteperdrix; +Cc: xenomai
On Mon, 2006-08-21 at 16:26 +0200, Gilles Chanteperdrix wrote:
> Heikki Lindholm wrote:
> > Since your hardware AFAIK does not have an FPU, shouldn't you be
> > compiling Xenomai without hardware FPU support?
>
> Maybe we could prevent this mistake in Kconfig ?
Yes, at least for 2.6. Applied, thanks.
>
> plain text document attachment (xeno-hw-fpu-depends-on-ppc-fpu.patch)
> Index: ksrc/arch/powerpc/Kconfig
> ===================================================================
> --- ksrc/arch/powerpc/Kconfig (revision 1484)
> +++ ksrc/arch/powerpc/Kconfig (working copy)
> @@ -6,6 +6,7 @@
>
> config XENO_HW_FPU
> bool "Enable FPU support"
> + depends on PPC_FPU
> default y
> help
> The FPU executes instructions from the processor's normal
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 13:31 [Xenomai-help] Oops on PPC405EP Dirk Eibach
2006-08-21 13:50 ` Heikki Lindholm
@ 2006-08-21 13:53 ` Gilles Chanteperdrix
1 sibling, 0 replies; 11+ messages in thread
From: Gilles Chanteperdrix @ 2006-08-21 13:53 UTC (permalink / raw)
To: Dirk Eibach; +Cc: xenomai
Dirk Eibach wrote:
> NIP [c016892c] rthal_restore_fpu+0x10/0xe4
> LR [c003d8cc] xnpod_switch_fpu+0x94/0x12c
Could you run "switchtest" ? If there is a FPU context switch error, you
should get an (hopefully more clear) error message.
--
Gilles Chanteperdrix.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [Xenomai-help] Oops on PPC405EP
@ 2006-08-21 12:15 Dirk Eibach
2006-08-21 12:57 ` Philippe Gerum
0 siblings, 1 reply; 11+ messages in thread
From: Dirk Eibach @ 2006-08-21 12:15 UTC (permalink / raw)
To: xenomai
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Hello,
I am using ftp://ftp.denx.de/pub/linux/linux-2.6.14.tar.bz2
Kernelsources, xenomai-2.2.0.
My hardware is Dave PPChameleon (PPC404EP).
I have built and installed kernel and xenomai successfully.
When I run xeno-test I end up with:
Oops: Exception in kernel mode, sig: 4 [#1]
NIP: C016772C LR: C003C7B0 SP: C1A19E50 REGS: c1a19da0 TRAP: 0700 Not
tainted
MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
TASK = c1a10b60[500] 'sampling-497' THREAD: c1a18000
Last syscall: 50332203
GPR00: C1A10D48 C1A19E50 C1A10B60 C1A10D48 C0005940 0002B030 0007C45F
C1A10B5F
GPR08: 00000001 00400000 00000001 C0260040 00000000 10020184 01FEF400
00000000
GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A19F50
C021C420
GPR24: 0000000E C0250000 C0260000 00000000 00000018 C0261350 C0362768
C0261380
Call trace: [c00421fc] [c0042668] [c0043530] [c0035708] [c000b418]
[c0002bf4]
Attached is the full log.
Cheers.
--
Dirk Eibach <eibach@domain.hid>
Guntermann & Drunck Systementwicklung GmbH
F & E
Dortmunder Str. 4a, D-57234 Wilnsdorf
Tel.: +49 (0) 2739 8901 100, Fax.: +49 (0) 2739 8901 120
[-- Attachment #2: xeno-test.log --]
[-- Type: application/octet-stream, Size: 6412 bytes --]
/home/de/src/xenomai/xenomai-2.2.0/install/bin # ./xeno-test
xeno-test: started
withBusybox is 1
xeno-test: running tests
Thu Jan 1 01:01:15 CET 1970
running: ./xeno-config --verbose
xeno-config --verbose
--version="2.2.0"
--cc="powerpc-405-linux-gnu-gcc"
--arch="powerpc"
--prefix="/home/de/src/xenomai/xenomai-2.2.0/install/"
--xeno-cflags="-I. -I/home/de/src/xenomai/xenomai-2.2.0/install//include -O2 -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe"
--xeno-ldflags="-L/home/de/src/xenomai/xenomai-2.2.0/install//lib -lpthread -rdynamic"
--posix-cflags="-I. -I/home/de/src/xenomai/xenomai-2.2.0/install//include -I/home/de/src/xenomai/xenomai-2.2.0/install//include/posix -O2 -"
--posix-ldflags="-L/home/de/src/xenomai/xenomai-2.2.0/install//lib -lpthread_rt -lpthread -lrt -rdynamic"
--uvm-cflags="-I. -I/home/de/src/xenomai/xenomai-2.2.0/install//include -O2 -D_GNU_SOURCE -D_REENTRANT -D__XENO__ -Wall -pipe -D__XENO_UVM_"
--uvm-ldflags="-u__xeno_skin_init -L/home/de/src/xenomai/xenomai-2.2.0/install//lib -luvm -lnucleus_uvm -lpthread"
--library-dir="/home/de/src/xenomai/xenomai-2.2.0/install//lib"
Thu Jan 1 01:01:15 CET 1970
running: ./xeno-info
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
BusyBox v1.1.0 (2006.08.21-11:31+0000) multi-call binary
Linux CATCenterOS 2.6.14 #3 Mon Aug 21 11:31:05 CEST 2006 ppc unknown
module-init-tools found
Modules Loaded
Thu Jan 1 01:01:16 CET 1970
running: cat /proc/cpuinfo
processor : 0
cpu : 405EP
clock : 133MHz
revision : 9.80 (pvr 5121 0950)
bogomips : 133.12
machine : DAVE PPChameleonEVB
plb bus clock : 133MHz
pci bus clock : 33MHz
Thu Jan 1 01:01:17 CET 1970
running: md5sum /proc/cpuinfo # cpuinfo fingerprint
bd5c627d3bd83dbdff0ffba66167c3b3 /proc/cpuinfo
Thu Jan 1 01:01:17 CET 1970
running: cat /proc/ipipe/Linux
Priority=100, Id=0x00000000
irq0-31: accepted
irq32: accepted, virtual
irq33-34: grabbed, virtual
irq35: passed, virtual
Thu Jan 1 01:01:17 CET 1970
running: cat /proc/ipipe/Xenomai
Invariant head, Id=0x58454e4f
irq0-31: passed
irq32: wired, virtual
irq33-34: passed, virtual
irq35: wired, virtual
Thu Jan 1 01:01:17 CET 1970
running: cat /proc/ipipe/version
1.3-05
Thu Jan 1 01:01:17 CET 1970
running: generate_loads 1
dd workload started, pids 233 stored in /var/lock/xeno-test.43.pids
Thu Jan 1 01:01:17 CET 1970
running: cat /proc/interrupts
CPU0
10: 0 UIC0 Level MAL SERR
11: 2850 UIC0 Level MAL TX EOB
12: 3507 UIC0 Level MAL RX EOB
13: 0 UIC0 Level MAL TX DE
14: 0 UIC0 Level MAL RX DE
15: 0 UIC0 Level EMAC
BAD: 0
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/loadavg
0.08 0.02 0.01 3/22 248
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/meminfo
MemTotal: 29964 kB
MemFree: 24376 kB
Buffers: 0 kB
Cached: 2328 kB
SwapCached: 0 kB
Active: 1928 kB
Inactive: 1180 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 29964 kB
LowFree: 24376 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
Mapped: 1716 kB
Slab: 1616 kB
CommitLimit: 14980 kB
Committed_AS: 3868 kB
PageTables: 144 kB
VmallocTotal: 606136 kB
VmallocUsed: 4488 kB
VmallocChunk: 601524 kB
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/xenomai/apc
APC CPU0
0: 0 (pipe_wakeup)
1: 0 (lostage_handler)
2: 0 (registry_export)
3: 0 (pipe_flush)
4: 0 (posix_signals_handler)
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/xenomai/faults
TRAP CPU0
0: 0 (Data or instruction access)
1: 0 (Alignment)
2: 0 (Altivec unavailable)
3: 0 (Program check exception)
4: 0 (Machine check exception)
5: 0 (Unknown)
6: 0 (Instruction breakpoint)
7: 0 (Run mode exception)
8: 0 (Single-step exception)
9: 0 (Non-recoverable exception)
10: 0 (Software emulation)
11: 0 (Debug)
12: 0 (SPE)
13: 0 (Altivec assist)
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/xenomai/hal
1.3-05
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/xenomai/irq
IRQ CPU0
32: 7843
35: 0
Thu Jan 1 01:01:18 CET 1970
running: cat /proc/xenomai/latency
9495
Thu Jan 1 01:01:19 CET 1970
running: cat /proc/xenomai/sched
CPU PID PRI TIMEOUT STAT NAME
0 0 -1 0 R ROOT
Mem: 5892K used, 24072K free, 0K shrd, 0K buff, 2376K cached
Load average: 0.31, 0.07, 0.02 (State: S=sleeping R=running, W=waiting)
PID USER STATUS RSS PPID %CPU %MEM COMMAND
233 root R 432 1 96.9 1.4 dd
387 root R 788 386 3.8 2.6 top
41 root S 876 1 0.0 2.9 sh
43 root S 628 41 0.0 2.0 xeno-test
40 root S 624 1 0.0 2.0 dropbear
1 root S 560 0 0.0 1.8 init
Thu Jan 1 01:01:22 CET 1970
running: ./run -- -sh -T 120 -t0
*
*
* Type ^C to stop this application.
*
*
== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in microseconds
Oops: Exception in kernel mode, sig: 4 [#1]
NIP: C016772C LR: C003C7B0 SP: C1A19E50 REGS: c1a19da0 TRAP: 0700 Not tainted
MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
TASK = c1a10b60[500] 'sampling-497' THREAD: c1a18000
Last syscall: 50332203
GPR00: C1A10D48 C1A19E50 C1A10B60 C1A10D48 C0005940 0002B030 0007C45F C1A10B5F
GPR08: 00000001 00400000 00000001 C0260040 00000000 10020184 01FEF400 00000000
GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A19F50 C021C420
GPR24: 0000000E C0250000 C0260000 00000000 00000018 C0261350 C0362768 C0261380
Call trace: [c00421fc] [c0042668] [c0043530] [c0035708] [c000b418] [c0002bf4]
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [Xenomai-help] Oops on PPC405EP
2006-08-21 12:15 Dirk Eibach
@ 2006-08-21 12:57 ` Philippe Gerum
0 siblings, 0 replies; 11+ messages in thread
From: Philippe Gerum @ 2006-08-21 12:57 UTC (permalink / raw)
To: Dirk Eibach; +Cc: xenomai
On Mon, 2006-08-21 at 14:15 +0200, Dirk Eibach wrote:
> Oops: Exception in kernel mode, sig: 4 [#1]
> NIP: C016772C LR: C003C7B0 SP: C1A19E50 REGS: c1a19da0 TRAP: 0700
> Not tainted
> MSR: 0002b030 EE: 1 PR: 0 FP: 1 ME: 1 IR/DR: 11
> TASK = c1a10b60[500] 'sampling-497' THREAD: c1a18000
> Last syscall: 50332203
> GPR00: C1A10D48 C1A19E50 C1A10B60 C1A10D48 C0005940 0002B030 0007C45F
> C1A10B5F
> GPR08: 00000001 00400000 00000001 C0260040 00000000 10020184 01FEF400
> 00000000
> GPR16: 00000001 FFFFFFFF 00000000 00000000 0FFAC420 00000000 C1A19F50
> C021C420
> GPR24: 0000000E C0250000 C0260000 00000000 00000018 C0261350 C0362768
> C0261380
> Call trace: [c00421fc] [c0042668] [c0043530] [c0035708] [c000b418]
> [c0002bf4]
>
Oops indeed. Could you objdump the kernel, and locate the symbols close
to the addresses 0xC016772C and 0xC003C7B0? TIA,
--
Philippe.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2006-08-21 16:50 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-21 13:31 [Xenomai-help] Oops on PPC405EP Dirk Eibach
2006-08-21 13:50 ` Heikki Lindholm
2006-08-21 14:06 ` Dirk Eibach
2006-08-21 14:26 ` Gilles Chanteperdrix
2006-08-21 14:37 ` Jan Kiszka
2006-08-21 16:46 ` Philippe Gerum
2006-08-21 16:50 ` Philippe Gerum
2006-08-21 14:38 ` Philippe Gerum
2006-08-21 13:53 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2006-08-21 12:15 Dirk Eibach
2006-08-21 12:57 ` Philippe Gerum
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.