From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <44BEA974.40708@domain.hid> Date: Wed, 19 Jul 2006 23:51:48 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Xenomai-core] Xenomai v2.2 References: <1153227929.5029.25.camel@domain.hid> <44BE8ECF.2050608@domain.hid> <44BE943E.80302@domain.hid> In-Reply-To: <44BE943E.80302@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD305008DD8D04FCBDFBBD2B9" 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: Hannes Mayer Cc: xenomai@xenomai.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD305008DD8D04FCBDFBBD2B9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hannes Mayer wrote: >=20 > ...out of curiosity and to test an older example, I compiled > in periodic timer support, recompiled and then it oopses > at boot. Screenshot: > http://www.captain.at/tmp/dsc05081.jpg > *shrugs* =2Econfig please. And it would also be more helpful if you could switch o= n debug symbols so that the oopses tell us where they happened. So this happened during boot or when running your test? Jan --------------enigD305008DD8D04FCBDFBBD2B9 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.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEvql0niDOoMHTA+kRAkUjAJ0e9wZPiqoU+IMQ3Q2oCi8Ry9vDQACbBJgr gP8tDJ+pAuCkzqeGLNrWhwg= =QLin -----END PGP SIGNATURE----- --------------enigD305008DD8D04FCBDFBBD2B9--