All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Thomas Sattler <sattler@med.uni-frankfurt.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: BUG: scheduling while atomic: chcpu/6197/0x00000002
Date: Thu, 28 Jun 2012 08:42:13 +0200	[thread overview]
Message-ID: <20120628064213.GC450@x1.osrc.amd.com> (raw)
In-Reply-To: <4FEBF277.90704@med.uni-frankfurt.de>

On Thu, Jun 28, 2012 at 07:58:15AM +0200, Thomas Sattler wrote:
> Am 27.06.2012 19:46, schrieb Borislav Petkov:
> > On Wed, Jun 27, 2012 at 01:41:25PM +0200, Thomas Sattler wrote:
> >> Linux dragon 3.4.4-rt13 #2 SMP PREEMPT Tue Jun 26 12:22:23 CEST 2012
> >> i686 Intel(R) Core(TM)2 CPU 6300 @ 1.86GHz GenuineIntel GNU/Linux
> >>
> >> still BUG message in dmesg:
> >>
> >> [  105.585086] BUG: scheduling while atomic: chcpu/2817/0x00000002
> >> [  105.585090] Modules linked in: loop rfcomm bnep btusb hid_microsoft
> >> usbhid hid uhci_hcd ehci_hcd 3c59x usbcore e1000e mii usb_common sg
> >> [  105.585109] Pid: 2817, comm: chcpu Not tainted 3.4.4-rt13 #2
> >> [  105.585111] Call Trace:
> >> [  105.585119]  [<c103df4d>] __schedule_bug+0x3d/0x42
> >> [  105.585124]  [<c1355474>] __schedule+0x68/0x571
> >> [  105.585130]  [<c1045840>] ? enqueue_entity+0x313/0x3d8
> >> [  105.585134]  [<c1355a22>] schedule+0x60/0x70
> >> [  105.585138]  [<c1354a42>] schedule_timeout+0x17/0x160
> >> [  105.585142]  [<c103ed57>] ? check_preempt_curr+0x29/0x64
> >> [  105.585146]  [<c135532d>] wait_for_common+0xa3/0xff
> >> [  105.585150]  [<c10412e2>] ? try_to_wake_up+0x391/0x391
> >> [  105.585154]  [<c135540a>] wait_for_completion+0x12/0x14
> >> [  105.585158]  [<c103781c>] kthread_create_on_node+0x71/0xb5
> >> [  105.585162]  [<c102542c>] ? put_online_cpus+0x44/0x44
> >> [  105.585167]  [<c1350101>] ? init_amd+0x42f/0x64f
> > 				 ^^^^^^^^
> > 
> > AFAICT, this shouldn't run on Intel hw. Can you send your .config.
> 
> /proc/config.gz is attached. Please note, that it's an -rt kernel.

I know.

But I don't see anything that sticks out in your .config.

So the stack trace, since it shows that the init_amd address is
unreliable, could be red herring...

Any chance you could try a non-rt kernel, possibly latest linus from
git.kernel.org to rule out an -rt issue?

Also, looks like your cpu can do 64-bit. Can you try a 64-bit kernel?

Also, what is the exact command line you're running with chcpu?

Thanks.

-- 
Regards/Gruss,
Boris.

  reply	other threads:[~2012-06-28  6:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 10:19 BUG: scheduling while atomic: chcpu/6197/0x00000002 Thomas Sattler
2012-06-18 12:33 ` Thomas Sattler
2012-06-20  9:15   ` Thomas Sattler
2012-06-25 12:58     ` Thomas Sattler
2012-06-27 11:41       ` Thomas Sattler
2012-06-27 12:26         ` Fwd: " 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
2012-06-27 17:46         ` Borislav Petkov
2012-06-28  5:58           ` Thomas Sattler
2012-06-28  6:42             ` Borislav Petkov [this message]
2012-06-28  9:24               ` Thomas Sattler
2012-06-28 10:21                 ` Borislav Petkov

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=20120628064213.GC450@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sattler@med.uni-frankfurt.de \
    --cc=tglx@linutronix.de \
    /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.