Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)

On Mon, Jun 19, 2006 at 11:39:47PM -0700, Andrew Morton wrote:

 > fc4?  You seem to have an RH-FCx which doesn't enable
 > CONFIG_DEBUG_SPINLOCK.  Or maybe we didn't have all that debug code in
 > 2.6.16.  Doesn't matter, really.

>From the uname, it looks like a recompiled Fedora kernel
(probably with that option turned off).

 > > Pid: 4239, comm: mpi_multibw Not tainted 2.6.16-1.2096_FC4.rootsmp #1

We helpfully appended the whoami output to it at buildtime.

		Dave

-- 
http://www.codemonkey.org.uk
-
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:
  • Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
    • From: Dave Olson <[email protected]>
  • Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
    • From: Andrew Morton <[email protected]>

• Prev by Date: E1000 zero copy
• Next by Date: Re: [patch 8/8] lock validator: add s390 to supported options
• Previous by thread: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
• Next by thread: Re: [patch] increase spinlock-debug looping timeouts (write_lock and NMI)
• 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]