From: Jeremy Fitzhardinge <jeremy@goop.org>
To: paulmck@linux.vnet.ibm.com
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Seeing "huh, entered softirq 8 ffffffff802682aa preempt_count 00000100, exited with 00010100?" in tip.git
Date: Thu, 29 Jan 2009 17:44:43 -0800 [thread overview]
Message-ID: <49825B8B.2000202@goop.org> (raw)
In-Reply-To: <20090130005953.GD6716@linux.vnet.ibm.com>
Paul E. McKenney wrote:
> On Thu, Jan 29, 2009 at 02:12:31PM -0800, Jeremy Fitzhardinge wrote:
>
>> When I boot my x86-64 tip.git kernel under Xen, I'm seeing:
>>
>> pnp: PnP ACPI: disabled
>> NET: Registered protocol family 2
>> huh, entered softirq 8 ffffffff802682aa preempt_count 00000100, exited with
>> 00010100?
>> IP route cache hash table entries: 512 (order: 0, 4096 bytes)
>> TCP established hash table entries: 1024 (order: 2, 16384 bytes)
>> [...]
>> XENBUS: Device with no driver: device/console/0
>> Freeing unused kernel memory: 372k freed
>> Red Hat nash version 6.0.19 starting
>> Mounting proc filesystem
>> Mounting sysfs filesystem
>> Creating /dev
>> BUG: scheduling while atomic: swapper/0/0x00010000
>> Modules linked in:
>> Pid: 0, comm: swapper Not tainted 2.6.29-rc3-tip #481
>> Call Trace:
>> [<ffffffff80238c1f>] __schedule_bug+0x62/0x66
>> [<ffffffff80211d2d>] ? retint_restore_args+0x5/0x20
>> [<ffffffff80503921>] __schedule+0x95/0x792
>> [<ffffffff802093aa>] ? _stext+0x3aa/0x1000
>> [<ffffffff802093aa>] ? _stext+0x3aa/0x1000
>> [<ffffffff805040c2>] schedule+0xe/0x22
>> [<ffffffff8020ff04>] cpu_idle+0x70/0x72
>> [<ffffffff804fc3a0>] cpu_bringup_and_idle+0x13/0x15
>> Creating initial device nodes
>> Setting up hotplug.
>>
>>
>> From what I can see, softirq 8 is the RCU softirq. I don't know if the
>> "scheduling while atomic" is related or not, but its two new schedulerish
>> symptoms appearing at once, so I think its likely they're related.
>>
>
> Hmmm... Mysterious, as you seem to be using classic RCU, which hasn't
> changed in awhile. Which branch of the tip tree are you using?
>
tip/master. It looks like this appeared since -rc1. Mu current
suspicion is the percpu changes, since I'm seeing some other strange
symptoms.
J
next prev parent reply other threads:[~2009-01-30 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:12 Seeing "huh, entered softirq 8 ffffffff802682aa preempt_count 00000100, exited with 00010100?" in tip.git Jeremy Fitzhardinge
2009-01-30 0:59 ` Paul E. McKenney
2009-01-30 1:44 ` Jeremy Fitzhardinge [this message]
2009-01-30 15:08 ` Ingo Molnar
2009-01-30 16:40 ` Jeremy Fitzhardinge
2009-01-30 22:17 ` Ingo Molnar
2009-01-30 22:34 ` Ingo Molnar
2009-01-31 0:48 ` Jeremy Fitzhardinge
2009-01-31 0:49 ` H. Peter Anvin
2009-01-31 0:54 ` Ingo Molnar
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=49825B8B.2000202@goop.org \
--to=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.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