Messages in this thread | | | Date | Thu, 2 Oct 2014 03:03:00 -0500 | From | Chuck Ebbert <> | Subject | Re: pipe/page fault oddness. |
| |
On Wed, 01 Oct 2014 23:32:15 -0400 Sasha Levin <sasha.levin@oracle.com> wrote:
> On 10/01/2014 06:28 PM, Chuck Ebbert wrote: > > On Wed, 01 Oct 2014 18:08:30 -0400 > > Sasha Levin <sasha.levin@oracle.com> wrote: > > > >> > On 10/01/2014 04:20 PM, Linus Torvalds wrote: > >>> > > So I'm really sending this patch out in the hope that it will get > >>> > > comments, fixup and possibly even testing by people who actually know > >>> > > the NUMA balancing code. Rik? Anybody? > >> > > >> > Hi Linus, > >> > > >> > I've tried this patch on the same configuration that was triggering > >> > the VM_BUG_ON that Hugh mentioned previously. Surprisingly enough it > >> > ran fine for ~20 minutes before exploding with: > >> > > >> > [ 2781.566206] kernel BUG at mm/huge_memory.c:1293! > > That's: > > BUG_ON(is_huge_zero_page(page)); > > > > Can you change your scripts to show the source code line when > > the error is a BUG_ON()? The machine code disassembly after the > > oops message doesn't really help. > > > > Hum? The source code line is the first line in the trace: > > [ 2781.566206] kernel BUG at mm/huge_memory.c:1293! >
I meant, display the contents of that line so we can see what the BUG_ON() was triggered by. In some cases you might have a custom patch applied or be running a version that some people don't have handy.
| |