Re: linux-2.4.3-ac14 spinlock problem?

2001-05-30 Thread Feng Xian

David,

Actually it happened only once. then I upgrade my kernel to 2.4.5. problem
disappeared. I just hope this maybe a known problem.

Thanks.

Alex


On Wed, 30 May 2001, David Howells wrote:

>
> > I was running something on my Dell dual p3 box (optiplex gx300). my kernel
> > is linux-2.4.3-ac14. I got the following message:
>
> How often did this message occur?
>
> > __rwsem_do_wake(): wait_list unexpectedly empty
> > [4191] c5966f60 = { 0001 })
> > kenel BUG at rwsem.c:99!
> > invalid operand: 
> > CPU:1
> > EIP:0010:[]
> > EFLAGS: 00010282
> > kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
> >
> >
> > I upgrade the kernel to 2.4.5, no such problem any more.
>
> I suspect something else corrupted the rw-semaphore structure, but that's very
> hard to prove unless you catch it in the act. If it happens again with any
> frequency, you might want to try turning on rwsem debugging.
>
> David
>

-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: linux-2.4.3-ac14 spinlock problem?

2001-05-30 Thread David Howells


> I was running something on my Dell dual p3 box (optiplex gx300). my kernel
> is linux-2.4.3-ac14. I got the following message:

How often did this message occur?

> __rwsem_do_wake(): wait_list unexpectedly empty
> [4191] c5966f60 = { 0001 })
> kenel BUG at rwsem.c:99!
> invalid operand: 
> CPU:1
> EIP:0010:[]
> EFLAGS: 00010282
> kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
> 
> 
> I upgrade the kernel to 2.4.5, no such problem any more.

I suspect something else corrupted the rw-semaphore structure, but that's very
hard to prove unless you catch it in the act. If it happens again with any
frequency, you might want to try turning on rwsem debugging.

David
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: linux-2.4.3-ac14 spinlock problem?

2001-05-30 Thread David Howells


 I was running something on my Dell dual p3 box (optiplex gx300). my kernel
 is linux-2.4.3-ac14. I got the following message:

How often did this message occur?

 __rwsem_do_wake(): wait_list unexpectedly empty
 [4191] c5966f60 = { 0001 })
 kenel BUG at rwsem.c:99!
 invalid operand: 
 CPU:1
 EIP:0010:[c0236b99]
 EFLAGS: 00010282
 kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
 
 
 I upgrade the kernel to 2.4.5, no such problem any more.

I suspect something else corrupted the rw-semaphore structure, but that's very
hard to prove unless you catch it in the act. If it happens again with any
frequency, you might want to try turning on rwsem debugging.

David
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



Re: linux-2.4.3-ac14 spinlock problem?

2001-05-30 Thread Feng Xian

David,

Actually it happened only once. then I upgrade my kernel to 2.4.5. problem
disappeared. I just hope this maybe a known problem.

Thanks.

Alex


On Wed, 30 May 2001, David Howells wrote:


  I was running something on my Dell dual p3 box (optiplex gx300). my kernel
  is linux-2.4.3-ac14. I got the following message:

 How often did this message occur?

  __rwsem_do_wake(): wait_list unexpectedly empty
  [4191] c5966f60 = { 0001 })
  kenel BUG at rwsem.c:99!
  invalid operand: 
  CPU:1
  EIP:0010:[c0236b99]
  EFLAGS: 00010282
  kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!
 
 
  I upgrade the kernel to 2.4.5, no such problem any more.

 I suspect something else corrupted the rw-semaphore structure, but that's very
 hard to prove unless you catch it in the act. If it happens again with any
 frequency, you might want to try turning on rwsem debugging.

 David


-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



linux-2.4.3-ac14 spinlock problem?

2001-05-29 Thread Feng Xian


Hi,

I was running something on my Dell dual p3 box (optiplex gx300). my kernel
is linux-2.4.3-ac14. I got the following message:


__rwsem_do_wake(): wait_list unexpectedly empty
[4191] c5966f60 = { 0001 })
kenel BUG at rwsem.c:99!
invalid operand: 
CPU:1
EIP:0010:[]
EFLAGS: 00010282
kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!


I upgrade the kernel to 2.4.5, no such problem any more.

Any idea?

Alex


-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



linux-2.4.3-ac14 spinlock problem?

2001-05-29 Thread Feng Xian


Hi,

I was running something on my Dell dual p3 box (optiplex gx300). my kernel
is linux-2.4.3-ac14. I got the following message:


__rwsem_do_wake(): wait_list unexpectedly empty
[4191] c5966f60 = { 0001 })
kenel BUG at rwsem.c:99!
invalid operand: 
CPU:1
EIP:0010:[c0236b99]
EFLAGS: 00010282
kenel BUG at /usr/src/2.4.3-ac14/include/asm/spinlock.h:104!


I upgrade the kernel to 2.4.5, no such problem any more.

Any idea?

Alex


-- 
Feng Xian
   _o) .~.  (o_
   /\\ /V\  //\
  _\_V// \\ V_/_
 /(   )\
  ^^-^^
   ALEX

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/