linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tim Sally <tsally@atomicpeace.com>
Cc: Thomas Sattler <sattler@med.uni-frankfurt.de>,
	richard -rw- weinberger <richard.weinberger@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Fwd: BUG: scheduling while atomic: chcpu/6197/0x00000002
Date: Wed, 27 Jun 2012 10:21:16 -0400	[thread overview]
Message-ID: <1340806876.16702.13.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20120627140119.GA8681@atomicpeace.com>

On Wed, 2012-06-27 at 10:01 -0400, Tim Sally wrote:
> I'm interested in this as well. -Tim
> 
> On Wed, Jun 27, 2012 at 03:32:06PM +0200, Thomas Sattler wrote:
> > > I believe CPU hotplug is still an issue with -rt, and
> > > this is a known problem.
> > 
> > Is there an (un-)official list of known problems? I'd
> > like to help by reporting issues without repeating
> > already known issues over and over again. :-)

Unfortunately, I do not believe such a list exists. Perhaps one should
be created ;-)

-- Steve



      reply	other threads:[~2012-06-27 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4FDF00CB.7090703@med.uni-frankfurt.de>
     [not found] ` <4FDF201E.2090408@med.uni-frankfurt.de>
     [not found]   ` <4FE19494.6000303@med.uni-frankfurt.de>
     [not found]     ` <4FE86067.9010408@med.uni-frankfurt.de>
     [not found]       ` <4FEAF165.9090008@med.uni-frankfurt.de>
2012-06-27 12:26         ` Fwd: BUG: scheduling while atomic: chcpu/6197/0x00000002 richard -rw- weinberger
2012-06-27 12:37           ` Steven Rostedt
2012-06-27 13:32             ` Thomas Sattler
2012-06-27 14:01               ` Tim Sally
2012-06-27 14:21                 ` Steven Rostedt [this message]

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=1340806876.16702.13.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=richard.weinberger@gmail.com \
    --cc=sattler@med.uni-frankfurt.de \
    --cc=tglx@linutronix.de \
    --cc=tsally@atomicpeace.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).