On Fri, Aug 12, 2005 at 12:35:05PM -0500, Phil Dier wrote: > On Fri, 12 Aug 2005 12:07:21 +1000 > Neil Brown <[EMAIL PROTECTED]> wrote: > > You could possibly put something like > > > > struct bio_vec *from; > > int i; > > bio_for_each_segment(from, bio, i) > > BUG_ON(page_zone(from->bv_page)==NULL); > > > > in generic_make_requst in drivers/block/ll_rw_blk.c, just before > > the call to q->make_request_fn. > > This might trigger the bug early enough to see what is happening. > > > I've got tests running with this code in place, by I/O is so slow now > I don't think it's going to oops (or if it does, it'll be a while).. > > Is there any other info I can collect to help track this down?
Well, while we are slowing things down in the name of debugging.. you might try setting the following debug options in your config: CONFIG_DEBUG_PAGEALLOC CONFIG_DEBUG_HIGHMEM CONFIG_DEBUG_SLAB CONFIG_FRAME_POINTER Can anyone think of anything else? According to the website you don't have these on right now. Sonny - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
