From: Robert Hancock <hancockr@shaw.ca>
To: Ian Kirk <intercede619@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG/CRASH help - 2.6.20 (fc5) - spinlock bad magic on CPU#0, kswapd
Date: Mon, 23 Apr 2007 23:02:01 -0600 [thread overview]
Message-ID: <462D8F49.60103@shaw.ca> (raw)
In-Reply-To: <fa.zMzheLQy67ZMGEuuN/3CmN/fQpQ@ifi.uio.no>
Ian Kirk wrote:
> Hi,
>
> I just wondered if the below type of crash was a known thing, and if
> there are any obvious things I can do to prevent/fix it ?
>
> BUG: spinlock bad magic on CPU#0, kswapd0/242 (Not tainted)
> lock: c06c9380, .magic: c06c9380, .owner:
> [<c06eba2a>] _raw_spin_lock+0x1a/0xd9
> [<c061e72f>] _spin_lock_irqsave+0x9/0xd
> [<c041febf>] __wake_up+0x18/0x43
> [<c04379ce>] __wake_up_bit+0x2e/0x33
> [<c045a496>] shrink_inactive_list+0x483/0x6c9
RAM issues are a possibility for this sort of problem, tried running
Memtest86+?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-04-24 5:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.zMzheLQy67ZMGEuuN/3CmN/fQpQ@ifi.uio.no>
2007-04-24 5:02 ` Robert Hancock [this message]
2007-04-22 12:38 BUG/CRASH help - 2.6.20 (fc5) - spinlock bad magic on CPU#0, kswapd Ian Kirk
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=462D8F49.60103@shaw.ca \
--to=hancockr@shaw.ca \
--cc=intercede619@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.