RE: 2.6.17-1.2145_FC5 mmap-related soft lockup

> 
> Are you able to confirm that setting CONFIG_DEBUG_SPINLOCK=n fixes it?
> 
> And are you able to get us a copy of that test app?

Yes, I just ran the test with 2.6.17.6.  With CONFIG_DEBUG_SPINLOCK=y
the test fails and the soft lockup situation often results.
However, when built with CONFIG_DEBUG_SPINLOCK=n, the test passes,
and runs rather quickly in comparison to when it fails.

I've attached a slightly updated version of the test case.
It is a little more carefully crafted and prints some
output so that you have some idea that it is working.

Attachment: mmap_soft_lockup_x86_64.c
Description: Binary data

---

• Follow-Ups:
  • Re: 2.6.17-1.2145_FC5 mmap-related soft lockup
    • From: Andrew Morton <[email protected]>

• References:
  • Re: 2.6.17-1.2145_FC5 mmap-related soft lockup
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [PATCH] sound: Conversions from kmalloc+memset to k(z|c)alloc.
• Next by Date: Re: [PATCH] drivers: Conversions from kmalloc+memset to k(z|c)alloc.
• Previous by thread: Re: 2.6.17-1.2145_FC5 mmap-related soft lockup
• Next by thread: Re: 2.6.17-1.2145_FC5 mmap-related soft lockup
• 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]