A similar-looking bug has started to sting me when building with certain
combinations of config options, particularly CONFIG_THUMB2_KERNEL.
A good way to debug this kind of thing is to build a uniprocessor kernel
with all caches (including any external L2) disabled -- this makes the
memory system
** Attachment added: config (closely based on the packaged natty kernel for
omap)
https://bugs.launchpad.net/linux-linaro/+bug/720055/+attachment/1885621/+files/.config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
i had a similar oops when bringing up another on-chip core (the SGX).
It turned out that the core's power and clock needed to be turned up
before executing code that poked at its registers; the imprecise data
abort reflected an aborted fetch from a memory location mapped to a
powered-down on-chip
After reading Dave's comments and takeing a look at Andy Green's config
I found that if I turn off CONFIG_OMAP2_DSS_SDI the problem goes away
which makes sense since Dave said commenting out
117 #ifdef CONFIG_OMAP2_DSS_SDI
118 SR(SDI_CONTROL);
119 SR(PLL_CONTROL);
120 #endif
made the
Turning off CONFIG_OMAP2_DSS_SDI has the side effect of turning off
CONFIG_PANEL_ACX565AKM which is the panel on the Nokia N900.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720055
Title:
I can also confirm that the 2.6.38-1000-linaro-omap kernel works on my
panda. I'm using the hwpack_linaro-
panda_20110303-0_armel_supported.tar.gz with the linaro-n-developer-
tar-20110303-0.tar.gz.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Anand, any news on this?
Currently we are working around this by not enabling the display
controller on omap4.
** Changed in: linux-linaro
Assignee: Nicolas Pitre (npitre) = Anand Gadiyar (gadiyar)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Thu, 3 Mar 2011, John Rigby wrote:
Currently we are working around this by not enabling the display
controller on omap4.
Might be worth testing again with the current head of linaro-2.6.38.
Andy Green says he's unable to reproduce this issue, presumably with
his own build. So that might
Specifically master on
http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git
with config from arch/arm/configs/omap4_panda_minimal_defconfig doesn't show
this problem for me and has display enabled; that tree is based on Nicolas'
tree.
--
You received this bug notification because
With: [0.00] Linux version 2.6.38-1000-linaro-omap (buildd@crabapple)
(gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3) ) #1-Ubuntu SMP Thu Feb 24
04:55:52 UTC 2011 (Ubuntu 2.6.38-1000.1-linaro-omap 2.6.38-rc6)
I no longer seem to be seeing this problem on my panda board. For full boot
** Changed in: linux-linaro-omap (Ubuntu)
Importance: Undecided = Critical
** Changed in: linux-linaro (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Could someone test the attached patch and see if it makes the problem go
away?
The display code use clk_enable/clk_disable APIs and the current
implementation appears to return immediately and not wait until the
modules are ready.
(I'm trying to reproduce the failure in parallel, but could take
With the patch I get:
arch/arm/mach-omap2/clock.c:46:2: error: implicit declaration of function
‘omap4_cm_wait_module_ready’
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720055
Title:
Unhandled
Oops. Sorry about that, I forgot to refresh the patch before sending it
out. Attached a version that actually compiles.
I have been able to reproduce the bug now - with your config. I do find
that the patch is not working - but I believe the fix would be along
similar lines. Debugging now.
**
Anand, I worked around the compile error and still have the error also.
I will wait now for an updated patch. I am adding a log for my upcoming
linux-linaro-2.6.38 based packaged kernel. I see lots of clock
errors/warnings there.
--
You received this bug notification because you are a member
Uncompressing Linux... done, booting the kernel.
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 2.6.38-1000-linaro-omap (jcrigby@jcrigby-laptop)
(gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-1ubuntu3ppa1) ) #1 SMP Tue Feb 22
I can reproduce the error on my board (every boot fails at the same
place) but the addresses change. The error occurs right before the OMAP
components are initialized (DSS, DISPC, DSI, DSI2). It doesn't matter if
I build the kernel myself or use a recent prebuild kernel from a hwpack
(e.g.
An imprecise abort is hard to track. Being imprecise means that the
cause happened in the past but the actual exception gets delayed.
Please provide more boot logs if the reported addresses appear
to be different. That still may help to find a correlation.
--
You received this bug notification
Ok, I get it now. I'll try to figure out what is going on.
** Changed in: linux-linaro (Ubuntu)
Assignee: (unassigned) = John Rigby (jcrigby)
** Also affects: linux-linaro-omap (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-linaro-omap (Ubuntu)
Assignee:
** Changed in: linux-linaro-omap (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720055
Title:
Unhandled fault: imprecise external abort (0x1406) at 0x2ada61a8
Verified that this is broken in linux-linaro-2.6.37. Passing it on to
Anand and Nicolas since that is where the display patches came from so
hopefully he can figure out what is wrong.
Here is what I did. I reset my tree to here:
commit fa3c5afc525bacfcdd2ba5107da5a2d93a04b32b
Merge: 054fcd5
** Attachment added: kernel.config
https://bugs.launchpad.net/ubuntu/+source/linux-linaro-omap/+bug/720055/+attachment/1856552/+files/kernel.config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: boot.txt
https://bugs.launchpad.net/ubuntu/+source/linux-linaro-omap/+bug/720055/+attachment/1856553/+files/boot.txt
** Also affects: linux-linaro
Importance: Undecided
Status: New
** Changed in: linux-linaro
Assignee: (unassigned) = Nicolas Pitre
This is not a linux-linaro kernel, the log says Ubuntu
2.6.35-903.17-omap4 2.6.35.3 which looks like a Ubuntu OMAP4 kernel. So
what package should this bug be filed against?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Log is using a quite old x-loader/u-boot combination, and also Ubuntu
kernel instead of linaro one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720055
Title:
Unhandled fault: imprecise external
** Changed in: linux-linaro (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720055
Title:
Unhandled fault: imprecise external abort (0x1406) at 0x2ada61a8
--
Sorry, should have warned you. You are seeing the master image boot at
the top before the system gets deployed. You need to look further down
in the boot log to see the new image booting:
Linux version 2.6.37-1003-linaro-omap (buildd@gourd) (gcc version 4.5.2
(Ubuntu/Linaro 4.5.2-2ubuntu2) )
27 matches
Mail list logo
