Re: [next-20150119]regression (mm)?
On Fri, Jan 23, 2015 at 10:37:46PM -0600, Nishanth Menon wrote: On 03:13-20150124, Kirill A. Shutemov wrote: On 09:39-20150123, Tyler Baker wrote: [...] I just reviewed the boot logs for next-20150123 and there still seems to be a related issue. I've been boot testing multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still seem broken. [...] Okay, proof of concept patch is below. It's going to break every other architecture with FIRST_USER_ADDRESS != 0, but I think it's cleaner way to go. Testing on my end: just ran through this set (+ logs similar to Tyler's from my side): next-20150123 (multi_v7_defconfig == !LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2219449 2: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219450 3: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219451 4: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219452 TOTAL = 4 boards, Booted Boards = 4, No Boot boards = 0 next-20150123-LPAE-Logging enabled[1] (multi_v7_defconfig +LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: FAIL: http://paste.ubuntu.org.cn/2220938 2: dra72x-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220943 3: dra7xx-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220947 4: omap5-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220955 TOTAL = 4 boards, Booted Boards = 0, No Boot boards = 4 next-20150123-LPAE-new-patch [2] (multi_v7_defconfig + LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221047 2: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221065 3: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221069 4: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221070 TOTAL = 4 boards, Booted Boards = 4, No Boot boards = 0 next-20150123-new-patch[2] (multi_v7_defconfig == !LPAE) 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221277 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221278 3: am437x-sk: BOOT: FAIL: http://paste.ubuntu.org.cn/2221279 (unrelated) 4:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2221280 5: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2221281 6:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221282 7: BeagleBoard-XM: BOOT: FAIL: http://paste.ubuntu.org.cn/2221283 (unrelated) 8:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221284 9: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2221285 10: beaglebone: BOOT: FAIL: http://paste.ubuntu.org.cn/2221286 (unrelated) 11: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221287 12: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221288 13: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221289 14: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2221290 15: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221291 16:sdp4430: BOOT: PASS: http://paste.ubuntu.org.cn/2221292 TOTAL = 16 boards, Booted Boards = 13, No Boot boards = 3 next-20150123-new-patch[2] (omap2plus_defconfig) 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221653 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221654 3: am437x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221656 4:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2221659 5: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2221660 6:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221661 7: BeagleBoard-XM: BOOT: PASS: http://paste.ubuntu.org.cn/2221670 8:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221676 9: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2221683 10: beaglebone: BOOT: PASS: http://paste.ubuntu.org.cn/2221690 11: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221692 12: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221695 13: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221700 14: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2221704 15: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221707 16:sdp4430: BOOT: PASS: http://paste.ubuntu.org.cn/2221713 TOTAL = 16
Re: [next-20150119]regression (mm)?
On 26 January 2015 at 04:00, Kirill A. Shutemov kir...@shutemov.name wrote: On Fri, Jan 23, 2015 at 10:37:46PM -0600, Nishanth Menon wrote: On 03:13-20150124, Kirill A. Shutemov wrote: On 09:39-20150123, Tyler Baker wrote: [...] I just reviewed the boot logs for next-20150123 and there still seems to be a related issue. I've been boot testing multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still seem broken. [...] Okay, proof of concept patch is below. It's going to break every other architecture with FIRST_USER_ADDRESS != 0, but I think it's cleaner way to go. Testing on my end: just ran through this set (+ logs similar to Tyler's from my side): next-20150123 (multi_v7_defconfig == !LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2219449 2: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219450 3: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219451 4: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219452 TOTAL = 4 boards, Booted Boards = 4, No Boot boards = 0 next-20150123-LPAE-Logging enabled[1] (multi_v7_defconfig +LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: FAIL: http://paste.ubuntu.org.cn/2220938 2: dra72x-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220943 3: dra7xx-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220947 4: omap5-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220955 TOTAL = 4 boards, Booted Boards = 0, No Boot boards = 4 next-20150123-LPAE-new-patch [2] (multi_v7_defconfig + LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221047 2: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221065 3: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221069 4: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221070 TOTAL = 4 boards, Booted Boards = 4, No Boot boards = 0 next-20150123-new-patch[2] (multi_v7_defconfig == !LPAE) 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221277 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221278 3: am437x-sk: BOOT: FAIL: http://paste.ubuntu.org.cn/2221279 (unrelated) 4:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2221280 5: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2221281 6:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221282 7: BeagleBoard-XM: BOOT: FAIL: http://paste.ubuntu.org.cn/2221283 (unrelated) 8:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221284 9: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2221285 10: beaglebone: BOOT: FAIL: http://paste.ubuntu.org.cn/2221286 (unrelated) 11: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221287 12: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221288 13: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221289 14: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2221290 15: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221291 16:sdp4430: BOOT: PASS: http://paste.ubuntu.org.cn/2221292 TOTAL = 16 boards, Booted Boards = 13, No Boot boards = 3 next-20150123-new-patch[2] (omap2plus_defconfig) 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221653 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221654 3: am437x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221656 4:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2221659 5: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2221660 6:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221661 7: BeagleBoard-XM: BOOT: PASS: http://paste.ubuntu.org.cn/2221670 8:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221676 9: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2221683 10: beaglebone: BOOT: PASS: http://paste.ubuntu.org.cn/2221690 11: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221692 12: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221695 13: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221700 14: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2221704 15: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221707 16:
Re: [next-20150119]regression (mm)?
Hi, On 23 January 2015 at 09:27, Nishanth Menon n...@ti.com wrote: On 16:05-20150120, Kirill A. Shutemov wrote: [..] Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com Just to close on this thread: https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks good and back to old status. Thank you folks for all the help. I just reviewed the boot logs for next-20150123 and there still seems to be a related issue. I've been boot testing multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still seem broken. For example here are two boots with exynos5250-arndale, one with multi_v7_defconfig+CONFIG_ARM_LPAE=y [1] and the other with multi_v7_defconfig[2]. You can see the kernel configurations with CONFIG_ARM_LPAE=y show the splat: [ 14.605950] [ cut here ] [ 14.609163] WARNING: CPU: 1 PID: 63 at ../mm/mmap.c:2858 exit_mmap+0x1b8/0x224() [ 14.616548] Modules linked in: [ 14.619553] CPU: 1 PID: 63 Comm: init Not tainted 3.19.0-rc5-next-20150123 #1 [ 14.626713] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree) [ 14.632830] [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [ 14.640473] [] (show_stack) from [] (dump_stack+0x78/0x94) [ 14.647678] [] (dump_stack) from [] (warn_slowpath_common+0x74/0xb0) [ 14.655744] [] (warn_slowpath_common) from [] (warn_slowpath_null+0x1c/0x24) [ 14.664510] [] (warn_slowpath_null) from [] (exit_mmap+0x1b8/0x224) [ 14.672497] [] (exit_mmap) from [] (mmput+0x40/0xf8) [ 14.679180] [] (mmput) from [] (flush_old_exec+0x328/0x604) [ 14.686471] [] (flush_old_exec) from [] (load_elf_binary+0x26c/0x11f4) [ 14.694715] [] (load_elf_binary) from [] (search_binary_handler+0x98/0x244) [ 14.703395] [] (search_binary_handler) from [] (do_execveat_common+0x4dc/0x5bc) [ 14.712421] [] (do_execveat_common) from [] (do_execve+0x28/0x30) [ 14.720235] [] (do_execve) from [] (ret_fast_syscall+0x0/0x34) [ 14.727782] ---[ end trace 5e3ca48b454c7e0a ]--- [ 14.733758] [ cut here ] Has anyone else tested with CONFIG_ARM_LPAE=y that can confirm my findings? -- Regards, Nishanth Menon ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel [1] http://storage.kernelci.org/next/next-20150123/arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y/lab-tbaker/boot-exynos5250-arndale.html [2] http://storage.kernelci.org/next/next-20150123/arm-multi_v7_defconfig/lab-tbaker/boot-exynos5250-arndale.html Cheers, Tyler -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On 16:05-20150120, Kirill A. Shutemov wrote: [..] Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com Just to close on this thread: https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks good and back to old status. Thank you folks for all the help. -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On Fri, Jan 23, 2015 at 12:37:06PM -0600, Nishanth Menon wrote:
On 09:39-20150123, Tyler Baker wrote:
Hi,
On 23 January 2015 at 09:27, Nishanth Menon n...@ti.com wrote:
On 16:05-20150120, Kirill A. Shutemov wrote:
[..]
Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com
Reported-by: Nishanth Menon n...@ti.com
Just to close on this thread:
https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks good
and back to old status. Thank you folks for all the help.
I just reviewed the boot logs for next-20150123 and there still seems
to be a related issue. I've been boot testing
multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still
seem broken.
For example here are two boots with exynos5250-arndale, one with
multi_v7_defconfig+CONFIG_ARM_LPAE=y [1] and the other with
multi_v7_defconfig[2]. You can see the kernel configurations with
CONFIG_ARM_LPAE=y show the splat:
[ 14.605950] [ cut here ]
[ 14.609163] WARNING: CPU: 1 PID: 63 at ../mm/mmap.c:2858
exit_mmap+0x1b8/0x224()
[ 14.616548] Modules linked in:
[ 14.619553] CPU: 1 PID: 63 Comm: init Not tainted
3.19.0-rc5-next-20150123 #1
[ 14.626713] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 14.632830] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 14.640473] [] (show_stack) from [] (dump_stack+0x78/0x94)
[ 14.647678] [] (dump_stack) from [] (warn_slowpath_common+0x74/0xb0)
[ 14.655744] [] (warn_slowpath_common) from []
(warn_slowpath_null+0x1c/0x24)
[ 14.664510] [] (warn_slowpath_null) from [] (exit_mmap+0x1b8/0x224)
[ 14.672497] [] (exit_mmap) from [] (mmput+0x40/0xf8)
[ 14.679180] [] (mmput) from [] (flush_old_exec+0x328/0x604)
[ 14.686471] [] (flush_old_exec) from [] (load_elf_binary+0x26c/0x11f4)
[ 14.694715] [] (load_elf_binary) from []
(search_binary_handler+0x98/0x244)
[ 14.703395] [] (search_binary_handler) from []
(do_execveat_common+0x4dc/0x5bc)
[ 14.712421] [] (do_execveat_common) from [] (do_execve+0x28/0x30)
[ 14.720235] [] (do_execve) from [] (ret_fast_syscall+0x0/0x34)
[ 14.727782] ---[ end trace 5e3ca48b454c7e0a ]---
[ 14.733758] [ cut here ]
Has anyone else tested with CONFIG_ARM_LPAE=y that can confirm my findings?
Uggh... I missed since i was looking at non LPAE omap2plus_defconfig.
Dual A15 OMAP5432 with multi_v7_defconfig + CONFIG_ARM_LPAE=y
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/omap5-evm.txt
Dual A15 DRA7/AM572x with same configuration as above.
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra7xx-evm.txt
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/am57xx-evm.txt
Single A15 DRA72 with same configuration as above:
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra72x-evm.txt
You are right. the issue re-appears with LPAE on :(
Apologies on missing that.
Guys, could you instrument mm_{inc,dec}_nr_pmds() with dump_stack() +
printk() of the counter and add printk() on mmap_exit() then run a simple
program which triggers the issue?
--
Kirill A. Shutemov
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On 09:39-20150123, Tyler Baker wrote: Hi, On 23 January 2015 at 09:27, Nishanth Menon n...@ti.com wrote: On 16:05-20150120, Kirill A. Shutemov wrote: [..] Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com Just to close on this thread: https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks good and back to old status. Thank you folks for all the help. I just reviewed the boot logs for next-20150123 and there still seems to be a related issue. I've been boot testing multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still seem broken. For example here are two boots with exynos5250-arndale, one with multi_v7_defconfig+CONFIG_ARM_LPAE=y [1] and the other with multi_v7_defconfig[2]. You can see the kernel configurations with CONFIG_ARM_LPAE=y show the splat: [ 14.605950] [ cut here ] [ 14.609163] WARNING: CPU: 1 PID: 63 at ../mm/mmap.c:2858 exit_mmap+0x1b8/0x224() [ 14.616548] Modules linked in: [ 14.619553] CPU: 1 PID: 63 Comm: init Not tainted 3.19.0-rc5-next-20150123 #1 [ 14.626713] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree) [ 14.632830] [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [ 14.640473] [] (show_stack) from [] (dump_stack+0x78/0x94) [ 14.647678] [] (dump_stack) from [] (warn_slowpath_common+0x74/0xb0) [ 14.655744] [] (warn_slowpath_common) from [] (warn_slowpath_null+0x1c/0x24) [ 14.664510] [] (warn_slowpath_null) from [] (exit_mmap+0x1b8/0x224) [ 14.672497] [] (exit_mmap) from [] (mmput+0x40/0xf8) [ 14.679180] [] (mmput) from [] (flush_old_exec+0x328/0x604) [ 14.686471] [] (flush_old_exec) from [] (load_elf_binary+0x26c/0x11f4) [ 14.694715] [] (load_elf_binary) from [] (search_binary_handler+0x98/0x244) [ 14.703395] [] (search_binary_handler) from [] (do_execveat_common+0x4dc/0x5bc) [ 14.712421] [] (do_execveat_common) from [] (do_execve+0x28/0x30) [ 14.720235] [] (do_execve) from [] (ret_fast_syscall+0x0/0x34) [ 14.727782] ---[ end trace 5e3ca48b454c7e0a ]--- [ 14.733758] [ cut here ] Has anyone else tested with CONFIG_ARM_LPAE=y that can confirm my findings? Uggh... I missed since i was looking at non LPAE omap2plus_defconfig. Dual A15 OMAP5432 with multi_v7_defconfig + CONFIG_ARM_LPAE=y https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/omap5-evm.txt Dual A15 DRA7/AM572x with same configuration as above. https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra7xx-evm.txt https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/am57xx-evm.txt Single A15 DRA72 with same configuration as above: https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra72x-evm.txt You are right. the issue re-appears with LPAE on :( Apologies on missing that. -- Regards, Nishanth Menon ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel [1] http://storage.kernelci.org/next/next-20150123/arm-multi_v7_defconfig+CONFIG_ARM_LPAE=y/lab-tbaker/boot-exynos5250-arndale.html [2] http://storage.kernelci.org/next/next-20150123/arm-multi_v7_defconfig/lab-tbaker/boot-exynos5250-arndale.html Cheers, Tyler -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On 22:22-20150123, Kirill A. Shutemov wrote:
On Fri, Jan 23, 2015 at 12:37:06PM -0600, Nishanth Menon wrote:
On 09:39-20150123, Tyler Baker wrote:
Hi,
On 23 January 2015 at 09:27, Nishanth Menon n...@ti.com wrote:
On 16:05-20150120, Kirill A. Shutemov wrote:
[..]
Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com
Reported-by: Nishanth Menon n...@ti.com
Just to close on this thread:
https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks good
and back to old status. Thank you folks for all the help.
I just reviewed the boot logs for next-20150123 and there still seems
to be a related issue. I've been boot testing
multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still
seem broken.
For example here are two boots with exynos5250-arndale, one with
multi_v7_defconfig+CONFIG_ARM_LPAE=y [1] and the other with
multi_v7_defconfig[2]. You can see the kernel configurations with
CONFIG_ARM_LPAE=y show the splat:
[ 14.605950] [ cut here ]
[ 14.609163] WARNING: CPU: 1 PID: 63 at ../mm/mmap.c:2858
exit_mmap+0x1b8/0x224()
[ 14.616548] Modules linked in:
[ 14.619553] CPU: 1 PID: 63 Comm: init Not tainted
3.19.0-rc5-next-20150123 #1
[ 14.626713] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 14.632830] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 14.640473] [] (show_stack) from [] (dump_stack+0x78/0x94)
[ 14.647678] [] (dump_stack) from [] (warn_slowpath_common+0x74/0xb0)
[ 14.655744] [] (warn_slowpath_common) from []
(warn_slowpath_null+0x1c/0x24)
[ 14.664510] [] (warn_slowpath_null) from [] (exit_mmap+0x1b8/0x224)
[ 14.672497] [] (exit_mmap) from [] (mmput+0x40/0xf8)
[ 14.679180] [] (mmput) from [] (flush_old_exec+0x328/0x604)
[ 14.686471] [] (flush_old_exec) from [] (load_elf_binary+0x26c/0x11f4)
[ 14.694715] [] (load_elf_binary) from []
(search_binary_handler+0x98/0x244)
[ 14.703395] [] (search_binary_handler) from []
(do_execveat_common+0x4dc/0x5bc)
[ 14.712421] [] (do_execveat_common) from [] (do_execve+0x28/0x30)
[ 14.720235] [] (do_execve) from [] (ret_fast_syscall+0x0/0x34)
[ 14.727782] ---[ end trace 5e3ca48b454c7e0a ]---
[ 14.733758] [ cut here ]
Has anyone else tested with CONFIG_ARM_LPAE=y that can confirm my
findings?
Uggh... I missed since i was looking at non LPAE omap2plus_defconfig.
Dual A15 OMAP5432 with multi_v7_defconfig + CONFIG_ARM_LPAE=y
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/omap5-evm.txt
Dual A15 DRA7/AM572x with same configuration as above.
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra7xx-evm.txt
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/am57xx-evm.txt
Single A15 DRA72 with same configuration as above:
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra72x-evm.txt
You are right. the issue re-appears with LPAE on :(
Apologies on missing that.
Guys, could you instrument mm_{inc,dec}_nr_pmds() with dump_stack() +
printk() of the counter and add printk() on mmap_exit() then run a simple
program which triggers the issue?
The simplest program I think we are all running is boot to shell - I
mean, have'nt spend more time digging at it as I am not in a familiar
territory here. :( is there any instrumentation patch you want us to try?
--
Regards,
Nishanth Menon
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
Hi Kirill,
On 23 January 2015 at 12:22, Kirill A. Shutemov kir...@shutemov.name wrote:
On Fri, Jan 23, 2015 at 12:37:06PM -0600, Nishanth Menon wrote:
On 09:39-20150123, Tyler Baker wrote:
Hi,
On 23 January 2015 at 09:27, Nishanth Menon n...@ti.com wrote:
On 16:05-20150120, Kirill A. Shutemov wrote:
[..]
Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com
Reported-by: Nishanth Menon n...@ti.com
Just to close on this thread:
https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks good
and back to old status. Thank you folks for all the help.
I just reviewed the boot logs for next-20150123 and there still seems
to be a related issue. I've been boot testing
multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still
seem broken.
For example here are two boots with exynos5250-arndale, one with
multi_v7_defconfig+CONFIG_ARM_LPAE=y [1] and the other with
multi_v7_defconfig[2]. You can see the kernel configurations with
CONFIG_ARM_LPAE=y show the splat:
[ 14.605950] [ cut here ]
[ 14.609163] WARNING: CPU: 1 PID: 63 at ../mm/mmap.c:2858
exit_mmap+0x1b8/0x224()
[ 14.616548] Modules linked in:
[ 14.619553] CPU: 1 PID: 63 Comm: init Not tainted
3.19.0-rc5-next-20150123 #1
[ 14.626713] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 14.632830] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 14.640473] [] (show_stack) from [] (dump_stack+0x78/0x94)
[ 14.647678] [] (dump_stack) from [] (warn_slowpath_common+0x74/0xb0)
[ 14.655744] [] (warn_slowpath_common) from []
(warn_slowpath_null+0x1c/0x24)
[ 14.664510] [] (warn_slowpath_null) from [] (exit_mmap+0x1b8/0x224)
[ 14.672497] [] (exit_mmap) from [] (mmput+0x40/0xf8)
[ 14.679180] [] (mmput) from [] (flush_old_exec+0x328/0x604)
[ 14.686471] [] (flush_old_exec) from [] (load_elf_binary+0x26c/0x11f4)
[ 14.694715] [] (load_elf_binary) from []
(search_binary_handler+0x98/0x244)
[ 14.703395] [] (search_binary_handler) from []
(do_execveat_common+0x4dc/0x5bc)
[ 14.712421] [] (do_execveat_common) from [] (do_execve+0x28/0x30)
[ 14.720235] [] (do_execve) from [] (ret_fast_syscall+0x0/0x34)
[ 14.727782] ---[ end trace 5e3ca48b454c7e0a ]---
[ 14.733758] [ cut here ]
Has anyone else tested with CONFIG_ARM_LPAE=y that can confirm my findings?
Uggh... I missed since i was looking at non LPAE omap2plus_defconfig.
Dual A15 OMAP5432 with multi_v7_defconfig + CONFIG_ARM_LPAE=y
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/omap5-evm.txt
Dual A15 DRA7/AM572x with same configuration as above.
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra7xx-evm.txt
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/am57xx-evm.txt
Single A15 DRA72 with same configuration as above:
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra72x-evm.txt
You are right. the issue re-appears with LPAE on :(
Apologies on missing that.
Guys, could you instrument mm_{inc,dec}_nr_pmds() with dump_stack() +
printk() of the counter and add printk() on mmap_exit() then run a simple
program which triggers the issue?
For reference, here is the patch I've applied for testing, mostly
stolen from Felipe's debug patch above in this thread.
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 1fbd0e8..e5b0444 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1455,11 +1455,17 @@ static inline unsigned long mm_nr_pmds(struct
mm_struct *mm)
static inline void mm_inc_nr_pmds(struct mm_struct *mm)
{
atomic_long_inc(mm-nr_pmds);
+dump_stack();
+printk(KERN_INFO === %s nr_pmds %ld\n, __func__,
+atomic_long_read(mm-nr_pmds));
}
static inline void mm_dec_nr_pmds(struct mm_struct *mm)
{
atomic_long_dec(mm-nr_pmds);
+dump_stack();
+printk(KERN_INFO === %s nr_pmds %ld\n, __func__,
+atomic_long_read(mm-nr_pmds));
}
#endif
diff --git a/mm/mmap.c b/mm/mmap.c
index 6a7d36d..a16471f 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2809,6 +2809,7 @@ EXPORT_SYMBOL(vm_brk);
/* Release all mmaps. */
void exit_mmap(struct mm_struct *mm)
{
+ printk(KERN_INFO === %s exit_mmap enter\n, __func__);
struct mmu_gather tlb;
struct vm_area_struct *vma;
unsigned long nr_accounted = 0;
I applied this patch to the tip of linux-next, configured for
multi_v7_defconfig and set CONFIG_ARM_LPAE=y. The log for this arndale
boot can be found here [1]. For good measure, I then rebuilt the
kernel with CONFIG_ARM_LPAE=n and booted the same platform again. This
log can be found here [2].
Happy hunting!
--
Kirill A. Shutemov
[1] http://storage.kernelci.org/debug/mm/arndale-lpae-debug-next-20150123.html
[2]
Re: [next-20150119]regression (mm)?
On Fri, Jan 23, 2015 at 02:42:17PM -0800, Tyler Baker wrote:
Hi Kirill,
On 23 January 2015 at 12:22, Kirill A. Shutemov kir...@shutemov.name wrote:
On Fri, Jan 23, 2015 at 12:37:06PM -0600, Nishanth Menon wrote:
On 09:39-20150123, Tyler Baker wrote:
Hi,
On 23 January 2015 at 09:27, Nishanth Menon n...@ti.com wrote:
On 16:05-20150120, Kirill A. Shutemov wrote:
[..]
Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com
Reported-by: Nishanth Menon n...@ti.com
Just to close on this thread:
https://github.com/nmenon/kernel-test-logs/tree/next-20150123 looks
good
and back to old status. Thank you folks for all the help.
I just reviewed the boot logs for next-20150123 and there still seems
to be a related issue. I've been boot testing
multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still
seem broken.
For example here are two boots with exynos5250-arndale, one with
multi_v7_defconfig+CONFIG_ARM_LPAE=y [1] and the other with
multi_v7_defconfig[2]. You can see the kernel configurations with
CONFIG_ARM_LPAE=y show the splat:
[ 14.605950] [ cut here ]
[ 14.609163] WARNING: CPU: 1 PID: 63 at ../mm/mmap.c:2858
exit_mmap+0x1b8/0x224()
[ 14.616548] Modules linked in:
[ 14.619553] CPU: 1 PID: 63 Comm: init Not tainted
3.19.0-rc5-next-20150123 #1
[ 14.626713] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
[ 14.632830] [] (unwind_backtrace) from [] (show_stack+0x10/0x14)
[ 14.640473] [] (show_stack) from [] (dump_stack+0x78/0x94)
[ 14.647678] [] (dump_stack) from [] (warn_slowpath_common+0x74/0xb0)
[ 14.655744] [] (warn_slowpath_common) from []
(warn_slowpath_null+0x1c/0x24)
[ 14.664510] [] (warn_slowpath_null) from [] (exit_mmap+0x1b8/0x224)
[ 14.672497] [] (exit_mmap) from [] (mmput+0x40/0xf8)
[ 14.679180] [] (mmput) from [] (flush_old_exec+0x328/0x604)
[ 14.686471] [] (flush_old_exec) from [] (load_elf_binary+0x26c/0x11f4)
[ 14.694715] [] (load_elf_binary) from []
(search_binary_handler+0x98/0x244)
[ 14.703395] [] (search_binary_handler) from []
(do_execveat_common+0x4dc/0x5bc)
[ 14.712421] [] (do_execveat_common) from [] (do_execve+0x28/0x30)
[ 14.720235] [] (do_execve) from [] (ret_fast_syscall+0x0/0x34)
[ 14.727782] ---[ end trace 5e3ca48b454c7e0a ]---
[ 14.733758] [ cut here ]
Has anyone else tested with CONFIG_ARM_LPAE=y that can confirm my
findings?
Uggh... I missed since i was looking at non LPAE omap2plus_defconfig.
Dual A15 OMAP5432 with multi_v7_defconfig + CONFIG_ARM_LPAE=y
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/omap5-evm.txt
Dual A15 DRA7/AM572x with same configuration as above.
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra7xx-evm.txt
https://github.com/nmenon/kernel-test-logs/blob/next-20150123/multi_lpae_defconfig/am57xx-evm.txt
Single A15 DRA72 with same configuration as above:
https://raw.githubusercontent.com/nmenon/kernel-test-logs/next-20150123/multi_lpae_defconfig/dra72x-evm.txt
You are right. the issue re-appears with LPAE on :(
Apologies on missing that.
Guys, could you instrument mm_{inc,dec}_nr_pmds() with dump_stack() +
printk() of the counter and add printk() on mmap_exit() then run a simple
program which triggers the issue?
For reference, here is the patch I've applied for testing, mostly
stolen from Felipe's debug patch above in this thread.
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 1fbd0e8..e5b0444 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1455,11 +1455,17 @@ static inline unsigned long mm_nr_pmds(struct
mm_struct *mm)
static inline void mm_inc_nr_pmds(struct mm_struct *mm)
{
atomic_long_inc(mm-nr_pmds);
+dump_stack();
+printk(KERN_INFO === %s nr_pmds %ld\n, __func__,
+atomic_long_read(mm-nr_pmds));
}
static inline void mm_dec_nr_pmds(struct mm_struct *mm)
{
atomic_long_dec(mm-nr_pmds);
+dump_stack();
+printk(KERN_INFO === %s nr_pmds %ld\n, __func__,
+atomic_long_read(mm-nr_pmds));
}
#endif
diff --git a/mm/mmap.c b/mm/mmap.c
index 6a7d36d..a16471f 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2809,6 +2809,7 @@ EXPORT_SYMBOL(vm_brk);
/* Release all mmaps. */
void exit_mmap(struct mm_struct *mm)
{
+ printk(KERN_INFO === %s exit_mmap enter\n, __func__);
struct mmu_gather tlb;
struct vm_area_struct *vma;
unsigned long nr_accounted = 0;
I applied this patch to the tip of linux-next, configured for
multi_v7_defconfig and set CONFIG_ARM_LPAE=y. The log for this arndale
boot can be found here [1]. For good measure, I then rebuilt the
kernel with CONFIG_ARM_LPAE=n and booted the same
Re: [next-20150119]regression (mm)?
On 03:13-20150124, Kirill A. Shutemov wrote: On 09:39-20150123, Tyler Baker wrote: [...] I just reviewed the boot logs for next-20150123 and there still seems to be a related issue. I've been boot testing multi_v7_defconfig+CONFIG_ARM_LPAE=y kernel configurations which still seem broken. [...] Okay, proof of concept patch is below. It's going to break every other architecture with FIRST_USER_ADDRESS != 0, but I think it's cleaner way to go. Testing on my end: just ran through this set (+ logs similar to Tyler's from my side): next-20150123 (multi_v7_defconfig == !LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2219449 2: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219450 3: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219451 4: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2219452 TOTAL = 4 boards, Booted Boards = 4, No Boot boards = 0 next-20150123-LPAE-Logging enabled[1] (multi_v7_defconfig +LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: FAIL: http://paste.ubuntu.org.cn/2220938 2: dra72x-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220943 3: dra7xx-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220947 4: omap5-evm: BOOT: FAIL: http://paste.ubuntu.org.cn/2220955 TOTAL = 4 boards, Booted Boards = 0, No Boot boards = 4 next-20150123-LPAE-new-patch [2] (multi_v7_defconfig + LPAE) 1:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221047 2: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221065 3: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221069 4: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221070 TOTAL = 4 boards, Booted Boards = 4, No Boot boards = 0 next-20150123-new-patch[2] (multi_v7_defconfig == !LPAE) 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221277 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221278 3: am437x-sk: BOOT: FAIL: http://paste.ubuntu.org.cn/2221279 (unrelated) 4:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2221280 5: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2221281 6:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221282 7: BeagleBoard-XM: BOOT: FAIL: http://paste.ubuntu.org.cn/2221283 (unrelated) 8:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221284 9: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2221285 10: beaglebone: BOOT: FAIL: http://paste.ubuntu.org.cn/2221286 (unrelated) 11: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221287 12: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221288 13: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221289 14: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2221290 15: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221291 16:sdp4430: BOOT: PASS: http://paste.ubuntu.org.cn/2221292 TOTAL = 16 boards, Booted Boards = 13, No Boot boards = 3 next-20150123-new-patch[2] (omap2plus_defconfig) 1: am335x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221653 2: am335x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221654 3: am437x-sk: BOOT: PASS: http://paste.ubuntu.org.cn/2221656 4:am43xx-epos: BOOT: PASS: http://paste.ubuntu.org.cn/2221659 5: am43xx-gpevm: BOOT: PASS: http://paste.ubuntu.org.cn/2221660 6:BeagleBoard-X15(am57xx-evm): BOOT: PASS: http://paste.ubuntu.org.cn/2221661 7: BeagleBoard-XM: BOOT: PASS: http://paste.ubuntu.org.cn/2221670 8:beagleboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221676 9: beaglebone-black: BOOT: PASS: http://paste.ubuntu.org.cn/2221683 10: beaglebone: BOOT: PASS: http://paste.ubuntu.org.cn/2221690 11: dra72x-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221692 12: dra7xx-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221695 13: omap5-evm: BOOT: PASS: http://paste.ubuntu.org.cn/2221700 14: pandaboard-es: BOOT: PASS: http://paste.ubuntu.org.cn/2221704 15: pandaboard-vanilla: BOOT: PASS: http://paste.ubuntu.org.cn/2221707 16:sdp4430: BOOT: PASS: http://paste.ubuntu.org.cn/2221713 TOTAL = 16 boards, Booted Boards = 16, No Boot boards = 0 [1] http://paste.ubuntu.org.cn/2220994 (based on diff from Tyler B) [2] https://patchwork.kernel.org/patch/5698491/ -- Regards, Nishanth Menon
Re: [next-20150119]regression (mm)?
2015-01-20 15:05 GMT+01:00 Kirill A. Shutemov kirill.shute...@linux.intel.com: Russell King - ARM Linux wrote: On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote: Better option would be converting 2-lvl ARM configuration to asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible. Well, IMHO the folded approach in asm-generic was done the wrong way which barred ARM from ever using it. Okay, I see. Regarding the topic bug. Completely untested patch is below. Could anybody check if it helps? From 34b9182d08ef2b541829e305fcc91ef1d26b27ea Mon Sep 17 00:00:00 2001 From: Kirill A. Shutemov kirill.shute...@linux.intel.com Date: Tue, 20 Jan 2015 15:47:22 +0200 Subject: [PATCH] arm: define __PAGETABLE_PMD_FOLDED for !LPAE ARM uses custom implementation of PMD folding in 2-level page table case. Generic code expects to see __PAGETABLE_PMD_FOLDED to be defined if PMD is folded, but ARM doesn't do this. Let's fix it. Defining __PAGETABLE_PMD_FOLDED will drop out unused __pmd_alloc(). It also fixes problems with recently-introduced pmd accounting on ARM without LPAE. Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com --- arch/arm/include/asm/pgtable-2level.h | 2 ++ 1 file changed, 2 insertions(+) Helps for this issue on Exynos 4412 (Trats2) and Exynos 5420 (Arndale Octa): Tested-by: Krzysztof Kozlowski k.kozlow...@samsung.com Off-topic: Using smp_processor_id() in preemptible still screams [1] [1] https://lkml.org/lkml/2015/1/20/162 Best regards, Krzysztof -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On 01/20/2015 04:05 PM, Kirill A. Shutemov wrote: Russell King - ARM Linux wrote: On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote: Better option would be converting 2-lvl ARM configuration to asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible. Well, IMHO the folded approach in asm-generic was done the wrong way which barred ARM from ever using it. Okay, I see. Regarding the topic bug. Completely untested patch is below. Could anybody check if it helps? From 34b9182d08ef2b541829e305fcc91ef1d26b27ea Mon Sep 17 00:00:00 2001 From: Kirill A. Shutemov kirill.shute...@linux.intel.com Date: Tue, 20 Jan 2015 15:47:22 +0200 Subject: [PATCH] arm: define __PAGETABLE_PMD_FOLDED for !LPAE ARM uses custom implementation of PMD folding in 2-level page table case. Generic code expects to see __PAGETABLE_PMD_FOLDED to be defined if PMD is folded, but ARM doesn't do this. Let's fix it. Defining __PAGETABLE_PMD_FOLDED will drop out unused __pmd_alloc(). It also fixes problems with recently-introduced pmd accounting on ARM without LPAE. Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com --- arch/arm/include/asm/pgtable-2level.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/include/asm/pgtable-2level.h b/arch/arm/include/asm/pgtable-2level.h index bcc5e300413f..bfd662e49a25 100644 --- a/arch/arm/include/asm/pgtable-2level.h +++ b/arch/arm/include/asm/pgtable-2level.h @@ -10,6 +10,8 @@ #ifndef _ASM_PGTABLE_2LEVEL_H #define _ASM_PGTABLE_2LEVEL_H +#define __PAGETABLE_PMD_FOLDED + /* * Hardware-wise, we have a two level page table structure, where the first * level has 4096 entries, and the second level has 256 entries. Each entry Among other boards I have my daVinci board (OMAP-L138-EVM) boots fine with this patch. Tested-by: Peter Ujfalusi peter.ujfal...@ti.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote:
Better option would be converting 2-lvl ARM configuration to
asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible.
Well, IMHO the folded approach in asm-generic was done the wrong way
which barred ARM from ever using it.
By that, I mean that the asm-generic stuff encapsulates a pgd into a pud,
and a pud into a pmd:
typedef struct { pgd_t pgd; } pud_t;
typedef struct { pud_t pud; } pmd_t;
This, I assert, is the wrong way around. Think about it when you have a
real 4 level page table structure - a single pgd points to a set of puds.
So, one pgd encapsulates via a pointer a set of puds. One pud does not
encapsulate a set of pgds.
What we have on ARM is slightly different: because of the sizes of page
tables, we have a pgd entry which is physically two page table pointers.
However, there are cases where we want to access these as two separate
pointers.
So, we define pgd_t to be an array of two u32's, and a pmd_t to be a
single entry. This works fine, we set the masks, shifts and sizes
appropriately so that the pmd code is optimised away, but leaves us with
the ability to go down to the individual pgd_t entries when we need to
(eg, for section mappings, writing the pgd pointers for page tables,
etc.)
I think I also ran into problems with:
#define pmd_val(x) (pud_val((x).pud))
#define __pmd(x)((pmd_t) { __pud(x) } )
too - but it's been a very long time since the nopmd.h stuff was
introduced, and I last looked at it.
In any case, what we have today is what has worked for well over a decade
(and pre-dates nopmd.h), and I'm really not interested today in trying to
rework tonnes of code to make use of nopmd.h - especially as it will most
likely require nopmd.h to be rewritten too, and we now have real 3 level
page table support (which I have no way to test.)
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
Russell King - ARM Linux wrote: On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote: Better option would be converting 2-lvl ARM configuration to asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible. Well, IMHO the folded approach in asm-generic was done the wrong way which barred ARM from ever using it. Okay, I see. Regarding the topic bug. Completely untested patch is below. Could anybody check if it helps? From 34b9182d08ef2b541829e305fcc91ef1d26b27ea Mon Sep 17 00:00:00 2001 From: Kirill A. Shutemov kirill.shute...@linux.intel.com Date: Tue, 20 Jan 2015 15:47:22 +0200 Subject: [PATCH] arm: define __PAGETABLE_PMD_FOLDED for !LPAE ARM uses custom implementation of PMD folding in 2-level page table case. Generic code expects to see __PAGETABLE_PMD_FOLDED to be defined if PMD is folded, but ARM doesn't do this. Let's fix it. Defining __PAGETABLE_PMD_FOLDED will drop out unused __pmd_alloc(). It also fixes problems with recently-introduced pmd accounting on ARM without LPAE. Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com --- arch/arm/include/asm/pgtable-2level.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/include/asm/pgtable-2level.h b/arch/arm/include/asm/pgtable-2level.h index bcc5e300413f..bfd662e49a25 100644 --- a/arch/arm/include/asm/pgtable-2level.h +++ b/arch/arm/include/asm/pgtable-2level.h @@ -10,6 +10,8 @@ #ifndef _ASM_PGTABLE_2LEVEL_H #define _ASM_PGTABLE_2LEVEL_H +#define __PAGETABLE_PMD_FOLDED + /* * Hardware-wise, we have a two level page table structure, where the first * level has 4096 entries, and the second level has 256 entries. Each entry -- 2.1.4 -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On Tue, Jan 20, 2015 at 12:05 PM, Kirill A. Shutemov kirill.shute...@linux.intel.com wrote: Russell King - ARM Linux wrote: On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote: Better option would be converting 2-lvl ARM configuration to asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible. Well, IMHO the folded approach in asm-generic was done the wrong way which barred ARM from ever using it. Okay, I see. Regarding the topic bug. Completely untested patch is below. Could anybody check if it helps? Yes, it helps. Now I can boot mx6 running linux-next 20150120 with your patch applied. -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On Tue, Jan 20, 2015 at 12:50:59PM -0200, Fabio Estevam wrote: On Tue, Jan 20, 2015 at 12:05 PM, Kirill A. Shutemov kirill.shute...@linux.intel.com wrote: Russell King - ARM Linux wrote: On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote: Better option would be converting 2-lvl ARM configuration to asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible. Well, IMHO the folded approach in asm-generic was done the wrong way which barred ARM from ever using it. Okay, I see. Regarding the topic bug. Completely untested patch is below. Could anybody check if it helps? Yes, it helps. Now I can boot mx6 running linux-next 20150120 with your patch applied. worked fine here too with AM437x SK, AM437x IDK and BeagleBoneBlack. thanks -- balbi signature.asc Description: Digital signature
Re: [next-20150119]regression (mm)?
On 16:05-20150120, Kirill A. Shutemov wrote: Russell King - ARM Linux wrote: On Tue, Jan 20, 2015 at 02:16:43AM +0200, Kirill A. Shutemov wrote: Better option would be converting 2-lvl ARM configuration to asm-generic/pgtable-nopmd.h, but I'm not sure if it's possible. Well, IMHO the folded approach in asm-generic was done the wrong way which barred ARM from ever using it. Okay, I see. Regarding the topic bug. Completely untested patch is below. Could anybody check if it helps? From 34b9182d08ef2b541829e305fcc91ef1d26b27ea Mon Sep 17 00:00:00 2001 From: Kirill A. Shutemov kirill.shute...@linux.intel.com Date: Tue, 20 Jan 2015 15:47:22 +0200 Subject: [PATCH] arm: define __PAGETABLE_PMD_FOLDED for !LPAE ARM uses custom implementation of PMD folding in 2-level page table case. Generic code expects to see __PAGETABLE_PMD_FOLDED to be defined if PMD is folded, but ARM doesn't do this. Let's fix it. Defining __PAGETABLE_PMD_FOLDED will drop out unused __pmd_alloc(). It also fixes problems with recently-introduced pmd accounting on ARM without LPAE. Signed-off-by: Kirill A. Shutemov kirill.shute...@linux.intel.com Reported-by: Nishanth Menon n...@ti.com --- arch/arm/include/asm/pgtable-2level.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/include/asm/pgtable-2level.h b/arch/arm/include/asm/pgtable-2level.h index bcc5e300413f..bfd662e49a25 100644 --- a/arch/arm/include/asm/pgtable-2level.h +++ b/arch/arm/include/asm/pgtable-2level.h @@ -10,6 +10,8 @@ #ifndef _ASM_PGTABLE_2LEVEL_H #define _ASM_PGTABLE_2LEVEL_H +#define __PAGETABLE_PMD_FOLDED + /* * Hardware-wise, we have a two level page table structure, where the first * level has 4096 entries, and the second level has 256 entries. Each entry -- 2.1.4 Above helps the TI platforms 1: am335x-evm: BOOT: PASS: am335x-evm.txt 2: am335x-sk: BOOT: PASS: am335x-sk.txt 3: am3517-evm: BOOT: PASS: am3517-evm.txt 4: am37x-evm: BOOT: PASS: am37x-evm.txt 5: am437x-sk: BOOT: PASS: am437x-sk.txt 6:am43xx-epos: BOOT: PASS: am43xx-epos.txt 7: am43xx-gpevm: BOOT: PASS: am43xx-gpevm.txt 8:BeagleBoard-X15(am57xx-evm): BOOT: PASS: am57xx-evm.txt 9: BeagleBoard-XM: BOOT: PASS: beagleboard.txt 10:beagleboard-vanilla: BOOT: PASS: beagleboard-vanilla.txt 11: beaglebone-black: BOOT: PASS: beaglebone-black.txt 12: beaglebone: BOOT: PASS: beaglebone.txt 13: craneboard: BOOT: PASS: craneboard.txt 14: dra72x-evm: BOOT: PASS: dra72x-evm.txt 15: dra7xx-evm: BOOT: PASS: dra7xx-evm.txt 16: OMAP3430-Labrador(LDP): BOOT: PASS: ldp.txt 17: n900: BOOT: FAIL: n900.txt (legacy issue with my farm) 18: omap5-evm: BOOT: PASS: omap5-evm.txt 19: pandaboard-es: BOOT: PASS: pandaboard-es.txt 20: pandaboard-vanilla: BOOT: PASS: pandaboard-vanilla.txt 21:sdp2430: BOOT: PASS: sdp2430.txt 22:sdp3430: BOOT: PASS: sdp3430.txt 23:sdp4430: BOOT: PASS: sdp4430.txt TOTAL = 23 boards, Booted Boards = 22, No Boot boards = 1 please feel free to add my Tested-by: Nishanth Menon n...@ti.com -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
Felipe Balbi wrote: Hi, On Mon, Jan 19, 2015 at 10:42:04AM -0600, Nishanth Menon wrote: Most platforms seem broken intoday's next tag. https://github.com/nmenon/kernel-test-logs/tree/next-20150119 (defconfig: omap2plus_defconfig) [7.166600] [ cut here ] [7.171676] WARNING: CPU: 0 PID: 54 at mm/mmap.c:2859 exit_mmap+0x1a8/0x21c() [7.179194] Modules linked in: [7.182479] CPU: 0 PID: 54 Comm: init Not tainted 3.19.0-rc5-next-20150119-2-gfdefcded1272 #1 [7.191863] Hardware name: Generic AM33XX (Flattened Device Tree) [7.198318] [c00153f0] (unwind_backtrace) from [c0011a74] (show_stack+0x10/0x14) [7.206528] [c0011a74] (show_stack) from [c0580150] (dump_stack+0x78/0x94) [7.214191] [c0580150] (dump_stack) from [c003d4d0] (warn_slowpath_common+0x7c/0xb4) [7.222751] [c003d4d0] (warn_slowpath_common) from [c003d524] (warn_slowpath_null+0x1c/0x24) [7.232038] [c003d524] (warn_slowpath_null) from [c012de64] (exit_mmap+0x1a8/0x21c) [7.240536] [c012de64] (exit_mmap) from [c003abb8] (mmput+0x44/0xec) [7.247612] [c003abb8] (mmput) from [c0151368] (flush_old_exec+0x300/0x5a4) [7.255357] [c0151368] (flush_old_exec) from [c0195c10] (load_elf_binary+0x2ec/0x1144) [7.264111] [c0195c10] (load_elf_binary) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.273311] [c0150ea0] (search_binary_handler) from [c019554c] (load_script+0x260/0x280) [7.282232] [c019554c] (load_script) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.291066] [c0150ea0] (search_binary_handler) from [c0151f0c] (do_execveat_common+0x538/0x6c4) [7.300628] [c0151f0c] (do_execveat_common) from [c01520c4] (do_execve+0x2c/0x34) [7.308881] [c01520c4] (do_execve) from [c000e5e0] (ret_fast_syscall+0x0/0x4c) [7.316881] ---[ end trace 3b8a46b1b280f423 ]--- seems like it's caused by: b316feb3c37ff19cddcaf1f6b5056c633193257d is the first bad commit Adding Kiryl to the loop. git bisect start # good: [ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc] Linux 3.19-rc5 git bisect good ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc # bad: [a0d4287f787889e59db0fd295853a0f1f55d0699] Add linux-next specific files for 20150119 git bisect bad a0d4287f787889e59db0fd295853a0f1f55d0699 # good: [1c2f70b77b8ca77f10c59d479d009e07359d00d2] Merge remote-tracking branch 'drm/drm-next' git bisect good 1c2f70b77b8ca77f10c59d479d009e07359d00d2 # good: [73c1390843223d8bfc85795c560c36b3d0ffee40] Merge remote-tracking branch 'leds/for-next' git bisect good 73c1390843223d8bfc85795c560c36b3d0ffee40 # good: [7bc6bef35d48e91ad796b6eead7304998842c782] Merge remote-tracking branch 'pinctrl/for-next' git bisect good 7bc6bef35d48e91ad796b6eead7304998842c782 # bad: [45e1eaa38732ffa3de0d18fe95d2d2b960a7c777] lib: bitmap: change bitmap_shift_right to take unsigned parameters git bisect bad 45e1eaa38732ffa3de0d18fe95d2d2b960a7c777 # good: [c82a73a0369a7dd6dcfaf9e6bd572a4e5deda223] mm, page_alloc: reduce number of alloc_pages* functions' parameters git bisect good c82a73a0369a7dd6dcfaf9e6bd572a4e5deda223 # bad: [0b1c810fbc4bbff7e314dd6ff91c2b4af499199d] mm: don't split THP page when syscall is called git bisect bad 0b1c810fbc4bbff7e314dd6ff91c2b4af499199d # good: [54faa439355a9ae476a446429967e9e38f04363e] oom, PM: make OOM detection in the freezer path raceless git bisect good 54faa439355a9ae476a446429967e9e38f04363e # bad: [b6c9f11c6b6993303067f7c04a73258226a6e77e] mm/compaction: add tracepoint to observe behaviour of compaction defer git bisect bad b6c9f11c6b6993303067f7c04a73258226a6e77e # good: [9ce5d3fb13a80f28db450de4ecf2727893e99c93] mm: pagemap_read: limit scan to virtual region being asked git bisect good 9ce5d3fb13a80f28db450de4ecf2727893e99c93 # bad: [1a7a376546ca56e7750987c15d0c7541c17a512c] mm/compaction: change tracepoint format from decimal to hexadecimal git bisect bad 1a7a376546ca56e7750987c15d0c7541c17a512c # bad: [4081187ff19cf2186010c003939c17d70d0bbb27] page_writeback: put account_page_redirty() after set_page_dirty() git bisect bad 4081187ff19cf2186010c003939c17d70d0bbb27 # bad: [b316feb3c37ff19cddcaf1f6b5056c633193257d] mm: account pmd page tables to the process git bisect bad b316feb3c37ff19cddcaf1f6b5056c633193257d # first bad commit: [b316feb3c37ff19cddcaf1f6b5056c633193257d] mm: account pmd page tables to the process I've added a dump_mm() call when the bug happens followed by a while (true) loop (to avoid constant reprinting of the same thing), here's what I get: [7.235903] [ cut here ] [7.240881] WARNING: CPU: 0 PID: 58 at mm/mmap.c:2859 exit_mmap+0x1b4/0x218() [7.248369] Modules linked in: ipv6 autofs4 [7.252792] CPU: 0 PID: 58 Comm: systemd Not tainted 3.19.0-rc5-next-20150119-dirty #888 [7.261274] Hardware name:
Re: [next-20150119]regression (mm)?
On 01/19/2015 10:59 AM, Tyler Baker wrote: I can confirm, I am observing the same issue in my lab. 15 platforms failed to boot on next-20150119. http://kernelci.org/boot/?next-20150119fail http://kernelci.org/boot/all/job/next/kernel/next-20150119/ I see many platforms succeed in lab-khilman, but fails in your farm as well :( For example: http://storage.kernelci.org/next/next-20150119/arm-imx_v6_v7_defconfig/lab-khilman/boot-imx6q-wandboard.txt has the same errors, but marked success. http://storage.kernelci.org/next/next-20150119/arm-imx_v6_v7_defconfig/lab-tbaker/boot-imx6q-wandboard.txt is marked fail. I suppose this is much worse than the pass status indicates. On Monday, 19 January 2015, Nishanth Menon n...@ti.com mailto:n...@ti.com wrote: Hi, Most platforms seem broken intoday's next tag. https://github.com/nmenon/kernel-test-logs/tree/next-20150119 (defconfig: omap2plus_defconfig) [7.166600] [ cut here ] [7.171676] WARNING: CPU: 0 PID: 54 at mm/mmap.c:2859 exit_mmap+0x1a8/0x21c() [7.179194] Modules linked in: [7.182479] CPU: 0 PID: 54 Comm: init Not tainted 3.19.0-rc5-next-20150119-2-gfdefcded1272 #1 [7.191863] Hardware name: Generic AM33XX (Flattened Device Tree) [7.198318] [c00153f0] (unwind_backtrace) from [c0011a74] (show_stack+0x10/0x14) [7.206528] [c0011a74] (show_stack) from [c0580150] (dump_stack+0x78/0x94) [7.214191] [c0580150] (dump_stack) from [c003d4d0] (warn_slowpath_common+0x7c/0xb4) [7.222751] [c003d4d0] (warn_slowpath_common) from [c003d524] (warn_slowpath_null+0x1c/0x24) [7.232038] [c003d524] (warn_slowpath_null) from [c012de64] (exit_mmap+0x1a8/0x21c) [7.240536] [c012de64] (exit_mmap) from [c003abb8] (mmput+0x44/0xec) [7.247612] [c003abb8] (mmput) from [c0151368] (flush_old_exec+0x300/0x5a4) [7.255357] [c0151368] (flush_old_exec) from [c0195c10] (load_elf_binary+0x2ec/0x1144) [7.264111] [c0195c10] (load_elf_binary) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.273311] [c0150ea0] (search_binary_handler) from [c019554c] (load_script+0x260/0x280) [7.282232] [c019554c] (load_script) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.291066] [c0150ea0] (search_binary_handler) from [c0151f0c] (do_execveat_common+0x538/0x6c4) [7.300628] [c0151f0c] (do_execveat_common) from [c01520c4] (do_execve+0x2c/0x34) [7.308881] [c01520c4] (do_execve) from [c000e5e0] (ret_fast_syscall+0x0/0x4c) [7.316881] ---[ end trace 3b8a46b1b280f423 ]--- -- Regards, Nishanth Menon ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org javascript:; http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- Tyler Baker Tech Lead, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
On 19 January 2015 at 09:04, Nishanth Menon n...@ti.com wrote: On 01/19/2015 10:59 AM, Tyler Baker wrote: I can confirm, I am observing the same issue in my lab. 15 platforms failed to boot on next-20150119. http://kernelci.org/boot/?next-20150119fail http://kernelci.org/boot/all/job/next/kernel/next-20150119/ I see many platforms succeed in lab-khilman, but fails in your farm as well :( For example: http://storage.kernelci.org/next/next-20150119/arm-imx_v6_v7_defconfig/lab-khilman/boot-imx6q-wandboard.txt has the same errors, but marked success. http://storage.kernelci.org/next/next-20150119/arm-imx_v6_v7_defconfig/lab-tbaker/boot-imx6q-wandboard.txt is marked fail. I suppose this is much worse than the pass status indicates. I agree. I believe this boots were marked as 'passed' because the platforms eventually reached userspace despite the kernel spewing errors. I've re-run a few of my boots, and sometimes the platform reaches userspace, other times it hangs. On Monday, 19 January 2015, Nishanth Menon n...@ti.com mailto:n...@ti.com wrote: Hi, Most platforms seem broken intoday's next tag. https://github.com/nmenon/kernel-test-logs/tree/next-20150119 (defconfig: omap2plus_defconfig) [7.166600] [ cut here ] [7.171676] WARNING: CPU: 0 PID: 54 at mm/mmap.c:2859 exit_mmap+0x1a8/0x21c() [7.179194] Modules linked in: [7.182479] CPU: 0 PID: 54 Comm: init Not tainted 3.19.0-rc5-next-20150119-2-gfdefcded1272 #1 [7.191863] Hardware name: Generic AM33XX (Flattened Device Tree) [7.198318] [c00153f0] (unwind_backtrace) from [c0011a74] (show_stack+0x10/0x14) [7.206528] [c0011a74] (show_stack) from [c0580150] (dump_stack+0x78/0x94) [7.214191] [c0580150] (dump_stack) from [c003d4d0] (warn_slowpath_common+0x7c/0xb4) [7.222751] [c003d4d0] (warn_slowpath_common) from [c003d524] (warn_slowpath_null+0x1c/0x24) [7.232038] [c003d524] (warn_slowpath_null) from [c012de64] (exit_mmap+0x1a8/0x21c) [7.240536] [c012de64] (exit_mmap) from [c003abb8] (mmput+0x44/0xec) [7.247612] [c003abb8] (mmput) from [c0151368] (flush_old_exec+0x300/0x5a4) [7.255357] [c0151368] (flush_old_exec) from [c0195c10] (load_elf_binary+0x2ec/0x1144) [7.264111] [c0195c10] (load_elf_binary) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.273311] [c0150ea0] (search_binary_handler) from [c019554c] (load_script+0x260/0x280) [7.282232] [c019554c] (load_script) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.291066] [c0150ea0] (search_binary_handler) from [c0151f0c] (do_execveat_common+0x538/0x6c4) [7.300628] [c0151f0c] (do_execveat_common) from [c01520c4] (do_execve+0x2c/0x34) [7.308881] [c01520c4] (do_execve) from [c000e5e0] (ret_fast_syscall+0x0/0x4c) [7.316881] ---[ end trace 3b8a46b1b280f423 ]--- -- Regards, Nishanth Menon ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org javascript:; http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -- Tyler Baker Tech Lead, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- Regards, Nishanth Menon -- Tyler Baker Tech Lead, LAVA Linaro.org | Open source software for ARM SoCs Follow Linaro: http://www.facebook.com/pages/Linaro http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [next-20150119]regression (mm)?
Hi, On Mon, Jan 19, 2015 at 10:42:04AM -0600, Nishanth Menon wrote: Most platforms seem broken intoday's next tag. https://github.com/nmenon/kernel-test-logs/tree/next-20150119 (defconfig: omap2plus_defconfig) [7.166600] [ cut here ] [7.171676] WARNING: CPU: 0 PID: 54 at mm/mmap.c:2859 exit_mmap+0x1a8/0x21c() [7.179194] Modules linked in: [7.182479] CPU: 0 PID: 54 Comm: init Not tainted 3.19.0-rc5-next-20150119-2-gfdefcded1272 #1 [7.191863] Hardware name: Generic AM33XX (Flattened Device Tree) [7.198318] [c00153f0] (unwind_backtrace) from [c0011a74] (show_stack+0x10/0x14) [7.206528] [c0011a74] (show_stack) from [c0580150] (dump_stack+0x78/0x94) [7.214191] [c0580150] (dump_stack) from [c003d4d0] (warn_slowpath_common+0x7c/0xb4) [7.222751] [c003d4d0] (warn_slowpath_common) from [c003d524] (warn_slowpath_null+0x1c/0x24) [7.232038] [c003d524] (warn_slowpath_null) from [c012de64] (exit_mmap+0x1a8/0x21c) [7.240536] [c012de64] (exit_mmap) from [c003abb8] (mmput+0x44/0xec) [7.247612] [c003abb8] (mmput) from [c0151368] (flush_old_exec+0x300/0x5a4) [7.255357] [c0151368] (flush_old_exec) from [c0195c10] (load_elf_binary+0x2ec/0x1144) [7.264111] [c0195c10] (load_elf_binary) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.273311] [c0150ea0] (search_binary_handler) from [c019554c] (load_script+0x260/0x280) [7.282232] [c019554c] (load_script) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.291066] [c0150ea0] (search_binary_handler) from [c0151f0c] (do_execveat_common+0x538/0x6c4) [7.300628] [c0151f0c] (do_execveat_common) from [c01520c4] (do_execve+0x2c/0x34) [7.308881] [c01520c4] (do_execve) from [c000e5e0] (ret_fast_syscall+0x0/0x4c) [7.316881] ---[ end trace 3b8a46b1b280f423 ]--- seems like it's caused by: b316feb3c37ff19cddcaf1f6b5056c633193257d is the first bad commit Adding Kiryl to the loop. git bisect start # good: [ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc] Linux 3.19-rc5 git bisect good ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc # bad: [a0d4287f787889e59db0fd295853a0f1f55d0699] Add linux-next specific files for 20150119 git bisect bad a0d4287f787889e59db0fd295853a0f1f55d0699 # good: [1c2f70b77b8ca77f10c59d479d009e07359d00d2] Merge remote-tracking branch 'drm/drm-next' git bisect good 1c2f70b77b8ca77f10c59d479d009e07359d00d2 # good: [73c1390843223d8bfc85795c560c36b3d0ffee40] Merge remote-tracking branch 'leds/for-next' git bisect good 73c1390843223d8bfc85795c560c36b3d0ffee40 # good: [7bc6bef35d48e91ad796b6eead7304998842c782] Merge remote-tracking branch 'pinctrl/for-next' git bisect good 7bc6bef35d48e91ad796b6eead7304998842c782 # bad: [45e1eaa38732ffa3de0d18fe95d2d2b960a7c777] lib: bitmap: change bitmap_shift_right to take unsigned parameters git bisect bad 45e1eaa38732ffa3de0d18fe95d2d2b960a7c777 # good: [c82a73a0369a7dd6dcfaf9e6bd572a4e5deda223] mm, page_alloc: reduce number of alloc_pages* functions' parameters git bisect good c82a73a0369a7dd6dcfaf9e6bd572a4e5deda223 # bad: [0b1c810fbc4bbff7e314dd6ff91c2b4af499199d] mm: don't split THP page when syscall is called git bisect bad 0b1c810fbc4bbff7e314dd6ff91c2b4af499199d # good: [54faa439355a9ae476a446429967e9e38f04363e] oom, PM: make OOM detection in the freezer path raceless git bisect good 54faa439355a9ae476a446429967e9e38f04363e # bad: [b6c9f11c6b6993303067f7c04a73258226a6e77e] mm/compaction: add tracepoint to observe behaviour of compaction defer git bisect bad b6c9f11c6b6993303067f7c04a73258226a6e77e # good: [9ce5d3fb13a80f28db450de4ecf2727893e99c93] mm: pagemap_read: limit scan to virtual region being asked git bisect good 9ce5d3fb13a80f28db450de4ecf2727893e99c93 # bad: [1a7a376546ca56e7750987c15d0c7541c17a512c] mm/compaction: change tracepoint format from decimal to hexadecimal git bisect bad 1a7a376546ca56e7750987c15d0c7541c17a512c # bad: [4081187ff19cf2186010c003939c17d70d0bbb27] page_writeback: put account_page_redirty() after set_page_dirty() git bisect bad 4081187ff19cf2186010c003939c17d70d0bbb27 # bad: [b316feb3c37ff19cddcaf1f6b5056c633193257d] mm: account pmd page tables to the process git bisect bad b316feb3c37ff19cddcaf1f6b5056c633193257d # first bad commit: [b316feb3c37ff19cddcaf1f6b5056c633193257d] mm: account pmd page tables to the process I've added a dump_mm() call when the bug happens followed by a while (true) loop (to avoid constant reprinting of the same thing), here's what I get: [7.235903] [ cut here ] [7.240881] WARNING: CPU: 0 PID: 58 at mm/mmap.c:2859 exit_mmap+0x1b4/0x218() [7.248369] Modules linked in: ipv6 autofs4 [7.252792] CPU: 0 PID: 58 Comm: systemd Not tainted 3.19.0-rc5-next-20150119-dirty #888 [7.261274] Hardware name: Generic AM43 (Flattened Device Tree) [7.267512] [c0015afc] (unwind_backtrace) from [c001221c] (show_stack+0x10/0x14) [
[next-20150119]regression (mm)?
Hi, Most platforms seem broken intoday's next tag. https://github.com/nmenon/kernel-test-logs/tree/next-20150119 (defconfig: omap2plus_defconfig) [7.166600] [ cut here ] [7.171676] WARNING: CPU: 0 PID: 54 at mm/mmap.c:2859 exit_mmap+0x1a8/0x21c() [7.179194] Modules linked in: [7.182479] CPU: 0 PID: 54 Comm: init Not tainted 3.19.0-rc5-next-20150119-2-gfdefcded1272 #1 [7.191863] Hardware name: Generic AM33XX (Flattened Device Tree) [7.198318] [c00153f0] (unwind_backtrace) from [c0011a74] (show_stack+0x10/0x14) [7.206528] [c0011a74] (show_stack) from [c0580150] (dump_stack+0x78/0x94) [7.214191] [c0580150] (dump_stack) from [c003d4d0] (warn_slowpath_common+0x7c/0xb4) [7.222751] [c003d4d0] (warn_slowpath_common) from [c003d524] (warn_slowpath_null+0x1c/0x24) [7.232038] [c003d524] (warn_slowpath_null) from [c012de64] (exit_mmap+0x1a8/0x21c) [7.240536] [c012de64] (exit_mmap) from [c003abb8] (mmput+0x44/0xec) [7.247612] [c003abb8] (mmput) from [c0151368] (flush_old_exec+0x300/0x5a4) [7.255357] [c0151368] (flush_old_exec) from [c0195c10] (load_elf_binary+0x2ec/0x1144) [7.264111] [c0195c10] (load_elf_binary) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.273311] [c0150ea0] (search_binary_handler) from [c019554c] (load_script+0x260/0x280) [7.282232] [c019554c] (load_script) from [c0150ea0] (search_binary_handler+0x88/0x1ac) [7.291066] [c0150ea0] (search_binary_handler) from [c0151f0c] (do_execveat_common+0x538/0x6c4) [7.300628] [c0151f0c] (do_execveat_common) from [c01520c4] (do_execve+0x2c/0x34) [7.308881] [c01520c4] (do_execve) from [c000e5e0] (ret_fast_syscall+0x0/0x4c) [7.316881] ---[ end trace 3b8a46b1b280f423 ]--- -- Regards, Nishanth Menon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
