Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-07 Thread Tetsuo Handa
Holger Schurig wrote: > So I did an "arm-linux-gnueabihf-objdump -Sgd linux/vmlinux", not sure > if that helps: > > c00972ec <__rmqueue>: > * Do the hard work of removing an element from the buddy allocator. > * Call me with the zone->lock already held. > */ > static struct page

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-07 Thread Tetsuo Handa
Holger Schurig wrote: > So I did an "arm-linux-gnueabihf-objdump -Sgd linux/vmlinux", not sure > if that helps: > > c00972ec <__rmqueue>: > * Do the hard work of removing an element from the buddy allocator. > * Call me with the zone->lock already held. > */ > static struct page

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-07 Thread Holger Schurig
I have rejoiced prematurely, it just now took way longer I hit the segfault. Previously 1m or at max 2m was enough. root@ptxc:~# stress-ng --sock 20 stress-ng: info: [359] dispatching hogs: 0 I/O-Sync, 0 CPU, 0 VM-mmap, 0 HDD-Write, 0 Fork, 0 Context-switch, 0 Pipe, 0 Cache, 20 Socket, 0 Yield,

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-07 Thread Holger Schurig
I have rejoiced prematurely, it just now took way longer I hit the segfault. Previously 1m or at max 2m was enough. root@ptxc:~# stress-ng --sock 20 stress-ng: info: [359] dispatching hogs: 0 I/O-Sync, 0 CPU, 0 VM-mmap, 0 HDD-Write, 0 Fork, 0 Context-switch, 0 Pipe, 0 Cache, 20 Socket, 0 Yield,

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-07 Thread Holger Schurig
I compared my config with imx_v6_v7_defconfig which didn't segfault. After I turned on CONFIG_SWAP, my segfault vanished. I did turn off CONFIG_SWAP because my device only has SD-Card and eMMC. So I never intended to create a swap partition. And thought "why compile it in the kernel when I never

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-07 Thread Holger Schurig
I compared my config with imx_v6_v7_defconfig which didn't segfault. After I turned on CONFIG_SWAP, my segfault vanished. I did turn off CONFIG_SWAP because my device only has SD-Card and eMMC. So I never intended to create a swap partition. And thought "why compile it in the kernel when I never

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-04 Thread Holger Schurig
Tetsui wrote: > This might be a mm problem. Please send to linux...@kvack.org . > > Before doing so, please identify line number using > > $ addr2line -i -e /path/to/vmlinux c0097288 > > etc. if built with CONFIG_DEBUG_INFO=y. > (If CONFIG_DEBUG_INFO=n, please rebuild with CONFIG_DEBUG_INFO=y

Re: 4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-04 Thread Holger Schurig
Tetsui wrote: > This might be a mm problem. Please send to linux...@kvack.org . > > Before doing so, please identify line number using > > $ addr2line -i -e /path/to/vmlinux c0097288 > > etc. if built with CONFIG_DEBUG_INFO=y. > (If CONFIG_DEBUG_INFO=n, please rebuild with CONFIG_DEBUG_INFO=y

4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-03 Thread Holger Schurig
Hi, on my system I can reproduce reliably a kernel OOPS when I run stress-ng ("apt-get install stress-ng"). Any help on how to track this down would be appreciated, networking code is outside of my comfort zone (I'm just a dilettante at device drivers ...). It takes only a minute or two to get

4.4.3: OOPS when running "stress-ng --sock 5"

2016-03-03 Thread Holger Schurig
Hi, on my system I can reproduce reliably a kernel OOPS when I run stress-ng ("apt-get install stress-ng"). Any help on how to track this down would be appreciated, networking code is outside of my comfort zone (I'm just a dilettante at device drivers ...). It takes only a minute or two to get