From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <46D301EE.5020805@domain.hid> Date: Mon, 27 Aug 2007 18:55:10 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <3535aae80708090211m198a1b87o9ae164fd94362838@domain.hid> <46BC1494.2010303@domain.hid> <3535aae80708100805l526475ebt5e4ff54c92f7daab@domain.hid> <46BC8074.3090104@domain.hid> <18112.1512.506911.608273@domain.hid> <3535aae80708130810s603edb7fo9f7be56342ddf921@domain.hid> <46C08E61.9060204@domain.hid> <3535aae80708140826o107e0fa3wee8db991ec1e14bd@domain.hid> <3535aae80708270627l4064dd1fif3e6aa10314d38f@domain.hid> In-Reply-To: <3535aae80708270627l4064dd1fif3e6aa10314d38f@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig26455F9F67E0B373BAC0CD37" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-help] hard lock-up List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: andy motten Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig26455F9F67E0B373BAC0CD37 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable andy motten wrote: >> >> I will run continuously several tests on the pc (including "latency -f= ") >> for the rest of this week. Since I am not in the office during this pe= riod >> (so not in the neighborhood of this problematic pc). >> And I hope (I hope not in vain) that the latency tracer will give us a= >> hint for the reason of the hard lock ups (if a hard lock up happens du= ring >> this period). >> >> andy >> >=20 >=20 > Hello, >=20 > Since we are having a hard time finding the hard lock-ups. We have tak= en a > closer look at the failed tests of orocos (maybe the source of the prob= lem > is the same). These failures occur during the make check execution. >=20 > The following tests FAILED: > 2 - task-test (OTHER-FAULT) > 3 - event-test (OTHER-FAULT) > 4 - taskcontext-test (OTHER-FAULT) >=20 > When we perform a single test, e.g task-test, we get the the following > messages: Killed > The OROCOS messages are then: >=20 > 0.000 [ Info ][Logger] Successfully extracted environment variable > ORO_LOGLEVEL > 0.001 [ Info ][Logger] OROCOS version '1.2.1' compiled with GCC > 4.1.2.Orocos Logging Activated at level : [ Debug ] ( 6 ) > 0.001 [ Info ][Logger] Reference System Time is : 880886725351 ticks = ( > 315.369 seconds ). > 0.002 [ Info ][Logger] Logging is relative to this time. > 0.002 [ Info ][Logger] Xenomai Periodic Timer runs in preemptive > 'one-shot' mode. > 0.003 [ Debug ][Logger] Xenomai Timer and Main Task Created > 0.003 [ Debug ][Logger] MainThread started. > 0.003 [ Debug ][Logger] Starting StartStopManager. > 0.004 [ Info ][Toolkit] Loading Tool RealTime. > 0.005 [ Debug ][Toolkit] Registered Type 'int' to the Orocos Type Syst= em. > 0.005 [ Debug ][Toolkit] Registered Type 'uint' to the Orocos Type Sys= tem. > 0.006 [ Debug ][Toolkit] Registered Type 'double' to the Orocos Type > System. > 0.006 [ Debug ][Toolkit] Registered Type 'bool' to the Orocos Type Sys= tem. > 0.006 [ Debug ][Toolkit] Registered Type 'PropertyBag' to the Orocos T= ype > System. > 0.007 [ Debug ][Toolkit] Registered Type 'float' to the Orocos Type Sy= stem. > 0.007 [ Debug ][Toolkit] Registered Type 'char' to the Orocos Type Sys= tem. > 0.008 [ Debug ][Toolkit] Registered Type 'array' to the Orocos Type Sy= stem. > 0.008 [ Debug ][Toolkit] Registered Type 'string' to the Orocos Type > System. > 0.010 [ Debug ][./task-test::main()] ORO_main starting... > 0.010 [ Info ][./task-test::main()] LogLevel unaltered by test-runner= =2E > 0.011 [ Info ][./task-test::main()] Creating PeriodicThread for sched= uler: > 0 > 0.012 [ Info ][TimerThreadInstance] PeriodicThread created with sched= uler > type '0', priority 15 and period 0.01. > 0.013 [ Debug ][Logger] Periodic Thread TimerThreadInstance started. > 0.014 [ Info ][PThread] PeriodicThread created with scheduler type '0= ', > priority 99 and period 0.1. > 0.014 [ Debug ][Logger] Periodic Thread PThread started. > 0.115 [ Debug ][Logger] Periodic Thread PThread stopping... done. > 0.115 [ Debug ][Logger] Periodic Thread PThread started. > 1.216 [ Debug ][Logger] Periodic Thread PThread stopping... done. > 1.216 [ Debug ][~PeriodicThread] Terminating PThread >=20 > On the serial console we get the following listing (complete listing in= > appendix): >=20 > Xenomai: starting native API services. > I-pipe: Detected illicit call from domain 'Xenomai' > into a service reserved for domain 'Linux' and below. > f635be74 00000000 00000000 52544149 f635be98 c0104789 c02cfa4f > c02f5b80 > f6c4e2f0 f635beb0 c0137d69 c02c256c c02c1186 c02c01b8 f8c0b280 > f635bebc > c0132981 f60a1730 f635bed8 f8bd8570 c010ef8c 00000000 f60a0120 > f8beefe0 > Call Trace: > [] show_trace_log_lvl+0x1f/0x35 > [] show_stack_log_lvl+0xaa/0xcf > [] show_stack+0x2f/0x36 > [] ipipe_check_context+0x7a/0x81 > [] module_put+0x19/0x7d > [] xnshadow_unmap+0xbc/0xff [xeno_nucleus] > [] __shadow_delete_hook+0x25/0x27 [xeno_native] > [] xnpod_delete_thread+0x1b9/0x2aa [xeno_nucleus] > [] rt_task_delete+0x140/0x145 [xeno_native] > [] __rt_task_delete+0x58/0x69 [xeno_native] > [] hisyscall_event+0x185/0x291 [xeno_nucleus] > [] __ipipe_dispatch_event+0xc0/0x1da > [] __ipipe_syscall_root+0x43/0x10a > [] system_call+0x29/0x41 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D That specific Xenomai bug should be fixed in 2.4, please check your testcase against -rc1 e.g. Unfortunately we have no backport of the fix in 2.3 yet. Can't tell right now if this is tricky, but this test demonstrates that $SOMETHING should be done... Jan --------------enig26455F9F67E0B373BAC0CD37 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.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG0wHyniDOoMHTA+kRAo00AJ4j7RaGEPqxlhlUX8MHopEMzBMIDQCeItto 8/EiDGWzUh4D0ULYzhNXUwg= =nJSW -----END PGP SIGNATURE----- --------------enig26455F9F67E0B373BAC0CD37--