> > On 01/25/2012 10:18 PM, Paul Walmsley wrote: > > - If your oopses are consistently in the same places, add some debugging > > to that code to determine which line is actually causing the oops. > > (CC:d linux-mtd.) > > They are semi-consistent I'd say. The oops trace I posted is by far the > most common. > > > problem to mysteriously disappear. Doing this analysis should provide a > > good clue as to where to look next. I personally would be rather > > suspicious of that > > > > ri->data_crc = cpu_to_je32(crc32(0, comprbuf, cdatalen)); > > > > in jffs2_write_inode_range(). > > That is indeed the place where crc32 is called from . I'll see it I can > track the use of comprbuf. > > > - Try turning on JFFS2 debugging and seeing if you can reproduce it. > > The output might provide a clue as to where the problem would be. > I would also turn off SUMMARY in JFFS2, I tried it long ago and it didn't make much of a difference. Jocke -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
