2.6.11: spinlock problem

Hi,

I'm seeing a spinlock held panic with a kernel stack like this:

spinlock - panic, lock already held
..
__do_softirq
do_softirq
=========
do_IRQ
common_interrupt
spinlock/spinunlock
..

when I load up the system in testing.
The code protected by the spinlock is quite small - counter increment.

I'm using 2.6.11-1.1369_FC4 #1, installed inside of vmware,
running as a guest on a Windows XP box.

Is this
(a) linux allowing the IRQ too early
(b) vmware not doing something right
(c) enivitable
(d) somehow my fault
(e) something else?

Thanks,
Darren
-
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/

Follow-Ups:
- Re: 2.6.11: spinlock problem
  - From: "Hareesh Nagarajan" <[email protected]>
- Re: 2.6.11: spinlock problem
  - From: "linux-os \(Dick Johnson\)" <[email protected]>

Prev by Date: [PATCH] sched.h: increment TASK_COMM_LEN to 20 bytes
Next by Date: [GIT PATCH] Geode patches for 2.6.17
Previous by thread: [PATCH] sched.h: increment TASK_COMM_LEN to 20 bytes
Next by thread: Re: 2.6.11: spinlock problem
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]