From: Don Zickus <dzickus@redhat.com>
To: ZAK Magnus <zakmagnus@google.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Mandeep Singh Baines <msb@chromium.org>
Subject: Re: [PATCH v3 2/2] Make hard lockup detection use timestamps
Date: Fri, 29 Jul 2011 09:10:09 -0400 [thread overview]
Message-ID: <20110729131009.GQ2581@redhat.com> (raw)
In-Reply-To: <CAAuSN93Qjk4eEAvm_Xn=O-0t+qhAyKmxy6HyPuyzJ35tX2u_CQ@mail.gmail.com>
On Thu, Jul 28, 2011 at 05:16:00PM -0700, ZAK Magnus wrote:
> No news?
>
> I've been testing and looking into issues and I realized dump_stack()
> calls touch_nmi_watchdog(). That wrecks what the patch is trying to do
> so I'm changing it to save the trace and print it later after the
> stall has completed. This would also resolve some other things you
> were saying weren't so good. Hopefully the logic is similar enough
> that some things you may have learned still apply.
Sorry, I have been caught up with a bunch of other work related issues
here. I should be able to poke at this today.
Yeah, I forgot about the console write path. That was causing another
separate problem for me a while ago with softlockups causing a
touch_nmi_watchdog on all cpus. I still have to trade fixes to get that
in.
Cheers,
Don
next prev parent reply other threads:[~2011-07-29 13:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 18:11 [PATCH v3 2/2] Make hard lockup detection use timestamps Alex Neronskiy
2011-07-22 19:53 ` Don Zickus
2011-07-22 22:34 ` ZAK Magnus
2011-07-25 12:44 ` Don Zickus
2011-07-29 0:16 ` ZAK Magnus
2011-07-29 13:10 ` Don Zickus [this message]
2011-07-29 20:55 ` Don Zickus
2011-07-29 23:12 ` ZAK Magnus
2011-08-01 12:52 ` Don Zickus
2011-08-01 18:33 ` ZAK Magnus
2011-08-01 19:24 ` Don Zickus
2011-08-01 20:11 ` ZAK Magnus
2011-08-03 18:27 ` ZAK Magnus
2011-08-03 19:44 ` Don Zickus
2011-08-03 19:11 ` Don Zickus
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=20110729131009.GQ2581@redhat.com \
--to=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=msb@chromium.org \
--cc=zakmagnus@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox