Hi all,
I got some bad news last night. Our ISP told me there would be a delay in getting our service up and running in the new offices. I spoke to them this morning and they're telling me that it will *probably* be Wednesday before we get connectivity, but we will know more on Monday.
As a consequence I am putting v.l.o back online and delaying the move. My intention is to take it offline again on Thursday of next week and move on Friday. Obviously this plan may be fluid based on the news we get on Monday. I will obviously keep you all posted.
Many apologies for the delay and thanks for your patience,
Dave
Dave Pigott
Validation Engineer
T: +44 1223 45 00 24 | M +44 7940 45 93 44
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
Basically without this patch changing the mode of thermal zone
is not possible as wrong string size is passed to strncmp.
Signed-off-by: Amit Daniel Kachhap <amit.kachhap(a)linaro.org>
---
drivers/thermal/thermal_sys.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/thermal/thermal_sys.c b/drivers/thermal/thermal_sys.c
index 220ce7e..96da1af 100644
--- a/drivers/thermal/thermal_sys.c
+++ b/drivers/thermal/thermal_sys.c
@@ -152,9 +152,9 @@ mode_store(struct device *dev, struct device_attribute *attr,
if (!tz->ops->set_mode)
return -EPERM;
- if (!strncmp(buf, "enabled", sizeof("enabled")))
+ if (!strncmp(buf, "enabled", sizeof("enabled") - 1))
result = tz->ops->set_mode(tz, THERMAL_DEVICE_ENABLED);
- else if (!strncmp(buf, "disabled", sizeof("disabled")))
+ else if (!strncmp(buf, "disabled", sizeof("disabled") - 1))
result = tz->ops->set_mode(tz, THERMAL_DEVICE_DISABLED);
else
result = -EINVAL;
--
1.7.1
Hi,
The migration of ci.linaro.org to new hardware is complete. We hope
that this will result in a more stable and responsive system. We have
had a few builds run successfully so everything seems to be fine, but
we will be keeping an eye on it. Please let the infrastructure team
know of any problems that you see with the new set up and we will make
sure they are fixed ASAP.
Thanks,
--
James Tunnicliffe
This patch series moves various functionality duplicated in platform
cpuidle drivers to the core cpuidle driver. Also, the platform irq
disabling was removed as it appears that all calls into
cpuidle_call_idle will have already called local_irq_disable().
These changes have been pulled into linux-next.
Len, Andrew, can a request be made for Linus to pull these changes?
Acked-by: Jean Pihet<j-pihet(a)ti.com> (v6)
Tested-by: Jean Pihet<j-pihet(a)ti.com> (v6, omap3)
Tested-by: Amit Daniel<amit.kachhap(a)linaro.org> (v6, Exynos4)
Tested-by: Robert Lee<rob.lee(a)linaro.org> (imx51, imx6q)
Reviewed-by: Kevin Hilman <khilman(a)ti.com>
Reviewed-by: Daniel Lezcano <daniel.lezcano(a)linaro.org>
Reviewed-by: Deepthi Dharwar<deepthi(a)linux.vnet.ibm.com> (core cpuidle only)
v8 changes:
* v7 testing in linux-next revealed a bug reported by Hugh Dickins on x86
platforms. Investigated and fixed by Daniel Lezcano.
* Made a slight change to the defaut ARM WFI state macro as Daniel Lezcano
suggested the previous interface was prone to mis-use by platforms that
set power_specified to 1.
* updated to kernel v3.3
These v8 fixes have been applied to the pull tree being used by linux-next:
git://git.linaro.org/people/rob_lee/linux.git cpuidle_consol_pull
v7 submission can be found here:
http://www.spinics.net/lists/arm-kernel/msg162290.html
v7 changes:
* Made some struct whitespace alignment changes.
* Fixed a coding style violation (thanks Jean Pihet)
* Fixed a bug in davinci cpuidle (thanks Jean Pihet)
* Corrected the common ARM cpuidle WFI state description to be ARM platform
agnostic (thanks Kevin Hilman)
* Fixed the problem causing x86 and PPC builds to fail (thanks Deepthi)
* Re-added a line of code that was mistakenly removed (thanks Deepthi)
v6 submission can be found here:
http://www.spinics.net/lists/arm-kernel/msg162018.html
v6 changes:
* Fixed mindless bug in CONFIG_ARCH_HAS_RELAX code in drivers/cpuidle/cpuidle.c
* Removed inline from wrapper function (thanks Mike Turquette and Rob Herring)
* Add zeroing out of last_residency if error value is returned (thanks Mike)
* Made drivers/cpuidle/cpuidle.c more intelligently handle en_core_tk_irqen
flag allowing removal of the if (en_core_tk_irqen) in cpuidle_idle_call (thanks
Daniel Lezcano)
* Moved CPUIDLE_ARM_WFI_STATE macro to arch/arm/include/asm/cpuidle.h (thanks
Jean Pihet)
* Cleaned up some comments and a stray change (thanks Jean)
v5 submission can be found here:
http://www.spinics.net/lists/arm-kernel/msg161596.html
v5 changes:
* Added common cpu_do_idle function to core cpuidle
* Added time keep irq en wrapper to core cpuidle
* Removed pre/post enter
* Re-added platforms that can use new common code.
v4 submission can be found here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-January/082742.h…
v4 changes:
* Removed drivers/cpuidle/common.c
** Removed the initialization helper functions
** Removed the wrapper used to consolidate time keeping and irq enable/disable
* Add time keeping and local_irq_disable handling in cpuidle_call_idle().
* Made necessary modifications to a few platforms that required the most changes
** Note on omap3: changed structure of omap3_idle_drvdata and added
per_next_state and per_saved_state vars to accomodate new framework.
v3 submission can be found here:
http://www.spinics.net/lists/arm-kernel/msg156751.html
v3 changes:
* Made various code organization and style changes as suggested in v2 review.
(thanks Mark Brown, Rob Herring, Mike Turquette, Kevin Hillman, Daniel Lezcano)
* Removed at91 use of common code. A separate effort is underway to clean
at91 code and the author has offered to convert to common interface as part
of those changes (if this common interface is accepted in time).
* Made platform cpuidle_driver objects __initdata and dynamically added one
persistent instance of this object in common code.
* Removed imx5 pm usage of gpc_dvfs clock as it is no longer needed after
being enabled during clock initialization.
* Re-organized patches.
v2 submission can be found here:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/144199
v2 changes:
* Common interface moved to drivers/cpuidle and made non arch-specific.
* Made various fixes and suggested additions to the common cpuidle
code from v1 review. (Thanks Rob Herring and Mark Brown)
* Added callback for filling in driver_data field as needed.
* Modified the various platforms with these changes.
v1 submission can be found here:
http://comments.gmane.org/gmane.linux.ports.arm.kernel/142791
Robert Lee (8):
cpuidle: Add common time keeping and irq enabling
ARM: at91: Consolidate time keeping and irq enable
ARM: kirkwood: Consolidate time keeping and irq enable
ARM: davinci: Consolidate time keeping and irq enable
ARM: omap: Consolidate OMAP3 time keeping and irq enable
ARM: omap: Consolidate OMAP4 time keeping and irq enable
ARM: shmobile: Consolidate time keeping and irq enable
SH: shmobile: Consolidate time keeping and irq enable
arch/arm/include/asm/cpuidle.h | 30 ++++++++++++
arch/arm/kernel/Makefile | 2 +-
arch/arm/kernel/cpuidle.c | 21 +++++++++
arch/arm/mach-at91/cpuidle.c | 67 ++++++++++-----------------
arch/arm/mach-davinci/cpuidle.c | 82 +++++++++++++--------------------
arch/arm/mach-kirkwood/cpuidle.c | 72 +++++++++--------------------
arch/arm/mach-omap2/cpuidle34xx.c | 42 +++++++----------
arch/arm/mach-omap2/cpuidle44xx.c | 21 ++-------
arch/arm/mach-shmobile/cpuidle.c | 31 +++----------
arch/sh/kernel/cpu/shmobile/cpuidle.c | 10 ++--
drivers/cpuidle/cpuidle.c | 66 +++++++++++++++++++++++---
include/linux/cpuidle.h | 13 +++++-
12 files changed, 231 insertions(+), 226 deletions(-)
create mode 100644 arch/arm/include/asm/cpuidle.h
create mode 100644 arch/arm/kernel/cpuidle.c
--
1.7.9.4
Hi,
It is my intention to take ci.linaro.org offline for about 15 minutes
at 13:45 UTC (http://www.worldtimeserver.com/current_time_in_UTC.aspx)
so we can duplicate the server and start moving it to a larger EC2
instance. Users will know that ci.linaro.org has been running very
slowly for a while and we hope that this move will make it usable
while we continue to debug the performance problems that we are
seeing.
If the downtime will cause you significant problems, please get in
touch and we will arrange a better time.
Thanks,
--
James Tunnicliffe
Forwarding a post from debian-arm. I think I may be affected by this
bug. Could anyone help me check if this still applies to
3.1.1-1400-linaro-lt-mx5.
Best regards
ZK
------ Wiadomość oryginalna ------
Temat: Re: Linux 2.6.35.3 Kernel for ARM and SATA problems
Odesłano-Data: Tue, 20 Mar 2012 01:25:53 +0000 (UTC)
Odesłano-Od: debian-arm(a)lists.debian.org
Data: Mon, 19 Mar 2012 18:25:03 -0700
Nadawca: Mike Thompson <mpthompson(a)gmail.com>
Adresat: Phil Endecott <spam_from_debian_arm(a)chezphil.org>
Kopia: debian-arm(a)lists.debian.org
On Sun, Mar 18, 2012 at 1:38 PM, Phil Endecott
<spam_from_debian_arm(a)chezphil.org
<mailto:spam_from_debian_arm@chezphil.org>> wrote:
It works for me. I seem to recall a small amount of agro getting
the kernel
config right, but u-boot was always able to recognise the device. I
suggest
that you find (borrow) another SATA device to test with.
Good luck!
I was able to borrow another SATA drive and that works, thank heaven. I
thought I was going crazy for a while -- don't ask how many times I
re-compiled the kernel.
I did trace the problems I having to the ahci code in the kernel not
properly handling an ahci CONINIT event generated by my WD5000BEVT
drive. Seems this drive has extra SATA features implemented so that it
can be used in hot-plug arrays and these features aren't recognized by
the kernel driver so it just seems to shut down the drive and ignore
it. The other SATA drive that I do have working with the kernel doesn't
implement the extra features so the kernel is happy. Presumably these
problems were fixed in later kernels and the patches didn't make it into
Freescales 2.6.35.3 branch. On the other hand, the kernel might be fine
and the firmware in the drive isn't conforming to the ahci specs, but I
think that wold cause problems with the drive on other systems. I'm
going to keep looking into this as I do want to get my 500GB SATA drive
working with the iMX53 Quick Start.
Mike
This is just an early notification that the Linaro validation farm will be
physically moving to a new site next week. Unfortunately, the network
cables won't stretch that far, so it will mean some downtime. :)
Here's the tentative plan:
Wednesday, March 21st - the rack with the toolchain server will be shut
down, crated and sent off
Thursday, March 22nd - pretty much everything else will go offline (main
LAVA server, development boards)
Friday, March 23rd - physical move will happen, and if all goes well (what
could possibly go wrong?!) the main site and as many of the boards as
possible will go back online in their new home
Saturday, March 24th to Sunday, March 25th - finish configuring and
bringing up cloud services, toolchain server, etc.
There's another bit of good news here, that the lab will be getting a much
needed upgrade in the internet connection. A partial (but significant one)
at first, and a bigger one in about a month or so with redundant
connections.
Bear in mind that this is just the tentative plan, Dave or I will send out
a reminder and update as the date gets closer, or if something changes.
Thanks,
Paul Larson