On Wed, Feb 05, 2003 at 11:41:39PM -0800, Andrew Morton wrote:
> At a guess, I'd say that a disk device driver has dropped an interrupt and
> I/O completion has not happened.
>
> Check your kernel log and dmesg output for anything untoward, and then try
> invoking sysrq-P and sysrq-T to find out where everythihg is stuck.
Unrelated to this problem, but it reminded me...
I've not heard any compelling arguments saying that these[1] patches
are wrong.
Dave
[1] http://www.uwsg.iu.edu/hypermail/linux/kernel/0301.1/2217.html
-- | Dave Jones. http://www.codemonkey.org.uk | SuSE Labs - 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/
This archive was generated by hypermail 2b29 : Fri Feb 07 2003 - 22:00:20 EST