From: "Alexey Zaytsev" <alexey.zaytsev@gmail.com>
To: "Laurent Riffard" <laurent.riffard@free.fr>
Cc: "Kernel development list" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>
Subject: Re: next-20090107: WARNING: at kernel/sched.c:4435 sub_preempt_count
Date: Fri, 9 Jan 2009 13:09:22 +0300 [thread overview]
Message-ID: <f19298770901090209m7076f3afyd1e01e0fc9bbca59@mail.gmail.com> (raw)
In-Reply-To: <4966897E.5020302@free.fr>
One more instance of http://marc.info/?l=linux-kernel&m=123134586202636&w=2
Added Ingo Molnar to CC.
On Fri, Jan 9, 2009 at 02:17, Laurent Riffard <laurent.riffard@free.fr> wrote:
> hello,
>
> I'm getting this warning in dmesg since 2.6.28-next-20081229:
>
> WARNING: at kernel/sched.c:4435 sub_preempt_count+0x7e/0x8f()
> Hardware name: M68SM-S2L
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.28-next-20090107-09542-gdbcea38 #71
> Call Trace:
> [<c0224f35>] warn_slowpath+0x80/0xb6
> [<c024140d>] lock_acquire+0x76/0x7e
> [<c03be817>] _spin_unlock_irq+0x20/0x51
> [<c0240278>] trace_hardirqs_on_caller+0xf8/0x12e
> [<c03be81f>] _spin_unlock_irq+0x28/0x51
> [<c03be83c>] _spin_unlock_irq+0x45/0x51
> [<c022c865>] run_timer_softirq+0x178/0x180
> [<c022211c>] run_rebalance_domains+0x27/0x8f
> [<c023ef58>] trace_hardirqs_off_caller+0x2c/0x87
> [<c0220788>] sub_preempt_count+0x7e/0x8f
> <IRQ> [<c024ef74>] handle_level_irq+0x0/0x9d
> [<c022950e>] irq_exit+0x43/0x87
> [<c0204d9e>] do_IRQ+0xec/0x102
> [<c02035ec>] common_interrupt+0x2c/0x34
> [<c02168dc>] native_safe_halt+0x2/0x3
> [<c04aadd3>] check_bugs+0x9f/0xd8
> [<c04a47e8>] start_kernel+0x2f9/0x306
> ---[ end trace 4eaa2a86a8e2da22 ]---
>
> In previous releases (2.6.27-next-20081020 to 2.6.28-rc7-next-20081203), I was getting "WARNING: at kernel/sched.c:4354 do_softirq" with more or less the same stack trace:
Rinning -next and not reporting bugs sounds a bit counter-productive. ;(
> Checking 'hlt' instruction... <4>------------[ cut here ]------------
> WARNING: at kernel/sched.c:4332 do_softirq+0x61/0xb3()
> Modules linked in:
> Pid: 0, comm: swapper Not tainted 2.6.28-rc2-next-20081027-02513-g5362c2b #46
> Call Trace:
> [<c02234b8>] warn_on_slowpath+0x40/0x59
> [<c023e07b>] trace_hardirqs_on_caller+0xe3/0x12d
> [<c03b295a>] _spin_unlock_irq+0x3c/0x48
> [<c0220deb>] run_rebalance_domains+0x29/0x96
> [<c022793f>] __do_softirq+0xc5/0xf9
> [<c022787a>] __do_softirq+0x0/0xf9
> <IRQ> [<c024bf72>] handle_level_irq+0x0/0x9f
> [<c02279b6>] irq_exit+0x43/0x8b
> [<c0205eec>] do_IRQ+0xef/0x107
> [<c0204628>] common_interrupt+0x28/0x30
> [<c04cfadf>] check_bugs+0x91/0xbb
> [<c04c782c>] start_kernel+0x308/0x318
> ---[ end trace 4eaa2a86a8e2da22 ]---
> OK.
>
>
> Full dmesg and .config for 2.6.28-next-20090107 are attached (actually this is linux-next tree + reiser4 patches, but I verified that this WARNING does appear without reiser4 patches in 2.6.28-next-20081230).
>
next prev parent reply other threads:[~2009-01-09 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 23:17 Laurent Riffard
2009-01-09 10:09 ` Alexey Zaytsev [this message]
2009-01-11 2:49 ` Ingo Molnar
2009-01-14 2:00 ` Nick Piggin
2009-01-18 18:22 ` Alexey Zaytsev
2009-01-18 18:24 ` Ingo Molnar
2009-01-18 18:24 ` Alexey Zaytsev
2009-01-25 0:33 ` Alexey Zaytsev
2009-01-26 14:43 ` Ingo Molnar
2009-01-26 14:53 ` Alexey Zaytsev
2009-01-26 15:09 ` 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=f19298770901090209m7076f3afyd1e01e0fc9bbca59@mail.gmail.com \
--to=alexey.zaytsev@gmail.com \
--cc=laurent.riffard@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome