From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Clark Williams <williams@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
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] 4.0.4-rt1
Date: Thu, 11 Jun 2015 14:38:56 +0200 [thread overview]
Message-ID: <20150611123856.GH16115@linutronix.de> (raw)
In-Reply-To: <5567C741.5010007@localhost>
* Fernando Lopez-Lezcano | 2015-05-28 18:56:17 [-0700]:
>On 05/26/2015 12:41 PM, Fernando Lopez-Lezcano wrote:
>Oh well. Second time the machine hangs in two days in the same way
>(otherwise very stable running 3.18.x-rty)
http://marc.info/?l=linux-rt-users&m=143402285006570&w=2
In future
>May 28 18:49:21 localhost kernel: Call Trace:
>May 28 18:49:21 localhost kernel: [<ffffffff811b8d8f>]
>__remove_mapping+0x12f/0x1a0
>May 28 18:49:21 localhost kernel: [<ffffffff811bba3f>]
>shrink_page_list+0x5ef/0xc30
>May 28 18:49:21 localhost kernel: [<ffffffff811bc709>]
>shrink_inactive_list+0x1e9/0x630
Please make sure you client does not end the line for you. It is hard to
read. And I may not want to…
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-11 12:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 21:39 [ANNOUNCE] 4.0.4-rt1 Sebastian Andrzej Siewior
2015-05-19 22:33 ` Carsten Emde
2015-05-19 22:51 ` Pavel Vasilyev
2015-05-20 7:12 ` Sebastian Andrzej Siewior
2015-05-20 13:18 ` Daniel Wagner
2015-05-19 22:48 ` Pavel Vasilyev
2015-05-20 3:14 ` Mike Galbraith
2015-05-20 10:06 ` Pavel Vasilyev
2015-06-11 12:09 ` Sebastian Andrzej Siewior
2015-05-23 11:57 ` Pavel Vasilyev
2015-06-11 12:08 ` Sebastian Andrzej Siewior
2015-05-24 20:59 ` Fernando Lopez-Lezcano
2015-06-11 12:22 ` [PATCH] ASoC: Intel: sst: use ; instead of , at the of a C statement Sebastian Andrzej Siewior
2015-06-11 13:04 ` Mats Karrman
2015-06-11 13:14 ` [PATCH v2] " Sebastian Andrzej Siewior
2015-06-12 7:22 ` Vinod Koul
2015-06-12 10:37 ` Mark Brown
2015-05-26 13:34 ` [ANNOUNCE] 4.0.4-rt1 Clark Williams
2015-05-26 13:38 ` Steven Rostedt
2015-05-26 13:48 ` Clark Williams
2015-05-26 14:49 ` Mike Galbraith
2015-05-26 15:19 ` Steven Rostedt
2015-05-26 15:43 ` Clark Williams
2015-05-26 19:41 ` Fernando Lopez-Lezcano
2015-05-29 1:56 ` Fernando Lopez-Lezcano
2015-06-09 16:45 ` Fernando Lopez-Lezcano
2015-06-09 22:05 ` Pavel Vasilyev
2015-06-10 2:41 ` Mike Galbraith
2015-06-10 3:10 ` Fernando Lopez-Lezcano
2015-06-09 22:10 ` Pavel Vasilyev
2015-06-11 12:38 ` Sebastian Andrzej Siewior [this message]
2015-05-28 8:41 ` Joakim Hernberg
2015-06-11 12:34 ` Sebastian Andrzej Siewior
2015-05-27 9:44 ` Joakim Hernberg
2015-05-27 10:19 ` Jeremy Jongepier
2015-05-28 8:33 ` Joakim Hernberg
2015-05-27 15:50 ` Ralf Mardorf
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=20150611123856.GH16115@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=nando@ccrma.Stanford.EDU \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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).