All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyle Maroney <km@barrett.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] Xenomai 2.6.1 x86 Boot Hanging
Date: Thu, 19 Jul 2012 13:07:33 -0400	[thread overview]
Message-ID: <50083ED5.1010007@barrett.com> (raw)
In-Reply-To: <50080CB0.8030400@siemens.com>

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: <http://www.xenomai.org/pipermail/xenomai/attachments/20120719/c3ee7350/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sparse_irq_locked.png
Type: image/png
Size: 40858 bytes
Desc: not available
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20120719/c3ee7350/attachment-0001.png>

  reply	other threads:[~2012-07-19 17:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 13:17 [Xenomai] Xenomai 2.6.1 x86 Boot Hanging Kyle Maroney
2012-07-19 13:33 ` Jan Kiszka
2012-07-19 17:07   ` Kyle Maroney [this message]
2012-07-19 18:30     ` Jan Kiszka
2012-07-24 20:10   ` Gilles Chanteperdrix
2012-07-24 20:31     ` Kyle Maroney
2012-07-24 20:32       ` Gilles Chanteperdrix
2012-07-24 20:55       ` Gilles Chanteperdrix
2012-07-25 21:18         ` Kyle Maroney
2012-07-25 21:20           ` Gilles Chanteperdrix
2012-07-25 21:35             ` Kyle Maroney
2012-07-25 21:37               ` Gilles Chanteperdrix
2012-07-25 21:49                 ` Gilles Chanteperdrix
2012-07-25  9:29     ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50083ED5.1010007@barrett.com \
    --to=km@barrett.com \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.