All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Soft lockup issue in Linux 4.1.9
Date: Thu, 1 Oct 2015 06:41:46 +0200	[thread overview]
Message-ID: <560CB98A.10107@tomt.net> (raw)
In-Reply-To: <pan.2015.09.30.22.37.34@googlemail.com>

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 hit by this, but
> you are probably the first one to get a meaningful stacktrace! \o/
>
>> [  204.478380] Call Trace:
>> [  204.478381]  <IRQ>
>> [  204.478385]  [<ffffffff81076121>] ? try_to_del_timer_sync+0x43/0x4d
>> [  204.478386]  [<ffffffff810760de>] ? del_timer+0x4d/0x4d
>> [  204.478388]  [<ffffffff8107614b>] ? del_timer_sync+0x20/0x3d
>
> Can you try to revert
>
>     [PATCH 4.1 157/159] inet: fix races with reqsk timers
>
> and see how that works for you? I'll do the same on my end. So far the
> only thing I ever could gleam was an rcu stall after cpuidle_enter(),
> but never anything regarding the timer - though it was definitely
> related to NIC activity after idle.

I'm running with this patch reverted now as well. 2 hours no issues so 
far, but I can't conclude anything yet as I've seen it take up to 6+ 
hours to explode here. As a result the bisect was going veeery slowly.

  reply	other threads:[~2015-10-01  4:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 21:59 Soft lockup issue in Linux 4.1.9 Olivier Bonvalet
2015-09-30 22:37 ` Holger Hoffstätte
2015-10-01  4:41   ` Andre Tomt [this message]
2015-10-01 10:51     ` Holger Hoffstätte
     [not found] ` <560D1223.3070606@googlemail.com>
     [not found]   ` <CANn89i+B5T4Rhs8HnrC0+f+GhLvBFfpr4BVDvhkVOveSfy9B8Q@mail.gmail.com>
2015-10-01 11:43     ` Holger Hoffstätte
2015-10-01 11:52       ` Eric Dumazet
2015-10-02  6:52         ` Andre Tomt
2015-10-02  7:17           ` Holger Hoffstätte
2015-10-02 19:25             ` Wolfgang Walter
2015-10-02 19:25               ` Wolfgang Walter
2015-10-03 19:14             ` Thomas D.
2015-10-17 23:41               ` Greg Kroah-Hartman
2015-10-17 23:41                 ` Greg Kroah-Hartman
2015-10-02 20:04         ` Thomas Gleixner
2015-10-02 20:59           ` Eric Dumazet
2015-10-02 21:04             ` Thomas Gleixner
2015-10-02 21:32               ` Eric Dumazet
2015-10-08 16:56         ` Christoph Biedl
2015-10-08 19:27           ` Holger Hoffstätte

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=560CB98A.10107@tomt.net \
    --to=andre@tomt.net \
    --cc=holger.hoffstaette@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.