kmem_alloc deadlock in SLES9 SP3

To:	linux-xfs@xxxxxxxxxxx
Subject:	kmem_alloc deadlock in SLES9 SP3
From:	Heilige Gheist <hgheist@xxxxxxxxx>
Date:	Mon, 8 Jan 2007 04:41:07 -0800 (PST)
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=VLrCwkPST9v1+AfD3UCSbDzdDULB1OtBKId/alYx4gebrPsK4xhbvmUpRlUIUoq8tf6Sizyz0XLKrU7tw8F9bC+vbaUwsCsWwypmOAknlSw2IfeNO6F6R/jBh3RGytim5cu6h9DZ395dwbxt/mCxJmeLIV/XgYL02Gn/cTemOd0=;
Sender:	xfs-bounce@xxxxxxxxxxx

I'm getting occassional system freezes preceded by spurious
kmem_deadlock messages.
The system is running SLES9 SP3, xfs with large (~1GB) fragmented
files, using real-time section.
The message is 
Jan  8 06:27:55 ce-9 kernel: XFS: possible memory allocation deadlock
in kmem_alloc (mode:0x2d0)

ce-9:~ # uname -a
Linux ce-9 2.6.5-7.276-bigsmp #2 SMP Tue Sep 19 05:27:23 IDT 2006 i686
i686 i386 GNU/Linux

The similar bug report http://oss.sgi.com/bugzilla/show_bug.cgi?id=410
recommends upgrading to 2.6.17 to make use of new incore extent
management code.
Is there a version of commercial Linux (RHEL/SLES) that incorporates
this fix? SLES10 is based on 2.6.16 kernel.

--alan

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

<Prev in Thread]	Current Thread	[Next in Thread>
kmem_alloc deadlock in SLES9 SP3, Heilige Gheist <=

Previous by Date:	Re: xfs_file_ioctl / xfs_freeze: BUG: warning at kernel/mutex-debug.c:80/debug_mutex_unlock(), Sami Farin
Next by Date:	Re: BUG: warning at mm/truncate.c:60/cancel_dirty_page(), Sami Farin
Previous by Thread:	xfs_repair: corrupt inode error, Jyrki Muukkonen
Next by Thread:	What's wrong with XFS?, Dave N
Indexes:	[Date] [Thread] [Top] [All Lists]