linaro-kernel

linaro-kernel@lists.linaro.org

10095 discussions

[RFC PATCH 0/2] Add support for Samsung GH7 PCIe controller

by Jingoo Han

This patch adds support for Samsung GH7 PCIe host controller. Samsung GH7 PCIe controller driver has dependency on the PCI arm64 arch support. So, the Liviu Dudau's patcheset for creating generic host_bridge from device tree [1] and supporting PCI in AArch64 [2] are required. This patch is marked as RFC, so any comment will be welcomed. Thank you. [1] http://www.spinics.net/lists/linux-pci/msg29786.html [2] http://www.spinics.net/lists/linux-pci/msg29793.html Jingoo Han (2) PCI: designware: Add ARM64 PCI support PCI: exynos: Add PCIe support for Samsung GH7 SoC --- drivers/pci/host/Kconfig | 2 +- drivers/pci/host/pci-exynos.c | 135 +++++++++++++++++++++++++++++++++--- drivers/pci/host/pcie-designware.c | 32 +++++++++ 3 files changed, 158 insertions(+), 11 deletions(-) Best regards, Jingoo Han

11 years, 2 months

[PATCH 01/13] video: sh_mobile_lcdcfb depends on meram

by Peter Griffin

From: Arnd Bergmann <arnd(a)arndb.de> The sh_mobile_lcdcfb driver calls interfaces provided by the corresponding "meram" helper. This fails if meram is a module but lcdcfb is built-in. To work around it, this uses special Kconfig magic to only allow lcdcfb to be built if a) both are modules, b) meram is built-in, or c) meram is disabled and the helpers stubbed out Changing meram from 'y' to 'm' now forces clcd to be a module as well, which seems to be the desired behavior. Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> Signed-off-by: Peter Griffin <peter.griffin(a)linaro.org> Cc: Simon Horman <horms+renesas(a)verge.net.au> Cc: Magnus Damm <magnus.damm(a)gmail.com> Cc: linux-sh(a)vger.kernel.org Cc: Jean-Christophe Plagniol-Villard <plagnioj(a)jcrosoft.com> Cc: Tomi Valkeinen <tomi.valkeinen(a)ti.com> Cc: linux-fbdev(a)vger.kernel.org --- drivers/video/fbdev/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig index e1f4727..a4116bf 100644 --- a/drivers/video/fbdev/Kconfig +++ b/drivers/video/fbdev/Kconfig @@ -1971,6 +1971,7 @@ config FB_W100 config FB_SH_MOBILE_LCDC tristate "SuperH Mobile LCDC framebuffer support" depends on FB && (SUPERH || ARCH_SHMOBILE) && HAVE_CLK + depends on FB_SH_MOBILE_MERAM || !FB_SH_MOBILE_MERAM select FB_SYS_FILLRECT select FB_SYS_COPYAREA select FB_SYS_IMAGEBLIT -- 1.7.9.5

11 years, 2 months

[PATCH 3.11 155/182] tick-common: Fix wrong check in tick_check_replacement()

by Luis Henriques

3.11.10.9 -stable review patch. If anyone has any objections, please let me know. ------------------ From: Viresh Kumar <viresh.kumar(a)linaro.org> commit 521c42990e9d561ed5ed9f501f07639d0512b3c9 upstream. tick_check_replacement() returns if a replacement of clock_event_device is possible or not. It does this as the first check: if (tick_check_percpu(curdev, newdev, smp_processor_id())) return false; Thats wrong. tick_check_percpu() returns true when the device is useable. Check for false instead. [ tglx: Massaged changelog ] Signed-off-by: Viresh Kumar <viresh.kumar(a)linaro.org> Cc: linaro-kernel(a)lists.linaro.org Cc: fweisbec(a)gmail.com Cc: Arvind.Chauhan(a)arm.com Cc: linaro-networking(a)linaro.org Link: http://lkml.kernel.org/r/486a02efe0246635aaba786e24b42d316438bf3b.139753798… Signed-off-by: Thomas Gleixner <tglx(a)linutronix.de> Signed-off-by: Luis Henriques <luis.henriques(a)canonical.com> --- kernel/time/tick-common.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/time/tick-common.c b/kernel/time/tick-common.c index 64522ec..271ce26 100644 --- a/kernel/time/tick-common.c +++ b/kernel/time/tick-common.c @@ -260,7 +260,7 @@ static bool tick_check_preferred(struct clock_event_device *curdev, bool tick_check_replacement(struct clock_event_device *curdev, struct clock_event_device *newdev) { - if (tick_check_percpu(curdev, newdev, smp_processor_id())) + if (!tick_check_percpu(curdev, newdev, smp_processor_id())) return false; return tick_check_preferred(curdev, newdev); -- 1.9.1

11 years, 2 months

[Query]: hrtimers: why don't we consider hrtimers in get_next_timer_interrupt()

by Viresh Kumar

Hi, File: hrtimer.c Function: hrtimer_get_next_event() I was looking closely at what's waking up my system and found this piece of code: ktime_t hrtimer_get_next_event(void) { if (!hrtimer_hres_active()) { find next hrtimer event .... } } Which probably means that: "don't consider hrtimers for getting next timer event if we are running ticks in high resolution mode". And I couldn't understand why is it so? When hres_active isn't set, we run hrtimer handlers from timer handlers, which means that timers would be sufficient in finding the next event and we don't need to check for hrtimers. But when hres_active is set, hrtimers could be set to fire before the next timer event and so we must take them into account. I am new to this whole world of core frameworks and might be missing something very very obvious. But its always better to ask than to ignore and think that things are probably fine and just shut up. Thanks for your patience during my learning curve :) -- viresh

11 years, 2 months

mainline boot: 48 pass, 0 fail (v3.15-rc2-69-g1aae31c)

by Kevin's boot bot

Tree/Branch: mainline Git describe: v3.15-rc2-69-g1aae31c Full Report =========== arm-davinci_all_defconfig ------------------------- legacy,dm365evm 0 min 17.6 sec: PASS da850-evm 0 min 15.7 sec: PASS arm-tegra_defconfig ------------------- tegra30-beaver 0 min 17.3 sec: PASS arm-omap2plus_defconfig ----------------------- legacy,3730xm 0 min 51.6 sec: PASS am335x-boneblack 0 min 44.5 sec: PASS omap3-beagle-xm 0 min 58.1 sec: PASS legacy,3530beagle 0 min 36.8 sec: PASS (Warnings: 1) omap4-panda 1 min 7.6 sec: PASS omap3-overo-tobi 0 min 23.4 sec: PASS (Warnings: 1) am335x-bone 0 min 27.4 sec: PASS omap3-overo-storm-tobi 0 min 24.9 sec: PASS omap5-uevm 1 min 8.2 sec: PASS (Warnings: 1) omap3-n900 0 min 42.3 sec: PASS (Warnings: 1) legacy,n900 0 min 48.5 sec: PASS (Warnings: 1) omap4-panda-es 1 min 1.3 sec: PASS legacy,3730storm 0 min 20.4 sec: PASS legacy,3530overo 0 min 21.0 sec: PASS (Warnings: 1) arm-imx_v6_v7_defconfig ----------------------- imx6dl-wandboard,wand-dual 0 min 18.9 sec: PASS imx6dl-wandboard,wand-solo 0 min 18.7 sec: PASS imx6q-wandboard 0 min 17.2 sec: PASS arm-multi_v7_defconfig ---------------------- qcom-apq8074-dragonboard 0 min 17.0 sec: PASS ste-snowball 1 min 18.4 sec: PASS tegra30-beaver 0 min 19.6 sec: PASS am335x-boneblack 0 min 42.3 sec: PASS omap3-beagle-xm 0 min 49.3 sec: PASS sun7i-a20-cubieboard2 0 min 12.4 sec: PASS armada-370-mirabox 0 min 22.4 sec: PASS omap4-panda 0 min 53.0 sec: PASS armada-xp-openblocks-ax3-4 0 min 25.3 sec: PASS sun4i-a10-cubieboard 0 min 18.7 sec: PASS bcm28155-ap 0 min 26.2 sec: PASS omap3-overo-tobi 0 min 25.2 sec: PASS (Warnings: 1) imx6dl-wandboard,wand-solo 0 min 18.5 sec: PASS am335x-bone 0 min 26.9 sec: PASS omap3-overo-storm-tobi 0 min 23.8 sec: PASS omap5-uevm 1 min 42.2 sec: PASS (Warnings: 1) omap3-n900 0 min 35.1 sec: PASS (Warnings: 1) imx6q-wandboard 0 min 16.6 sec: PASS omap4-panda-es 0 min 53.9 sec: PASS imx6dl-wandboard,wand-dual 0 min 18.2 sec: PASS arm-sunxi_defconfig ------------------- sun7i-a20-cubieboard2 0 min 22.9 sec: PASS sun4i-a10-cubieboard 0 min 18.0 sec: PASS arm-bcm_defconfig ----------------- bcm28155-ap 0 min 23.9 sec: PASS arm-exynos_defconfig -------------------- exynos5250-arndale 0 min 27.2 sec: PASS arm-u8500_defconfig ------------------- ste-snowball 0 min 30.2 sec: PASS arm-mvebu_v7_defconfig ---------------------- armada-xp-openblocks-ax3-4 0 min 22.2 sec: PASS armada-370-mirabox 0 min 20.2 sec: PASS arm-sama5_defconfig ------------------- sama5d35ek 0 min 17.3 sec: PASS

11 years, 2 months

[PATCH] ARM64: disable DCACHE_WORD_ACCESS in big endian case

by Victor Kamensky

If DCACHE_WORD_ACCESS is enabled big endian image failed to boot. commit 7bc13fd33adb9536bd73965cd46bbf7377df097c "arm64: dcache: select DCACHE_WORD_ACCESS for little-endian CPUs" enabled this setting for both big endian and little endian cpus. And code in commit itself seems to be endian agnostic, however other, i.e C, code that sits under DCACHE_WORD_ACCESS seems to be not endian agnostic, I could not figure out where though. Solution is to enable DCACHE_WORD_ACCESS only if little endian mode is enabled (default). Signed-off-by: Victor Kamensky <victor.kamensky(a)linaro.org> --- arch/arm64/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig index e6e4d37..106ac4f 100644 --- a/arch/arm64/Kconfig +++ b/arch/arm64/Kconfig @@ -13,7 +13,7 @@ config ARM64 select CLONE_BACKWARDS select COMMON_CLK select CPU_PM if (SUSPEND || CPU_IDLE) - select DCACHE_WORD_ACCESS + select DCACHE_WORD_ACCESS if !CPU_BIG_ENDIAN select GENERIC_CLOCKEVENTS select GENERIC_CLOCKEVENTS_BROADCAST if SMP select GENERIC_CPU_AUTOPROBE -- 1.8.1.4

11 years, 2 months

[PATCH v2] ARM: uprobes need icache flush after xol write

by Victor Kamensky

Hi Guys, This second version of patch to flush icache and dcache after uprobes xol write to make written instruction available in icache. Please see [1] for initial discussion. This patch follows Russell's suggestion, and function that does cache flush after xol slot instruction write is shared/reused with similar one implemented already for ptrace code. In order to reuse common implementation but to avoid vma use by xol_get_insn_slot I split flush_ptrace_access into two functions. Where first part retrieves all required conditions from vma and places them into flags variable and then calls second function which is common code. Also I had to change xol_get_insn_slot function to map page into kernel explicitly within function without use of copy_to_page helper because ARM cache flush code need both kernel address through which instruction write happens and virtual address of user-land process where instruction will end up. I hope this call back is universal enough so other CPU could implement their cache invalidation/sync after uprobes xol instruction write logic based on provided parameters. I've tested it on Arndale board with my SystemTap test case that had cache problem before. Disassemble of flush_uprobe_xol_access in case of Arndale shows that compiler does good job and optimizes out all flags check effectively leaving on this cpu call to flush_icache_alias or call to v7_coherent_user_range (__cpuc_coherent_kern_range). Also tested basic user-level debugging. Wondering on what ARM boards/cpus could we test cache_is_vivt() and cache_is_vipt_aliasing cases ... Just to summarize, please note on [1] there were couple other suggestions: Oleg suggested to use flush_icache_user_range but Russell argument was that meaning of the function is lost and on ARM it is not implemented in such way that it could address the issue anyway. Please see [2] for details. Note it would has vma problem use or not, that should be hacked. Dave Martin suggested to use flush_icache_range, which is effectively better way to call __cpuc_coherent_[kern|user]_range(s,e), that was originally suggested. But Russell explained that it won't be enough in case of user-land process pages and variety of cache types have to be covered. Note for kernel pages it would be OK and it is used in multiple places like kprobes, modules, etc. Thanks, Victor [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/245595.html http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/245427.html [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-April/245605.html Victor Kamensky (1): ARM: uprobes need icache flush after xol write arch/arm/include/asm/cacheflush.h | 2 ++ arch/arm/kernel/uprobes.c | 6 ++++++ arch/arm/mm/flush.c | 41 +++++++++++++++++++++++++++++++++------ include/linux/uprobes.h | 3 +++ kernel/events/uprobes.c | 33 +++++++++++++++++++++++++------ 5 files changed, 73 insertions(+), 12 deletions(-) -- 1.8.1.4

11 years, 2 months

Re: [PATCH] Input: ads7877: Remove bitrotted comment

by Mark Brown

On Tue, Apr 22, 2014 at 05:39:28PM -0700, Dmitry Torokhov wrote: > On Tue, Apr 22, 2014 at 10:18:21PM +0100, Mark Brown wrote: > > Remove the bitrotted comment, though in actual fact the use case mentioned > > is a great use for spi_async() since it would cut down on latency handling > > the interrupt by saving us a context switch before we start SPI. > > This was previously implemented, it was removed in commit b534422b2d11 > > (Input: ad7877 - switch to using threaded IRQ) for code complexity reasons. > > It may be better to revert that commit instead. > Hmm, maybe.. although I think original would cause device 'stuck' if > call to spi_async() fails, so probably not a straight revert... Probably best just to apply this, then - someone can always reimplement if they need to.

11 years, 2 months

next boot: 47 pass, 4 fail (next-20140422)

by Kevin's boot bot

Tree/Branch: next Git describe: next-20140422 Failed boot tests (console logs at the end) =========================================== legacy,3730xm: FAIL: omap2plus_defconfig omap5-uevm: FAIL: omap2plus_defconfig legacy,3530overo: FAIL: omap2plus_defconfig exynos5420-arndale-octa: FAIL: exynos_defconfig Full Report =========== omap2plus_defconfig ------------------- legacy,3730xm 2 min 52.2 sec: FAIL am335x-boneblack 0 min 44.3 sec: PASS omap3-beagle-xm 0 min 58.1 sec: PASS legacy,3530beagle 0 min 35.0 sec: PASS (Warnings: 1) omap4-panda 1 min 18.4 sec: PASS omap3-overo-tobi 0 min 23.2 sec: PASS (Warnings: 1) am335x-bone 0 min 27.6 sec: PASS omap3-overo-storm-tobi 0 min 24.8 sec: PASS omap5-uevm 1 min 11.2 sec: FAIL omap3-n900 0 min 43.5 sec: PASS (Warnings: 1) legacy,n900 0 min 43.4 sec: PASS (Warnings: 1) omap4-panda-es 1 min 21.8 sec: PASS legacy,3730storm 0 min 23.1 sec: PASS legacy,3530overo 0 min 20.3 sec: FAIL (Warnings: 1) multi_lpae_defconfig -------------------- omap5-uevm 1 min 34.9 sec: PASS (Warnings: 1) sun7i-a20-cubieboard2 0 min 12.4 sec: PASS tegra_defconfig --------------- tegra30-beaver 0 min 17.5 sec: PASS imx_v6_v7_defconfig ------------------- imx6dl-wandboard,wand-dual 0 min 18.7 sec: PASS imx6dl-wandboard,wand-solo 0 min 18.9 sec: PASS imx6q-wandboard 0 min 17.3 sec: PASS sunxi_defconfig --------------- sun7i-a20-cubieboard2 0 min 22.4 sec: PASS sun4i-a10-cubieboard 0 min 17.7 sec: PASS bcm_defconfig ------------- bcm28155-ap 0 min 23.2 sec: PASS mvebu_v7_defconfig ------------------ armada-xp-openblocks-ax3-4 0 min 22.2 sec: PASS armada-370-mirabox 0 min 20.3 sec: PASS exynos_defconfig ---------------- exynos5420-arndale-octa 0 min 38.2 sec: FAIL exynos5250-arndale 0 min 30.3 sec: PASS multi_v7_defconfig ------------------ qcom-apq8074-dragonboard 0 min 16.4 sec: PASS ste-snowball 1 min 20.7 sec: PASS tegra30-beaver 0 min 17.1 sec: PASS am335x-boneblack 0 min 38.3 sec: PASS omap3-beagle-xm 0 min 46.1 sec: PASS sun7i-a20-cubieboard2 0 min 12.4 sec: PASS armada-370-mirabox 0 min 19.6 sec: PASS omap4-panda 0 min 55.0 sec: PASS armada-xp-openblocks-ax3-4 0 min 26.7 sec: PASS sun4i-a10-cubieboard 0 min 17.4 sec: PASS bcm28155-ap 0 min 27.7 sec: PASS omap3-overo-tobi 0 min 22.5 sec: PASS (Warnings: 1) imx6dl-wandboard,wand-solo 0 min 18.3 sec: PASS am335x-bone 0 min 26.7 sec: PASS omap3-overo-storm-tobi 0 min 23.9 sec: PASS omap5-uevm 1 min 36.9 sec: PASS (Warnings: 1) omap3-n900 0 min 39.8 sec: PASS (Warnings: 1) imx6q-wandboard 0 min 17.2 sec: PASS omap4-panda-es 0 min 50.6 sec: PASS imx6dl-wandboard,wand-dual 0 min 18.3 sec: PASS u8500_defconfig --------------- ste-snowball 0 min 31.0 sec: PASS sama5_defconfig --------------- sama5d35ek 0 min 17.3 sec: PASS davinci_all_defconfig --------------------- legacy,dm365evm 0 min 17.5 sec: PASS da850-evm 0 min 15.7 sec: PASS Console logs for failures ========================= omap2plus_defconfig ------------------- legacy,3730xm: FAIL: last 80 lines of boot log: ----------------------------------------------- [ 0.854461] Key type id_resolver registered [ 0.854492] Key type id_legacy registered [ 0.854675] jffs2: version 2.2. (NAND) (SUMMARY) B) 2001-2006 Red Hat, Inc. [ 0.855590] msgmni has been set to 979 [ 0.862762] io scheduler noop registered [ 0.862823] io scheduler deadline registered [ 0.862915] io scheduler cfq registered (default) [ 0.867523] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 0.876220] omap_uart omap_uart.0: no wakeirq for uart0 [ 0.878021] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 88, base_baud = 3000000) is a OMAP UART0 [ 0.880218] omap_uart omap_uart.1: no wakeirq for uart0 [ 0.881378] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 89, base_baud = 3000000) is a OMAP UART1 [ 0.882873] omap_uart omap_uart.2: no wakeirq for uart0 [ 0.883728] omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 90, base_baud = 3000000) is a OMAP UART2 [ 1.619354] console [ttyO2] enabled [ 1.625732] omap_uart omap_uart.3: no wakeirq for uart0 [ 1.632293] omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 96, base_baud = 3000000) is a OMAP UART3 [ 1.682739] brd: module loaded [ 1.708679] loop: module loaded [ 1.731109] twl 1-0048: PIH (irq 23) chaining IRQs 338..346 [ 1.737609] twl 1-0048: power (irq 343) chaining IRQs 346..353 [ 1.749114] twl4030_gpio twl4030_gpio: gpio (irq 338) chaining IRQs 354..371 [ 1.763580] platform usb_phy_gen_xceiv.2: Driver usb_phy_gen_xceiv requests probe deferral [ 1.778625] hsusb2_vcc: at 3300 mV [ 1.786254] vdd_mpu_iva: 600 <--> 1450 mV normal [ 1.793823] vdd_core: 600 <--> 1450 mV normal [ 1.801544] VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby [ 1.811859] VDAC: 1800 mV normal standby [ 1.818817] VDVI: 1800 mV normal standby [ 1.826904] VSIM: 1800 <--> 3000 mV at 1800 mV normal standby [ 1.841491] mtdoops: mtd device (mtddev=name/number) must be supplied [ 1.860382] usbcore: registered new interface driver asix [ 1.866363] usbcore: registered new interface driver ax88179_178a [ 1.872894] usbcore: registered new interface driver cdc_ether [ 1.879302] usbcore: registered new interface driver smsc95xx [ 1.885528] usbcore: registered new interface driver net1080 [ 1.891601] usbcore: registered new interface driver cdc_subset [ 1.898010] usbcore: registered new interface driver zaurus [ 1.904174] usbcore: registered new interface driver cdc_ncm [ 1.911651] usbcore: registered new interface driver cdc_wdm [ 1.917907] usbcore: registered new interface driver usb-storage [ 1.924468] usbcore: registered new interface driver usbtest [ 1.939544] mousedev: PS/2 mouse device common for all mice [ 1.952545] input: twl4030_pwrbutton as /devices/platform/omap_i2c.1/i2c-1/1-004b/twl4030_pwrbutton/input/input0 [ 1.971130] twl_rtc twl_rtc: Power up reset detected. [ 1.978454] twl_rtc twl_rtc: Enabling TWL-RTC [ 1.991790] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 [ 2.001312] i2c /dev entries driver [ 2.008056] Driver for 1-wire Dallas network protocol. [ 2.020385] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec [ 2.408294] ledtrig-cpu: registered to indicate activity on CPUs [ 2.415466] usbcore: registered new interface driver usbhid [ 2.421295] usbhid: USB HID core driver [ 2.426788] oprofile: using arm/armv7 [ 2.431427] TCP: cubic registered [ 2.434936] Initializing XFRM netlink socket [ 2.439636] NET: Registered protocol family 17 [ 2.444396] NET: Registered protocol family 15 [ 2.449554] Key type dns_resolver registered [ 2.469543] ThumbEE CPU extension supported. [ 2.474121] Registering SWP/SWPB emulation handler [ 2.493530] VDVI: incomplete constraints, leaving on [ 2.500579] VDAC: incomplete constraints, leaving on [ 2.505981] hsusb2_vcc: incomplete constraints, leaving on [ 2.518554] input: gpio-keys as /devices/platform/gpio-keys/input/input1 [ 2.529388] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800) [ 2.615051] mmc0: host does not support reading read-only switch. assuming write-enable. [ 2.626770] mmc0: new high speed SDHC card at address 1234 [ 2.636322] mmcblk0: mmc0:1234 SA04G 3.63 GiB [ 2.649536] mmcblk0: p1 p2 [ 14.756835] EXT4-fs (mmcblk0p2): recovery complete [ 14.762451] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 14.771179] VFS: Mounted root (ext4 filesystem) on device 179:2. [ 14.782043] devtmpfs: mounted [ 14.786254] Freeing unused kernel memory: 388K (c07a3000 - c0804000) [ 113.016174] random: nonblocking pool is initialized ~$off # PYBOOT: Exception: userspace: ERROR: Never found root shell # PYBOOT: Time: 172.19 seconds. # PYBOOT: Result: FAIL omap5-uevm: FAIL: last 80 lines of boot log: -------------------------------------------- U-Boot# if test -n ${preboot}; then run preboot; fi if test -n ${preboot}; then run preboot; fi (Re)start USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... found: 002/033 2 3 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found U-Boot# setenv autoload no; setenv autoboot no setenv autoload no; setenv autoboot no U-Boot# dhcp dhcp Waiting for Ethernet connection... done. BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.1.200 U-Boot# setenv serverip 192.168.1.2 setenv serverip 192.168.1.2 U-Boot# if test -n ${netargs}; then run netargs; fi if test -n ${netargs}; then run netargs; fi U-Boot# tftp 0x82000000 192.168.1.2:tmp/omap5uevm-HPfgCa/zImage tftp 0x82000000 192.168.1.2:tmp/omap5uevm-HPfgCa/zImage Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.200 Filename 'tmp/omap5uevm-HPfgCa/zImage'. Load address: 0x82000000 Loading: *T ################################################################# ################################################################# ################################################################# ################################################################# ################################### 608.4 KiB/s done Bytes transferred = 4317152 (41dfe0 hex) U-Boot# tftp 0x81000000 192.168.1.2:buildroot.cpio.gz.uboot tftp 0x81000000 192.168.1.2:buildroot.cpio.gz.uboot Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.200 Filename 'buildroot.cpio.gz.uboot'. Load address: 0x81000000 Loading: *T ############################################ 111.3 KiB/s done Bytes transferred = 642602 (9ce2a hex) U-Boot# tftp 0x80f80000 192.168.1.2:tmp/omap5uevm-HPfgCa/omap5-uevm.dtb tftp 0x80f80000 192.168.1.2:tmp/omap5uevm-HPfgCa/omap5-uevm.dtb Waiting for Ethernet connection... done. Using sms0 device TFTP from server 192.168.1.2; our IP address is 192.168.1.200 Filename 'tmp/omap5uevm-HPfgCa/omap5-uevm.dtb'. Load address: 0x80f80000 Loading: *T #### 7.8 KiB/s done Bytes transferred = 44972 (afac hex) U-Boot# printenv bootargs printenv bootargs bootargs=console=ttyO2,115200n8 debug earlyprintk ip=192.168.1.200:192.168.1.2:192.168.1.254:255.255.255.0:::none:192.168.1.254 U-Boot# bootz 0x82000000 0x81000000 0x80f80000 bootz 0x82000000 0x81000000 0x80f80000 Kernel image @ 0x82000000 [ 0x000000 - 0x41dfe0 ] ## Loading init Ramdisk from Legacy Image at 81000000 ... Image Name: Image Type: ARM Linux RAMDisk Image (uncompressed) Data Size: 642538 Bytes = 627.5 KiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Using Device Tree in place at 80f80000, end 80f8dfab Starting kernel ... ~$off # PYBOOT: Exception: kernel: ERROR: did not start booting. # PYBOOT: Time: 71.17 seconds. # PYBOOT: Result: FAIL legacy,3530overo: FAIL: last 80 lines of boot log: -------------------------------------------------- [ 2.112182] twl 1-0048: PIH (irq 23) chaining IRQs 338..346 [ 2.118713] twl 1-0048: power (irq 343) chaining IRQs 346..353 [ 2.130645] twl4030_gpio twl4030_gpio: gpio (irq 338) chaining IRQs 354..371 [ 2.139221] gpiochip_find_base: found new base at 492 [ 2.145629] gpiochip_add: registered GPIOs 492 to 511 on device: twl4030 [ 2.156646] vdd_mpu_iva: 600 <--> 1450 mV normal [ 2.165466] vdd_core: 600 <--> 1450 mV normal [ 2.173828] VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby [ 2.184387] VDAC: 1800 mV normal standby [ 2.191406] VDVI: 1800 mV normal standby [ 2.203826] mtdoops: mtd device (mtddev=name/number) must be supplied [ 2.382659] libphy: smsc911x-mdio: probed [ 2.460845] smsc911x smsc911x.0 eth0: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=smsc911x-0:01, irq=-1) [ 2.472137] smsc911x smsc911x.0 eth0: MAC Address: 2e:9e:5e:9e:2a:4a [ 2.482421] usbcore: registered new interface driver asix [ 2.488311] usbcore: registered new interface driver ax88179_178a [ 2.495086] usbcore: registered new interface driver cdc_ether [ 2.501556] usbcore: registered new interface driver smsc95xx [ 2.507812] usbcore: registered new interface driver net1080 [ 2.514007] usbcore: registered new interface driver cdc_subset [ 2.520507] usbcore: registered new interface driver zaurus [ 2.526702] usbcore: registered new interface driver cdc_ncm [ 2.534667] usbcore: registered new interface driver cdc_wdm [ 2.541076] usbcore: registered new interface driver usb-storage [ 2.547668] usbcore: registered new interface driver usbtest [ 2.556915] mousedev: PS/2 mouse device common for all mice [ 2.567871] ads7846 spi1.0: touchscreen, irq 228 [ 2.575683] input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi_master/spi1/spi1.0/input/input0 [ 2.592895] input: twl4030_pwrbutton as /devices/platform/omap_i2c.1/i2c-1/1-004b/twl4030_pwrbutton/input/input1 [ 2.608551] twl_rtc twl_rtc: Power up reset detected. [ 2.614776] twl_rtc twl_rtc: Enabling TWL-RTC [ 2.629364] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0 [ 2.639221] i2c /dev entries driver [ 2.647216] Driver for 1-wire Dallas network protocol. [ 2.658416] omap_wdt: OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec [ 3.041229] omap_hsmmc omap_hsmmc.1: unable to get vmmc regulator -517 [ 3.048675] platform omap_hsmmc.1: Driver omap_hsmmc requests probe deferral [ 3.067108] ledtrig-cpu: registered to indicate activity on CPUs [ 3.074462] usbcore: registered new interface driver usbhid [ 3.080383] usbhid: USB HID core driver [ 3.086090] oprofile: using arm/armv7 [ 3.091033] TCP: cubic registered [ 3.094543] Initializing XFRM netlink socket [ 3.099182] NET: Registered protocol family 17 [ 3.104064] NET: Registered protocol family 15 [ 3.109252] Key type dns_resolver registered [ 3.141632] ThumbEE CPU extension supported. [ 3.146179] Registering SWP/SWPB emulation handler [ 3.161346] VDVI: incomplete constraints, leaving on [ 3.167236] VDAC: incomplete constraints, leaving on [ 3.175292] omap_hsmmc omap_hsmmc.1: unable to get vmmc regulator -517 [ 3.182708] platform omap_hsmmc.1: Driver omap_hsmmc requests probe deferral [ 3.195281] input: gpio-keys as /devices/platform/gpio-keys/input/input2 [ 3.207672] omap_hsmmc omap_hsmmc.1: unable to get vmmc regulator -517 [ 3.214965] platform omap_hsmmc.1: Driver omap_hsmmc requests probe deferral [ 3.225280] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:14 UTC (946684814) [ 3.410247] smsc911x smsc911x.0 eth0: SMSC911x/921x identified at 0xe087c000, IRQ: 290 [ 3.431213] IP-Config: Complete: [ 3.434600] device=eth0, hwaddr=2e:9e:5e:9e:2a:4a, ipaddr=192.168.1.155, mask=255.255.255.0, gw=192.168.1.254 [ 3.445587] host=192.168.1.155, domain=, nis-domain=(none) [ 3.451843] bootserver=192.168.1.2, rootserver=192.168.1.2, rootpath= [ 3.458862] nameserver0=192.168.1.254 [ 3.468688] Waiting for root device /dev/mmcblk0p2... [ 3.490997] mmc0: host does not support reading read-only switch. assuming write-enable. [ 3.506500] mmc0: new high speed SDHC card at address aaaa [ 3.516693] mmcblk0: mmc0:aaaa SU04G 3.69 GiB [ 3.537384] mmcblk0: p1 p2 [ 3.547332] omap_hsmmc omap_hsmmc.1: unable to get vmmc regulator -517 [ 3.554656] platform omap_hsmmc.1: Driver omap_hsmmc requests probe deferral [ 3.623046] EXT4-fs (mmcblk0p2): recovery complete [ 3.628875] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 3.637664] VFS: Mounted root (ext4 filesystem) on device 179:2. [ 3.649719] devtmpfs: error mounting -2 [ 3.655181] Freeing unused kernel memory: 388K (c07a3000 - c0804000) [ 3.662841] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. ~$off # PYBOOT: Exception: userspace: failed to find root shell: Kernel panic # PYBOOT: Time: 20.29 seconds. # PYBOOT: Warnings: 1 # PYBOOT: Result: FAIL exynos_defconfig ---------------- exynos5420-arndale-octa: FAIL: last 80 lines of boot log: --------------------------------------------------------- Connected to octa console [channel connected] (~$quit to exit) (user:khilman) is already connected ~$hardreset Command(octa console)> hardreset (user:khilman) Reboot octa 0 Reboot: octa ; phidget 3 6 : off, sleep, on U-Boot 2012.07-00001-g02b1decad082 (Feb 24 2014 - 14:16:18) for ARNDALE OCTA CPU: Exynos5420 Rev2.0 [Samsung SOC on SMP Platform Base on ARM CortexA15] APLL = 800MHz, KPLL = 600MHz MPLL = 532MHz, BPLL = 800MHz Board: ARNDALE OCTA DRAM: 2 GiB WARNING: Caches not enabled TrustZone Enabled BSP BL1 version: Checking Boot Mode ... SDMMC MMC: S5P_MSHC2: 0, S5P_MSHC0: 1 MMC Device 0: 7.4 GiB MMC Device 1: 3.6 GiB MMC Device 2: MMC Device 2 not found there are pending interrupts 0x00000001 In: serial Out: serial Err: serial Net: No ethernet found. (Re)start USB... USB: Register 1313 NbrPorts 3 USB EHCI 1.00 scanning bus for devices... The request port(2) is not configured The request port(2) is not configured 3 USB Device(s) found scanning bus for storage devices... 0 Storage Device(s) found scanning usb for ethernet devices... 1 Ethernet Device(s) found Hit any key to stop autoboot: 1 0 ** Unable to use mmc 0:2 for fatload ** ** Unable to use mmc 0:2 for fatload ** ARNDALE # ~$off # PYBOOT: Exception: Timeout exceeded in read_nonblocking(). <pexpect.spawn object at 0x1bd8f90> version: 2.3 ($Revision: 399 $) command: /usr/bin/conmux-console args: ['/usr/bin/conmux-console', 'vence/octa'] searcher: searcher_re: 0: re.compile("ARNDALE #") buffer (last 100 chars): before (last 100 chars): after: <class 'pexpect.TIMEOUT'> match: None match_index: None exitstatus: None flag_eof: False pid: 30870 child_fd: 4 closed: False timeout: 30 delimiter: <class 'pexpect.EOF'> logfile: <open file 'boot-exynos5420-arndale-octa.log', mode 'w' at 0x7fc9d8cf9b70> logfile_read: None logfile_send: None maxread: 2000 ignorecase: False searchwindowsize: None delaybeforesend: 0.05 delayafterclose: 0.1 delayafterterminate: 0.1 # PYBOOT: Time: 38.22 seconds. # PYBOOT: Result: FAIL

11 years, 2 months

kdump for Linaro? Or any ARM Linux?

by Andy Nicholas

Hello, hopefully this is the correct mailing list for this question: I'm working on a derivative of the mainline Linux 3.8 kernel and I'm trying to enable ARM kdump functionality to collect crashdumps when we have kernel problems. But, there's some kind of unresolved issue in arch/arm/mm/ioremap.c which prevents /proc/vmcore from being able to function properly. I checked and this appears to still be in kernel.org Linux 3.13. The target is a normal, recent ARMv7 chip. Has this issue been addressed in any version of Linaro's kernel? Or, is there a work-around? If not, how does a crashdump file get generated when/if the Linaro kernel crashes or a driver faults? >> WARNING: at arch/arm/mm/ioremap.c:244 __arm_ioremap_pfn_caller+0x1d8/0x1f0() >> Modules linked in: >> [<c0016660>] (unwind_backtrace+0x0/0x138) from [<c0020480>] (warn_slowpath_common+0x4c/0x64) >> [<c0020480>] (warn_slowpath_common+0x4c/0x64) from [<c00204b4>] (warn_slowpath_null+0x1c/0x24) >> [<c00204b4>] (warn_slowpath_null+0x1c/0x24) from [<c0018e9c>] (__arm_ioremap_pfn_caller+0x1d8/0x1f0) >> [<c0018e9c>] (__arm_ioremap_pfn_caller+0x1d8/0x1f0) from [<c0018f20>] (__arm_ioremap_caller+0x54/0x5c) >> [<c0018f20>] (__arm_ioremap_caller+0x54/0x5c) from [<c0018c58>] (__arm_ioremap+0x18/0x1c) >> [<c0018c58>] (__arm_ioremap+0x18/0x1c) from [<c00168fc>] (copy_oldmem_page+0x34/0xc0) >> [<c00168fc>] (copy_oldmem_page+0x34/0xc0) from [<c010350c>] (read_from_oldmem+0xb8/0xe4) >> [<c010350c>] (read_from_oldmem+0xb8/0xe4) from [<c05c37e0>] (parse_crash_elf32_headers+0x184/0x43c) >> [<c05c37e0>] (parse_crash_elf32_headers+0x184/0x43c) from [<c05c3b64>] (vmcore_init+0xcc/0x198) >> [<c05c3b64>] (vmcore_init+0xcc/0x198) from [<c000863c>] (do_one_initcall+0x34/0x184) >> [<c000863c>] (do_one_initcall+0x34/0x184) from [<c05b28dc>] (kernel_init_freeable+0xfc/0x1c8) >> [<c05b28dc>] (kernel_init_freeable+0xfc/0x1c8) from [<c04326d4>] (kernel_init+0x8/0xe4) >> [<c04326d4>] (kernel_init+0x8/0xe4) from [<c000ec58>] (ret_from_fork+0x14/0x3c) >> >> arch/arm/mm/ioremap.c:244 >> /* >> * Don't allow RAM to be mapped - this causes problems with ARMv6+ >> */ >> if (WARN_ON(pfn_valid(pfn))) >> return NULL; Thanks in advance for any help. -andy

11 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

linaro-kernel