> I was suspecting that the write() to the ramdisk device was hanging
> (which you could confirm by printk'ing an 'i' before and an 'o' after
> the write call in flush_window() in init/do_mounts.c or
> drivers/block/rd.c. If you end up with 'i' as the last character, its
> the write that hangs, if its an 'o' then its gunzip itself.)
last character is an "o". After that, "inflate_stored" was called ...
meaning the kernel doesn't think the data is compressed anymore. Looks
like somewhere the code can't handle this big chunk of data (8MB), whereas
the 6MB was ok.
Jeff
-
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/