From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4CC5DD1F.4090405@domain.hid> Date: Mon, 25 Oct 2010 21:40:15 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <4CC20AD2.4060501@domain.hid> <4CC44C02.4050003@domain.hid> <4CC5603E.1090707@domain.hid> <4CC566A2.2000702@domain.hid> <4CC5C93E.70503@domain.hid> In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE0099271D0642EFC00EA8357" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-help] Slow hard drive access in xenomai List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Pastor , Philippe Gerum Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE0099271D0642EFC00EA8357 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 25.10.2010 21:03, Peter Pastor wrote: > Hey Jan, >=20 > I did not apply any ubuntu patch for kernel 2.6.35 (since I do not have= > one). Also, good to know that I should not use xenomai patches togethe= r > with ubuntu patches. >=20 > Anyway, the problem occurred as well with the kernel 2.6.35 (see attach= ed > dmesg_bad_2.6.35) > I also attached the config. >=20 =2E.. > [ 5751.714643] irq 16: nobody cared (try booting with the "irqpoll" opt= ion) > [ 5751.714649] Pid: 0, comm: swapper Tainted: P 2.6.35-ipipe= -2.5.4-slim #2 > [ 5751.714653] Call Trace: > [ 5751.714655] [] __report_bad_irq+0x26/0xa0 > [ 5751.714668] [] note_interrupt+0x18c/0x1d0 > [ 5751.714672] [] handle_fasteoi_irq+0xcd/0x100 > [ 5751.714677] [] handle_irq+0x1d/0x30 > [ 5751.714681] [] do_IRQ+0x70/0x100 > [ 5751.714685] [] __ipipe_sync_stage+0x207/0x20d > [ 5751.714689] [] ? do_IRQ+0x0/0x100 > [ 5751.714692] [] ? __xirq_end+0x0/0x9c > [ 5751.714696] [] ? do_IRQ+0x0/0x100 > [ 5751.714700] [] __ipipe_walk_pipeline+0x113/0x120 > [ 5751.714706] [] __ipipe_handle_irq+0x124/0x310 > [ 5751.714708] [] ? __ipipe_ack_fasteoi_irq+0x0/0x10= > [ 5751.714712] [] common_interrupt+0x13/0x2c > [ 5751.714713] [] ? __ipipe_halt_root+0x26/0x= 40 > [ 5751.714718] [] ? atomic_notifier_call_chain+0x11/= 0x20 > [ 5751.714722] [] default_idle+0x45/0x50 > [ 5751.714725] [] cpu_idle+0x7a/0xd0 > [ 5751.714728] [] start_secondary+0x1c1/0x1c5 > [ 5751.714730] handlers: > [ 5751.714730] [] (usb_hcd_irq+0x0/0xb0) > [ 5751.714735] [] (mpt_interrupt+0x0/0xa00 [mptbase])= > [ 5751.714747] Disabling IRQ #16 I'm not yet sure, but a first thought: We have a shared fasteoi IRQ here, and we are on SMP. Compared to vanilla, the fasteoi flow of ipipe looks so much different to me ATM that I tend to believe two cores end up having this IRQ queued at the same time. One runs first and handles all triggers, the second bails out like above. Philippe, we _end_ fasteoi in the ipipe ack path. Do we mask them prior to this? What prevents a second IRQ arriving after this early eoi? Jan --------------enigE0099271D0642EFC00EA8357 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkzF3R8ACgkQitSsb3rl5xRBFQCgyYGqDLpmGpy1KtCZ7bv+GA08 vt4An1Q+oYpqELaleqECV/mA+mJFV+NB =Nszr -----END PGP SIGNATURE----- --------------enigE0099271D0642EFC00EA8357--