On Sat, Oct 03, 2015 at 09:14:16PM +0200, Thomas D. wrote:
> Hi,
>
> Holger Hoffstätte wrote:
> > Greg, any chance you can drop this into the pending 4.1.10? Otherwise people
> > will get another broken release.
>
> For me it looks like the request was too late, the patch is not included
> in
On Sat, Oct 03, 2015 at 09:14:16PM +0200, Thomas D. wrote:
> Hi,
>
> Holger Hoffstätte wrote:
> > Greg, any chance you can drop this into the pending 4.1.10? Otherwise people
> > will get another broken release.
>
> For me it looks like the request was too late, the patch is not included
> in
On 10/08/15 18:56, Christoph Biedl wrote:
> Eric Dumazet wrote...
>
> [ commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af ]
>
>> It definitely should help !
>
> Yesterday, I've experienced issues somewhat similar to this, but I'm
> not entirely sure:
>
> Four of five systems running 4.1.9
Eric Dumazet wrote...
[ commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af ]
> It definitely should help !
Yesterday, I've experienced issues somewhat similar to this, but I'm
not entirely sure:
Four of five systems running 4.1.9 stopped working. No reaction on
network, keyboard, serial console.
Eric Dumazet wrote...
[ commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af ]
> It definitely should help !
Yesterday, I've experienced issues somewhat similar to this, but I'm
not entirely sure:
Four of five systems running 4.1.9 stopped working. No reaction on
network, keyboard, serial console.
On 10/08/15 18:56, Christoph Biedl wrote:
> Eric Dumazet wrote...
>
> [ commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af ]
>
>> It definitely should help !
>
> Yesterday, I've experienced issues somewhat similar to this, but I'm
> not entirely sure:
>
> Four of five systems running 4.1.9
Hi,
Holger Hoffstätte wrote:
> Greg, any chance you can drop this into the pending 4.1.10? Otherwise people
> will get another broken release.
For me it looks like the request was too late, the patch is not included
in 4.1.10. So don't forget to re-apply the patch when doing the upgrade.
Greg,
Hi,
Holger Hoffstätte wrote:
> Greg, any chance you can drop this into the pending 4.1.10? Otherwise people
> will get another broken release.
For me it looks like the request was too late, the patch is not included
in 4.1.10. So don't forget to re-apply the patch when doing the upgrade.
Greg,
On Fri, 2015-10-02 at 23:04 +0200, Thomas Gleixner wrote:
> On Fri, 2 Oct 2015, Eric Dumazet wrote:
> > On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote:
> >
> > > What makes sure, that the timer cannot be readded while that timer
> > > callback is running?
> >
> > What is exactly your
On Fri, 2 Oct 2015, Eric Dumazet wrote:
> On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote:
>
> > What makes sure, that the timer cannot be readded while that timer
> > callback is running?
>
> What is exactly your question ?
CPU0CPU1
timer expires
On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote:
> What makes sure, that the timer cannot be readded while that timer
> callback is running?
What is exactly your question ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 1 Oct 2015, Eric Dumazet wrote:
> On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
> wrote:
> > On 10/01/15 13:29, Eric Dumazet wrote:
>
> >> commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
> >> Author: Eric Dumazet
> >> Date: Thu Aug 13 15:44:51 2015 -0700
> >>
> >> inet: fix
Am Freitag, 2. Oktober 2015, 09:17:16 schrieb Holger Hoffstätte:
> On 10/02/15 08:52, Andre Tomt wrote:
> > On 01. okt. 2015 13:52, Eric Dumazet wrote:
> >> On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
> >>
> >> wrote:
> >>> On 10/01/15 13:29, Eric Dumazet wrote:
> commit
On 10/02/15 08:52, Andre Tomt wrote:
> On 01. okt. 2015 13:52, Eric Dumazet wrote:
>> On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
>> wrote:
>>> On 10/01/15 13:29, Eric Dumazet wrote:
>>
commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
Author: Eric Dumazet
Date: Thu Aug 13
On 01. okt. 2015 13:52, Eric Dumazet wrote:
On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
wrote:
On 10/01/15 13:29, Eric Dumazet wrote:
commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
Author: Eric Dumazet
Date: Thu Aug 13 15:44:51 2015 -0700
inet: fix potential deadlock in
On 01. okt. 2015 13:52, Eric Dumazet wrote:
On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
wrote:
On 10/01/15 13:29, Eric Dumazet wrote:
commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
Author: Eric Dumazet
Date: Thu Aug 13
Am Freitag, 2. Oktober 2015, 09:17:16 schrieb Holger Hoffstätte:
> On 10/02/15 08:52, Andre Tomt wrote:
> > On 01. okt. 2015 13:52, Eric Dumazet wrote:
> >> On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
> >>
> >> wrote:
> >>> On 10/01/15 13:29, Eric Dumazet
On Thu, 1 Oct 2015, Eric Dumazet wrote:
> On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
> wrote:
> > On 10/01/15 13:29, Eric Dumazet wrote:
>
> >> commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
> >> Author: Eric Dumazet
> >> Date:
On Fri, 2015-10-02 at 23:04 +0200, Thomas Gleixner wrote:
> On Fri, 2 Oct 2015, Eric Dumazet wrote:
> > On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote:
> >
> > > What makes sure, that the timer cannot be readded while that timer
> > > callback is running?
> >
> > What is exactly your
On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote:
> What makes sure, that the timer cannot be readded while that timer
> callback is running?
What is exactly your question ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Fri, 2 Oct 2015, Eric Dumazet wrote:
> On Fri, 2015-10-02 at 22:04 +0200, Thomas Gleixner wrote:
>
> > What makes sure, that the timer cannot be readded while that timer
> > callback is running?
>
> What is exactly your question ?
CPU0CPU1
timer expires
On 10/02/15 08:52, Andre Tomt wrote:
> On 01. okt. 2015 13:52, Eric Dumazet wrote:
>> On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
>> wrote:
>>> On 10/01/15 13:29, Eric Dumazet wrote:
>>
commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
Author: Eric
On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
wrote:
> On 10/01/15 13:29, Eric Dumazet wrote:
>> commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
>> Author: Eric Dumazet
>> Date: Thu Aug 13 15:44:51 2015 -0700
>>
>> inet: fix potential deadlock in reqsk_queue_unlink()
>>
>> When
p 2015 23:59:43 +0200, Olivier Bonvalet wrote:
>>>>
>>>>> for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
>>>>> 4.1.9, and have some random soft lockup. If this can help :
>>>>
>>>> Congratulations! You're n
On Thu, 01 Oct 2015 06:41:46 +0200, Andre Tomt wrote:
> On 01. okt. 2015 00:37, Holger Hoffstätte wrote:
>> On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
>>
>>> for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
>>> 4.1.9,
On Thu, Oct 1, 2015 at 4:43 AM, Holger Hoffstätte
wrote:
> On 10/01/15 13:29, Eric Dumazet wrote:
>> commit 83fccfc3940c4a2db90fd7e7079f5b465cd8c6af
>> Author: Eric Dumazet
>> Date: Thu Aug 13 15:44:51 2015 -0700
>>
>> inet: fix
>>>> On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
>>>>
>>>>> for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
>>>>> 4.1.9, and have some random soft lockup. If this can help :
>>>>
>>>> Cong
On Thu, 01 Oct 2015 06:41:46 +0200, Andre Tomt wrote:
> On 01. okt. 2015 00:37, Holger Hoffstätte wrote:
>> On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
>>
>>> for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
>>> 4.1.9,
On 01. okt. 2015 00:37, Holger Hoffstätte wrote:
On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
4.1.9, and have some random soft lockup. If this can help :
Congratulations! You're not the first one to get
On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
> for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
> 4.1.9, and have some random soft lockup. If this can help :
Congratulations! You're not the first one to get hit by this, but
you are probably the fir
Hi,
for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
4.1.9, and have some random soft lockup. If this can help :
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00
On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
> for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
> 4.1.9, and have some random soft lockup. If this can help :
Congratulations! You're not the first one to get hit by this, but
you are probably the fir
Hi,
for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
4.1.9, and have some random soft lockup. If this can help :
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00
On 01. okt. 2015 00:37, Holger Hoffstätte wrote:
On Wed, 30 Sep 2015 23:59:43 +0200, Olivier Bonvalet wrote:
for information, I've just upgraded 6 servers from Linux 4.1.8 to Linux
4.1.9, and have some random soft lockup. If this can help :
Congratulations! You're not the first one to get
face if already configured
Florian Westphal (1):
netlink: don't hold mutex in rcu callback when releasing mmapd ring
Gavin Shan (2):
powerpc/pseries: Fix corrupted pdn list
powerpc/eeh: Fix fenced PHB caused by eeh_slot_error_detail()
Greg Kroah-Hartman (1):
Linux 4.1.9
Haggai Era
face if already configured
Florian Westphal (1):
netlink: don't hold mutex in rcu callback when releasing mmapd ring
Gavin Shan (2):
powerpc/pseries: Fix corrupted pdn list
powerpc/eeh: Fix fenced PHB caused by eeh_slot_error_detail()
Greg Kroah-Hartman (1):
Linux 4.1.9
Haggai Era
36 matches
Mail list logo