From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4576AB3D.3050308@domain.hid> Date: Wed, 06 Dec 2006 12:36:29 +0100 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-help] Crash using userspace interrupts References: <200612051557.44787.s.zimmermann@domain.hid> <45758AF3.6010907@domain.hid> <200612061202.52456.s.zimmermann@domain.hid> In-Reply-To: <200612061202.52456.s.zimmermann@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBF24E930492355EF41D89E20" Sender: jan.kiszka@domain.hid List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stephan Zimmermann Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBF24E930492355EF41D89E20 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Stephan Zimmermann wrote: > Am Dienstag, 5. Dezember 2006 16:06 schrieb Jan Kiszka: >> Stephan Zimmermann wrote: >>> Hello List, >>> I am facing a crashing kernel when I use some rt_interupt_xxx funtion= s in >>> my application. >>> >>> System: Dualcore AMD with Debian 3.1, kernel 2.7.17.14 with Xenomai S= VN >>> rev 1920. >>> >>> Kernel crashes, leaving the following last words in syslog, the syste= m >>> keeps responding, but I am unable to restart my application. >>> >>> >>> I-pipe: Domain Xenomai registered. >>> Dec 5 15:24:07 localhost kernel: Xenomai: hal/x86 started. >>> Dec 5 15:24:07 localhost kernel: Xenomai: real-time nucleus v2.3-rc1= >>> (Baroque) loaded. >> #1920 implies -rc2. Something is probably inconsistent in your build. >=20 > Well you where right, my build was broken somehow. I reinstalled=20 > everything (Kernel, Xenomai) from clean sources, leading to a build=20 > which claims to be rc2. Nevertheless my system crashes, giving=20 > the same errormessages in syslog.=20 > Things change if I run the same program on a single-cpu machine=20 > or compile my kernel without SMP support, then everything seems to work= fine. >=20 > Thanks again, Stephan >=20 > > I-pipe: Domain Xenomai registered. > Dec 6 11:38:08 localhost kernel: Xenomai: hal/x86 started. > Dec 6 11:38:08 localhost kernel: Xenomai: real-time nucleus v2.3-rc2 (= Baroque) loaded. > Dec 6 11:38:08 localhost kernel: Xenomai: starting native API services= =2E > Dec 6 11:39:13 localhost kernel: waiter =3D kernel/xenomai/nucl= eus/intr.c:627 (xnintr_attach(), CPU #1) > Dec 6 11:39:13 localhost kernel: owner =3D :0 ((),= CPU #0) > Dec 6 11:39:13 localhost kernel: d8e31e88 c02d426e c02dfcdd f96= a3385 00000000 00000000 00000000 00000000 > Dec 6 11:39:13 localhost kernel: 00000000 c03bf080 db303124 000= 00000 f966af7b db30312c db303120 00000000 > Dec 6 11:39:13 localhost kernel: 00000001 00000000 00000001 000= 00000 00000000 00000000 db303120 00000007 > Dec 6 11:39:13 localhost kernel: Call Trace: > Dec 6 11:39:13 localhost kernel: xnintr_attach+0xd1/0x287 = [xeno_nucleus] rt_intr_create+0x941/0x988 [xeno_native] > Dec 6 11:39:13 localhost kernel: __rt_intr_create+0xaf/0xf= 6 [xeno_native] rt_intr_handler+0x0/0x46 [xeno_native] > Dec 6 11:39:13 localhost kernel: rt_mutex_release+0x323/0x= 32f [xeno_native] hisyscall_event+0x13e/0x251 [xeno_nucleus] > Dec 6 11:39:13 localhost kernel: hisyscall_event+0x0/0x251= [xeno_nucleus] __ipipe_dispatch_event+0xd6/0x1dc > Dec 6 11:39:13 localhost kernel: __ipipe_syscall_root+0x9e= /0x147 sysenter_past_esp+0x3b/0x67 > Dec 6 11:39:13 localhost kernel: Xenomai: watchdog triggered -- killin= g runaway thread 'CAN-ISR-2' > That all sounds quite weird, also the spinlock debugger output above that says no one is owning the lock, but we are spinning on it. Please post your .config and a simple demo code producing this error. Does Xenomai 2.2.5 expose the same problem? Jan --------------enigBF24E930492355EF41D89E20 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFdqs9niDOoMHTA+kRAo/FAJ9REh3OPzrVI9TEuiGNpEBAzdDS+gCfWAN0 Y9vT0LYZsCrV6XRwGmPsn4U= =wCBW -----END PGP SIGNATURE----- --------------enigBF24E930492355EF41D89E20--