This bug has happened again. This is only the second time, and I'm really not sure how to replicate it. However there does appear to be a deadlock (or a crash with a lock held) happening.
This trace has a couple of threads that are a little past queue_log_writer:
One has a frame like "[<ffffffffa0384eec>] ? open_xa_root+0x8c/0xf0 [reiserfs]" after queue_log_writer.
Another has a frame "[<ffffffff81195486>] ? mark_buffer_dirty+0x66/0xa0".
The first program that froze (that I noticed) was emacs (3308).
This bug has happened again. This is only the second time, and I'm really not sure how to replicate it. However there does appear to be a deadlock (or a crash with a lock held) happening.
This trace has a couple of threads that are a little past queue_log_writer:
One has a frame like "[<ffffffffa038 4eec>] ? open_xa_ root+0x8c/ 0xf0 [reiserfs]" after queue_log_writer. 5486>] ? mark_buffer_ dirty+0x66/ 0xa0".
Another has a frame "[<ffffffff8119
The first program that froze (that I noticed) was emacs (3308).