Messages in this thread | | | Date | Thu, 7 Sep 2006 17:39:51 +0200 | From | Mattia Dongili <> | Subject | Re: JFS - real deadlock and lockdep warning (2.6.18-rc5-mm1) |
| |
On Wed, Sep 06, 2006 at 05:00:28PM -0500, Dave Kleikamp wrote: [...] > > I suspect JFS is guilty, anyway my HD has these partitions: > > I haven't got around to instrumenting jfs properly with > mutex_lock_nested(), so I know jfs doesn't run clean with lockdep > enabled. What that means is that these warnings don't necessarily point > to a real problem, and on the other hand, lockdep hasn't been run > correctly against jfs to prove that the mutex usage is safe. > > That said, I'm not aware of any known problems in jfs resulting in a > deadlock. Unfortunately, without being able to use sysrq, I don't have > any real good ideas for you off the top of my head to further track down > the problem.
yup... don't know if it could put some light but simply doing
$ mv ~/.firefox ~/.firefox.old $ cp ~/.firefox.old ~/.firefox
in order to allocate different inodes (right?) I can run Firefox with my favourite skin (the one that was causing the hang before).
> I'm pretty busy this week, but I'll try to get the lockdep stuff right > in jfs as soon as possible. Who knows? Maybe it will find a real > locking problem.
I'll try to keep the filesystem as is to be able to test any fix/test you'll propose (Eclipse still hangs the computer). Fortunately I have one more spare partition where I can move /home.
Thanks -- mattia :wq! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |