* FW: BUG in spinlock.h:133
@ 2002-03-04 11:50 Alexander Sandler
2002-03-04 18:43 ` Robert Love
0 siblings, 1 reply; 3+ messages in thread
From: Alexander Sandler @ 2002-03-04 11:50 UTC (permalink / raw)
To: Linux Kernel Mailing List (E-mail)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="x-user-defined", Size: 247 bytes --]
Hi.
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.
Alexandr Sandler.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: FW: BUG in spinlock.h:133
2002-03-04 11:50 FW: BUG in spinlock.h:133 Alexander Sandler
@ 2002-03-04 18:43 ` Robert Love
0 siblings, 0 replies; 3+ messages in thread
From: Robert Love @ 2002-03-04 18:43 UTC (permalink / raw)
To: Alexander Sandler; +Cc: Linux Kernel Mailing List (E-mail)
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: FW: BUG in spinlock.h:133
@ 2002-03-05 12:15 Alexander Sandler
0 siblings, 0 replies; 3+ messages in thread
From: Alexander Sandler @ 2002-03-05 12:15 UTC (permalink / raw)
To: Robert Love; +Cc: Linux Kernel "Mailing List (E-mail)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="x-user-defined", Size: 794 bytes --]
Hi.
I found it. It was an uninitialized semahore.
10x for help.
Alexandr Sandler.
> 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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-03-05 12:16 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-03-04 11:50 FW: BUG in spinlock.h:133 Alexander Sandler
2002-03-04 18:43 ` Robert Love
2002-03-05 12:15 Alexander Sandler
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®