[Xenomai] 3.14.17 patch initial ram disk hangup

[Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

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!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config
Type: application/octet-stream
Size: 163773 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150522/c24951de/attachment.obj>
-------------- next part --------------

Yogi

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Gilles Chanteperdrix]

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.

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.


I disabled CONFIG_XENOMAI and CONFIG_IPIPE - but when recompiling the kernel, I get:

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

I checked the config and both of those are set to “n”. What am I missing?

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.

Yogi

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Gilles Chanteperdrix]

On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote:
> 
> > On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

> On May 22, 2015, at 17:52, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> 
>> On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote:
>> 
>>> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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

Yogi

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Gilles Chanteperdrix]

On Fri, May 22, 2015 at 06:00:56PM -0400, Yogi A. Patel wrote:
> > On May 22, 2015, at 17:52, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> > 
> >> On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote:
> >> 
> >>> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

> On May 22, 2015, at 18:26, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> 
> On Fri, May 22, 2015 at 06:00:56PM -0400, Yogi A. Patel wrote:
>>> On May 22, 2015, at 17:52, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
>>> 
>>>> On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote:
>>>> 
>>>>> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.

Yes, I compiled an unpatched kernel with all the same options (turn off processor ACPI, frequency scaling, etc) and I can successfully boot up.

With the patched kernel, if I provide “noapci” to the kernel boot commands, I can get past the “Loading initial ramdisk” but then the system freezes prior to getting to the login screen.

I tried the same config with a patched 3.14.17 kernel on a different machine (not the same model as the one that is hanging at initrd) - and the system boots up successfully into 3.14.17 with xenomai.

Yogi

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Gilles Chanteperdrix]

On Sat, May 23, 2015 at 02:14:10PM -0400, Yogi A. Patel wrote:
> 
> > On May 22, 2015, at 18:26, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> > 
> > On Fri, May 22, 2015 at 06:00:56PM -0400, Yogi A. Patel wrote:
> >>> On May 22, 2015, at 17:52, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> >>> 
> >>>> On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote:
> >>>> 
> >>>>> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.
> 
> Yes, I compiled an unpatched kernel with all the same options (turn off processor ACPI, frequency scaling, etc) and I can successfully boot up.

I am sorry, but this does not look like the "exact same
configuration". To get the exact same configuration, simply copy the
damn .config file, the unpatched kernel kbuild system should cope
with the missing CONFIG_XENOMAI and CONFIG_IPIPE. This will remove
any uncertainty. Run diff to get 100% sure that nothing else is
changed.

Also, as mentioned in the documentation, starting from a "full
monty" configuration like the ones you find in a distribution, and
simply removing CONFIG_ACPI_PROCESSOR, CONFIG_CPUFREQ) IS NOT the
recommended way. It is better to start from a lean configuration
where only what you need is enabled, this makes the kernel build
process much faster and so further attempts less expensive, and you
have more chances to void enabling an option that nobody else uses
with Xenomai.

> 
> With the patched kernel, if I provide “noapci” to the kernel boot commands, I can get past the “Loading initial ramdisk” but then the system freezes prior to getting to the login screen.
> 
> I tried the same config with a patched 3.14.17 kernel on a different machine (not the same model as the one that is hanging at initrd) - and the system boots up successfully into 3.14.17 with xenomai.

The obvious answer, which I believe you can find many times
mentioned in the archives, and even in the troubleshooting guide Is
to disable the kernel "silent" mode if it is not disabled, and
enable early printk.

Seeing a user which does not read and follow the basic guides makes
me reluctant to answer him.

-- 
					    Gilles.

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

> On May 23, 2015, at 14:26, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
> 
> On Sat, May 23, 2015 at 02:14:10PM -0400, Yogi A. Patel wrote:
>> 
>>> On May 22, 2015, at 18:26, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
>>> 
>>> On Fri, May 22, 2015 at 06:00:56PM -0400, Yogi A. Patel wrote:
>>>>> On May 22, 2015, at 17:52, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> wrote:
>>>>> 
>>>>>> On Fri, May 22, 2015 at 05:37:16PM -0400, Yogi A. Patel wrote:
>>>>>> 
>>>>>>> On May 22, 2015, at 17:05, Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> 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.
>> 
>> Yes, I compiled an unpatched kernel with all the same options (turn off processor ACPI, frequency scaling, etc) and I can successfully boot up.
> 
> I am sorry, but this does not look like the "exact same
> configuration". To get the exact same configuration, simply copy the
> damn .config file, the unpatched kernel kbuild system should cope
> with the missing CONFIG_XENOMAI and CONFIG_IPIPE. This will remove
> any uncertainty. Run diff to get 100% sure that nothing else is
> changed.
> 
> Also, as mentioned in the documentation, starting from a "full
> monty" configuration like the ones you find in a distribution, and
> simply removing CONFIG_ACPI_PROCESSOR, CONFIG_CPUFREQ) IS NOT the
> recommended way. It is better to start from a lean configuration
> where only what you need is enabled, this makes the kernel build
> process much faster and so further attempts less expensive, and you
> have more chances to void enabling an option that nobody else uses
> with Xenomai.
> 
>> 
>> With the patched kernel, if I provide “noapci” to the kernel boot commands, I can get past the “Loading initial ramdisk” but then the system freezes prior to getting to the login screen.
>> 
>> I tried the same config with a patched 3.14.17 kernel on a different machine (not the same model as the one that is hanging at initrd) - and the system boots up successfully into 3.14.17 with xenomai.
> 
> The obvious answer, which I believe you can find many times
> mentioned in the archives, and even in the troubleshooting guide Is
> to disable the kernel "silent" mode if it is not disabled, and
> enable early printk.
> 
> Seeing a user which does not read and follow the basic guides makes
> me reluctant to answer him.
> 
> -- 
> 					    Gilles.


Sorry, Gilles - I do not mean to waste your time. I have spent time on the website and I have already disabled kernel silent and built early printk. Those didn’t help the case.

Going back to your original question about does it work with the exact same configuration (with the exception of CONFIG_XENOMAI and CONFIG_IPIPE) - the answer is yes.

I have successfully compiled a Xenomai patched 3.14.17 kernel by copying the original config file over and rebuilding from there. 

The diff between the config that I previously shared with you (which did not work) and the config that worked has no differences except for the fact that the missing IPIPE and Xenomai statements.

The machine that I am working on is a Dell Optiplex 9020 with a Intel i5-4670 processor.

Yogi

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Gilles Chanteperdrix]

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).

Sorry. I missed that information. Please try the latest available
I-pipe patch for Linux 3.14 instead of the one in Xenomai sources.

-- 
					    Gilles.

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Jan Kiszka]

On 2015-05-22 22:47, 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.

Please turn off CONFIG_IRQ_REMAP or boot the kernel with intremap=off.
This feature is not yet compatible with I-pipe. I guess we should encode
this into the x86 patch.

Jan

> 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!
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: config
> Type: application/octet-stream
> Size: 163773 bytes
> Desc: not available
> URL: <http://xenomai.org/pipermail/xenomai/attachments/20150522/c24951de/attachment.obj>
> -------------- next part --------------
> 
> Yogi
> 
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://xenomai.org/mailman/listinfo/xenomai
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://xenomai.org/pipermail/xenomai/attachments/20150524/a255b57d/attachment.sig>

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

On 05/24/2015 03:01 AM, Jan Kiszka wrote:
> On 2015-05-22 22:47, 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.
> Please turn off CONFIG_IRQ_REMAP or boot the kernel with intremap=off.
> This feature is not yet compatible with I-pipe. I guess we should encode
> this into the x86 patch.
>
> Jan
>
>> 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!
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: config
>> Type: application/octet-stream
>> Size: 163773 bytes
>> Desc: not available
>> URL: <http://xenomai.org/pipermail/xenomai/attachments/20150522/c24951de/attachment.obj>
>> -------------- next part --------------
>>
>> Yogi
>>
>> _______________________________________________
>> Xenomai mailing list
>> Xenomai@xenomai.org
>> http://xenomai.org/mailman/listinfo/xenomai
>>
>

I tried Jan's suggestion and it works with the 3.14.17-x84-6 ipipe patch 
- I can boot in get to a desktop/etc. However, the latencies are all 
over the place. I am seeing worst-case latencies anywhere between 2us-50us.

I tried Gilles' suggestion, too - and compiled with 3.14.17-x86-9 ipipe 
patch. Same thing as above.

I read around online about interrupt remapping - and I can't seem to 
find anything that hints at why this turning it off would cause the 
latencies to be all over the place.

Any thoughts/guidance appreciated!

Yogi

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Jeroen Van den Keybus]

> I read around online about interrupt remapping - and I can't seem to find
> anything that hints at why this turning it off would cause the latencies to
> be all over the place.

It shouldn't. There may be other reasons. But beware, in our tests the
Core i5/i7 showed about 29 us max. latency (running dohell), but
depending on the load, that can go up to 70 us (running a handbrake
video encoding session). What you see might actually be the best you
can get.

> Any thoughts/guidance appreciated!

You seem to be running a desktop distribution. Try leaving desktop
mode (kill the window manager / X). Check you're not running binary
graphics drivers. Unload as many drivers as you can.

Just some ideas; you don't seem to have provided a dmesg log.


Jeroen.


>
>
> Yogi
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://xenomai.org/mailman/listinfo/xenomai

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Yogi A. Patel]

On 05/25/2015 10:23 AM, Jeroen Van den Keybus wrote:
>> I read around online about interrupt remapping - and I can't seem to find
>> anything that hints at why this turning it off would cause the latencies to
>> be all over the place.
> It shouldn't. There may be other reasons. But beware, in our tests the
> Core i5/i7 showed about 29 us max. latency (running dohell), but
> depending on the load, that can go up to 70 us (running a handbrake
> video encoding session). What you see might actually be the best you
> can get.
I've been using "stress" to put a load on the system while running the 
xenomai latency test.

>> Any thoughts/guidance appreciated!
> You seem to be running a desktop distribution. Try leaving desktop
> mode (kill the window manager / X). Check you're not running binary
> graphics drivers. Unload as many drivers as you can.
You are correct. It looks like if I blacklist the radeon module (which I 
compiled with the kernel as a module, not using a binary), the latencies 
drop to 8-10us. I

> Just some ideas; you don't seem to have provided a dmesg log.
Sorry - dmesg log is attached. From just looking at the radeon specific 
messages, I don't quite see what the problem could be except for 
something internal to the radeon driver.

> Jeroen.
>
>
>>
>> Yogi
>>
>> _______________________________________________
>> Xenomai mailing list
>> Xenomai@xenomai.org
>> http://xenomai.org/mailman/listinfo/xenomai

-- 

Yogi A. Patel
@yapatel525 <https://twitter.com/yapatel525>

-------------- next part --------------
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.14.17-xenomai-2.6.4 (root@poseidon) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #1 SMP Mon May 25 08:46:12 EDT 2015
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.14.17-xenomai-2.6.4 root=UUID=bf43a50c-721b-49b6-8cef-d6f97aa4daa9 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 intremap=off
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] e820: BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x00000000000917ff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000091800-0x000000000009ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000d4b84fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000d4b85000-0x00000000d4b8bfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000d4b8c000-0x00000000d4fb9fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000d4fba000-0x00000000d543afff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000d543b000-0x00000000daeeafff] usable
[    0.000000] BIOS-e820: [mem 0x00000000daeeb000-0x00000000daffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000db000000-0x00000000db760fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000db761000-0x00000000db7fffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000db800000-0x00000000dbfb0fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000dbfb1000-0x00000000dbffffff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000dc000000-0x00000000dd71bfff] usable
[    0.000000] BIOS-e820: [mem 0x00000000dd71c000-0x00000000dd7fffff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000dd800000-0x00000000dee11fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000dee12000-0x00000000deffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f8000000-0x00000000fbffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000021dffffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.7 present.
[    0.000000] DMI: Dell Inc. OptiPlex 9020/0PC5F7, BIOS A05 12/05/2013
[    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000000] No AGP bridge found
[    0.000000] e820: last_pfn = 0x21e000 max_arch_pfn = 0x400000000
[    0.000000] MTRR default type: uncachable
[    0.000000] MTRR fixed ranges enabled:
[    0.000000]   00000-9FFFF write-back
[    0.000000]   A0000-BFFFF uncachable
[    0.000000]   C0000-DBFFF write-protect
[    0.000000]   DC000-E7FFF uncachable
[    0.000000]   E8000-FFFFF write-protect
[    0.000000] MTRR variable ranges enabled:
[    0.000000]   0 base 0000000000 mask 7E00000000 write-back
[    0.000000]   1 base 0200000000 mask 7FF0000000 write-back
[    0.000000]   2 base 0210000000 mask 7FF8000000 write-back
[    0.000000]   3 base 0218000000 mask 7FFC000000 write-back
[    0.000000]   4 base 021C000000 mask 7FFE000000 write-back
[    0.000000]   5 base 00E0000000 mask 7FE0000000 uncachable
[    0.000000]   6 disabled
[    0.000000]   7 disabled
[    0.000000]   8 disabled
[    0.000000]   9 disabled
[    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[    0.000000] original variable MTRRs
[    0.000000] reg 0, base: 0GB, range: 8GB, type WB
[    0.000000] reg 1, base: 8GB, range: 256MB, type WB
[    0.000000] reg 2, base: 8448MB, range: 128MB, type WB
[    0.000000] reg 3, base: 8576MB, range: 64MB, type WB
[    0.000000] reg 4, base: 8640MB, range: 32MB, type WB
[    0.000000] reg 5, base: 3584MB, range: 512MB, type UC
[    0.000000] total RAM covered: 8160M
[    0.000000] Found optimal setting for mtrr clean up
[    0.000000]  gran_size: 64K 	chunk_size: 64M 	num_reg: 6  	lose cover RAM: 0G
[    0.000000] New variable MTRRs
[    0.000000] reg 0, base: 0GB, range: 2GB, type WB
[    0.000000] reg 1, base: 2GB, range: 1GB, type WB
[    0.000000] reg 2, base: 3GB, range: 512MB, type WB
[    0.000000] reg 3, base: 4GB, range: 4GB, type WB
[    0.000000] reg 4, base: 8GB, range: 512MB, type WB
[    0.000000] reg 5, base: 8672MB, range: 32MB, type UC
[    0.000000] e820: update [mem 0xe0000000-0xffffffff] usable ==> reserved
[    0.000000] e820: last_pfn = 0xdee12 max_arch_pfn = 0x400000000
[    0.000000] found SMP MP-table at [mem 0x000fd9b0-0x000fd9bf] mapped at [ffff8800000fd9b0]
[    0.000000] Scanning 1 areas for low memory corruption
[    0.000000] Base memory trampoline at [ffff88000008b000] 8b000 size 24576
[    0.000000] Using GB pages for direct mapping
[    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[    0.000000]  [mem 0x00000000-0x000fffff] page 4k
[    0.000000] BRK [0x025ac000, 0x025acfff] PGTABLE
[    0.000000] BRK [0x025ad000, 0x025adfff] PGTABLE
[    0.000000] BRK [0x025ae000, 0x025aefff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0x21de00000-0x21dffffff]
[    0.000000]  [mem 0x21de00000-0x21dffffff] page 2M
[    0.000000] BRK [0x025af000, 0x025affff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0x21c000000-0x21ddfffff]
[    0.000000]  [mem 0x21c000000-0x21ddfffff] page 2M
[    0.000000] init_memory_mapping: [mem 0x200000000-0x21bffffff]
[    0.000000]  [mem 0x200000000-0x21bffffff] page 2M
[    0.000000] init_memory_mapping: [mem 0x00100000-0xd4b84fff]
[    0.000000]  [mem 0x00100000-0x001fffff] page 4k
[    0.000000]  [mem 0x00200000-0x3fffffff] page 2M
[    0.000000]  [mem 0x40000000-0xbfffffff] page 1G
[    0.000000]  [mem 0xc0000000-0xd49fffff] page 2M
[    0.000000]  [mem 0xd4a00000-0xd4b84fff] page 4k
[    0.000000] init_memory_mapping: [mem 0xd4b8c000-0xd4fb9fff]
[    0.000000]  [mem 0xd4b8c000-0xd4bfffff] page 4k
[    0.000000]  [mem 0xd4c00000-0xd4dfffff] page 2M
[    0.000000]  [mem 0xd4e00000-0xd4fb9fff] page 4k
[    0.000000] BRK [0x025b0000, 0x025b0fff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0xd543b000-0xdaeeafff]
[    0.000000]  [mem 0xd543b000-0xd55fffff] page 4k
[    0.000000]  [mem 0xd5600000-0xdadfffff] page 2M
[    0.000000]  [mem 0xdae00000-0xdaeeafff] page 4k
[    0.000000] BRK [0x025b1000, 0x025b1fff] PGTABLE
[    0.000000] init_memory_mapping: [mem 0xdb000000-0xdb760fff]
[    0.000000]  [mem 0xdb000000-0xdb5fffff] page 2M
[    0.000000]  [mem 0xdb600000-0xdb760fff] page 4k
[    0.000000] init_memory_mapping: [mem 0xdb800000-0xdbfb0fff]
[    0.000000]  [mem 0xdb800000-0xdbdfffff] page 2M
[    0.000000]  [mem 0xdbe00000-0xdbfb0fff] page 4k
[    0.000000] init_memory_mapping: [mem 0xdc000000-0xdd71bfff]
[    0.000000]  [mem 0xdc000000-0xdd5fffff] page 2M
[    0.000000]  [mem 0xdd600000-0xdd71bfff] page 4k
[    0.000000] init_memory_mapping: [mem 0xdd800000-0xdee11fff]
[    0.000000]  [mem 0xdd800000-0xdedfffff] page 2M
[    0.000000]  [mem 0xdee00000-0xdee11fff] page 4k
[    0.000000] init_memory_mapping: [mem 0x100000000-0x1ffffffff]
[    0.000000]  [mem 0x100000000-0x1ffffffff] page 1G
[    0.000000] RAMDISK: [mem 0x348d8000-0x36463fff]
[    0.000000] ACPI: RSDP 00000000000f0490 000024 (v02 DELL  )
[    0.000000] ACPI: XSDT 00000000dbfef080 000084 (v01 DELL    CBX3    01072009 AMI  00010013)
[    0.000000] ACPI: FACP 00000000dbffa498 00010C (v05 DELL    CBX3    01072009 AMI  00010013)
[    0.000000] ACPI: DSDT 00000000dbfef198 00B2FD (v02 DELL    CBX3    00000014 INTL 20091112)
[    0.000000] ACPI: FACS 00000000dd7fe080 000040
[    0.000000] ACPI: APIC 00000000dbffa5a8 000072 (v03 DELL    CBX3    01072009 AMI  00010013)
[    0.000000] ACPI: FPDT 00000000dbffa620 000044 (v01 DELL    CBX3    01072009 AMI  00010013)
[    0.000000] ACPI: SLIC 00000000dbffa668 000176 (v03 DELL    CBX3    01072009 MSFT 00010013)
[    0.000000] ACPI: LPIT 00000000dbffa7e0 00005C (v01 DELL    CBX3    00000000 AMI. 00000005)
[    0.000000] ACPI: SSDT 00000000dbffa840 000AD8 (v01  PmRef    CpuPm 00003000 INTL 20120711)
[    0.000000] ACPI: HPET 00000000dbffb318 000038 (v01 DELL    CBX3    01072009 AMI. 00000005)
[    0.000000] ACPI: SSDT 00000000dbffb350 00036D (v01 SataRe SataTabl 00001000 INTL 20120711)
[    0.000000] ACPI: MCFG 00000000dbffb6c0 00003C (v01 DELL    CBX3    01072009 MSFT 00000097)
[    0.000000] ACPI: SSDT 00000000dbffb700 003406 (v01 SaSsdt  SaSsdt  00003000 INTL 20091112)
[    0.000000] ACPI: ASF! 00000000dbffeb08 0000A5 (v32 INTEL       HCG 00000001 TFSM 000F4240)
[    0.000000] ACPI: DMAR 00000000dbffebb0 000080 (v01 INTEL      HSW  00000001 INTL 00000001)
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] No NUMA configuration found
[    0.000000] Faking a node at [mem 0x0000000000000000-0x000000021dffffff]
[    0.000000] Initmem setup node 0 [mem 0x00000000-0x21dffffff]
[    0.000000]   NODE_DATA [mem 0x21dff4000-0x21dff8fff]
[    0.000000] Reserving 128MB of memory at 704MB for crashkernel (System RAM: 8134MB)
[    0.000000]  [ffffea0000000000-ffffea00087fffff] PMD -> [ffff880215600000-ffff88021d5fffff] on node 0
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
[    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
[    0.000000]   Normal   [mem 0x100000000-0x21dffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00001000-0x00090fff]
[    0.000000]   node   0: [mem 0x00100000-0xd4b84fff]
[    0.000000]   node   0: [mem 0xd4b8c000-0xd4fb9fff]
[    0.000000]   node   0: [mem 0xd543b000-0xdaeeafff]
[    0.000000]   node   0: [mem 0xdb000000-0xdb760fff]
[    0.000000]   node   0: [mem 0xdb800000-0xdbfb0fff]
[    0.000000]   node   0: [mem 0xdc000000-0xdd71bfff]
[    0.000000]   node   0: [mem 0xdd800000-0xdee11fff]
[    0.000000]   node   0: [mem 0x100000000-0x21dffffff]
[    0.000000] On node 0 totalpages: 2082355
[    0.000000]   DMA zone: 64 pages used for memmap
[    0.000000]   DMA zone: 21 pages reserved
[    0.000000]   DMA zone: 3984 pages, LIFO batch:0
[    0.000000]   DMA32 zone: 14171 pages used for memmap
[    0.000000]   DMA32 zone: 906915 pages, LIFO batch:31
[    0.000000]   Normal zone: 18304 pages used for memmap
[    0.000000]   Normal zone: 1171456 pages, LIFO batch:31
[    0.000000] ACPI: PM-Timer IO Port: 0x1808
[    0.000000] ACPI: Local APIC address 0xfee00000
[    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)
[    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)
[    0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
[    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[    0.000000] ACPI: IRQ0 used by override.
[    0.000000] ACPI: IRQ2 used by override.
[    0.000000] ACPI: IRQ9 used by override.
[    0.000000] Using ACPI (MADT) for SMP configuration information
[    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
[    0.000000] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[    0.000000] nr_irqs_gsi: 40
[    0.000000] e820: [mem 0xdf000000-0xf7ffffff] available for PCI devices
[    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:4 nr_node_ids:1
[    0.000000] PERCPU: Embedded 95 pages/cpu @ffff88021dc00000 s359232 r8192 d21696 u524288
[    0.000000] pcpu-alloc: s359232 r8192 d21696 u524288 alloc=1*2097152
[    0.000000] pcpu-alloc: [0] 0 1 2 3 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 2049795
[    0.000000] Policy zone: Normal
[    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14.17-xenomai-2.6.4 root=UUID=bf43a50c-721b-49b6-8cef-d6f97aa4daa9 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=7 intremap=off
[    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
[    0.000000] Checking aperture...
[    0.000000] No AGP bridge found
[    0.000000] Calgary: detecting Calgary via BIOS EBDA area
[    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[    0.000000] Memory: 7948896K/8329420K available (7577K kernel code, 1045K rwdata, 3436K rodata, 1624K init, 7196K bss, 380524K reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
[    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000] 	Offload RCU callbacks from all CPUs
[    0.000000] 	Offload RCU callbacks from CPUs: 0-3.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS:16640 nr_irqs:712 16
[    0.000000] Interrupt pipeline (release #4)
[    0.000000] spurious 8259A interrupt: IRQ7.
[    0.000000] Console: colour dummy device 80x25
[    0.000000] console [tty0] enabled
[    0.000000] allocated 33554432 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] hpet clockevent registered
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 3392.201 MHz processor
[    0.000020] Calibrating delay loop (skipped), value calculated using timer frequency.. 6784.40 BogoMIPS (lpj=13568804)
[    0.000022] pid_max: default: 32768 minimum: 301
[    0.000026] ACPI: Core revision 20131218
[    0.005597] ACPI: All ACPI Tables successfully acquired
[    0.005716] Security Framework initialized
[    0.005726] AppArmor: AppArmor initialized
[    0.005727] Yama: becoming mindful.
[    0.006090] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes)
[    0.007180] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes)
[    0.007638] Mount-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.007645] Mountpoint-cache hash table entries: 16384 (order: 5, 131072 bytes)
[    0.007788] Initializing cgroup subsys memory
[    0.007791] Initializing cgroup subsys devices
[    0.007793] Initializing cgroup subsys freezer
[    0.007794] Initializing cgroup subsys net_cls
[    0.007795] Initializing cgroup subsys blkio
[    0.007796] Initializing cgroup subsys perf_event
[    0.007797] Initializing cgroup subsys hugetlb
[    0.007814] CPU: Physical Processor ID: 0
[    0.007815] CPU: Processor Core ID: 0
[    0.007818] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    0.007818] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
[    0.008561] mce: CPU supports 9 MCE banks
[    0.008571] CPU0: Thermal monitoring enabled (TM1)
[    0.008580] Last level iTLB entries: 4KB 1024, 2MB 1024, 4MB 1024
[    0.008580] Last level dTLB entries: 4KB 1024, 2MB 1024, 4MB 1024, 1GB 4
[    0.008580] tlb_flushall_shift: 6
[    0.008658] Freeing SMP alternatives memory: 28K (ffffffff81e9d000 - ffffffff81ea4000)
[    0.008660] ftrace: allocating 28024 entries in 110 pages
[    0.017026] dmar: Host address width 39
[    0.017027] dmar: DRHD base: 0x000000fed90000 flags: 0x1
[    0.017034] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap d2008c20660462 ecap f010da
[    0.017035] dmar: RMRR base: 0x000000def7c000 end: 0x000000def89fff
[    0.017469] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
[    0.057169] smpboot: CPU0: Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (fam: 06, model: 3c, stepping: 03)
[    0.057175] TSC deadline timer enabled
[    0.057181] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
[    0.057186] ... version:                3
[    0.057187] ... bit width:              48
[    0.057187] ... generic registers:      8
[    0.057188] ... value mask:             0000ffffffffffff
[    0.057189] ... max period:             0000ffffffffffff
[    0.057189] ... fixed-purpose events:   3
[    0.057190] ... event mask:             00000007000000ff
[    0.058195] x86: Booting SMP configuration:
[    0.058197] .... node  #0, CPUs:      #1
[    0.072063] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[    0.072111]  #2 #3
[    0.100037] x86: Booted up 1 node, 4 CPUs
[    0.100039] smpboot: Total of 4 processors activated (27137.60 BogoMIPS)
[    0.102354] devtmpfs: initialized
[    0.104003] EVM: security.selinux
[    0.104004] EVM: security.SMACK64
[    0.104005] EVM: security.ima
[    0.104006] EVM: security.capability
[    0.104494] pinctrl core: initialized pinctrl subsystem
[    0.104534] regulator-dummy: no parameters
[    0.104560] NET: Registered protocol family 16
[    0.104671] ACPI: bus type PCI registered
[    0.104672] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.104711] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000)
[    0.104713] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in E820
[    0.104750] PCI: Using configuration type 1 for base access
[    0.104754] dmi type 0xB1 record - unknown flag
[    0.105506] bio: create slab <bio-0> at 0
[    0.105597] ACPI: Added _OSI(Module Device)
[    0.105598] ACPI: Added _OSI(Processor Device)
[    0.105599] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.105600] ACPI: Added _OSI(Processor Aggregator Device)
[    0.108836] ACPI: Executed 1 blocks of module-level executable AML code
[    0.110700] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[    0.111412] ACPI: Interpreter enabled
[    0.111417] ACPI: (supports S0 S5)
[    0.111418] ACPI: Using IOAPIC for interrupt routing
[    0.111435] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.111557] ACPI: No dock devices found.
[    0.139992] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e])
[    0.139996] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.140383] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
[    0.140801] PCI host bridge to bus 0000:00
[    0.140802] pci_bus 0000:00: root bus resource [bus 00-3e]
[    0.140804] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7]
[    0.140805] pci_bus 0000:00: root bus resource [io  0x0d00-0xffff]
[    0.140806] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[    0.140807] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff]
[    0.140808] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff]
[    0.140809] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff]
[    0.140810] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfeafffff]
[    0.140815] pci 0000:00:00.0: [8086:0c00] type 00 class 0x060000
[    0.140874] pci 0000:00:01.0: [8086:0c01] type 01 class 0x060400
[    0.140900] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[    0.140965] pci 0000:00:14.0: [8086:8c31] type 00 class 0x0c0330
[    0.140983] pci 0000:00:14.0: reg 0x10: [mem 0xf7f20000-0xf7f2ffff 64bit]
[    0.141037] pci 0000:00:14.0: PME# supported from D3hot D3cold
[    0.141084] pci 0000:00:16.0: [8086:8c3a] type 00 class 0x078000
[    0.141102] pci 0000:00:16.0: reg 0x10: [mem 0xf7f3c000-0xf7f3c00f 64bit]
[    0.141158] pci 0000:00:16.0: PME# supported from D0 D3hot D3cold
[    0.141204] pci 0000:00:16.3: [8086:8c3d] type 00 class 0x070002
[    0.141218] pci 0000:00:16.3: reg 0x10: [io  0xf0a0-0xf0a7]
[    0.141226] pci 0000:00:16.3: reg 0x14: [mem 0xf7f3a000-0xf7f3afff]
[    0.141329] pci 0000:00:19.0: [8086:153a] type 00 class 0x020000
[    0.141344] pci 0000:00:19.0: reg 0x10: [mem 0xf7f00000-0xf7f1ffff]
[    0.141352] pci 0000:00:19.0: reg 0x14: [mem 0xf7f39000-0xf7f39fff]
[    0.141359] pci 0000:00:19.0: reg 0x18: [io  0xf040-0xf05f]
[    0.141412] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[    0.141462] pci 0000:00:1a.0: [8086:8c2d] type 00 class 0x0c0320
[    0.141480] pci 0000:00:1a.0: reg 0x10: [mem 0xf7f38000-0xf7f383ff]
[    0.141559] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
[    0.141609] pci 0000:00:1b.0: [8086:8c20] type 00 class 0x040300
[    0.141622] pci 0000:00:1b.0: reg 0x10: [mem 0xf7f30000-0xf7f33fff 64bit]
[    0.141683] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[    0.141729] pci 0000:00:1c.0: [8086:8c10] type 01 class 0x060400
[    0.141786] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[    0.141833] pci 0000:00:1c.1: [8086:8c12] type 01 class 0x060400
[    0.141892] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[    0.141939] pci 0000:00:1c.2: [8086:8c14] type 01 class 0x060400
[    0.141997] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[    0.142053] pci 0000:00:1d.0: [8086:8c26] type 00 class 0x0c0320
[    0.142071] pci 0000:00:1d.0: reg 0x10: [mem 0xf7f37000-0xf7f373ff]
[    0.142151] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
[    0.142202] pci 0000:00:1f.0: [8086:8c4e] type 00 class 0x060100
[    0.142338] pci 0000:00:1f.2: [8086:2822] type 00 class 0x010400
[    0.142351] pci 0000:00:1f.2: reg 0x10: [io  0xf090-0xf097]
[    0.142358] pci 0000:00:1f.2: reg 0x14: [io  0xf080-0xf083]
[    0.142365] pci 0000:00:1f.2: reg 0x18: [io  0xf070-0xf077]
[    0.142372] pci 0000:00:1f.2: reg 0x1c: [io  0xf060-0xf063]
[    0.142378] pci 0000:00:1f.2: reg 0x20: [io  0xf020-0xf03f]
[    0.142385] pci 0000:00:1f.2: reg 0x24: [mem 0xf7f36000-0xf7f367ff]
[    0.142418] pci 0000:00:1f.2: PME# supported from D3hot
[    0.142459] pci 0000:00:1f.3: [8086:8c22] type 00 class 0x0c0500
[    0.142472] pci 0000:00:1f.3: reg 0x10: [mem 0xf7f35000-0xf7f350ff 64bit]
[    0.142490] pci 0000:00:1f.3: reg 0x20: [io  0xf000-0xf01f]
[    0.142579] pci 0000:01:00.0: [1002:6611] type 00 class 0x030000
[    0.142592] pci 0000:01:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref]
[    0.142602] pci 0000:01:00.0: reg 0x18: [mem 0xf7e00000-0xf7e3ffff 64bit]
[    0.142609] pci 0000:01:00.0: reg 0x20: [io  0xe000-0xe0ff]
[    0.142621] pci 0000:01:00.0: reg 0x30: [mem 0xf7e40000-0xf7e5ffff pref]
[    0.142665] pci 0000:01:00.0: supports D1 D2
[    0.142666] pci 0000:01:00.0: PME# supported from D1 D2 D3hot
[    0.142706] pci 0000:01:00.1: [1002:aab0] type 00 class 0x040300
[    0.142718] pci 0000:01:00.1: reg 0x10: [mem 0xf7e60000-0xf7e63fff 64bit]
[    0.142785] pci 0000:01:00.1: supports D1 D2
[    0.148072] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.148073] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
[    0.148075] pci 0000:00:01.0:   bridge window [mem 0xf7e00000-0xf7efffff]
[    0.148078] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xefffffff 64bit pref]
[    0.148133] acpiphp: Slot [1] registered
[    0.148138] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    0.148220] pci 0000:03:00.0: [104c:8240] type 01 class 0x060400
[    0.148347] pci 0000:03:00.0: supports D1 D2
[    0.156081] pci 0000:00:1c.1: PCI bridge to [bus 03-04]
[    0.156086] pci 0000:00:1c.1:   bridge window [mem 0xf7d00000-0xf7dfffff]
[    0.156173] pci 0000:04:02.0: [1093:2890] type 00 class 0xff0000
[    0.156199] pci 0000:04:02.0: reg 0x10: [mem 0xf7d01000-0xf7d01fff]
[    0.156217] pci 0000:04:02.0: reg 0x14: [mem 0xf7d00000-0xf7d00fff]
[    0.156405] pci 0000:03:00.0: PCI bridge to [bus 04]
[    0.156417] pci 0000:03:00.0:   bridge window [mem 0xf7d00000-0xf7dfffff]
[    0.156503] pci 0000:05:00.0: [1093:c4c4] type 00 class 0x118000
[    0.156520] pci 0000:05:00.0: reg 0x10: [mem 0xf7c00000-0xf7c3ffff]
[    0.164086] pci 0000:00:1c.2: PCI bridge to [bus 05]
[    0.164090] pci 0000:00:1c.2:   bridge window [mem 0xf7c00000-0xf7cfffff]
[    0.164427] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.164462] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.164494] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 *10 11 12 14 15)
[    0.164526] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 10 11 12 14 15)
[    0.164557] ACPI: PCI Interrupt Link [LNKE] (IRQs *3 4 5 6 10 11 12 14 15)
[    0.164588] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0, disabled.
[    0.164620] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15)
[    0.164652] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 10 11 12 14 15)
[    0.164736] ACPI: Enabled 6 GPEs in block 00 to 3F
[    0.164791] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[    0.164792] vgaarb: loaded
[    0.164793] vgaarb: bridge control possible 0000:01:00.0
[    0.164897] SCSI subsystem initialized
[    0.164917] libata version 3.00 loaded.
[    0.164929] ACPI: bus type USB registered
[    0.164941] usbcore: registered new interface driver usbfs
[    0.164946] usbcore: registered new interface driver hub
[    0.164957] usbcore: registered new device driver usb
[    0.165014] PCI: Using ACPI for IRQ routing
[    0.166211] PCI: pci_cache_line_size set to 64 bytes
[    0.166265] e820: reserve RAM buffer [mem 0x00091800-0x0009ffff]
[    0.166267] e820: reserve RAM buffer [mem 0xd4b85000-0xd7ffffff]
[    0.166268] e820: reserve RAM buffer [mem 0xd4fba000-0xd7ffffff]
[    0.166268] e820: reserve RAM buffer [mem 0xdaeeb000-0xdbffffff]
[    0.166269] e820: reserve RAM buffer [mem 0xdb761000-0xdbffffff]
[    0.166270] e820: reserve RAM buffer [mem 0xdbfb1000-0xdbffffff]
[    0.166271] e820: reserve RAM buffer [mem 0xdd71c000-0xdfffffff]
[    0.166272] e820: reserve RAM buffer [mem 0xdee12000-0xdfffffff]
[    0.166273] e820: reserve RAM buffer [mem 0x21e000000-0x21fffffff]
[    0.166327] NetLabel: Initializing
[    0.166328] NetLabel:  domain hash size = 128
[    0.166328] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.166336] NetLabel:  unlabeled traffic allowed by default
[    0.166360] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.166364] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
[    0.168382] Switched to clocksource hpet
[    0.171643] AppArmor: AppArmor Filesystem Enabled
[    0.171656] pnp: PnP ACPI init
[    0.171665] ACPI: bus type PNP registered
[    0.171712] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
[    0.171714] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.171722] pnp 00:01: [dma 4]
[    0.171731] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
[    0.171745] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
[    0.171807] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
[    0.171837] pnp 00:04: Plug and Play ACPI device, IDs PNP0c04 (active)
[    0.171905] system 00:05: [io  0x0680-0x069f] has been reserved
[    0.171907] system 00:05: [io  0xffff] has been reserved
[    0.171908] system 00:05: [io  0xffff] has been reserved
[    0.171909] system 00:05: [io  0xffff] has been reserved
[    0.171910] system 00:05: [io  0x1c00-0x1cfe] has been reserved
[    0.171911] system 00:05: [io  0x1d00-0x1dfe] has been reserved
[    0.171912] system 00:05: [io  0x1e00-0x1efe] has been reserved
[    0.171913] system 00:05: [io  0x1f00-0x1ffe] has been reserved
[    0.171915] system 00:05: [io  0x1800-0x18fe] could not be reserved
[    0.171916] system 00:05: [io  0x164e-0x164f] has been reserved
[    0.171917] system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.171933] pnp 00:06: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.171961] system 00:07: [io  0x1854-0x1857] has been reserved
[    0.171962] system 00:07: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.172020] system 00:08: [io  0x0a00-0x0a0f] has been reserved
[    0.172021] system 00:08: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.172050] system 00:09: [io  0x04d0-0x04d1] has been reserved
[    0.172052] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.172439] pnp 00:0a: [dma 0 disabled]
[    0.172463] pnp 00:0a: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.172737] system 00:0b: [mem 0xfed1c000-0xfed1ffff] has been reserved
[    0.172738] system 00:0b: [mem 0xfed10000-0xfed17fff] has been reserved
[    0.172740] system 00:0b: [mem 0xfed18000-0xfed18fff] has been reserved
[    0.172741] system 00:0b: [mem 0xfed19000-0xfed19fff] has been reserved
[    0.172742] system 00:0b: [mem 0xf8000000-0xfbffffff] has been reserved
[    0.172743] system 00:0b: [mem 0xfed20000-0xfed3ffff] has been reserved
[    0.172744] system 00:0b: [mem 0xfed90000-0xfed93fff] could not be reserved
[    0.172745] system 00:0b: [mem 0xfed45000-0xfed8ffff] has been reserved
[    0.172747] system 00:0b: [mem 0xff000000-0xffffffff] has been reserved
[    0.172748] system 00:0b: [mem 0xfee00000-0xfeefffff] could not be reserved
[    0.172749] system 00:0b: [mem 0xf7fdf000-0xf7fdffff] has been reserved
[    0.172750] system 00:0b: [mem 0xf7fe0000-0xf7feffff] has been reserved
[    0.172752] system 00:0b: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.172892] pnp: PnP ACPI: found 12 devices
[    0.172893] ACPI: bus type PNP unregistered
[    0.178704] pci 0000:00:01.0: PCI bridge to [bus 01]
[    0.178707] pci 0000:00:01.0:   bridge window [io  0xe000-0xefff]
[    0.178709] pci 0000:00:01.0:   bridge window [mem 0xf7e00000-0xf7efffff]
[    0.178711] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xefffffff 64bit pref]
[    0.178714] pci 0000:00:1c.0: PCI bridge to [bus 02]
[    0.178723] pci 0000:03:00.0: PCI bridge to [bus 04]
[    0.178729] pci 0000:03:00.0:   bridge window [mem 0xf7d00000-0xf7dfffff]
[    0.178741] pci 0000:00:1c.1: PCI bridge to [bus 03-04]
[    0.178745] pci 0000:00:1c.1:   bridge window [mem 0xf7d00000-0xf7dfffff]
[    0.178751] pci 0000:00:1c.2: PCI bridge to [bus 05]
[    0.178756] pci 0000:00:1c.2:   bridge window [mem 0xf7c00000-0xf7cfffff]
[    0.178763] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7]
[    0.178764] pci_bus 0000:00: resource 5 [io  0x0d00-0xffff]
[    0.178765] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[    0.178766] pci_bus 0000:00: resource 7 [mem 0x000dc000-0x000dffff]
[    0.178767] pci_bus 0000:00: resource 8 [mem 0x000e0000-0x000e3fff]
[    0.178768] pci_bus 0000:00: resource 9 [mem 0x000e4000-0x000e7fff]
[    0.178769] pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfeafffff]
[    0.178770] pci_bus 0000:01: resource 0 [io  0xe000-0xefff]
[    0.178771] pci_bus 0000:01: resource 1 [mem 0xf7e00000-0xf7efffff]
[    0.178772] pci_bus 0000:01: resource 2 [mem 0xe0000000-0xefffffff 64bit pref]
[    0.178773] pci_bus 0000:03: resource 1 [mem 0xf7d00000-0xf7dfffff]
[    0.178774] pci_bus 0000:04: resource 1 [mem 0xf7d00000-0xf7dfffff]
[    0.178775] pci_bus 0000:05: resource 1 [mem 0xf7c00000-0xf7cfffff]
[    0.178791] NET: Registered protocol family 2
[    0.178907] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
[    0.179002] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[    0.179106] TCP: Hash tables configured (established 65536 bind 65536)
[    0.179116] TCP: reno registered
[    0.179124] UDP hash table entries: 4096 (order: 5, 131072 bytes)
[    0.179144] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)
[    0.179183] NET: Registered protocol family 1
[    0.220466] pci 0000:01:00.0: Boot video device
[    0.220479] PCI: CLS 64 bytes, default 64
[    0.220511] Trying to unpack rootfs image as initramfs...
[    0.526739] Freeing initrd memory: 28208K (ffff8800348d8000 - ffff880036464000)
[    0.526747] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[    0.526750] software IO TLB [mem 0xd6eeb000-0xdaeeb000] (64MB) mapped at [ffff8800d6eeb000-ffff8800daeeafff]
[    0.526881] RAPL PMU detected, hw unit 2^-14 Joules, API unit is 2^-32 Joules, 3 fixed counters 655360 ms ovfl timer
[    0.526909] microcode: CPU0 sig=0x306c3, pf=0x2, revision=0x16
[    0.526914] microcode: CPU1 sig=0x306c3, pf=0x2, revision=0x16
[    0.526921] microcode: CPU2 sig=0x306c3, pf=0x2, revision=0x16
[    0.526927] microcode: CPU3 sig=0x306c3, pf=0x2, revision=0x16
[    0.526965] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[    0.526975] Scanning for low memory corruption every 60 seconds
[    0.527130] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.527141] Initialise system trusted keyring
[    0.527166] audit: initializing netlink subsys (disabled)
[    0.527176] audit: type=2000 audit(1432565388.524:1): initialized
[    0.549692] I-pipe: head domain Xenomai registered.
[    0.549738] Xenomai: hal/x86_64 started.
[    0.549754] Xenomai: scheduling class idle registered.
[    0.549755] Xenomai: scheduling class rt registered.
[    0.550592] Xenomai: real-time nucleus v2.6.4 (Jumpin' Out) loaded.
[    0.550593] Xenomai: debug mode enabled.
[    0.551002] Xenomai: disabling automatic C1E state promotion on Intel processor
[    0.551012] Xenomai: SMI-enabled chipset found, but SMI workaround disabled
[    0.551012]          (see xeno_hal.smi parameter). You may encounter
[    0.551012]          high interrupt latencies!
[    0.551043] Xenomai: starting native API services.
[    0.551044] Xenomai: starting POSIX services.
[    0.551097] Xenomai: starting RTDM services.
[    0.551158] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[    0.552026] zbud: loaded
[    0.552117] VFS: Disk quotas dquot_6.5.2
[    0.552143] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.552444] fuse init (API version 7.22)
[    0.552497] msgmni has been set to 15580
[    0.552530] Key type big_key registered
[    0.552828] Key type asymmetric registered
[    0.552829] Asymmetric key parser 'x509' registered
[    0.552848] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[    0.552873] io scheduler noop registered
[    0.552874] io scheduler deadline registered (default)
[    0.552891] io scheduler cfq registered
[    0.553022] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
[    0.553117] pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
[    0.553215] pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
[    0.553313] pcieport 0000:00:1c.2: irq 43 for MSI/MSI-X
[    0.553373] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
[    0.553374] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
[    0.553375] pci 0000:01:00.1: Signaling PME through PCIe PME interrupt
[    0.553377] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
[    0.553389] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
[    0.553393] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
[    0.553404] pcieport 0000:00:1c.1: Signaling PME through PCIe PME interrupt
[    0.553405] pci 0000:03:00.0: Signaling PME through PCIe PME interrupt
[    0.553406] pci 0000:04:02.0: Signaling PME through PCIe PME interrupt
[    0.553409] pcie_pme 0000:00:1c.1:pcie01: service driver pcie_pme loaded
[    0.553423] pcieport 0000:00:1c.2: Signaling PME through PCIe PME interrupt
[    0.553424] pci 0000:05:00.0: Signaling PME through PCIe PME interrupt
[    0.553427] pcie_pme 0000:00:1c.2:pcie01: service driver pcie_pme loaded
[    0.553434] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[    0.553443] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[    0.553468] vesafb: mode is 1920x1080x32, linelength=7680, pages=0
[    0.553468] vesafb: scrolling: redraw
[    0.553470] vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
[    0.553482] vesafb: framebuffer at 0xe0000000, mapped to 0xffffc90004f00000, using 8128k, total 8128k
[    0.663902] Console: switching to colour frame buffer device 240x67
[    0.773905] fb0: VESA VGA frame buffer device
[    0.773919] ipmi message handler version 39.2
[    0.773970] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
[    0.773973] ACPI: Power Button [PWRB]
[    0.773995] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
[    0.773996] ACPI: Power Button [PWRF]
[    0.774019] GHES: HEST is not enabled!
[    0.774064] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    0.794664] 00:0a: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    0.815623] 0000:00:16.3: ttyS4 at I/O 0xf0a0 (irq = 19, base_baud = 115200) is a 16550A
[    0.815775] Linux agpgart interface v0.103
[    0.816645] brd: module loaded
[    0.817082] loop: module loaded
[    0.817298] libphy: Fixed MDIO Bus: probed
[    0.817352] tun: Universal TUN/TAP device driver, 1.6
[    0.817353] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    0.817376] PPP generic driver version 2.4.2
[    0.817399] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.817401] ehci-pci: EHCI PCI platform driver
[    0.817470] ehci-pci 0000:00:1a.0: EHCI Host Controller
[    0.817474] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
[    0.817484] ehci-pci 0000:00:1a.0: debug port 2
[    0.821389] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
[    0.821399] ehci-pci 0000:00:1a.0: irq 16, io mem 0xf7f38000
[    0.832666] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
[    0.832690] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    0.832691] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.832692] usb usb1: Product: EHCI Host Controller
[    0.832693] usb usb1: Manufacturer: Linux 3.14.17-xenomai-2.6.4 ehci_hcd
[    0.832694] usb usb1: SerialNumber: 0000:00:1a.0
[    0.832759] hub 1-0:1.0: USB hub found
[    0.832762] hub 1-0:1.0: 3 ports detected
[    0.832899] ehci-pci 0000:00:1d.0: EHCI Host Controller
[    0.832902] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
[    0.832911] ehci-pci 0000:00:1d.0: debug port 2
[    0.836806] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
[    0.836815] ehci-pci 0000:00:1d.0: irq 23, io mem 0xf7f37000
[    0.848675] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
[    0.848692] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    0.848693] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.848694] usb usb2: Product: EHCI Host Controller
[    0.848695] usb usb2: Manufacturer: Linux 3.14.17-xenomai-2.6.4 ehci_hcd
[    0.848696] usb usb2: SerialNumber: 0000:00:1d.0
[    0.848754] hub 2-0:1.0: USB hub found
[    0.848756] hub 2-0:1.0: 3 ports detected
[    0.848831] ehci-platform: EHCI generic platform driver
[    0.848836] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.848838] ohci-pci: OHCI PCI platform driver
[    0.848843] ohci-platform: OHCI generic platform driver
[    0.848847] uhci_hcd: USB Universal Host Controller Interface driver
[    0.848923] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.848926] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3
[    0.849004] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported
[    0.849017] xhci_hcd 0000:00:14.0: irq 44 for MSI/MSI-X
[    0.849058] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    0.849059] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.849060] usb usb3: Product: xHCI Host Controller
[    0.849061] usb usb3: Manufacturer: Linux 3.14.17-xenomai-2.6.4 xhci_hcd
[    0.849062] usb usb3: SerialNumber: 0000:00:14.0
[    0.849117] hub 3-0:1.0: USB hub found
[    0.849132] hub 3-0:1.0: 15 ports detected
[    0.851875] xhci_hcd 0000:00:14.0: xHCI Host Controller
[    0.851877] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 4
[    0.851906] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    0.851907] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.851908] usb usb4: Product: xHCI Host Controller
[    0.851909] usb usb4: Manufacturer: Linux 3.14.17-xenomai-2.6.4 xhci_hcd
[    0.851909] usb usb4: SerialNumber: 0000:00:14.0
[    0.851966] hub 4-0:1.0: USB hub found
[    0.851976] hub 4-0:1.0: 6 ports detected
[    0.852763] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    0.855711] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.855714] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.855782] mousedev: PS/2 mouse device common for all mice
[    0.855844] rtc_cmos 00:06: RTC can wake from S4
[    0.855935] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[    0.855960] rtc_cmos 00:06: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[    0.856001] device-mapper: uevent: version 1.0.3
[    0.856040] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[    0.856042] ledtrig-cpu: registered to indicate activity on CPUs
[    0.856097] TCP: cubic registered
[    0.856161] NET: Registered protocol family 10
[    0.856291] NET: Registered protocol family 17
[    0.856296] Key type dns_resolver registered
[    0.856453] Loading compiled-in X.509 certificates
[    0.856973] Loaded X.509 cert 'Magrathea: Glacier signing key: ff216ba2407100b2f7f35aca1050e688e189d850'
[    0.856978] registered taskstats version 1
[    0.858125] Key type trusted registered
[    0.859102] Key type encrypted registered
[    0.860060] AppArmor: AppArmor sha1 policy hashing enabled
[    0.860061] IMA: No TPM chip found, activating TPM-bypass!
[    0.860395] regulator-dummy: disabling
[    0.860455] rtc_cmos 00:06: setting system clock to 2015-05-25 14:49:49 UTC (1432565389)
[    0.860481] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    0.860482] EDD information not available.
[    0.861107] Freeing unused kernel memory: 1624K (ffffffff81d07000 - ffffffff81e9d000)
[    0.861108] Write protecting the kernel read-only data: 12288k
[    0.861976] Freeing unused kernel memory: 604K (ffff880001769000 - ffff880001800000)
[    0.862804] Freeing unused kernel memory: 660K (ffff880001b5b000 - ffff880001c00000)
[    0.869960] systemd-udevd[119]: starting version 204
[    0.877121] video: module verification failed: signature and/or  required key missing - tainting kernel
[    0.880885] pps_core: LinuxPPS API ver. 1 registered
[    0.880887] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.880890] drm: module has bad taint, not creating trace events
[    0.881399] [drm] Initialized drm 1.1.0 20060810
[    0.881507] PTP clock support registered
[    0.881998] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[    0.882000] e1000e: Copyright(c) 1999 - 2013 Intel Corporation.
[    0.882144] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[    0.882158] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[    0.884665] radeon: module has bad taint, not creating trace events
[    0.885206] [drm] radeon kernel modesetting enabled.
[    0.885231] checking generic (e0000000 7f0000) vs hw (e0000000 10000000)
[    0.885232] fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
[    0.885241] Console: switching to colour dummy device 80x25
[    0.885438] [drm] initializing kernel modesetting (OLAND 0x1002:0x6611 0x1028:0x210B).
[    0.885445] [drm] register mmio base: 0xF7E00000
[    0.885446] [drm] register mmio size: 262144
[    0.885502] ATOM BIOS: C55303
[    0.885625] radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M used)
[    0.885626] radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
[    0.885627] [drm] Detected VRAM RAM=1024M, BAR=256M
[    0.885628] [drm] RAM width 64bits DDR
[    0.885650] [TTM] Zone  kernel: Available graphics memory: 3990010 kiB
[    0.885651] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    0.885651] [TTM] Initializing pool allocator
[    0.885655] [TTM] Initializing DMA pool allocator
[    0.885666] [drm] radeon: 1024M of VRAM memory ready
[    0.885667] [drm] radeon: 1024M of GTT memory ready.
[    0.885676] [drm] Loading OLAND Microcode
[    0.885720] [drm] radeon/OLAND_mc2.bin: 31452 bytes
[    0.885735] [drm] Internal thermal controller with fan control
[    0.885774] [drm] probing gen 2 caps for device 8086:c01 = 261ad01/e
[    0.892775] [drm] radeon: dpm initialized
[    0.892841] [drm] GART: num cpu pages 262144, num gpu pages 262144
[    0.894405] [drm] probing gen 2 caps for device 8086:c01 = 261ad01/e
[    0.894410] [drm] enabling PCIE gen 3 link speeds, disable with radeon.pcie_gen2=0
[    1.055073] e1000e 0000:00:19.0 eth0: registered PHC clock
[    1.055076] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) f8:b1:56:b7:f8:17
[    1.055077] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    1.055122] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[    1.055138] ahci 0000:00:1f.2: version 3.0
[    1.055253] ahci 0000:00:1f.2: irq 46 for MSI/MSI-X
[    1.055292] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6 Gbps 0x7 impl RAID mode
[    1.055294] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio slum part ems apst 
[    1.069150] scsi0 : ahci
[    1.069232] scsi1 : ahci
[    1.069305] scsi2 : ahci
[    1.069369] scsi3 : ahci
[    1.069435] scsi4 : ahci
[    1.069500] scsi5 : ahci
[    1.069531] ata1: SATA max UDMA/133 abar m2048@0xf7f36000 port 0xf7f36100 irq 46
[    1.069533] ata2: SATA max UDMA/133 abar m2048@0xf7f36000 port 0xf7f36180 irq 46
[    1.069535] ata3: SATA max UDMA/133 abar m2048@0xf7f36000 port 0xf7f36200 irq 46
[    1.069536] ata4: DUMMY
[    1.069537] ata5: DUMMY
[    1.069537] ata6: DUMMY
[    1.144806] usb 1-1: new high-speed USB device number 2 using ehci-pci
[    1.277255] usb 1-1: New USB device found, idVendor=8087, idProduct=8008
[    1.277256] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.277394] hub 1-1:1.0: USB hub found
[    1.277504] hub 1-1:1.0: 6 ports detected
[    1.388909] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    1.388925] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.388941] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    1.388942] usb 2-1: new high-speed USB device number 2 using ehci-pci
[    1.389505] ata1.00: ATA-7: WDC WD800JD-75MSA3, 10.01E04, max UDMA/133
[    1.389507] ata1.00: 156250000 sectors, multi 16: LBA48 NCQ (depth 31/32), AA
[    1.390061] ata2.00: ATA-8: ST500DM002-1BD142, KC47, max UDMA/133
[    1.390063] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[    1.390102] ata1.00: configured for UDMA/133
[    1.390163] scsi 0:0:0:0: Direct-Access     ATA      WDC WD800JD-75MS 10.0 PQ: 0 ANSI: 5
[    1.390249] sd 0:0:0:0: [sda] 156250000 512-byte logical blocks: (80.0 GB/74.5 GiB)
[    1.390254] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.390265] sd 0:0:0:0: [sda] Write Protect is off
[    1.390266] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.390274] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.391517] ata2.00: configured for UDMA/133
[    1.391567] scsi 1:0:0:0: Direct-Access     ATA      ST500DM002-1BD14 KC47 PQ: 0 ANSI: 5
[    1.391632] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[    1.391634] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[    1.391654] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    1.391668] sd 1:0:0:0: [sdb] Write Protect is off
[    1.391670] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.391690] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.392632] ata3.00: ATAPI: TSSTcorp DVD+/-RW SH-216DB, D100, max UDMA/100
[    1.395066] ata3.00: configured for UDMA/100
[    1.397162] scsi 2:0:0:0: CD-ROM            TSSTcorp DVD+-RW SH-216DB D100 PQ: 0 ANSI: 5
[    1.405481]  sdb: sdb1
[    1.405635] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.407446] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    1.407448] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.407512] sr 2:0:0:0: Attached scsi CD-ROM sr0
[    1.407556] sr 2:0:0:0: Attached scsi generic sg2 type 5
[    1.440323]  sda: sda1 sda2 < sda5 >
[    1.440458] sd 0:0:0:0: [sda] Attached SCSI disk
[    1.521360] usb 2-1: New USB device found, idVendor=8087, idProduct=8000
[    1.521362] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.521505] hub 2-1:1.0: USB hub found
[    1.521610] hub 2-1:1.0: 8 ports detected
[    1.524960] tsc: Refined TSC clocksource calibration: 3392.145 MHz
[    1.797100] usb 2-1.3: new low-speed USB device number 3 using ehci-pci
[    1.894156] usb 2-1.3: New USB device found, idVendor=413c, idProduct=2005
[    1.894158] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.894159] usb 2-1.3: Product: DELL USB Keyboard
[    1.894160] usb 2-1.3: Manufacturer: DELL
[    1.895063] hidraw: raw HID events driver (C) Jiri Kosina
[    1.897708] usbcore: registered new interface driver usbhid
[    1.897709] usbhid: USB HID core driver
[    1.898044] input: DELL DELL USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:413C:2005.0001/input/input5
[    1.898110] hid-generic 0003:413C:2005.0001: input,hidraw0: USB HID v1.10 Keyboard [DELL DELL USB Keyboard] on usb-0000:00:1d.0-1.3/input0
[    1.965313] usb 2-1.4: new low-speed USB device number 4 using ehci-pci
[    2.061470] usb 2-1.4: New USB device found, idVendor=046d, idProduct=c077
[    2.061472] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.061473] usb 2-1.4: Product: USB Optical Mouse
[    2.061474] usb 2-1.4: Manufacturer: Logitech
[    2.063443] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/0003:046D:C077.0002/input/input6
[    2.063538] hid-generic 0003:046D:C077.0002: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.0-1.4/input0
[    2.133381] usb 2-1.6: new full-speed USB device number 5 using ehci-pci
[    2.239760] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000).
[    2.239852] radeon 0000:01:00.0: WB enabled
[    2.239854] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and cpu addr 0xffff88020bc61c00
[    2.239855] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000040000c04 and cpu addr 0xffff88020bc61c04
[    2.239856] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000040000c08 and cpu addr 0xffff88020bc61c08
[    2.239858] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and cpu addr 0xffff88020bc61c0c
[    2.239859] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000040000c10 and cpu addr 0xffff88020bc61c10
[    2.241402] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc900058b5a18
[    2.241403] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.241404] [drm] Driver supports precise vblank timestamp query.
[    2.241421] radeon 0000:01:00.0: irq 47 for MSI/MSI-X
[    2.241430] radeon 0000:01:00.0: radeon: using MSI.
[    2.241455] [drm] radeon: irq initialized.
[    2.253169] usb 2-1.6: New USB device found, idVendor=3923, idProduct=717b
[    2.253170] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.253172] usb 2-1.6: Product: NI USB-6009
[    2.253173] usb 2-1.6: Manufacturer: National Instruments
[    2.253174] usb 2-1.6: SerialNumber: 013541DB
[    2.481230] [drm] ring test on 0 succeeded in 1 usecs
[    2.481236] [drm] ring test on 1 succeeded in 1 usecs
[    2.481240] [drm] ring test on 2 succeeded in 1 usecs
[    2.481303] [drm] ring test on 3 succeeded in 2 usecs
[    2.481311] [drm] ring test on 4 succeeded in 1 usecs
[    2.667380] Switched to clocksource tsc
[    2.667387] [drm] ring test on 5 succeeded in 2 usecs
[    2.667392] [drm] UVD initialized successfully.
[    2.667599] [drm] ib test on ring 0 succeeded in 0 usecs
[    2.667622] [drm] ib test on ring 1 succeeded in 0 usecs
[    2.667644] [drm] ib test on ring 2 succeeded in 0 usecs
[    2.667666] [drm] ib test on ring 3 succeeded in 0 usecs
[    2.667690] [drm] ib test on ring 4 succeeded in 1 usecs
[    2.818463] [drm] ib test on ring 5 succeeded
[    2.819005] [drm] Radeon Display Connectors
[    2.819006] [drm] Connector 0:
[    2.819007] [drm]   DP-1
[    2.819008] [drm]   HPD1
[    2.819009] [drm]   DDC: 0x6540 0x6540 0x6544 0x6544 0x6548 0x6548 0x654c 0x654c
[    2.819009] [drm]   Encoders:
[    2.819010] [drm]     DFP1: INTERNAL_UNIPHY
[    2.819011] [drm] Connector 1:
[    2.819012] [drm]   DVI-I-1
[    2.819012] [drm]   HPD2
[    2.819013] [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
[    2.819014] [drm]   Encoders:
[    2.819014] [drm]     DFP2: INTERNAL_UNIPHY
[    2.819015] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    2.875551] [drm] fb mappable at 0xE1480000
[    2.875553] [drm] vram apper at 0xE0000000
[    2.875554] [drm] size 8294400
[    2.875554] [drm] fb depth is 24
[    2.875555] [drm]    pitch is 7680
[    2.875591] fbcon: radeondrmfb (fb0) is primary device
[    2.991036] Console: switching to colour frame buffer device 240x67
[    2.996564] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[    2.996565] radeon 0000:01:00.0: registered panic notifier
[    3.006490] [drm] Initialized radeon 2.37.0 20080528 for 0000:01:00.0 on minor 0
[    3.317702] raid6: sse2x1   10804 MB/s
[    3.385728] raid6: sse2x2   13649 MB/s
[    3.453757] raid6: sse2x4   15701 MB/s
[    3.521785] raid6: avx2x1   20705 MB/s
[    3.589812] raid6: avx2x2   24084 MB/s
[    3.657841] raid6: avx2x4   27811 MB/s
[    3.657841] raid6: using algorithm avx2x4 (27811 MB/s)
[    3.657842] raid6: using avx2x2 recovery algorithm
[    3.657930] xor: automatically using best checksumming function:
[    3.697856]    avx       : 23206.000 MB/sec
[    3.699280] btrfs: module has bad taint, not creating trace events
[    3.699464] bio: create slab <bio-1> at 1
[    3.699610] Btrfs loaded
[    3.700369] random: nonblocking pool is initialized
[    4.087291] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[   19.126219] Adding 8270844k swap on /dev/sda5.  Priority:-1 extents:1 across:8270844k FS
[   19.439145] systemd-udevd[394]: starting version 204
[   19.996736] systemd-udevd[421]: renamed network interface eth0 to eth1
[   20.406078] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182f conflicts with OpRegion 0x0000000000001800-0x000000000000187f (\PMIO) (20131218/utaddress-258)
[   20.406082] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   20.406085] ACPI Warning: SystemIO range 0x0000000000001c30-0x0000000000001c3f conflicts with OpRegion 0x0000000000001c00-0x0000000000001c3f (\GPRL) (20131218/utaddress-258)
[   20.406087] ACPI Warning: SystemIO range 0x0000000000001c30-0x0000000000001c3f conflicts with OpRegion 0x0000000000001c00-0x0000000000001fff (\GPR_) (20131218/utaddress-258)
[   20.406089] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   20.406090] ACPI Warning: SystemIO range 0x0000000000001c00-0x0000000000001c2f conflicts with OpRegion 0x0000000000001c00-0x0000000000001c3f (\GPRL) (20131218/utaddress-258)
[   20.406092] ACPI Warning: SystemIO range 0x0000000000001c00-0x0000000000001c2f conflicts with OpRegion 0x0000000000001c00-0x0000000000001fff (\GPR_) (20131218/utaddress-258)
[   20.406094] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   20.406094] lpc_ich: Resource conflict(s) found affecting gpio_ich
[   20.481564] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   20.542056] lp: driver loaded but no devices found
[   20.564891] audit: type=1400 audit(1432565409.190:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=483 comm="apparmor_parser"
[   20.564901] audit: type=1400 audit(1432565409.190:3): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=483 comm="apparmor_parser"
[   20.564903] audit: type=1400 audit(1432565409.194:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=483 comm="apparmor_parser"
[   20.565103] audit: type=1400 audit(1432565409.194:5): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=483 comm="apparmor_parser"
[   20.565105] audit: type=1400 audit(1432565409.194:6): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=483 comm="apparmor_parser"
[   20.565202] audit: type=1400 audit(1432565409.194:7): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=483 comm="apparmor_parser"
[   20.603256] mei_me 0000:00:16.0: irq 48 for MSI/MSI-X
[   20.617443] ppdev: user-space parallel port driver
[   20.886818] device-mapper: multipath: version 1.6.0 loaded
[   20.992306] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2)
[   21.168412] Analogy: MITE: Available NI device IDs: 0xc4c4 0x2890
[   21.196785] AVX2 version of gcm_enc/dec engaged.
[   21.651675] snd_hda_codec: module has bad taint, not creating trace events
[   21.722879] snd_hda_intel: module has bad taint, not creating trace events
[   21.723024] snd_hda_intel 0000:00:1b.0: irq 49 for MSI/MSI-X
[   21.723138] hda-intel 0000:01:00.1: Handle VGA-switcheroo audio client
[   21.723139] hda-intel 0000:01:00.1: Using LPIB position fix
[   21.723140] hda-intel 0000:01:00.1: Force to non-snoop mode
[   21.723192] snd_hda_intel 0000:01:00.1: irq 50 for MSI/MSI-X
[   21.725367] hda-intel 0000:01:00.1: Enable sync_write for stable communication
[   21.810158] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input8
[   21.810204] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input7
[   21.886328] kvm: module has bad taint, not creating trace events
[   21.939721] SKU: Nid=0x1d sku_cfg=0x40400001
[   21.939723] SKU: port_connectivity=0x1
[   21.939724] SKU: enable_pcbeep=0x0
[   21.939725] SKU: check_sum=0x00000000
[   21.939725] SKU: customization=0x00000000
[   21.939726] SKU: external_amp=0x0
[   21.939726] SKU: platform_type=0x0
[   21.939727] SKU: swap=0x0
[   21.939728] SKU: override=0x1
[   21.939983] autoconfig: line_outs=1 (0x1b/0x0/0x0/0x0/0x0) type:line
[   21.939984]    speaker_outs=1 (0x14/0x0/0x0/0x0/0x0)
[   21.939984]    hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[   21.939985]    mono: mono_out=0x0
[   21.939986]    inputs:
[   21.939987]      Front Mic=0x1a
[   21.939988]      Rear Mic=0x18
[   21.939988] realtek: No valid SSID, checking pincfg 0x40400001 for NID 0x1d
[   21.939989] realtek: Enabling init ASM_ID=0x0001 CODEC_ID=10ec0280
[   21.944466] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[   21.944664] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[   21.944713] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[   21.944754] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[   23.481104] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   28.847202] init: failsafe main process (837) killed by TERM signal
[   29.675287] audit: type=1400 audit(1432565418.298:8): apparmor="STATUS" operation="profile_load" name="/usr/lib/cups/backend/cups-pdf" pid=973 comm="apparmor_parser"
[   29.675291] audit: type=1400 audit(1432565418.298:9): apparmor="STATUS" operation="profile_load" name="/usr/sbin/cupsd" pid=973 comm="apparmor_parser"
[   29.675495] audit: type=1400 audit(1432565418.298:10): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=973 comm="apparmor_parser"
[   29.882806] audit: type=1400 audit(1432565418.506:11): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=983 comm="apparmor_parser"
[   29.882811] audit: type=1400 audit(1432565418.506:12): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=983 comm="apparmor_parser"
[   29.882813] audit: type=1400 audit(1432565418.506:13): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=983 comm="apparmor_parser"
[   29.883013] audit: type=1400 audit(1432565418.506:14): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=983 comm="apparmor_parser"
[   29.883015] audit: type=1400 audit(1432565418.506:15): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=983 comm="apparmor_parser"
[   29.883112] audit: type=1400 audit(1432565418.506:16): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=983 comm="apparmor_parser"
[   29.883150] audit: type=1400 audit(1432565418.506:17): apparmor="STATUS" operation="profile_load" name="/usr/sbin/cups-browsed" pid=987 comm="apparmor_parser"
[   30.750957] init: cups main process (974) killed by HUP signal
[   30.750963] init: cups main process ended, respawning
[   31.321265] Bluetooth: Core ver 2.18
[   31.321276] NET: Registered protocol family 31
[   31.321277] Bluetooth: HCI device and connection manager initialized
[   31.321283] Bluetooth: HCI socket layer initialized
[   31.321284] Bluetooth: L2CAP socket layer initialized
[   31.321289] Bluetooth: SCO socket layer initialized
[   31.560610] Bluetooth: RFCOMM TTY layer initialized
[   31.560617] Bluetooth: RFCOMM socket layer initialized
[   31.560621] Bluetooth: RFCOMM ver 1.11
[   31.593362] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   31.593364] Bluetooth: BNEP filters: protocol multicast
[   31.593368] Bluetooth: BNEP socket layer initialized
[   35.084855] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[   35.187047] e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
[   35.187137] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[   38.954159] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[   38.954189] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   39.293523] init: plymouth-upstart-bridge main process ended, respawning
[   39.295616] init: plymouth-upstart-bridge main process (1267) terminated with status 1
[   39.295622] init: plymouth-upstart-bridge main process ended, respawning
[   41.105252] Analogy: analogy_ni_pcimio: pcimio_attach: found pci-6036e board
[   41.105284] Analogy: analogy_ni_pcimio: pcimio_attach: found irq 19
[   42.092513] vboxdrv: Found 4 processor cores.
[   42.092687] vboxdrv: fAsync=0 offMin=0x1b4 offMax=0xda0
[   42.092735] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
[   42.092736] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007).
[   42.299830] vboxpci: IOMMU not found (not registered)
[   43.078387] init: plymouth-stop pre-start process (1635) terminated with status 1
[   49.235898] audit_printk_skb: 123 callbacks suppressed
[   49.235901] audit: type=1400 audit(1432565437.850:59): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name="/etc/dconf/profile/gdm" pid=1907 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=117 ouid=0
[   60.115207] audit: type=1400 audit(1432565448.728:60): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=2199 comm="apparmor_parser"
[   60.115212] audit: type=1400 audit(1432565448.728:61): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=2199 comm="apparmor_parser"
[   60.115418] audit: type=1400 audit(1432565448.728:62): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=2199 comm="apparmor_parser"

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Gilles Chanteperdrix]

On Mon, May 25, 2015 at 11:06:25AM -0400, Yogi A. Patel wrote:
> 
> On 05/25/2015 10:23 AM, Jeroen Van den Keybus wrote:
> >>I read around online about interrupt remapping - and I can't seem to find
> >>anything that hints at why this turning it off would cause the latencies to
> >>be all over the place.
> >It shouldn't. There may be other reasons. But beware, in our tests the
> >Core i5/i7 showed about 29 us max. latency (running dohell), but
> >depending on the load, that can go up to 70 us (running a handbrake
> >video encoding session). What you see might actually be the best you
> >can get.
> I've been using "stress" to put a load on the system while running the
> xenomai latency test.
> 
> >>Any thoughts/guidance appreciated!
> >You seem to be running a desktop distribution. Try leaving desktop
> >mode (kill the window manager / X). Check you're not running binary
> >graphics drivers. Unload as many drivers as you can.
> You are correct. It looks like if I blacklist the radeon module (which I
> compiled with the kernel as a module, not using a binary), the latencies
> drop to 8-10us. I

The information that would be interesting would be whether you are
running the proprietary module. Even though proprietary modules
seem like being compiled, they in fact compile a small glue over a
big binary blob. Obviously, the I-pipe patch can not patch that
binary blob, so, you can only hope that the glue compiles what the
I-pipe patch would want to patch.

Anyway, this log message:
> [    0.880890] drm: module has bad taint, not creating trace events
Suggests that you are running the proprietary blob.

Also, something to note, once again, is that if you care about
performances, you should not have a kernel with everything enabled.
Notably not any form of tracing or debugging.

On the other hand, this message:
> [   21.886328] kvm: module has bad taint, not creating trace events
would suggest that you have rather a module/kernel mismatch. This
too can be detrimental to performances if you are running plain
linux modules with an I-pipe patched kernel.

However, looking at all this, I do not find any evidence that
disabling irq remapping created any performance issue, and I really
do not understand the logic that lead you to this weird conclusion.

-- 
					    Gilles.

Re: [Xenomai] 3.14.17 patch initial ram disk hangup

[Jeroen Van den Keybus]

> You are correct. It looks like if I blacklist the radeon module (which I
> compiled with the kernel as a module, not using a binary), the latencies
> drop to 8-10us. I
>
> Just some ideas; you don't seem to have provided a dmesg log.
>
> Sorry - dmesg log is attached. From just looking at the radeon specific
> messages, I don't quite see what the problem could be except for something
> internal to the radeon driver.

Well, at least we now know that you are running with a HD8xxx GPU, and
what I find intriguing is the date reported by the driver:

[drm] Initialized radeon 2.37.0 20080528 for 0000:01:00.0 on minor 0

I would definitely check your driver. especially verify that fglrx is
NOT running. Apart from that:

[    0.877121] video: module verification failed: signature and/or
required key missing - tainting kernel
[ 0.880890] drm: module has bad taint, not creating trace events
[ 0.884665] radeon: module has bad taint, not creating trace events
...

you have no less than 6 tainting warnings for a kernel you claim to
have built yourself. Are you sure you didn't turn the module
versioning check off ? To me it seems your modules (or not all of
them) and kernel do not match. If so, all bets are off and this setup
could only be running by coincidence. You could even be running
modules that aren't patched at all in a patched kernel.

I also see a 'vboxdrv' driver. I have absolutely no idea what its
impact on I-pipe would be, but it sounds bad to me (along with kvm).
This is the type of thing you would only enable / try when the system
is working properly. I wouldn't even allow it to initialize.

Apart from that, there is indeed not much that can be learnt from your
dmesg log...

Other suggestions include trying to use the on-CPU video (but you must
have the proper chipset for this), remove the Radeon and save some
energy in the process.

It is imperative that you do as Gilles said: minimize the .config
(you'd be amazed how much you can throw away and still keep the Ubuntu
desktop). It compiles much faster and at least you are more likely to
throw an eye on the compile log afterwards.


Jeroen.


>
> Jeroen.
>
>
>
> Yogi
>
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://xenomai.org/mailman/listinfo/xenomai
>
>
> --
>
> Yogi A. Patel
> @yapatel525
>