Re: 2.6.11: spinlock problem

• To: "Darren Reed" <[email protected]>
• Subject: Re: 2.6.11: spinlock problem
• From: "Hareesh Nagarajan" <[email protected]>
• Date: Fri, 23 Jun 2006 12:19:13 -0700
• Cc: [email protected]
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ecg4G4SJbakLrTu3ucy/CEPZeBCh++vP04sUVREzJ3KkOOWSH5Ow4fdiHRX9pyZ4H2ni38zn2RLo5Q/bu5OgU7279440satHG3RvZibK9+MEsHkByv+EhkOg1LbTWQ4ZPQ7/ge6XnGLPmv4dTPtLAmTUIS5LGnTFKEsypj949cQ=
• In-reply-to: <[email protected]>
• References: <[email protected]>
• Sender: [email protected]

On 6/23/06, Darren Reed <[email protected]> wrote:

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

Turn on spin lock debugging.

--
./hareesh
-
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/

---

• References:
  • 2.6.11: spinlock problem
    • From: Darren Reed <[email protected]>

• Prev by Date: Re: [RFC][PATCH] avoid cpu hot removal if busy take3
• Next by Date: Re: 2.6.17-mm1
• Previous by thread: Re: 2.6.11: spinlock problem
• 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]