From: Pavel Vasilyev <pavel@pavlinux.ru>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.12.8-rt11
Date: Mon, 27 Jan 2014 13:42:29 +0400 [thread overview]
Message-ID: <52E62A05.7080802@pavlinux.ru> (raw)
In-Reply-To: <52E61C52.6070104@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1739 bytes --]
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;
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.
Varia hardware: One Opteron 285, 2-cpus (4 cores). Six Intel Atoms devices
kernels compiled as x86_32.
I have my patches, but I tested both with them and without them.
---
Behold! 3.12.8-rt11, RT_FULL mode, kernel cmdline: init=/bin/bash
1.
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
2.
in single mode: After 2 minutes timeout: see screenshot
http://i59.fastpic.ru/big/2014/0127/bc/0f9e04536181286f820ecaae5a8481bc.jpg
3.
command killall -15 freezed system!
Kernel compiled with debug information starts to work normally, but of course
slower. :D
--
Pavel.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-27 9:42 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 [this message]
2014-01-27 18:24 ` Steven Rostedt
2014-01-27 22:01 ` Carsten Emde
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=52E62A05.7080802@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--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).