From: Thomas Sattler <sattler@med.uni-frankfurt.de>
To: Borislav Petkov <bp@alien8.de>,
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 07:58:15 +0200 [thread overview]
Message-ID: <4FEBF277.90704@med.uni-frankfurt.de> (raw)
In-Reply-To: <20120627174649.GA28137@x1.osrc.amd.com>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
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.
Thomas
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 15178 bytes --]
next prev parent reply other threads:[~2012-06-28 5:58 UTC|newest]
Thread overview: 10+ 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 17:46 ` Borislav Petkov
2012-06-28 5:58 ` Thomas Sattler [this message]
2012-06-28 6:42 ` Borislav Petkov
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=4FEBF277.90704@med.uni-frankfurt.de \
--to=sattler@med.uni-frankfurt.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox