> > Also, I got panics when unmounting reiser4 filesystems with > > 2.6.20-rc1-mm1 but I guess this is related to your waring about > > reiser4 being broken in 2.6.19-mm1 (even if it is not listed in > > notes for 2.6.20-rc1-mm1)... I attach dmesg and config, but the > > reiser4 panics did not get logged and I am not able to reboot on > > 2.6.20-rc1-mm1 right now. For the moment, I mainly wanted to report > > the xfs messages which seems a bit suspect.
> The reiser4 failure is unexpected. Could you please see if you can > capture a trace, let the people at [EMAIL PROTECTED] know? Ok, I've handwritten the messages, here they are : reiser4 panicked cowardly : reiser4[umount(2451)] : commit_current_atom (fs/reiser4/txmngr.c:1087) (zam-597) write log failed (-5) [ got 2 copies of them because I have 2 reiser4 fs) I got them mainly when I try to reboot or halt the machine, and the process doesn't finish, the computer gets stuck after the reiser4 messages. This is only with 2.6.20-mm1, not 2.6.19-rc6-mm2. -- Damien Wyart - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
