From: Robert Love <rml@tech9.net>
To: Alexander Sandler <ASandler@store-age.com>
Cc: Linux Kernel "Mailing List (E-mail)" <linux-kernel@vger.kernel.org>
Subject: Re: FW: BUG in spinlock.h:133
Date: 04 Mar 2002 13:43:51 -0500 [thread overview]
Message-ID: <1015267432.15479.11.camel@phantasy> (raw)
In-Reply-To: <DCC3761A6EC31643A3BAF8BB584B26CC0AAE8A@exchange.store-age.com>
In-Reply-To: <DCC3761A6EC31643A3BAF8BB584B26CC0AAE8A@exchange.store-age.com>
On Mon, 2002-03-04 at 06:50, Alexander Sandler wrote:
> I am getting a BUG in include/asm-i386/spinlock.h:133 when I am doing some
> I/O with driver I am working on. Does anyone has any idea what it can be?
> The system is Linux RedHat 7.1 on dual CPU machine running kernel 2.4.16.
That BUG means lock->magic was not set properly, which is a debug-only
parameter to make sure the lock was properly initialized.
Thus, either you are not properly initializing your spin_locks or there
is a memory corruption problem.
The EIP at the time of the BUG should of been reported - what was it?
Find it in your System.map to see where the problem is ...
Robert Love
next prev parent reply other threads:[~2002-03-04 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 11:50 Alexander Sandler
2002-03-04 18:43 ` Robert Love [this message]
2002-03-05 12:15 Alexander Sandler
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=1015267432.15479.11.camel@phantasy \
--to=rml@tech9.net \
--cc=ASandler@store-age.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
all inboxes | Powered by JetHome®