Hi,
We have installed Ubuntu 12.04 (Precise Pangolin) 64-bit.
But unable to install svn.
rajkiran@rajkiran-OptiPlex-780:~$ sudo apt-get install subversion
Reading package lists... Error!
W: Duplicate sources.list entry cdrom://Ubuntu 12.04.1 LTS _Precise Pangolin_ -
Release amd64 (20120823.1)/
On Tuesday 19 February 2013 11:51 PM, Daniel Lezcano wrote:
On 02/19/2013 07:10 PM, Thomas Gleixner wrote:
On Tue, 19 Feb 2013, Daniel Lezcano wrote:
I am working on identifying the different wakeup sources from the
interrupts and I have a question regarding the timer broadcast.
The broadcast
Hi Amit,
Yes, all power management failures have bugs for them, please go to those
test result spreadsheets with the specific column I wrote in this report.
There are detailed logs in the bug attachment.
Thanks.
Best Regards
Botao Sun
On Thu, Feb 21, 2013 at 5:11 PM, Amit Kucheria wrote:
> O
On Thu, Feb 21, 2013 at 11:24 AM, Botao Sun wrote:
> Calendar Week 8, 2013: Here is test result summary for Linux Linaro ubuntu
> Quantal image on following boards:
>
> 1) ARM Versatile Express A9;
> 2) Samsung Arndale;
> 3) TI Panda 4430;
> 4) TI Panda 4460;
> 5) ST Ericsson Snowball.
>
> Synopsi
For the nsec resolution conversions to be useful on non 64-bit
architectures, do_div() needs to be used for the 64-bit divisions.
Signed-off-by: Kevin Hilman
---
include/asm-generic/cputime_nsecs.h | 51 +++--
1 file changed, 37 insertions(+), 14 deletions(-)
dif
Use the atomic64_* accessors for all the kernel_cpustat fields to
ensure atomic access on non-64 bit platforms.
Thanks to Mats Liljegren for CGROUP_CPUACCT related fixes.
Cc: Mats Liljegren
Signed-off-by: Kevin Hilman
---
fs/proc/stat.c | 40 ---
With the 64-bit requirement removed from virt CPU accounting,
allow ARM platforms to enable it.
Signed-off-by: Kevin Hilman
---
arch/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index 9bbe760..732f8d3 100644
--- a/arch/arm/Kconfig
+++ b/arch
Frederic,
Here is a first pass at some changes needed in order to add ARM
support.
I have another series coming that instruments the syscalls, exceptions
etc. on ARM also, but this one is just to get some prerequisites out
for broader discussion.
This series applies on top of your 3.8-rc6-nohz4
The 64-bit requirement can be removed after the conversion of
kernel_cpustat accessors to the portable atomic64 accessors.
Signed-off-by: Kevin Hilman
---
init/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/Kconfig b/init/Kconfig
index 3abb019..b13af06 100644
--
So that it can build on !KVM systems too.
Signed-off-by: Kevin Hilman
---
kernel/context_tracking.c | 4
1 file changed, 4 insertions(+)
diff --git a/kernel/context_tracking.c b/kernel/context_tracking.c
index 74f68f4..6fe96b1 100644
--- a/kernel/context_tracking.c
+++ b/kernel/context_tra
On Wed, 2013-02-20 at 11:28 -0500, Nicolas Pitre wrote:
> On Wed, 20 Feb 2013, Jon Medhurst (Tixy) wrote:
>
> > After some time investigating why I wasn't seeing some kernel section
> > mismatch errors that someone else was seeing, I found the cause was that
> > in Linaro we build Thumb2 kernels i
On Wed, 20 Feb 2013, Jon Medhurst (Tixy) wrote:
> After some time investigating why I wasn't seeing some kernel section
> mismatch errors that someone else was seeing, I found the cause was that
> in Linaro we build Thumb2 kernels in the main, and modpost.c doesn't
> have support for any of the Th
Hi all,
A little feedback for the Linaro Mini Summit on virtio-mmio.
There are a couple of items that GreenSocs should probably do, as we've done
much of the background work. Namely, right now, we are deep in the throws of
upstreaming the prerequisites for virtio-mmio to Qemu, then we'll move
On 02/19/2013 10:21 AM, Daniel Lezcano wrote:
> On 02/19/2013 07:10 PM, Thomas Gleixner wrote:
>> On Tue, 19 Feb 2013, Daniel Lezcano wrote:
>>> I am working on identifying the different wakeup sources from the
>>> interrupts and I have a question regarding the timer broadcast.
>>>
>>> The broadcas
On Tue, 19 Feb 2013, Andy Lutomirski wrote:
> On 02/19/2013 10:21 AM, Daniel Lezcano wrote:
> > On 02/19/2013 07:10 PM, Thomas Gleixner wrote:
> >> On Tue, 19 Feb 2013, Daniel Lezcano wrote:
> >>> I am working on identifying the different wakeup sources from the
> >>> interrupts and I have a questi
2013/2/8 Vincent Guittot :
> On 8 February 2013 16:35, Frederic Weisbecker wrote:
>> What if the following happen (inventing function names but you get the idea):
>>
>> CPU 0 CPU 1
>>
>> dom = new_domain(...) {
>>nr_cpus_busy = 0;
>>
On Tue, 19 Feb 2013, Daniel Lezcano wrote:
> I am working on identifying the different wakeup sources from the
> interrupts and I have a question regarding the timer broadcast.
>
> The broadcast timer is setup to the next event and that will wake up any
> idle cpu belonging to the "broadcast cpuma
2013/2/18 Frederic Weisbecker :
> 2013/2/8 Vincent Guittot :
>> On 8 February 2013 16:35, Frederic Weisbecker wrote:
>>> What if the following happen (inventing function names but you get the
>>> idea):
>>>
>>> CPU 0 CPU 1
>>>
>>> dom = new_domain(...) {
On 02/20/2013 12:54 PM, Amit Kucheria wrote:
> On Tue, Feb 19, 2013 at 10:11 AM, Sanjay Singh Rawat
> wrote:
>> Add functionality to record the overall and current runtime cpuidle
>> statistics.
>
> I'd like the output to be something list this:
>
> [state1]: [number of times entered]: [average
After some time investigating why I wasn't seeing some kernel section
mismatch errors that someone else was seeing, I found the cause was that
in Linaro we build Thumb2 kernels in the main, and modpost.c doesn't
have support for any of the Thumb relocation types in addend_arm_rel().
I thought I wo
On Tue, Feb 19, 2013 at 10:11 AM, Sanjay Singh Rawat
wrote:
> Add functionality to record the overall and current runtime cpuidle
> statistics.
I'd like the output to be something list this:
[state1]: [number of times entered]: [average residency]: [std.
deviation(residency)]: [variance]
[state2
Mark
I can solve the MX record issue.
In *theory*, if a system is trying to send email and it cannot find an MX
record, it *should* fall back to looking for an A record (which does exist)
but not everything follows that.
Philip
On 20 February 2013 11:11, Mark Hambleton wrote:
> > I understa
> I understand your viewpoint, but the most important part is: mails should
> reach
> everybody as soon as possible. Currently few of them are never reaching us :)
There does appear to be some tech issues with this list too, I was being
blocked from posting to the list and after some investig
So we could flip the management of the list on its head, then, and make the
list wide open but blacklist spammers ... except that you then find
yourself in a reactive mode. In other words, spam gets onto the list
because the list is open, so you add the sender's email address to the
blacklist, whic
On 20 February 2013 16:19, Wookey wrote:
> +++ Philip Colmer [2013-02-20 08:36 +]:
>>I'm not entirely comfortable with blindly white-listing anyone who posts
>>to linaro-dev with something that doesn't look like spam, for several
>>reasons:
>>1. That is not a great way to run a
+++ Philip Colmer [2013-02-20 08:36 +]:
>I'm not entirely comfortable with blindly white-listing anyone who posts
>to linaro-dev with something that doesn't look like spam, for several
>reasons:
>1. That is not a great way to run a moderated mailing list.
>2. IT aren't going
On 19 February 2013 18:54, Alexander Sack wrote:
> On Tue, Feb 19, 2013 at 6:03 PM, James Tunnicliffe
> wrote:
>> On 19 February 2013 16:08, Alexander Sack wrote:
>>> On Tue, Feb 19, 2013 at 2:53 PM, James Tunnicliffe
>>> wrote:
Good point! I would be pleasantly surprised if an image + hwp
On 20 February 2013 14:06, Philip Colmer wrote:
> I'm not entirely comfortable with blindly white-listing anyone who posts to
> linaro-dev with something that doesn't look like spam, for several reasons:
>
> 1. That is not a great way to run a moderated mailing list.
> 2. IT aren't going to be in
I'm not entirely comfortable with blindly white-listing anyone who posts to
linaro-dev with something that doesn't look like spam, for several reasons:
1. That is not a great way to run a moderated mailing list.
2. IT aren't going to be in the best position to say whether or not the
sender *should
29 matches
Mail list logo
