Re: Linux 4.1.28

2016-08-02 Thread Michal Kubecek
On Tue, Aug 02, 2016 at 06:14:22PM +0200, Thomas Voegtle wrote: > On Wed, 20 Jul 2016, Michal Kubecek wrote: > > >On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: > >>And that one? > >>Happens while trying to start a firewall script with iptables-restore. > >> > >>[ 180.071999] NMI

Re: Linux 4.1.28

2016-08-02 Thread Thomas Voegtle
On Wed, 20 Jul 2016, Michal Kubecek wrote: On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: And that one? Happens while trying to start a firewall script with iptables-restore. [ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [iptables-restor:2338] ... [ 1

Re: Linux 4.1.28

2016-07-29 Thread Josh Hunt
On Fri, Jul 15, 2016 at 6:54 AM, Sasha Levin wrote: > On 07/15/2016 07:38 AM, Thomas Voegtle wrote: >> On Wed, 13 Jul 2016, Sasha Levin wrote: >> >>> I'm announcing the release of the 4.1.28 kernel. >> >> I have a serious memleak with 4.1.28 (like 20mb/s) >> I stripped down my kernel config and st

Re: Linux 4.1.28

2016-07-20 Thread Thomas Voegtle
On Wed, 20 Jul 2016, Michal Kubecek wrote: On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: And that one? Happens while trying to start a firewall script with iptables-restore. [ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [iptables-restor:2338] ... [ 1

Re: Linux 4.1.28

2016-07-20 Thread Michal Kubecek
On Fri, Jul 15, 2016 at 03:04:48PM +0200, Thomas Voegtle wrote: > And that one? > Happens while trying to start a firewall script with iptables-restore. > > [ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [iptables-restor:2338] ... > [ 180.072000] Call Trace: > [ 180.07200

Re: Linux 4.1.28

2016-07-20 Thread Arkadiusz Miskiewicz
On Wednesday 20 of July 2016, Arkadiusz Miskiewicz wrote: > On Friday 15 of July 2016, Thomas Voegtle wrote: > > On Fri, 15 Jul 2016, Sasha Levin wrote: > > > On 07/15/2016 07:38 AM, Thomas Voegtle wrote: > > >> On Wed, 13 Jul 2016, Sasha Levin wrote: > > >>> I'm announcing the release of the 4.1.2

Re: Linux 4.1.28

2016-07-19 Thread Arkadiusz Miskiewicz
On Friday 15 of July 2016, Thomas Voegtle wrote: > On Fri, 15 Jul 2016, Sasha Levin wrote: > > On 07/15/2016 07:38 AM, Thomas Voegtle wrote: > >> On Wed, 13 Jul 2016, Sasha Levin wrote: > >>> I'm announcing the release of the 4.1.28 kernel. > >> > >> I have a serious memleak with 4.1.28 (like 20mb

Re: Linux 4.1.28

2016-07-15 Thread Thomas Voegtle
On Fri, 15 Jul 2016, Sasha Levin wrote: On 07/15/2016 07:38 AM, Thomas Voegtle wrote: On Wed, 13 Jul 2016, Sasha Levin wrote: I'm announcing the release of the 4.1.28 kernel. I have a serious memleak with 4.1.28 (like 20mb/s) I stripped down my kernel config and started a bisect, which came

Re: Linux 4.1.28

2016-07-15 Thread Sasha Levin
On 07/15/2016 07:38 AM, Thomas Voegtle wrote: > On Wed, 13 Jul 2016, Sasha Levin wrote: > >> I'm announcing the release of the 4.1.28 kernel. > > I have a serious memleak with 4.1.28 (like 20mb/s) > I stripped down my kernel config and started a bisect, which came to: > > # first bad commit: [c5

Re: Linux 4.1.28

2016-07-15 Thread Thomas Voegtle
On Wed, 13 Jul 2016, Sasha Levin wrote: I'm announcing the release of the 4.1.28 kernel. I have a serious memleak with 4.1.28 (like 20mb/s) I stripped down my kernel config and started a bisect, which came to: # first bad commit: [c5ad33184354260be6d05de57e46a5498692f6d6] mm/swap.c: flush lru

Re: Linux 4.1.28

2016-07-14 Thread Takashi Iwai
Hi Sasha, On Thu, 14 Jul 2016 04:23:56 +0200, Sasha Levin wrote: > > I'm announcing the release of the 4.1.28 kernel. > > All users of the 4.1 kernel series must upgrade. > > The updated 4.1.y git tree can be found at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.gi

Linux 4.1.28

2016-07-13 Thread Sasha Levin
owser: http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary Linux 4.1.28 Al Viro (1): make nfs_atomic_open() call d_drop() o