From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <46860AC9.8080907@domain.hid> Date: Sat, 30 Jun 2007 09:48:25 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <1183144465.6574.99.camel@domain.hid> In-Reply-To: <1183144465.6574.99.camel@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE1D1B7124C74696F1B8EC697" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-core] Support for 2.6.22/x86 List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: rpm@xenomai.org Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE1D1B7124C74696F1B8EC697 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Philippe Gerum wrote: > Our development trunk now contains the necessary support for running > Xenomai over 2.6.22/x86. This work boils down to enabling Xenomai to us= e > the generic clock event device abstraction that comes with newest > kernels. Other archs / kernel versions still work the older way, until > all archs eventually catch up with clockevents upstream. >=20 > This support won't be backported to 2.3.x, because it has some > significant impact on the nucleus. Tested as thoroughly as possible her= e > on low-end and mid-range x86 boxen, including SMP. >=20 > Please give this hell. >=20 > http://download.gna.org/adeos/patches/v2.6/i386/adeos-ipipe-2.6.22-rc6-= i386-1.9-00.patch >=20 Running some tests, the gate to hell just opened: [ 210.247006] BUG: sleeping function called from invalid context at kernel/sched.c:3941 [ 210.248171] in_atomic():1, irqs_disabled():1 [ 210.248828] no locks held by frag-ip/881. [ 210.249494] [] show_trace_log_lvl+0x1f/0x34 [ 210.250523] [] show_trace+0x17/0x19 [ 210.257778] [] dump_stack+0x1b/0x1d [ 210.258070] [] __might_sleep+0xda/0xe1 [ 210.258365] [] wait_for_completion+0x1f/0xc3 [ 210.258688] [] set_cpus_allowed+0x77/0x95 [ 210.258992] [] lostage_handler+0x75/0x201 [xeno_nucleus] [ 210.259551] [] rthal_apc_handler+0x5c/0x89 [ 210.259869] [] __ipipe_sync_stage+0x13a/0x147 [ 210.260204] [] __ipipe_syscall_root+0x1a6/0x1c8 [ 210.260536] [] system_call+0x29/0x41 Setup is latest SVN + a "few" patches (the well-known ones), CONFIG_SMP, qemu -smp 2, RTnet in loopback mode, just terminating the frag-ip example= =2E However, this gremlin looks like it is /far/ older than 2.6.22 support. Calling set_cpus_allowed() from atomic lostage_handler is simply bogus, I'm afraid. :-/ Jan --------------enigE1D1B7124C74696F1B8EC697 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 iD8DBQFGhgrKniDOoMHTA+kRAsdVAJsGqHB7pjTbpuEW07AzPSKFSM9e+ACeK3lQ L1ucCl+yBfxDU01GaMwSwUI= =QpBy -----END PGP SIGNATURE----- --------------enigE1D1B7124C74696F1B8EC697--