I got some new information: Before soft lockup message is out, we have: [EMAIL PROTECTED] home]# cat /proc/slabinfo |grep buffer_head buffer_head 10927942 10942560 120 32 1 : tunables 32 16 8 : slabdata 341955 341955 6 : globalstat 37602996 11589379 1174373 6 0 1 6918 12166031 1013708 : cpustat 35254590 2350698 13610965 907286
Then after buffer_head is freed, we have: [EMAIL PROTECTED] home]# cat /proc/slabinfo |grep buffer_head buffer_head 9542 36384 120 32 1 : tunables 32 16 8 : slabdata 1137 1137 245 : globalstat 37602996 11589379 1174373 6 0 1 6983 20507478 1708818 : cpustat 35254625 2350704 16027174 1068367 Does this huge number of buffer_head cause the soft lockup? Thanks, Forrest On 4/11/07, Pekka Enberg <[EMAIL PROTECTED]> wrote:
On 4/11/07, Zhao Forrest <[EMAIL PROTECTED]> wrote: > We're using RHEL5 with kernel version 2.6.18-8.el5. > When doing a stress test on raw device for about 3-4 hours, we found > the soft lockup message in dmesg. > I know we're not reporting the bug on the latest kernel, but does any > expert know if this is the known issue in old kernel? Or why > kmem_cache_free occupy CPU for more than 10 seconds? Sounds like slab corruption. CONFIG_DEBUG_SLAB should tell you more.
- 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/
