> Not sure what's going on with the i_sem, are you playing with the loopfile
> somehow during the sync?
No. It's sitting in /var/cache/ext3test, and nothing else touches it.
> Can you also try to find more info about c01efe72
> <stext_lock+ee2/273a> with an objdump -j .text.lock? (should be the
> slow path of down() corresponding to the i_sem down in lo_send)
I guess I'm a bit uneducated, but objdump -j .text.lock vmlinux
doesn't work here, I'm obviously doing something wrong.
> are you sure it's really related to the loop device? (and not a
> ""genuine"" IDE lockup or something like that)
Yes, I'm sure. Without using the loop device, the system works fine,
as far as I can tell, and even with the loop device, 2.4.14 is OK.
--pgp-sign-Multipart_Fri_Dec_21_20:34:33_2001-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
iEYEABECAAYFAjwjjtIACgkQR47eFMOy/N7PawCeNjm7V1HTux4SiYNgNnKfLYtA
S0MAoM4TedXf43K28qG2IXvkSSd71F3s
=vOGu
-----END PGP SIGNATURE-----
--pgp-sign-Multipart_Fri_Dec_21_20:34:33_2001-1--
-
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/