On Mon, Jun 16, 2008 at 07:54:08PM +0200, Jan Kara wrote: > > On Thu, 12 Jun 2008, Holger Kiehl wrote: > > > > >On Thu, 12 Jun 2008, Aneesh Kumar K.V wrote: > > > > > >>On Thu, Jun 12, 2008 at 02:07:30PM +0000, Holger Kiehl wrote: > > >>>This time there is no OOPS and system is still up running without any > > >>>problem (except any process wanting to write something to this filesystem > > >>>gets stuck forever). > > >>> > > >>>What can I do to help find the problem? The system is still up with all > > >>>those > > >>>process hanging in D-state. > > >>> > > >> > > >>if you can login to the system get the dmesg output after > > >> > > >>echo t > /proc/sysrq-trigger > > >> > > >Unfortunately I have not set CONFIG_MAGIC_SYSRQ. Tomorrow I will try to > > >reproduce this with a kernel that has CONFIG_MAGIC_SYSRQ set. > > > > > After recompiling, rebooting and run afdbench first I got an OOPS and the > > system hanged up solid. The only thing I was able to catch is this: > > > > RIP [<ffffffff803019f9>] jbd2_journal_release_jbd_inode+0xcb/0x100 > > RSP <ffff8101fe259c18> > > > > This was copied by hand. And this I cut 'cut and past' from my terminal: > > > > kernel: Code: c3 e8 31 ce f3 ff 41 fe 04 24 e8 fe 3f 16 00 4c 89 fe 48 89 > > df e8 5f cd f3 ff eb 82 48 83 7d 00 00 74 27 48 8b 55 10 48 8b 45 18 <48> > > 89 42 08 48 89 10 48 c7 45 18 00 02 20 00 48 c7 45 10 00 01 > Aneesh found cause of this oops I think... Aneesh, would you send the > fix to Holger? Thanks. > That fix was mainly done with the help of Holger. Many thanks to him for doing multiple test during weekend with different combination. He had already confirmed that the fix worked for me. There is another issue that he is hitting when running the test with mke2fs -m 0. But I think that is not related to lock inversion. -aneesh -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
