On Wed, Aug 04, 2010 at 11:40:02AM -0400, Ilia Mirkin wrote: > On Wed, Aug 4, 2010 at 2:53 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > > On Wed, Aug 04, 2010 at 12:39:08AM -0400, Ilia Mirkin wrote: > >> On Wed, Aug 4, 2010 at 12:27 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > >> > On Tue, Aug 03, 2010 at 09:15:53PM -0400, Ilia Mirkin wrote: > >> >> On Tue, Aug 3, 2010 at 8:47 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: > >> >> > 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. .... > > OK, that doesn't help - it followed into the inline function > > rather than telling me which of the two calls in the function it > > was. I guess I'll need the disassembly output to work it out. > > Can you send the output of "disass xfs_ilock" instead? Thanks. > > Looks like it's the first one. Yup, that's what it looks like to me, too. That means it's the XFS_IOLOCK_EXCL it is blocking trying to get, not the XFS_ILOCK_EXCL. Well, that makes sense, and tells me that the lockdep "held locks" output at the end also includes locks we are trying to obtain. That clears up that confusion. Ok, I'll work from there. Thanks, Ilia. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
