From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.14.6 BUG: spinlock cpu recursion on CPU#1, kswapd0/185
Date: Mon, 3 Apr 2006 11:08:11 +0200 [thread overview]
Message-ID: <20060403090811.GA27736@janus> (raw)
Cannot reproduce but the stack trace might be useful:
kernel: BUG: spinlock cpu recursion on CPU#1, kswapd0/185
kernel: lock: cedef1d0, .magic: dead4ead, .owner: lk166/2501, .owner_cpu: 1
kernel: [dump_stack+23/32] dump_stack+0x17/0x20
kernel: [spin_bug+134/144] spin_bug+0x86/0x90
kernel: [_raw_spin_lock+85/128] _raw_spin_lock+0x55/0x80
kernel: [_spin_lock+9/16] _spin_lock+0x9/0x10
kernel: [page_check_address+27/128] page_check_address+0x1b/0x80
kernel: [page_referenced_one+71/208] page_referenced_one+0x47/0xd0
kernel: [page_referenced_file+128/192] page_referenced_file+0x80/0xc0
kernel: [page_referenced+125/144] page_referenced+0x7d/0x90
kernel: [shrink_list+200/1024] shrink_list+0xc8/0x400
kernel: [shrink_cache+262/672] shrink_cache+0x106/0x2a0
kernel: [shrink_zone+197/256] shrink_zone+0xc5/0x100
kernel: [balance_pgdat+598/832] balance_pgdat+0x256/0x340
kernel: [kswapd+220/272] kswapd+0xdc/0x110
kernel: [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
gcc version 3.3.5 (Debian 1:3.3.5-13)
--
Frank
reply other threads:[~2006-04-03 9:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060403090811.GA27736@janus \
--to=frankvm@frankvm.com \
--cc=linux-kernel@vger.kernel.org \
/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