Re: Oops in ring_buffer_alloc_read_page()
From: Andi Kleen
Date: Sun Jun 23 2013 - 14:06:32 EST
> Good question! I tried disabling CPA self-test and the BUG does not
> show up for 10000 boots. So this should be the root cause.
The test is very different now than what I wrote originally, but I would
generally expect any bug to be in change_page_attr(), not be in the
> > > [ 36.776024] *pde = 0e3e1067 *pte = 061e7260
The oops is in a 2MB page that should not have changed by CPA
in theory (it just adds 4KB pages)
I suppose you could log the addresses touched by the test and compare
to the oops addresses.
Most likely the reason you don't see it all the time is that the
test is randomized. So you could make it more stable by fixing
the seed in pageattr-test and perhaps changing it to use more
> > > [ 36.776024] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
Could be also some virtualization problem?
ak@xxxxxxxxxxxxxxx -- Speaking for myself only
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/