From: Carsten Emde <C.Emde@osadl.org>
To: pavel@pavlinux.ru
Cc: Steven Rostedt <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.12.8-rt11
Date: Mon, 27 Jan 2014 23:01:47 +0100 [thread overview]
Message-ID: <52E6D74B.80401@osadl.org> (raw)
In-Reply-To: <20140127132411.6f420c8f@gandalf.local.home>
On 01/27/2014 07:24 PM, Steven Rostedt wrote:
> On Mon, 27 Jan 2014 13:42:29 +0400
> Pavel Vasilyev <pavel@pavlinux.ru> wrote:
>
>> 27.01.2014 12:44, Sebastian Andrzej Siewior пишет:
>>> On 01/26/2014 10:25 PM, Pavel Vasilyev wrote:
>>>> 25.01.2014 17:45, Sebastian Andrzej Siewior пишет:
>>>>> Dear RT folks!
>>>>
>>>>
>>>> Gentlemen, let's have a month of stress testing! Divide tasks
>>>> testing subsystem: USB, NET, MM, ACPI, AUDIO, VIDEO By CPUs:
>>>> ARM/PPC/X86/X86_64...
>>>>
>>>> Purely on observations noted that in September 2013, the quality
>>>> and stability of the code has deteriorated dramatically.
>>>
>>> By September 2k13, do you mean a specific v3.10-RT release?
>>>
>>
>> Any after 3.2.x-rt
>>
>> Maybe I'm doing something wrong, but:
>>
>> 1) All kernels (3.2, 3.8, 3.12, 3.13,...) are working normally without patches;
>>
>> 2) 3.2 works fine in CONFIG_PREEMPT_RT_BASE or CONFIG_PREEMPT_RT_FULL modes;
>>
>> 3) 3.10 not works at all, even without -RT patches;
>
> Please report the problems here to LKML (linux-kernel@vger.kernel.org)
> to the appropriate maintainers. As well as the stable@vger.kernel.org
> mailing list.
>
>>
>> 4) 3.12 work only as CONFIG_PREEMPT_RT_BASE or CONFIG_PREEMPT_RT_FULL in
>> uniprocessor mode (maxcpus=0, nosmp). Newer patches (Oct.-Dec.) did not work,
>> even in RT_BASE mode.
>
> Does 3.12 work without the -rt patches?
>
>>
>> Varia hardware: One Opteron 285, 2-cpus (4 cores). Six Intel Atoms devices
>> kernels compiled as x86_32.
>
> I have an intel atom dev board hanging around somewhere. I'll see if I
> can test this. Can you send me your config privately.
I can offer help as well. And I am most curious to learn what prevents
your systems from booting. Please send me your config as well - I'll run
(or at least try to run) it on a couple of spare farm systems.
-Carsten.
next prev parent reply other threads:[~2014-01-27 22:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 13:45 [ANNOUNCE] 3.12.8-rt11 Sebastian Andrzej Siewior
2014-01-25 21:34 ` Mike Galbraith
2014-01-26 9:28 ` Pavel Vasilyev
2014-01-26 21:25 ` Pavel Vasilyev
2014-01-27 8:44 ` Sebastian Andrzej Siewior
2014-01-27 9:42 ` Pavel Vasilyev
2014-01-27 18:24 ` Steven Rostedt
2014-01-27 22:01 ` Carsten Emde [this message]
2014-01-31 22:22 ` Sebastian Andrzej Siewior
2014-01-27 4:54 ` Carsten Emde
2014-01-27 9:14 ` Mike Galbraith
2014-01-29 14:30 ` Joakim Hernberg
2014-01-31 22:11 ` Sebastian Andrzej Siewior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52E6D74B.80401@osadl.org \
--to=c.emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@pavlinux.ru \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).