http://bugzilla.kernel.org/show_bug.cgi?id=14256 --- Comment #45 from carlos.velasco@xxxxxxxxxxxxxxxx 2010-01-28 17:19:13 --- Sorry about delay, I made further tests. I think the patch is good and this is another problem. The oops happened during TEST of the eglibc. This has been solved by the patch. This second issue is related to the INSTALL of the eglibc. After "make install" and reboot I always see an umount busy message for /. This busy message was not seen before because we stepped into the oops umounting /tmp, before umounting /. I tried downgrading to linux kernel 2.6.28 but I couldn't, I receive an NMI interrupt and system hang before testing with this kernel. So I have issued a "ps -ef" and a lsof just before the umount all. Looking output of ps, there are no user processes apart of these: root 30920 1 0 17:50 ttyS1 00:00:00 init [6] root 30921 30920 0 17:50 ttyS1 00:00:00 /bin/bash /etc/rc.d/init.d/rc 6 root 31085 30921 0 17:50 ttyS1 00:00:00 /bin/bash /etc/rc.d/rc6.d/S70mou Umount command is: "umount -a -d -r >/dev/null" I ONLY see this error when installing eglibc. Rebooting the system without installing eglibc is successful without errors. Looking into LSOF, I have been looking into differences between a "good reboot" and a "bad reboot - umount busy". I can only see that in the "bad reboot" the SIZE/OFF columns are empty for the new installed eglibc files. Bad: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME init 1 root DEL REG 253,1 887056 /lib64/libc-2.10.1.so init 1 root DEL REG 253,1 887055 /lib64/ld-2.10.1.so Good: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME init 1 root mem REG 253,1 1752309 887013 /lib64/libc-2.10.1.so init 1 root mem REG 253,1 149463 887007 /lib64/ld-2.10.1.so Not sure how to proceed from here. Not sure if this is an ext3 issue also... -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- 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
