linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH -rt] printk: Don't emit console_cpu_notify() for CPU_DYING
Date: Wed, 16 Nov 2011 09:19:50 -0500	[thread overview]
Message-ID: <1321453190.4181.21.camel@frodo> (raw)
In-Reply-To: <20111116094219.GA9281@zhy>

On Wed, 2011-11-16 at 17:42 +0800, Yong Zhang wrote:
> Otherwise we will get below warning:
> 
> BUG: sleeping function called from invalid context at /build/linux/kernel/rtmutex.c:645
> in_atomic(): 1, irqs_disabled(): 1, pid: 1054, name: migration/9
> no locks held by migration/9/1054.
> irq event stamp: 36
> hardirqs last  enabled at (35): [<ffffffff815f5b50>] _raw_spin_unlock_irq+0x30/0x70
> hardirqs last disabled at (36): [<ffffffff810b7eaf>] stop_machine_cpu_stop+0x8f/0x110
> softirqs last  enabled at (0): [<ffffffff81051b53>] copy_process+0x6d3/0x1640
> softirqs last disabled at (0): [<          (null)>]           (null)
> Pid: 1054, comm: migration/9 Not tainted 3.2.0-rc1-rt2-11312-gbf51260-dirty #12
> Call Trace:

Thomas, doesn't printk not print to serial in atomic contexts? Or did
that change?

-- Steve



  reply	other threads:[~2011-11-16 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16  9:42 [PATCH -rt] printk: Don't emit console_cpu_notify() for CPU_DYING Yong Zhang
2011-11-16 14:19 ` Steven Rostedt [this message]
2011-11-16 14:48   ` Thomas Gleixner
2011-11-17  5:29     ` Yong Zhang

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=1321453190.4181.21.camel@frodo \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yong.zhang0@gmail.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).