From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <45DEC483.3080803@domain.hid> Date: Fri, 23 Feb 2007 11:40:03 +0100 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-core] soft lockup detected on AT91RM9200 References: <45DEBF20.2060907@domain.hid> In-Reply-To: <45DEBF20.2060907@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF468D32E7AEA50EED6433D7F" Sender: jan.kiszka@domain.hid List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Steven Scholz Cc: Xenomai-core@domain.hid This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF468D32E7AEA50EED6433D7F Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Steven Scholz wrote: > Hi Gilles, >=20 > I am running xenomai (svn 22.02.2007) with adeos-ipipe-2.6.19-arm-1.6-0= 2.patch > on our AT91RM9200 board. (# CONFIG_PREEMPT is not set) >=20 > When starting latency with 100=B5s period I get >=20 > ~ # latency > =3D=3D Sampling period: 100 us > =3D=3D Test mode: periodic user-mode task > =3D=3D All results in microseconds > warming up... > BUG: soft lockup detected on CPU#0! > [] (dump_stack+0x0/0x14) from [] (softlockup_tick+0= x98/0xb8) > [] (softlockup_tick+0x0/0xb8) from [] (run_local_ti= mers+0x18/0x1c) r7 =3D 00000011 r6 =3D 00000000 r5 =3D 00000000 r4 =3D= C02F8940 > [] (run_local_timers+0x0/0x1c) from [] (update_proc= ess_times+0x44/0x6c)[] (update_process_times+0x0/0x6c) from [] (timer_tick+0xf8/0x120) r5 =3D C01F9DE0 r4 =3D C01F0660 > [] (timer_tick+0x0/0x120) from [] (at91rm9200_timer= _interrupt+0x34/0xf8) r5 =3D C01F9DE0 r4 =3D C01F0660 > [] (at91rm9200_timer_interrupt+0x0/0xf8) from [] (h= andle_IRQ_event+0x38/0x6c) r5 =3D 00000000 r4 =3D C01AD8F0 > [] (handle_IRQ_event+0x0/0x6c) from [] (handle_leve= l_irq+0x74/0xcc) r7 =3D 00000011 r6 =3D C01AF2C0 r5 =3D 00000011 r4 =3D= C01A8440 > [] (handle_level_irq+0x0/0xcc) from [] (asm_do_IRQ+= 0x48/0x60) r5 =3D 00000000 r4 =3D C0213930 > [] (asm_do_IRQ+0x0/0x60) from [] (__ipipe_sync_stag= e+0x208/0x290) r5 =3D 00000000 r4 =3D C01AF2C8 > [] (__ipipe_sync_stage+0x0/0x290) from [] (__ipipe_= walk_pipeline+0xa4/0xc8) > [] (__ipipe_walk_pipeline+0x0/0xc8) from [] (__ipip= e_handle_irq+0x18c/0x19c) r7 =3D 00000011 r6 =3D C01FC2C0 r5 =3D 000000= 11 r4 =3D FFFFFFFF > [] (__ipipe_handle_irq+0x0/0x19c) from [] (__ipipe_= grab_irq+0xbc/0x120) > [] (__ipipe_grab_irq+0x0/0x120) from [] (__irq_svc+= 0x24/0x4c) > [] (__ipipe_unstall_root+0x0/0x4c) from [] (__ipipe= _restore_root+0x20/0x24) > [] (__ipipe_restore_root+0x0/0x24) from [] (hrtimer= _try_to_cancel+0x6c/0x74) > [] (hrtimer_try_to_cancel+0x0/0x74) from [] (hrtime= r_cancel+0x18/0x24) r7 =3D 00000000 r6 =3D 00000001 r5 =3D C1D82000 r4= =3D C1D83F3C > [] (hrtimer_cancel+0x0/0x24) from [] (do_nanosleep+= 0x50/0x80) r4 =3D C1D83F3C > [] (do_nanosleep+0x0/0x80) from [] (hrtimer_nanosle= ep+0x4c/0x16c) r6 =3D 00000001 r5 =3D C1D83F3C r4 =3D 00000000 > [] (hrtimer_nanosleep+0x0/0x16c) from [] (sys_nanos= leep+0x9c/0xb0)[] (sys_nanosleep+0x0/0xb0) from [] (r= et_fast_syscall+0x0/0x10) r6 =3D 00000000 r5 =3D BEAB9D5E r4 =3D 000000= 00 >=20 >=20 > This text is printed very slowly onto teh serial console. Also the time= r leds blinks very slowly. > I'd say 10 times slower. >=20 > Ideas? How can I help with debugging this? >=20 ARM platforms have hardware-related worst-case latencies in the range of 200 us under Linux (or is the AT91 mmu-less?). So if you set up a task with a 100 us period and load your system, you will more sooner than later see a total overload of both RT and non-RT part - not to speak of countless deadline misses. What happens if you move your task period more in the range of, say, 500 down to 300 us? Jan --------------enigF468D32E7AEA50EED6433D7F 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 iD8DBQFF3sSDniDOoMHTA+kRAjv6AJ9/gS99ucKWEH2O7tKENABbw04LwACfb9qg zDTfM+aWSWKZ+no1H+u2jPk= =67yR -----END PGP SIGNATURE----- --------------enigF468D32E7AEA50EED6433D7F--