From: Georgiewskiy Yuriy <bottleman@icf.org.ru>
To: hermann <brummer-@web.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Maarten Lankhorst <m.b.lankhorst@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Darren Hart <dvhart@linux.intel.com>
Subject: Re: [ANNOUNCE] 3.0-rt3
Date: Sun, 24 Jul 2011 21:23:34 +0400 (MSD) [thread overview]
Message-ID: <alpine.DEB.2.02.1107242118510.14833@icf.org.ru> (raw)
In-Reply-To: <1311525756.2276.6.camel@box>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1578 bytes --]
On 2011-07-24 18:42 +0200, hermann wrote Thomas Gleixner:
Hi, I confirm it too - random freezes during normal work, no load, no logs too, sometimes
while starting X, sometimes after X started and worked, also randome freezes
while suspend-resume то ram aka ACPI S3 state.
h> schrieb Thomas Gleixner:
h>
h>> Dear RT Folks,
h>>
h>> I'm pleased to announce the 3.0-rt3 release.
h>>
h>> Changes versus 3.0-rt2:
h>>
h>> * Fix earlyprintk really
h>>
h>
h>Hi
h>
h>I still have some trouble with rt1 - rt3.
h>During boot, the kernel is absolutely silent, sometimes it hangs on boot,
h>sometimes it hangs on login, sometimes it freeze without any known reason
h>during session (no heavy load or some thing like that).
h>I cant find any meaningful log, so I just can report it as it is here.
h>rc7-rt0 works very well here, I build 3.0-rt1 - rt3 with the same config
h>then rt0.
h>
h>regards
h>hermann
h>
h>--
h>To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
h>the body of a message to majordomo@vger.kernel.org
h>More majordomo info at http://vger.kernel.org/majordomo-info.html
h>
C уважением With Best Regards
Георгиевский Юрий. Georgiewskiy Yuriy
+7 4872 711666 +7 4872 711666
факс +7 4872 711143 fax +7 4872 711143
Компания ООО "Ай Ти Сервис" IT Service Ltd
http://nkoort.ru http://nkoort.ru
JID: GHhost@icf.org.ru JID: GHhost@icf.org.ru
YG129-RIPE YG129-RIPE
next prev parent reply other threads:[~2011-07-24 18:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 10:33 Thomas Gleixner
2011-07-24 14:40 ` Maarten Lankhorst
2011-07-24 16:12 ` Thomas Gleixner
2011-07-24 16:42 ` hermann
2011-07-24 16:44 ` Thomas Gleixner
2011-07-24 16:53 ` hermann
2011-07-24 17:23 ` Georgiewskiy Yuriy [this message]
2011-07-25 22:20 ` Darren Hart
2011-07-26 6:00 ` Darren Hart
2011-07-26 11:44 ` Maarten Lankhorst
2011-07-26 17:01 ` Darren Hart
2011-07-26 17:11 ` Maarten Lankhorst
2011-07-27 1:57 ` [ANNOUNCE] 3.0-rt3 (futex_requeue bad spinlock magic) Darren Hart
2011-07-27 8:25 ` Darren Hart
2011-07-26 9:01 ` [ANNOUNCE] 3.0-rt3 Thomas Gleixner
2011-07-25 22:55 ` Fernando Lopez-Lezcano
2011-07-26 9:13 ` Uwe Kleine-König
2011-07-26 23:52 ` Fernando Lopez-Lezcano
2011-07-26 23:57 ` Fernando Lopez-Lezcano
2011-07-26 3:11 ` Frank Rowand
2011-07-26 9:30 ` Uwe Kleine-König
2011-07-26 3:12 ` Frank Rowand
2011-07-26 9:19 ` Uwe Kleine-König
2011-07-26 9:25 ` Thomas Gleixner
2011-07-26 3:14 ` Frank Rowand
2011-07-26 3:49 ` Darren Hart
2011-07-26 6:20 ` Yong Zhang
2011-07-27 18:05 ` N, Mugunthan V
2011-07-27 18:32 ` Thomas Gleixner
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=alpine.DEB.2.02.1107242118510.14833@icf.org.ru \
--to=bottleman@icf.org.ru \
--cc=brummer-@web.de \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=m.b.lankhorst@gmail.com \
--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
all inboxes | Powered by JetHome®