All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cristian Rodríguez" <crrodriguez@opensuse.org>
To: Neal Cardwell <ncardwell@google.com>
Cc: Netdev <netdev@vger.kernel.org>,
	Yuchung Cheng <ycheng@google.com>,
	Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: BUG: soft lockup - CPU#6 stuck for 22s! [httpd2-event:15597]
Date: Wed, 29 Aug 2012 23:05:10 -0400	[thread overview]
Message-ID: <503ED866.3020609@opensuse.org> (raw)
In-Reply-To: <CADVnQy=bdHm2jcuReZaxr-qRMRWLDLnVP-jkzBTE-HPZ9FROmw@mail.gmail.com>

El mié 29 ago 2012 21:37:46 CLT, Neal Cardwell escribió:

Hi neal, thanks for taking a look at this..

> 1) Are you still seeing this problem in your workload? If so, would
> you have time to try another small patch to add instrumentation to
> track down the cause?

After Eric's patch I no longer see this backtrace or hang, however the 
machine does
hang apparently for another reason that I have been unable to capture
no clue at all in the logs and the KVM-over-ip video does not respond 
after hang, needing a reset,
that's strange though, as it is usually able to display kernel messages 
after a crash.

> 2) Do you happen to run with the tcp_mtu_probing sysctl enabled?

   No, sysctl returns : net.ipv4.tcp_mtu_probing = 0

      reply	other threads:[~2012-08-30  3:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25  0:50 BUG: soft lockup - CPU#6 stuck for 22s! [httpd2-event:15597] Cristian Rodríguez
2012-08-25  8:59 ` Eric Dumazet
2012-08-25  9:14   ` Eric Dumazet
2012-08-25 11:47     ` Eric Dumazet
2012-08-25 17:45       ` Cristian Rodríguez
2012-08-25 17:52       ` Eric Dumazet
2012-08-27  4:02       ` Neal Cardwell
2012-08-27  4:06         ` Eric Dumazet
2012-08-30  1:37           ` Neal Cardwell
2012-08-30  3:05             ` Cristian Rodríguez [this message]

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=503ED866.3020609@opensuse.org \
    --to=crrodriguez@opensuse.org \
    --cc=eric.dumazet@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=ycheng@google.com \
    /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.