I've been experiencing solid hangs on my beaglexm with v3.7 after
kexec:
here is my .config (omap2plus + EHCI/OHCI + CPUFREQ + DEVTMP):
http://people.canonical.com/~ppisati/omap3_cpufreq_kexec/config
here is the diff i added to get some debugging:
On Tue, Dec 11, 2012 at 08:20:13PM +, Paul Walmsley wrote:
On Tue, 11 Dec 2012, Paolo Pisati wrote:
I've been experiencing solid hangs on my beaglexm with v3.7 after
kexec:
Does it crash if you boot v3.7 directly from the bootloader, i.e., without
kexec?
nope, works perfectly fine
On Tue, Dec 11, 2012 at 08:32:25PM +, Paul Walmsley wrote:
On Tue, 11 Dec 2012, Paul Walmsley wrote:
On Tue, 11 Dec 2012, Paolo Pisati wrote:
I've been experiencing solid hangs on my beaglexm with v3.7 after
kexec:
Does it crash if you boot v3.7 directly from the bootloader
Signed-off-by: Paolo Pisati paolo.pis...@canonical.com
---
drivers/regulator/core.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index e872c8b..c347fd0 100644
--- a/drivers/regulator/core.c
+++ b
Paolo Pisati (1):
regulator: core: if voltage scaling fails, restore original voltage
values
drivers/regulator/core.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
--
1.7.10.4
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body
On Thu, Dec 13, 2012 at 05:15:33AM +, Mark Brown wrote:
On Wed, Dec 12, 2012 at 12:45:52PM +0100, Paolo Pisati wrote:
And after a second look it's clear what's going on:
After a second look at what? You've not provided any context, I've no
idea what you're talking about here.
forgot
95a3c23ae620c1b4c499746e70f4034bdc067737
Author: Mark Brown broo...@opensource.wolfsonmicro.com
Date: Thu Dec 16 15:49:37 2010 +
regulator: Optimise out noop voltage changes
Paolo Pisati (1):
regulator: core: if voltage scaling fails, restore original voltage
values
drivers/regulator/core.c
Signed-off-by: Paolo Pisati paolo.pis...@canonical.com
Tested-by: Robert Nelson robertcnel...@gmail.com
---
drivers/regulator/core.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index e872c8b..c347fd0
On Thu, Dec 13, 2012 at 11:47:15AM +0200, Felipe Balbi wrote:
On Thu, Dec 13, 2012 at 10:13:00AM +0100, Paolo Pisati wrote:
Signed-off-by: Paolo Pisati paolo.pis...@canonical.com
Tested-by: Robert Nelson robertcnel...@gmail.com
please read Documentation/stable_kernel_rules.txt, you'll see
Compilation fix - leftover from:
commit 998c336d4c7183301ed6a6ca93952f63e3cf694f
Author: Tomi Valkeinen tomi.valkei...@ti.com
Date: Wed May 30 13:26:00 2012 +0300
OMAPDSS: remove omap_dss_device's suspend/resume
Cc: stable sta...@vger.kernel.org # v3.7
Signed-off-by: Paolo Pisati
On Thu, Jan 10, 2013 at 09:42:27PM +0100, Paolo Pisati wrote:
Compilation fix - leftover from:
commit 998c336d4c7183301ed6a6ca93952f63e3cf694f
Author: Tomi Valkeinen tomi.valkei...@ti.com
Date: Wed May 30 13:26:00 2012 +0300
OMAPDSS: remove omap_dss_device's suspend/resume
Cc
Hi,
i can't boot my pandaes with 3.8rc4 + cpu_freq + ehci/ohci enabled, as it
usually
hangs with:
[ 26.718322] INFO: rcu_sched detected stalls on CPUs/tasks: { 1} (detected by
0, t=2690 jiffies, g=4294967100, c=4294967099, q=749)
[ 26.730682] Task dump for CPU 1:
[ 26.734069] udevd
I keep getting this BUG() when there's IPV6 traffic in in my lan on a panda
board
with these configs:
-start from a vanilla omap config
(make ARCH=arm omap2plus_defconfig)
-enable IPV6 and PREEMPT_VOLUNTARY
-turn off
CONFIG_DEBUG_SPINLOCK
CONFIG_DEBUG_MUTEXES
CONFIG_DEBUG_LOCK_ALLOC
On Fri, Feb 22, 2013 at 12:36:37PM +, Russell King - ARM Linux wrote:
On Thu, Feb 21, 2013 at 10:48:19AM +0100, Paolo Pisati wrote:
any idea how can i debug this?
Please try this patch, and report back whether it solves your problem.
Thanks.
yes, it solves my problem: any chance we can
will be published in the kernel repository)
please? Thanks.
absolutely:
Reported-by: Paolo Pisati p.pis...@gmail.com
Tested-by: Paolo Pisati p.pis...@gmail.com
--
bye,
p.
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
i know we switched to dtb-only booting, but what's happened to wifi?
3.5.x:
flag@flag-desktop:~$ ls -la /sys/bus/platform/devices/wl12xx/
total 0
drwxr-xr-x 5 root root0 set 13 17:26 .
drwxr-xr-x 4 root root0 set 13 17:26 ..
-rw-r--r-- 1 root root 4096 set 13 17:28 bt_coex_state
Dear,
after the inclusion of 851320e:
ARM: dts: Fix muxing and regulator for wl12xx on the SDIO bus for pandaboard
wlan0 is back on my pandaes, but it doesn't work and my logs are swamped
with:
[ 56.255401] wlcore: ERROR timeout waiting for the hardware to complete
initialization
[
Vanilla 3.12 multi_v7_defconfig + cpu_idle result in a solid hang on my pandaes
board: has anyone experienced it before? is cpu_idle safe on omap4?
same kernel boots fine on omap3 and some other arm boards fwiw.
if you want to reproduce it:
config:
Signed-off-by: Paolo Pisati paolo.pis...@canonical.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |9 -
arch/arm/boot/dts/omap4-panda-es.dts |3 ++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot
Signed-off-by: Paolo Pisati paolo.pis...@canonical.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi |9 -
arch/arm/boot/dts/omap4-panda-es.dts |3 ++-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot
HDMI codec dummy entries for Panda/ES.
Signed-off-by: Paolo Pisati paolo.pis...@canonical.com
---
Depends on 0f7f3d1 ASoC: hdmi-codec: Add devicetree binding with
documentation, eligible for a 3.14-rcX fix.
arch/arm/boot/dts/omap4-panda-common.dtsi |9 -
arch/arm/boot/dts/omap4
On Wed, Feb 19, 2014 at 10:15:24AM +0200, Peter Ujfalusi wrote:
diff --git a/arch/arm/boot/dts/omap4-panda-common.dtsi
b/arch/arm/boot/dts/omap4-panda-common.dtsi
index 88c6a05..f4aeaa1 100644
--- a/arch/arm/boot/dts/omap4-panda-common.dtsi
+++
I've been experiencing hangs on reboot on two different panda boards (es rev1
and vanilla rev a1) with v3.14-rc8 (but reproducible in 3.13 too):
toolchanin: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7)
the config is a multi_v7_defconfig plus a couple of codepages:
On Thu, Mar 27, 2014 at 06:54:14PM +0100, Paolo Pisati wrote:
I've been experiencing hangs on reboot on two different panda boards (es rev1
and vanilla rev a1) with v3.14-rc8 (but reproducible in 3.13 too):
toolchanin: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7)
the config
On Wed, Apr 02, 2014 at 10:15:13AM -0700, Tony Lindgren wrote:
Paul uses MMC filesystem, I use NFS. As Felipe Pointed out as well, I
did rootcause MMC filesystem mount issue here:
http://marc.info/?l=linux-omapm=139637044425644w=2
Balaji, care to take a look at the issue for MMC? It may
I'm having an hard time making the vanilla v7_defconfig boot off the mmc on my
pandaboard:
[1.698272] omap_hsmmc 4809c000.mmc: unable to get vmmc regulator -517
[1.705139] platform 4809c000.mmc: Driver omap_hsmmc requests probe deferral
[1.712890] omap_hsmmc 480d5000.mmc: unable to
On Wed, Sep 10, 2014 at 11:50:01AM -0500, Nishanth Menon wrote:
On 17:33-20140910, Paolo Pisati wrote:
I'm having an hard time making the vanilla v7_defconfig boot off the mmc on
my
pandaboard:
V3.15:
https://github.com/nmenon/kernel-test-logs/blob/v3.15/multi_v7_defconfig/pandaboard
On Thu, Sep 11, 2014 at 10:01:32AM +0200, Paolo Pisati wrote:
On Wed, Sep 10, 2014 at 11:50:01AM -0500, Nishanth Menon wrote:
On 17:33-20140910, Paolo Pisati wrote:
I'm having an hard time making the vanilla v7_defconfig boot off the mmc
on my
pandaboard:
V3.15:
https
Lately i've been trying to track down a panic i hit when i pass the mem=256M
option to a 3.16 kernel on a bleaglebone black, and i noticed this:
dtc -I dtb ./arch/arm/boot/dts/am335x-boneblack.dtb
...
memory {
device_type = memory;
reg = 0x8000
On Sun, Jan 18, 2015 at 06:38:46PM +0100, Geert Uytterhoeven wrote:
The boot loader copied the DT to the end of real RAM, not to the end of
the 256 MiB block? Hence the kernel accesses unmapped memory
when checking the FDT header?
actually everything is below 256M since physical memory
Boot hangs when passing mem=256M to a 3.16 kernel (but i was able to reproduce
it with multi_v7_defconfig on a 3.19rcX kernel too):
80e6d694: 0024 65746e49 6c616e72..$.Internal
80e6d6a4: 72726520 203a726f 73706f4f 2035203a error: Oops: 5
80e6d6b4: 5d31235b 504d5320
The question is two-folded, hence the crossposting.
I have a kernel that runs perfectly on my beaglebone black, except for one thing
- the kmod for the watchdog is not autoloaded upon boot albeit the device-tree
node is present:
ubuntu@beaglebone:~$ dmesg | grep wdt
ubuntu@beaglebone:~$ ll
32 matches
Mail list logo
