From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Sat, 23 May 2015 00:26:27 +0200 From: Gilles Chanteperdrix Message-ID: <20150522222627.GC1987@hermes.click-hack.org> References: <245D3361-0412-466A-BFA1-22F2EDDC18B6@gatech.edu> <20150522210503.GA1987@hermes.click-hack.org> <9184F070-BBB8-44F8-AD64-79536BCDFA52@gatech.edu> <20150522215216.GB1987@hermes.click-hack.org> <64026009-C15A-45D5-B090-94546E3E25BB@gatech.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <64026009-C15A-45D5-B090-94546E3E25BB@gatech.edu> Subject: Re: [Xenomai] 3.14.17 patch initial ram disk hangup List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Yogi A. Patel" Cc: "xenomai@xenomai.org" On Fri, May 22, 2015 at 06:00:56PM -0400, Yogi A. Patel wrote: > > On May 22, 2015, at 17:52, Gilles Chanteperdrix wrote: > > > >> On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote: > >> > >>> On May 22, 2015, at 17:05, Gilles Chanteperdrix wrote: > >>> > >>> On Fri, May 22, 2015 at 04:47:59PM -0400, Yogi A. Patel wrote: > >>>> Hi - > >>>> > >>>> I have a Dell OptiPlex 9020 running 3.14.17. I am trying to get this system to run 3.14.17 with xenomai (using the 3.14.17 patch in the xenomai 2.6.4 source). > >>>> > >>>> The computer hangs when I select the kernel at “Loading initial ram disk”. I tried booting into recovery mode and go the following output: > >>>> > >>>> Kernel panic - not syncing: timer doesn’t work through Interrupt-remapped IO-APIC. > >>>> CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.17-xenomai-2.6.4. > >>>> > >>>> I’m having a hard time finding the source of the error. I’ve attached my config file. Any suggestions appreciated! > >>> > >>> Does the exact same kernel configuration, but without CONFIG_IPIPE > >>> and CONFIG_XENOMAI work ? > >>> > >>> -- > >>> Gilles. > >> > >> Sorry, I may have misunderstood but if you’re asking if 3.14.17 works out of the box (withough being patched), then yes it does work. > > > > The question is: with the exact same configuration? > > > > -- > > Gilles. > > I can't get the kernel to compile if I turn those two options off (but leave everything else the same). > > I get the following error: > > kernel/fork.c: In function ‘dup_task_struct’: > kernel/fork.c:317:29: error: ‘struct thread_info’ has no member named ‘ipipe_data’ > __ipipe_init_threadinfo(&ti->pipe_data); > make[2] *** [kernel/fork.o] Error 1 > make[1] *** [kernel] Error 2 You were talking about the unpatched kernel. Does the unpatched kernel work with the exact same configuration (only without CONFIG_IPIPE and CONFIG_XENOMAI). -- Gilles.