From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4976C98D.1020402@domain.hid> Date: Wed, 21 Jan 2009 08:06:53 +0100 From: Jan Kiszka MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFE6329CE4557104AF36907C8" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-help] Xenomai on Intel Core2 Quad CPU List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bruno Rouchouse Cc: "Xenomai-help@domain.hid" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFE6329CE4557104AF36907C8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Bruno Rouchouse wrote: > Problem solved! >=20 > It was apparently coming from some kernel debugging feature that I acti= vated > in my configuration. I haven't identified precisely which one since I u= nset > a couple of them at the same time. If you could post a diff of your config anyway, it would be a good starting point for further experiment. /me would like to learn which one bites us (and maybe fix this). Jan --------------enigFE6329CE4557104AF36907C8 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.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkl2yZMACgkQniDOoMHTA+m5swCaAqLJIsT4s9ejpg+cMJ3xTkVL EWAAnA8Ivzo9dp5BzuA8vFFScyv8/tOt =lv0q -----END PGP SIGNATURE----- --------------enigFE6329CE4557104AF36907C8--