From: Tejun Heo <tj@kernel.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: general protection fault: 0000 [#1] PREEMPT SMP
Date: Tue, 24 Aug 2010 10:58:02 +0200 [thread overview]
Message-ID: <4C73899A.304@kernel.org> (raw)
In-Reply-To: <20100813134756.GA5235@swordfish.minsk.epam.com>
Hello,
On 08/13/2010 03:47 PM, Sergey Senozhatsky wrote:
> [ 29.943019] [<ffffffff81065893>] lock_acquire+0x97/0xb6
..
> [ 29.943257] [<ffffffff8137568d>] _raw_spin_lock_irqsave+0x4e/0x60
..
> [ 29.943376] [<ffffffff8137145b>] percpu_counter_hotcpu_callback+0x3e/0x93
It's getting gpf at spin_lock_irqsave(&fbc->lock) in
percpu_counter_hotplug_callback(). percpu_counter keeps track of all
the allocated percpu counters and walk them on cpu up/down events.
It's most likely one of its users freed or corrupted the percpu
counter structure without properly destroying it. Adding debugobj is
probably the best way to track down the offending user.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-24 9:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 13:47 general protection fault: 0000 [#1] PREEMPT SMP Sergey Senozhatsky
2010-08-24 8:58 ` Tejun Heo [this message]
2010-08-24 9:15 ` Sergey Senozhatsky
2010-08-24 10:12 ` percpu_counter: add debugobj support Tejun Heo
2010-08-24 10:13 ` [PATCH REPOST 2.6.36-rc2] " Tejun Heo
2010-08-24 13:26 ` Thomas Gleixner
2010-08-24 9:08 ` general protection fault: 0000 [#1] PREEMPT SMP Yong Zhang
2010-08-24 9:17 ` Sergey Senozhatsky
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=4C73899A.304@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sergey.senozhatsky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox