On Tue, 2014-01-14 at 02:31 -0500, Len Brown wrote:
This is a false alarm.
Thanks for the follow-up, Mel.
Agreed, it makes no sense for ebizzy measure 'throughput', when a
library debug bottleneck
prevents it from scaling past 3% CPU utilization.
Still, the broken configuration did
On Tue, 2014-01-14 at 09:01 +0100, Mike Galbraith wrote:
On Tue, 2014-01-14 at 02:31 -0500, Len Brown wrote:
This is a false alarm.
Thanks for the follow-up, Mel.
Agreed, it makes no sense for ebizzy measure 'throughput', when a
library debug bottleneck
prevents it from scaling
On 14/01/2014 03:14, Jason Cooper wrote:
Gregory,
On Wed, Jan 08, 2014 at 04:06:25PM +0100, Gregory CLEMENT wrote:
Hi,
Here come the 5th version of the series fixing the i2c bus hang on A0
version of the Armada XP SoCs. It occurred on the early release of the
OpenBlocks AX3-4 boards.
On Mon, Jan 13, 2014 at 09:58:32AM -0800, gre...@linuxfoundation.org wrote:
The patch below does not apply to the 3.10-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email the backport, including the original git commit
id to
At Tue, 14 Jan 2014 14:07:36 +0800,
Hui Wang wrote:
On some AIO (All In One) models with the codec alc668
(Vendor ID: 0x10ec0668) on it, when we plug a headphone into the jack,
the system will switch the output to headphone and set the speaker to
automute as well as change the speaker
From: walt
On 01/09/2014 03:50 PM, Sarah Sharp wrote:
On Tue, Jan 07, 2014 at 03:57:00PM -0800, walt wrote:
I've wondered if my xhci problems might be caused by hardware quirks, and
wondering why I seem to be the only one who has this problem.
Maybe I could take one for the team by
Il 14/01/2014 07:24, Li Zefan ha scritto:
From: Andy Honig aho...@google.com
commit fda4e2e85589191b123d31cdc21fd33ee70f50fd upstream.
In kvm_lapic_sync_from_vapic and kvm_lapic_sync_to_vapic there is the
potential to corrupt kernel memory if userspace provides an address that
is at the
On Mon, Jan 13, 2014 at 06:52:06PM -0800, Guenter Roeck wrote:
Hi Greg,
I get the following new build failure for 3.10 and 3.12.
Affected are m68k:allmodconfig and sparc64:allmodconfig.
drivers/net/virtio_net.c: In function 'receive_mergeable':
drivers/net/virtio_net.c:330:29: warning:
On Tue, Jan 14, 2014 at 09:35:44AM +, Steve Capper wrote:
On Mon, Jan 13, 2014 at 09:58:32AM -0800, gre...@linuxfoundation.org wrote:
The patch below does not apply to the 3.10-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email
On 01/14/2014 03:47 AM, Michael S. Tsirkin wrote:
On Mon, Jan 13, 2014 at 06:52:06PM -0800, Guenter Roeck wrote:
Hi Greg,
I get the following new build failure for 3.10 and 3.12.
Affected are m68k:allmodconfig and sparc64:allmodconfig.
drivers/net/virtio_net.c: In function
At Mon, 13 Jan 2014 16:27:21 -0800,
Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.8 release.
There are 77 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
On Tue, Jan 14, 2014 at 06:35:12AM -0800, Guenter Roeck wrote:
On 01/14/2014 03:47 AM, Michael S. Tsirkin wrote:
On Mon, Jan 13, 2014 at 06:52:06PM -0800, Guenter Roeck wrote:
Hi Greg,
I get the following new build failure for 3.10 and 3.12.
Affected are m68k:allmodconfig and
The sata_mv driver supports the SATA IP found in several Marvell SoCs.
As some new SATA registers have been introduced with the Armada 370/XP
SoCs, a way to identify them is needed.
This patch introduces a new compatible string for the SATA IP found in
Armada 370/XP SoCs.
Signed-off-by: Simon
From: Lior Amsalem al...@marvell.com
On Armada 370/XP SoCs, once a disk is removed from a SATA port, then the
re-plug events are not detected by the sata_mv driver. This patch fixes
the issue by updating the PHY speed in the LP_PHY_CTL register (0x58)
according to the SControl speed.
Note that
Hello,
This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
SoCs: once a disk is removed from a SATA port, then the re-plug events
are not detected by the sata_mv driver.
This should be applied to the -stable kernels 3.10 and onwards.
Changes since v1:
- Introduces a new
This patch updates the Armada 370/XP SATA node with the new compatible
string marvell,armada-370-xp-sata.
Signed-off-by: Simon Guinot simon.gui...@sequanux.org
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Jason Cooper ja...@lakedaemon.net
Cc: Andrew Lunn and...@lunn.ch
Cc: Gregory
Hi Simon,
On 14/01/2014 15:50, Simon Guinot wrote:
This patch updates the Armada 370/XP SATA node with the new compatible
string marvell,armada-370-xp-sata.
Usually we try to use the name of the first SoC instead of a family name.
So here it should be marvell,armada-370-sata
Thanks,
Gregory
Hi Simon, Jeff, Tejun,
On 14/01/2014 15:50, Simon Guinot wrote:
The sata_mv driver supports the SATA IP found in several Marvell SoCs.
As some new SATA registers have been introduced with the Armada 370/XP
SoCs, a way to identify them is needed.
This patch introduces a new compatible string
Simon,
On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
Hello,
This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
SoCs: once a disk is removed from a SATA port, then the re-plug events
are not detected by the sata_mv driver.
This should be applied to the
Hey, Jason.
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
I see no point to breaking up this series only to have both pieces end
up in stable. Are you ok with taking the whole thing?
Yeah, sure. Gregory thought the device id could be better. Is that
not the case?
Thanks.
On Tue, Jan 14, 2014 at 10:21:12AM -0500, Tejun Heo wrote:
Hey, Jason.
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
I see no point to breaking up this series only to have both pieces end
up in stable. Are you ok with taking the whole thing?
Yeah, sure. Gregory thought
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
Hello,
This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
SoCs: once a disk is removed from a SATA port, then the re-plug events
And... despite typing the stable ML address quite often, I still got it
wrong. Need more coffee.
thx,
Jason.
arm-soc folks,
Sorry for the lateness in the window on this one. I'd like to see it
get into v3.13 if possible, but if it doesn't get there till v3.13.1, I
understand.
This fixes a
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
Hello,
This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
SoCs: once a disk is removed from a SATA port, then the re-plug events
As stable kernel older than 3.10 are no longer maintained
Please take a look at www.kernel.org
Both 3.4 and 3.2 have had stable updated this year.
Andrew
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a message to majord...@vger.kernel.org
More majordomo
On Tue, Jan 14, 2014 at 04:48:34PM +0100, Simon Guinot wrote:
As stable kernel older than 3.10 are no longer maintained, I think
we don't need to point out a specific commit as a -stable target.
Simply Cc'ing -stable without any extra informations should be good
enough.
Well, somebody
Finally the right email address this time
Sorry
Boaz
Original Message
Subject: Re: Fwd: [PATCH] pnfs-obj: Proper delay for NFS4ERR_RECALLCONFLICT in
layout_get_done
Date: Tue, 14 Jan 2014 17:10:58 +0200
From: Boaz Harrosh bharr...@panasas.com
To: Trond Myklebust
An NFS4ERR_RECALLCONFLICT is returned by server from a GET_LAYOUT
only when a Server Sent a RECALL do to that GET_LAYOUT, or
the RECALL and GET_LAYOUT crossed on the wire.
In any way this means we want to wait at most until in-flight IO
is finished and the RECALL can be satisfied.
So a proper
Simon,
On Tue, Jan 14, 2014 at 04:48:34PM +0100, Simon Guinot wrote:
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
Hello,
This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
On Mon, Jan 06, 2014 at 11:25:53PM +0100, Rafael J. Wysocki wrote:
Queued up as a fix for 3.13 (I fixed up the indentation).
Ah, sorry, I missed this chunk of the thread. If the system provides
valid _BIF data then we should possibly just fall back to that rather
than adding another quirk
On Thu, Jan 02, 2014 at 03:37:57PM +0800, Lan Tianyu wrote:
The aml method _BIX of NEC LZ750/LS returns a broken package which
skip the first member Revision according ACPI 5.0 spec Table 10-234.
Why don't we just ignore an invalid _BIX and fall back to _BIF? That
seems more reasonable than
On Tue, Jan 14, 2014 at 10:59:45AM -0500, Jason Cooper wrote:
...
The linux-stable team isn't the only people who find this information
useful. Distros maintaining older kernels would find it very helpful
when going through -stable patches to know easily if a patch should be
backported
On Mon, Jan 13, 2014 at 02:29:04PM -0700, Stephen Warren wrote:
From: Stephen Warren swar...@nvidia.com
The body of i2c_parent_is_i2c_adapter() is currently guarded by
CONFIG_I2C_MUX instead.
This paragraph sounds strange to me. I'll update it a little. After that
I'll go looking for a brown
On Tue, Jan 14, 2014 at 10:59:45AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 04:48:34PM +0100, Simon Guinot wrote:
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
Hello,
On Mon, Jan 13, 2014 at 03:39:07PM -0800, walt wrote:
On 01/09/2014 03:50 PM, Sarah Sharp wrote:
On Tue, Jan 07, 2014 at 03:57:00PM -0800, walt wrote:
I've wondered if my xhci problems might be caused by hardware quirks, and
wondering why I seem to be the only one who has this problem.
From: Stephen Warren swar...@nvidia.com
The current MAX8907 driver has two issues related to weekday value
handling:
1)
The HW WEEKDAY register has range 0..6 rather than 1..7 as documented.
Note that I validated the actual HW range by observing the HW register
roll from 6-0 rather than 6-7-1
Cc: stable@vger.kernel.org
Signed-off-by: Bjørn Mork bj...@mork.no
---
Hello Greg!
I saw your post on Google+ :-) You'll probably want one of
these nice adapters to go with that toy. It's simply not worth
the job making the console cable yourself.
Bjørn
drivers/usb/serial/ftdi_sio.c | 1
On Tue, Jan 14, 2014 at 04:47:48PM +0200, Michael S. Tsirkin wrote:
On Tue, Jan 14, 2014 at 06:35:12AM -0800, Guenter Roeck wrote:
On 01/14/2014 03:47 AM, Michael S. Tsirkin wrote:
On Mon, Jan 13, 2014 at 06:52:06PM -0800, Guenter Roeck wrote:
Hi Greg,
I get the following new build
On Tue, Jan 14, 2014 at 06:56:54PM +0100, Bjørn Mork wrote:
Cc: stable@vger.kernel.org
Signed-off-by: Bjørn Mork bj...@mork.no
---
Hello Greg!
I saw your post on Google+ :-) You'll probably want one of
these nice adapters to go with that toy. It's simply not worth
the job making the
Nicolas Ferre nicolas.fe...@atmel.com writes:
From: Jean-Jacques Hiblot jjhib...@traphandler.com
There was a copy/paste error when reading the nwe_pulse value.
Signed-off-by: Jean-Jacques Hiblot jjhib...@traphandler.com
Acked-by: Boris BREZILLON b.brezil...@overkiz.com
Cc: stable
Hello,
This patch series fixes a SATA disk hotplug issue for the Armada 370/XP
SoCs: once a disk is removed from a SATA port, then the re-plug events
are not detected by the sata_mv driver.
As this hotplug issue have been emphasized by 9ae6f740b49f
arm: mach-mvebu: add support for Armada 370 and
On Tue, 2014-01-14 at 17:32 +0200, Boaz Harrosh wrote:
An NFS4ERR_RECALLCONFLICT is returned by server from a GET_LAYOUT
only when a Server Sent a RECALL do to that GET_LAYOUT, or
the RECALL and GET_LAYOUT crossed on the wire.
In any way this means we want to wait at most until in-flight IO
The sata_mv driver supports the SATA IP found in several Marvell SoCs.
As some new SATA registers have been introduced with the Armada 370/XP
SoCs, a way to identify them is needed.
This patch introduces a new compatible string for the SATA IP found in
Armada 370/XP SoCs.
Signed-off-by: Simon
This patch updates the Armada 370/XP SATA node with the new compatible
string marvell,armada-370-sata.
Signed-off-by: Simon Guinot simon.gui...@sequanux.org
Cc: Thomas Petazzoni thomas.petazz...@free-electrons.com
Cc: Jason Cooper ja...@lakedaemon.net
Cc: Andrew Lunn and...@lunn.ch
Cc: Gregory
From: Lior Amsalem al...@marvell.com
On Armada 370/XP SoCs, once a disk is removed from a SATA port, then the
re-plug events are not detected by the sata_mv driver. This patch fixes
the issue by updating the PHY speed in the LP_PHY_CTL register (0x58)
according to the SControl speed.
Note that
Jason Cooper ja...@lakedaemon.net writes:
And... despite typing the stable ML address quite often, I still got it
wrong. Need more coffee.
thx,
Jason.
arm-soc folks,
Sorry for the lateness in the window on this one. I'd like to see it
get into v3.13 if possible, but if it doesn't get
On Tue, Jan 14, 2014 at 11:14:18AM -0800, Kevin Hilman wrote:
Jason Cooper ja...@lakedaemon.net writes:
And... despite typing the stable ML address quite often, I still got it
wrong. Need more coffee.
thx,
Jason.
arm-soc folks,
Sorry for the lateness in the window on this
On 01/13/2014 05:26 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.4.77 release.
There are 27 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 01/13/2014 05:26 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.27 release.
There are 62 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 01/13/2014 05:27 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.8 release.
There are 77 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
On Tue, Jan 14, 2014 at 06:56:54PM +0100, Bjørn Mork wrote:
Cc: stable@vger.kernel.org
Signed-off-by: Bjørn Mork bj...@mork.no
---
Hello Greg!
I saw your post on Google+ :-) You'll probably want one of
these nice adapters to go with
Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 (Delay creation of
khcvd thread) moved the call of hvc_init from being a device_initcall
into hvc_alloc, and used a non-null hvc_driver as indication of whether
hvc_init had already been called.
The problem with this is that hvc_driver is only
On Tue, Jan 14, 2014 at 04:03:37PM -0500, Paul Gortmaker wrote:
Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 (Delay creation of
khcvd thread) moved the call of hvc_init from being a device_initcall
into hvc_alloc, and used a non-null hvc_driver as indication of whether
hvc_init had already
On 01/14/2014 09:20 AM, Sarah Sharp wrote:
On Mon, Jan 13, 2014 at 03:39:07PM -0800, walt wrote:
Sarah, I just fixed my xhci bug for US$19.99 :)
#lspci | tail -1
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller
(rev 03)
This new NEC usb3 controller does
Greg,
I am going to do more testing but it seems that reverting this patch
from 3.4.69 fixes the BUG
commit b07ef016454ff46f98e633b5a6247ca7e343fb67
Author: Khalid Aziz khalid.a...@oracle.com
I also verified that I cannot reproduce this problem with 3.13-rc8
Guillaume.
On 14 Jan 21:34,
On Jan 14, 2014, at 17:21, Boaz Harrosh bharr...@panasas.com wrote:
On 01/14/2014 09:05 PM, Trond Myklebust wrote:
On Tue, 2014-01-14 at 17:32 +0200, Boaz Harrosh wrote:
For the default mount option of 'timeo=600', and the default #define
NFS4_POLL_RETRY_MIN==HZ/10, this means we can end
On Jan 14, 2014, at 17:43, Trond Myklebust trond.mykleb...@primarydata.com
wrote:
On Jan 14, 2014, at 17:21, Boaz Harrosh bharr...@panasas.com wrote:
On 01/14/2014 09:05 PM, Trond Myklebust wrote:
On Tue, 2014-01-14 at 17:32 +0200, Boaz Harrosh wrote:
For the default mount option of
On 01/14/2014 09:05 PM, Trond Myklebust wrote:
On Tue, 2014-01-14 at 17:32 +0200, Boaz Harrosh wrote:
For the default mount option of 'timeo=600', and the default #define
NFS4_POLL_RETRY_MIN==HZ/10, this means we can end up pounding the server
with 600 LAYOUTGET requests within the space
On Tue, Jan 14, 2014 at 10:02:28AM -0800, Guenter Roeck wrote:
On Tue, Jan 14, 2014 at 04:47:48PM +0200, Michael S. Tsirkin wrote:
On Tue, Jan 14, 2014 at 06:35:12AM -0800, Guenter Roeck wrote:
On 01/14/2014 03:47 AM, Michael S. Tsirkin wrote:
On Mon, Jan 13, 2014 at 06:52:06PM -0800,
On Mon, Jan 13, 2014 at 07:02:23PM -0800, Guenter Roeck wrote:
On 01/13/2014 04:26 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.27 release.
There are 62 patches in this series, all will be posted as a response
to this one. If anyone has any issues
On Tue, Jan 14, 2014 at 12:30:35PM -0700, Shuah Khan wrote:
On 01/13/2014 05:26 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.27 release.
There are 62 patches in this series, all will be posted as a response
to this one. If anyone has any issues with
On Tue, Jan 14, 2014 at 11:42:22PM +0900, Satoru Takeuchi wrote:
At Mon, 13 Jan 2014 16:27:21 -0800,
Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.12.8 release.
There are 77 patches in this series, all will be posted as a response
to this one. If
On Tue, Jan 14, 2014 at 10:59:45AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 04:48:34PM +0100, Simon Guinot wrote:
On Tue, Jan 14, 2014 at 10:14:04AM -0500, Jason Cooper wrote:
Simon,
On Tue, Jan 14, 2014 at 03:50:04PM +0100, Simon Guinot wrote:
Hello,
Commit 3dc6475 (bcm63xx_enet: add support Broadcom BCM6345 Ethernet)
changed the ENETDMA[CS] macros such that they are no longer macros, but
actual register offset definitions. The bcm63xx_udc driver was not
updated, and as a result, causes the following build error to pop up:
CC
On 01/15/2014 12:47 AM, Trond Myklebust wrote:
On Jan 14, 2014, at 17:43, Trond Myklebust trond.mykleb...@primarydata.com
wrote:
On Jan 14, 2014, at 17:21, Boaz Harrosh bharr...@panasas.com wrote:
On 01/14/2014 09:05 PM, Trond Myklebust wrote:
On Tue, 2014-01-14 at 17:32 +0200, Boaz
From: Andreas Rohner andreas.roh...@gmx.net
Subject: nilfs2: fix segctor bug that causes file system corruption
There is a bug in the function nilfs_segctor_collect, which results in
active data being written to a segment, that is marked as clean. It is
possible, that this segment is selected
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Mikulas Patocka mpato...@redhat.com
Subject: mm: fix crash when using XFS on loopback
The patch 8456a648cf44f (slab: use struct page for slab management)
causes a crash in the LVM2 testsuite on PA-RISC (the crashing test is
fsadm.sh). The testsuite doesn't crash on 3.12, crashes on
From: Qais Yousef qais.you...@imgtec.com
Subject: crash_dump: fix compilation error (on MIPS at least)
In file included from kernel/crash_dump.c:2:0:
include/linux/crash_dump.h:22:27: error: unknown type name `pgprot_t'
when CONFIG_CRASH_DUMP=y
The error was traced back to this commit:
Jason Wang jasow...@redhat.com writes:
From: Asias He asias.he...@gmail.com
vqs are freed in virtscsi_freeze but the hotcpu_notifier is not
unregistered. We will have a use-after-free usage when the notifier
callback is called after virtscsi_freeze.
Fixes:
hi Greg,
4f9b4fb7a2091eec339413a460b1665758401828
ARM: 7815/1: kexec: offline non panic CPUs on Kdump panic
This looks applicable to stable-3.10, that offlines non panic CPUs on
Kdump panic. Without this patch, the Kdump panic process will abort when
checking number of online CPUS in function
On Tue, Jan 14, 2014 at 09:37:22AM +0800, Li Zefan wrote:
On 2014/1/13 23:57, Greg Kroah-Hartman wrote:
On Mon, Jan 13, 2014 at 03:28:11PM +0800, Li Zefan wrote:
We have several long-term and extended stable kernels, and it's possible
that a bug fix is in some stable versions but is missing
From: Len Brown len.br...@intel.com
In Linux-3.9 we removed the mwait_idle() loop:
'x86 idle: remove mwait_idle() and idle=mwait cmdline param'
(69fb3676df3329a7142803bb3502fa59dc0db2e3)
The reasoning was that modern machines should be sufficiently
happy during the boot process using the
My late client made his last will and testament in your favour, i sent
letters to you but got no response, i advise you contact me
immediately.
Barr Mark Freedman
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a message to majord...@vger.kernel.org
More
74 matches
Mail list logo
