From: Steven Rostedt <rostedt@goodmis.org>
To: Tim Sander <tim.sander@hbm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.0.14-rt31
Date: Thu, 12 Jan 2012 08:54:44 -0500 [thread overview]
Message-ID: <1326376484.7642.65.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <201201121118.34776.tim.sander@hbm.com>
On Thu, 2012-01-12 at 11:18 +0100, Tim Sander wrote:
> Hi Steven
>
> I have just tested 3.0.14 with some local adaptions. Unfortunatly there we
> have still two errors here:
> Reboot ( of upstart) fails sometimes fails with the following message:
> "reboot: Unable to execute shutdown: Bad address"
What's the bad address? Was there a kernel oops?
> This problem can probably easily worked around by catching a failed execution
> and retry, but i am afraid that execution fails more often in other places and
> leads to silent functionality failures.
>
> and the running wild ksoftirqd0 most probably after the kernel message:
> "sched: RT throttling activated"
Hmm, that's not good. It means that an RT task is spinning too much.
> It also seems as if the system looks up after running ifconfig. But it seems as
> if the error only shows up most of the times if i am not around.
s/looks/locks/ ?
If it happens after ifconfig, then obviously that looks to be something
to do with either the network driver or the network stack.
But there's really nothing I can do to look into this without more
information.
-- Steve
next prev parent reply other threads:[~2012-01-12 13:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 3:40 [ANNOUNCE] 3.0.14-rt31 Steven Rostedt
2011-12-22 11:08 ` Raz
2011-12-22 11:50 ` Steven Rostedt
2011-12-22 12:08 ` Lars Segerlund
2011-12-22 13:53 ` John Kacur
2011-12-22 14:00 ` Georgiewskiy Yuriy
2011-12-22 14:44 ` Steven Rostedt
2011-12-22 15:29 ` Georgiewskiy Yuriy
2011-12-22 16:23 ` Steven Rostedt
2011-12-22 16:35 ` Georgiewskiy Yuriy
2011-12-24 0:02 ` Karsten Wiese
2011-12-24 14:13 ` Steven Rostedt
2011-12-24 16:16 ` Clark Williams
2012-01-10 18:53 ` Steven Rostedt
2012-01-10 23:56 ` Karsten Wiese
2012-01-04 15:19 ` Georgiewskiy Yuriy
2012-01-11 11:10 ` Karsten Wiese
2012-01-11 15:39 ` Steven Rostedt
2012-01-12 10:18 ` Tim Sander
2012-01-12 13:54 ` Steven Rostedt [this message]
2012-01-12 16:57 ` Tim Sander
2012-01-13 9:42 ` Tim Sander
2012-01-13 18:45 ` Bernardo Barros
2012-01-13 20:30 ` Tim Sander
2012-01-13 23:51 ` Steven Rostedt
2012-01-17 14:27 ` [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Tim Sander
2012-01-17 14:42 ` Steven Rostedt
2012-01-17 17:40 ` Mike Galbraith
2012-01-18 11:11 ` [ANNOUNCE] 3.0.14-rt31 - ksoftirq running wild - FEC ethernet driver to blame? Yep Tim Sander
2012-01-18 13:54 ` Mike Galbraith
2012-01-18 15:37 ` Steven Rostedt
2012-01-24 10:52 ` Tim Sander
2012-01-25 9:31 ` Tim Sander
2012-02-01 20:27 ` Steven Rostedt
2012-02-01 23:11 ` Tim Sander
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=1326376484.7642.65.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tim.sander@hbm.com \
--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).