From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <50083ED5.1010007@barrett.com> Date: Thu, 19 Jul 2012 13:07:33 -0400 From: Kyle Maroney MIME-Version: 1.0 References: <500808DC.1050800@barrett.com> <50080CB0.8030400@siemens.com> In-Reply-To: <50080CB0.8030400@siemens.com> Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Subject: Re: [Xenomai] Xenomai 2.6.1 x86 Boot Hanging List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: "xenomai@xenomai.org" On 07/19/2012 09:33 AM, Jan Kiszka wrote: > On 2012-07-19 15:17, Kyle Maroney wrote: >> Congratulations on the recent release of Xenomai 2.6.1. We are excited >> about the recent move to the ipipe core series and 3.x kernel patches >> becoming available for the x86 architecture. >> >> I have been able to successfully patch the vanilla kernel (3.2.19) with >> a slightly modified ipipe-core-3.2.21-x86-1 patch, and tested that >> working with a generic configuration. I also successfully patched >> vanilla + ubuntu diff + adeos, and tested this working as well. >> >> My problem is when I apply the xenomai configuration options after >> running the prepare kernel script. The kernel compiles successfully >> with no problems, however upon reboot I am met with the boot hanging at >> the purple boot screen of Ubuntu (no images). >> >> I have experimented with many config options for the past few days, and >> come to you for guidance. Please find attached my .config file. >> > There are obviously several issues remaining in the new x86 3.2 patch. I > just recently ran into some of them as well while updating RTnet. > Probably (hopefully) they are just related to debugging infrastructure. > Hope we can look into this over the next weeks. For now, disable > tracing, disable KGDB (which was also unsupported before BTW) and retry. > Ah, and I only tried 64 bit so far. > > Jan > Thank you for your advice. I understand (and enjoy) the implications of = working with such a new patch. Regarding disabling of the stated configuration options (tracing and = KGDB), I am having a problem that may be quickly answered. As you can see in the attached images, sparse irq numbering and kernel = debugging are locked 'enabled'. How did this happen? How can I disable = these options safely? Thanks! -Kyle -------------- next part -------------- A non-text attachment was scrubbed... Name: kernel_debugging_locked.png Type: image/png Size: 163965 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sparse_irq_locked.png Type: image/png Size: 40858 bytes Desc: not available URL: