Re: powerpc -next rebase WARNING

2012-05-21 Thread Benjamin Herrenschmidt
On Tue, 2012-05-22 at 11:51 +1000, Benjamin Herrenschmidt wrote: > Folks, bad news ... my fault. > > I accidentally forgot a --signoff on a git am command last week, meaning > that a pair of patches are in -next and not signed off by me. > > For various (legal) reasons that cannot go into Linus t

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Stephen Rothwell
On Tue, 22 May 2012 13:03:54 +1000 Stephen Rothwell wrote: > > On Mon, 21 May 2012 18:53:37 -0700 (PDT) David Rientjes > wrote: > > > > Yeah, it's sched/numa since that's what introduced numa_init(). It does > > for_each_node() for each node and does a kmalloc_node() even though that > > nod

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Michael Neuling
lub won't pass nid < 0. You're sure my patch is applied? :) I did have your patch applied but at "b4cdf91 sched/numa: Implement numa balancer" (where git bisect spotted the fail). If I apply your patch on the full next-20120521 it does fix the problem. Sorry for the confu

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Stephen Rothwell
Hi David, On Mon, 21 May 2012 18:53:37 -0700 (PDT) David Rientjes wrote: > > Yeah, it's sched/numa since that's what introduced numa_init(). It does > for_each_node() for each node and does a kmalloc_node() even though that > node may not be online. Slub ends up passing this node to the page

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread David Rientjes
On Tue, 22 May 2012, Michael Neuling wrote: > Sorry, got it... CONFIG_DEBUG_VM enabled below... > > pid_max: default: 32768 minimum: 301 > Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes) > Inode-cache hash table entries: 131072 (order: 4, 1048576 bytes) > Mount-cache hash table

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Michael Neuling
David Rientjes wrote: > On Tue, 22 May 2012, Michael Neuling wrote: > > > > > > Trying David's patch just posted doesn't fix it. > > > > > > > > > > > > > Hmm, what does CONFIG_DEBUG_VM say? > > > > > > No set. > > > > Sorry, should have read "Not set" > > > > I mean if it's set, what does

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread David Rientjes
On Tue, 22 May 2012, Michael Neuling wrote: > > > > Trying David's patch just posted doesn't fix it. > > > > > > > > > > Hmm, what does CONFIG_DEBUG_VM say? > > > > No set. > > Sorry, should have read "Not set" > I mean if it's set, what does it emit to the kernel log with my patch applied?

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Michael Neuling
Michael Neuling wrote: > > > Trying David's patch just posted doesn't fix it. > > > > > > > Hmm, what does CONFIG_DEBUG_VM say? > > No set. Sorry, should have read "Not set" mikey ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Michael Neuling
> > Trying David's patch just posted doesn't fix it. > > > > Hmm, what does CONFIG_DEBUG_VM say? No set. Mikey ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread David Rientjes
On Tue, 22 May 2012, Michael Neuling wrote: > console [tty0] enabled > console [hvc0] enabled > pid_max: default: 32768 minimum: 301 > Dentry cache hash table entries: 262144 (order: 5, 2097152 bytes) > Inode-cache hash table entries: 131072 (order: 4, 1048576 bytes) > Mount-cache hash table entri

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Michael Neuling
> Hi all, > > Last nights boot tests on various PowerPC systems failed like this: > > calling .numa_group_init+0x0/0x3c @ 1 > initcall .numa_group_init+0x0/0x3c returned 0 after 0 usecs > calling .numa_init+0x0/0x1dc @ 1 > Unable to handle kernel paging request for data at address 0x1688 >

Re: linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread David Rientjes
On Tue, 22 May 2012, Stephen Rothwell wrote: > Unable to handle kernel paging request for data at address 0x1688 > Faulting instruction address: 0xc016e154 > Oops: Kernel access of bad area, sig: 11 [#1] > SMP NR_CPUS=32 NUMA pSeries > Modules linked in: > NIP: c016e154 LR: c00

powerpc -next rebase WARNING

2012-05-21 Thread Benjamin Herrenschmidt
Folks, bad news ... my fault. I accidentally forgot a --signoff on a git am command last week, meaning that a pair of patches are in -next and not signed off by me. For various (legal) reasons that cannot go into Linus tree as-is, so I have to rebase the tree to fix it. Sorry about that ... Che

linux-next: PowerPC boot failures in next-20120521

2012-05-21 Thread Stephen Rothwell
Hi all, Last nights boot tests on various PowerPC systems failed like this: calling .numa_group_init+0x0/0x3c @ 1 initcall .numa_group_init+0x0/0x3c returned 0 after 0 usecs calling .numa_init+0x0/0x1dc @ 1 Unable to handle kernel paging request for data at address 0x1688 Faulting instructi

Re: Build regressions/improvements in v3.4

2012-05-21 Thread Geert Uytterhoeven
On Mon, May 21, 2012 at 9:51 PM, Geert Uytterhoeven wrote: > JFYI, when comparing v3.4 to v3.4-rc7[3], the summaries are: >  - build errors: +5/-14 + error: via-pmu-event.c: undefined reference to `.input_allocate_device': => .init.text+0x8aa4) + error: via-pmu-event.c: undefined reference t

Re: [PATCH v2] usb: fsl_udc: errata - postpone freeing current dTD

2012-05-21 Thread Felipe Balbi
Hi, On Mon, May 21, 2012 at 08:57:22AM +0200, Christoph Fritz wrote: > USB controller may access a wrong address for the dTD (endpoint transfer > descriptor) and then hang. This happens a lot when doing tests with > g_ether module and iperf, a tool for measuring maximum TCP and UDP > bandwidth. >

Re: [patch] hvc_xen: NULL dereference on allocation failure

2012-05-21 Thread Konrad Rzeszutek Wilk
On Tue, May 15, 2012 at 11:20:23AM +0100, Stefano Stabellini wrote: > On Tue, 15 May 2012, Dan Carpenter wrote: > > If kzalloc() returns a NULL here, we pass a NULL to > > xencons_disconnect_backend() which will cause an Oops. > > > > Also I removed the __GFP_ZERO while I was at it since kzalloc()

RE: [PATCH v2] usb: fsl_udc: errata - postpone freeing current dTD

2012-05-21 Thread Chen Peter-B29397
> > USB controller may access a wrong address for the dTD (endpoint transfer > descriptor) and then hang. This happens a lot when doing tests with > g_ether module and iperf, a tool for measuring maximum TCP and UDP > bandwidth. > > This hardware bug is explained in detail by errata number 2858