| To: | Ilia Mirkin <imirkin@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS hung on 2.6.33.3 kernel |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Wed, 4 Aug 2010 10:47:46 +1000 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <AANLkTi=EzePfBRdEFQo2BRtKy=464Ci6zPG=UyYJiwNp@xxxxxxxxxxxxxx> |
| References: | <AANLkTilX3l8TbUztLStj_u9OqOZnBrsNQxmeV4DuBmYJ@xxxxxxxxxxxxxx> <20100718012033.GA18888@dastard> <AANLkTikEv75KRyRTs4awmG894NSKMnBkJNJPYsypMdWf@xxxxxxxxxxxxxx> <20100718235036.GC32635@dastard> <AANLkTi=EzePfBRdEFQo2BRtKy=464Ci6zPG=UyYJiwNp@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
Ilia, Can you send me the output of this for your kernel that the traces came from: $ gdb <path/to/vmlinux> (gdb) l *( xfs_write+0x2cc) You can run it against the vmlinux file in the kernel build directory. Basically I need to know which xfs_ilock() call in xfs_write() one of the mysqld-test processes is stuck on. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] dio: track and serialise unaligned direct IO, Mingming Cao |
|---|---|
| Next by Date: | Re: XFS hung on 2.6.33.3 kernel, Ilia Mirkin |
| Previous by Thread: | Re: XFS hung on 2.6.33.3 kernel, Ilia Mirkin |
| Next by Thread: | Re: XFS hung on 2.6.33.3 kernel, Ilia Mirkin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |