All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
Cc: "Ryan Hope" <rmh3093@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"Vegard Nossum" <vegard.nossum@gmail.com>
Subject: Re: [-mmotm] BUG: scheduling while atomic: swapper
Date: Tue, 26 Aug 2008 01:24:58 -0700	[thread overview]
Message-ID: <20080826012458.abe3bbba.akpm@linux-foundation.org> (raw)
In-Reply-To: <b647ffbd0808260111r2aed706cvc4c5d483912ec8c2@mail.gmail.com>

On Tue, 26 Aug 2008 10:11:24 +0200 "Dmitry Adamushko" <dmitry.adamushko@gmail.com> wrote:

> 2008/8/26 Ryan Hope <rmh3093@gmail.com>:
> > BUG: scheduling while atomic: swapper/1/0x00000002
> > Modules linked in:
> > Pid: 1, comm: swapper Tainted: G        W 2.6.27-rc4-zenmmotm1 #4
> >  [<c057a0c7>] schedule+0x287/0x6d0
> >  [<c03672e6>] vsnprintf+0x3a6/0x6c0
> >  [<c057a92d>] schedule_timeout+0x7d/0xb0
> >  [<c021e0c8>] __wake_up+0x38/0x50
> >  [<c057a74a>] wait_for_common+0x8a/0x130
> >  [<c0220ab0>] default_wake_function+0x0/0x10
> >  [<c0237743>] call_usermodehelper_exec+0xc3/0xf0
> >  [<c0362ede>] kobject_uevent_env+0x37e/0x3a0
> >  [<c03d5921>] device_add+0x551/0x630
> >  [<c03d5ac3>] device_create_vargs+0xb3/0xd0
> >  [<c06ccc47>] microcode_intel_module_init+0x0/0x39
> 
> It doesn't look like Linus's tree... there is no
> microcode_intel_module_init() in .27+. So what is it?

mmotm is linux-next plus -mm stuff

> Anyway, your trace might be explained by a bug that has been already
> fixed in Ingo's -tip.
> 
> Here is the commit:
> http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commit;h=8343ef2437c599d30568e6b5a257a40bf2f4902b

Yes, an unbalanced get_cpu() would explain it.

However that patch is already in current -mm.  Ryan, can you please
check to see if it's in the version you tested?  The "fixed" version
looks like this:

static int __init microcode_intel_module_init(void)
{
	struct cpuinfo_x86 *c = &cpu_data(get_cpu());

	if (c->x86_vendor == X86_VENDOR_INTEL)
		return microcode_init(&microcode_intel_ops, THIS_MODULE);
	else
		return -ENODEV;
}


  reply	other threads:[~2008-08-26  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26  2:09 [-mmotm] BUG: scheduling while atomic: swapper Ryan Hope
2008-08-26  6:37 ` Andrew Morton
2008-08-26  7:01   ` Vegard Nossum
2008-08-26  8:11 ` Dmitry Adamushko
2008-08-26  8:24   ` Andrew Morton [this message]
     [not found]     ` <9f8af95f0808260225u162da49aj1d6f6fd9db79499f@mail.gmail.com>
2008-08-26  9:29       ` james toy
2008-08-26 10:02       ` Dmitry Adamushko
2008-08-26 14:15         ` Ryan Hope
2008-08-26 14:53           ` Ryan Hope
2008-08-26 14:58             ` Ryan Hope

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=20080826012458.abe3bbba.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dmitry.adamushko@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmh3093@gmail.com \
    --cc=vegard.nossum@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.