What's the situation with it on tilt-3.4? 3.2 is too old to care about
but 3.4 needs to work under the same conditions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048056
Title:
perf_event_open
I'm afraid we don't use DS-5 on our side... if you know a Lukas Snetler
in ARM it might be worth having a chat though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018092
Title:
Perf test fails
Dave said that because we disable hw counters due to errata in the hw,
perf -e will fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1018092
Title:
Perf test fails on Pandaboard (3.4 TILT)
To
Well perf should work itself OK using the fallback timer-based method,
it's specifically this -e mode.
The hardware counters are in there and do stuff, the problem is (IIRC
overflow) interrupts are prone to get lost, distorting the numbers to
uselessness, and that problem is in the ARM core and
** Changed in: linaro-landing-team-ti
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971091
Title:
Pandaboard ES freezes with the default CPU scaling
AFAIK this should be solved in tilt-3.4, the problem was coming from
frequency update code which should now be in good shape.
** Changed in: linaro-landing-team-ti
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is working on tilt-tracking about to become tilt-3.4
** Changed in: linaro-landing-team-ti
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799921
Title:
I already found out the cause for this on the new tree and fixed it.
I'll prepare a patch on tilt-3.1 with the same fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/971091
Title:
Pandaboard ES
Please try the attached... something is wrong with my boot setup atm,
tilt-3.1 with or without this patch blows up in per_cpu code early in
boot so I can't test it. It's either boot pieces or toolchain, I moved
to Linaro 4.6.3 toolchain, which works OK on 3.3 stuff.
** Patch added:
** Changed in: linaro-landing-team-ti
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843628
Title:
perf failure on panda (omap4)
To manage notifications
Dave's also found the remaining 4460-specific PMU init issue, and his
fix
http://git.linaro.org/gitweb?p=landing-
teams/working/ti/kernel.git;a=patch;h=fab7a4a5a0cb4c8fc5692970be6e62aece99599c
is on tilt-3.1, tilt-linux-linaro-3.1 (linaro ubuntu basis) and tilt-
tracking.
--
You received this
About the platform_device, In tracking, for 4430 it's enabled and
believed workable. We can't get the unit to start up on 4460 yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843628
Title:
perf
Will, I just updated tilt-linux-linaro-3.1 with latest linux-linaro-3.1
from Nicolas tonight.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843628
Title:
perf failure on panda (omap4)
To manage
... and tilt-linux-linaro-3.1 now has the platform device patch in via
Dave.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/843628
Title:
perf failure on panda (omap4)
To manage notifications about
Guys on tilt-tracking we have a patch from Dave Long
http://git.linaro.org/gitweb?p=landing-
teams/working/ti/kernel.git;a=patch;h=32a92107a7137ea32a2209f83dd4bae42ad4ec7c
that re-enables these interrupts for 4430 Panda. We don't get any boot
crashes so far.
It doesn't hurt 4460 Panda, but it
** Changed in: linaro-landing-team-ti
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764796
Title:
Enable basic profiling tracing options in kernel
** Changed in: linaro-landing-team-ti
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764796
Title:
Enable basic profiling tracing options in kernel
I fixed it thismorning
http://git.linaro.org/gitweb?p=landing-
teams/working/ti/kernel.git;a=patch;h=e756cf5be3b63dc49c54a204b9d95332c07db7c5
it's part of the 3.1 stuff pushed on our repo now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Bluetooth is working OK in Ubuntu and Android I believe on both 3.0,
3.1-based kernels and 4430/4460.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789095
Title:
Bluetooth does not work on
I thought I saw in one of your boot traces recently it was being started
up now... you do indeed need uim started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789095
Title:
Bluetooth does not
I spent a couple of hours with a guy on irc the other week using ubuntu,
with HEAD uim started in /etc/rc.local and if you have a 4460, later
firmware, he was working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Great... I believe the Ancients of 2.6.35 did succeed to plug all this
together with udev fwiw.
Yes for a while, maybe still, we had to patch wl12xx sources to correct
the firmware subdir.
Android guys have their firmware in level above to match what the
drivers currently expect (and have
We've changed our omap4_defconfig to support the listed features on
tilt-tracking branch
http://git.linaro.org/gitweb?p=people/andygreen/kernel-
tilt.git;a=shortlog;h=refs/heads/tilt-tracking
in a few days when 3.1 releases that config should filter down to all
the other trees based on TILT 3.1
** Changed in: linaro-landing-team-ti
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/764796
Title:
Enable basic profiling tracing options in kernel configuation
To
Is this still broken on 3.0 kernel?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744458
Title:
hw perfevents on the pandabaord
To manage notifications about this bug go to:
tilt-3,0 is staying pretty much where it is, it's working with the
current arrangements for Android branch.
tilt-3.0-nodspvideo1 is getting new work from TI for various things and
is used to generate tilt-linux-linaro-3.0 now.
If you just want the vanilla branch the tilt-3.0-nodspvideo1 is the
Paolo it's solved on yesterday's (Aug 31) tilt-linux-linaro-3.0... your
package seems to have come from several days before?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/588638
Title:
console
This is solved as far as my colour-blind eyes can tell on today's tilt-
linux-linaro-3.0 on both HDMI and DVI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/588638
Title:
console colormap is wrong
Ming-Lei it sounds like a really good explanation. But when I test it,
I don't see any real difference on USB memory stick before and after.
Maybe my test is broken somehow?
8GB no-name USB stick
Before the patch --
root@linaro:~# dd if=/dev/urandom of=/media/dump bs=40960 count=1000
1000+0
Hi Ming-Lei -
What I like about your explanation is it allows cache status to be the
communication path for network traffic to impact the issue, ie network
activity finally spills the cache that does update the qtd descriptor
and then we get less deadtime. That sounds very good to me.
I'm using
Ah! /dev/urandom is the limiting factor ^^ USB HDD is also stuck at
1.9Mbps with the same test. Same test with of=/dev/null is only getting
2.0Mbps.
With the USB HDD and if=/dev/zero instead, and 10x count
root@linaro:~# dd if=/dev/zero of=/media/dump bs=40960 count=1
1+0 records in
Maybe the 1ms threshold thing is just to do with a threshold heuristic
where it stops using the scheduler and sleeping and instead spins
udelay() style, hence the 100% CPU. That's not to write off its effect
on the bug just a possible explanation of why it cares about 1ms or
less.
Reading these
Hi Jani -
No, Panda WLAN is on a 4-bit SDIO interface. So it's completely
different from ping on Ethernet, I don't know what that means that it
still changes USB throughput.
Also when I reproduced this via pinging ethernet, I only saw a 50%
increase in throughput; maybe it's to do with the
btsdio is evil I think bt connection on Panda is by UART not SDIO
How does the rest of your config about BT compare to omap4_defconfig on
my tree, eg CONFIG_TI_ST... and do you have uim daemon running?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
npitre tree doesn't have the necessary patches for BT. They're layered
out in my for-nicolas branch on top of npitre tree at the moment FWIW.
http://git.linaro.org/gitweb?p=people/andygreen/kernel-
tilt.git;a=shortlog;h=refs/heads/for-nicolas
Generally LT tree has radioactive patches that would
Seems to be two different issues, one is the original bug report and
this other random thing.
On my tree, with my config, I don't see this at all. Blanking occurs
but I can every time bring it back by waving the mouse a couple of
seconds without these errors.
Is the kernel you're seeing this
It's a different issue. This will solve it --
http://git.linaro.org/gitweb?p=people/andygreen/kernel-
tilt.git;a=patch;h=1b0d6d49516d29bf2d723e2789e6f0fcd483f7b7
On OMAP, if you try to touch any peripheral unit that is not clocked,
it'll blow a bus abort which shows up as one of these imprecise
These don't appear on my tree.
[0.867492] omap_hwmod: l3_div_ck: missing clockdomain for l3_div_ck.
[0.85] omap_hwmod: dss_dispc: softreset failed (waited 1 usec)
[0.908599] omap_hwmod: dss_rfbi: softreset failed (waited 1 usec)
[0.931549] omap_hwmod: ipu: failed to
rootwait should be optimal for this situation, something else is going
on like issue with card detect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712175
Title:
OMAP Beagle C4: kernel does not
rootwait / mmc is likely unrelated, it just happened to be where the
other core was when it blew. The first core is indeed in the same code
known to cause this.
Can you do like
zcat /proc/config.gz | grep SDI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Does your tree have the patch attached from Seb Jan?
** Patch added: omapfb lock fix
https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/720055/+attachment/1956893/+files/0001-OMAPFB-protect-console-while-re-allocating-FB.patch
--
You received this bug notification because you are a
I sent a patchset that was accepted into linux-omap 19 March which fixes
a problem in OMAP3 where it can fail to touch the correct register in
the I2C code, instead it touches a random-ish or non-existent I2C
register.
http://git.kernel.org/?p=linux/kernel/git/tmlind/linux-
It might be worth trying just aplay from the console, try to see if the
problem is coming from alsa side or pulse. What does cat
/proc/asound/cards say?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since Sebasien Jan took my patch into his tree, and the Ubuntu Panda
kernel is coming via his tree, it should mean that kernel has the patch
in it. You can confirm it with
$ dmesg | grep 6030: Interrupt status
if it shows anything it's using the patch.
--
You received this bug notification
I could reproduce this with strace cat /dev/ttyO2, it hung at the open()
but responded to ^C.
I couldn't reproduce the OOPS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728565
Title:
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
FWIW, I tried to reproduce this with CONFIG_HIGHMEM and 460M + 512M,
confirmed in /proc/meminfo that there is highmem and set it compiling a
kernel repeatedly. After 5 hours it didn't fail. This is with Seb
Jan's 2.6.38-rc2 tree.
I'll test it further later.
--
You received this bug
(#28 above is on an A1 board with ES2.1 silicon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633227
Title:
instabilities with highmem activated
--
ubuntu-bugs mailing list
After a lot of help from kenws testing, I have a small patch which
should stop the Panda going OFF. I can explain why it goes off without
the patch, but since TI won't let me have a twl6030 datasheet I can't
get right to the end yet.
Basically the Panda PMIC is seeing an overcurrent on one of
I added the modprobe ledtrig-heartbeat to /etc/rc.local for now,
although I'm sure there's a better place.
I cycled the power 10 times. 9 times it was normal, but one time there
was a 30s delay before boot completed. If it delayed 30s with LEDs off,
many people will think the board is OFF.
@Bryan is there any chance you can try specifically your SD Card
that fails in Ming Lei's new board? There are a lot of possible
variables like x-loader, U-Boot and kernel version, even maybe rootfs
actions that can be eliminated as the sole cause of the problem if that
same card works on his
Most of this confusion is coming because the LED trigger heartbeat is
being built as a module (why?) and not inserted.
If you type
modprobe ledtrig-heartbeat
at the prompt you will get the familiar flashing LED letting you know
the board is ON. So I guess the confusion about ON or OFF will be
I examined the pandaboard schematics and found that the SYS_BOOT[7..0]
pins are set to 1101 by default. These control the actions of the
ROM on the OMAP4. b5..b0 select the boot ordering; 000101 means try USB
boot first and MMC1 second.
In the case that no external power is connected to the
@Aneesh... my problem was with USB OTG power of the board, it is fixed
with the patches but you're right the bug in Launchpad is more about
dying later. Like yourself my board is not dying later either. My
patch also does prcm_init() earlier but after that there is another
problem with using
I was trying to power my Panda board from USB OTG connector, it dies
early in boot apparently in xloader or u-boot when connected to a
laptop.
I did three tests
1) Short the USB OTG 5V pin to the DC Jack 5V pin in case something in
the OTG 5V path makes trouble. It still dies in early boot.
2)
Well, there's no reason to expect it should be consistent since we
didn't compare which version of Xloader and U-Boot I am running and you
already have reason to believe the behaviour depends on that. However
what I reported is repeatable on this board with
Texas Instruments X-Loader 1.41 (Oct
AFAICT the latest X-loader amongst the various trees lives here
http://gitorious.org/x-loader
I built the current HEAD of it and got
Texas Instruments X-Loader 1.4.4ss (Feb 7 2011 - 21:09:54)
This boots fine under DC Jack power (derived from my laptop USB port)
and continues to turn the
I have an Acer Aspire 8920g and Alsa's snd-hda-intel does not have a
model that works completely on it yet. However after some help on the
Alsa lists, I was able to get it working for stereo anyway on internal
speakers. See this post:
http://mailman.alsa-project.org/pipermail/alsa-
58 matches
Mail list logo
