mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: netconsole hangs w/ alt-sysrq-t
Date: Thu, 1 Jul 2004 13:53:16 -0400	[thread overview]
Message-ID: <16612.20364.397802.306245@segfault.boston.redhat.com> (raw)
In-Reply-To: <20040701170512.GH25826@waste.org>

==> Regarding Re: netconsole hangs w/ alt-sysrq-t; Matt Mackall <mpm@selenic.com> adds:

mpm> On Thu, Jul 01, 2004 at 12:54:50PM -0400, Jeff Moyer wrote:
>> ==> Regarding Re: netconsole hangs w/ alt-sysrq-t; Matt Mackall
>> <mpm@selenic.com> adds:
>> 
mpm> On Mon, Jun 28, 2004 at 12:58:22PM -0400, Jeff Moyer wrote:
>> >> ==> Regarding Re: netconsole hangs w/ alt-sysrq-t; Matt Mackall >>
>> <mpm@selenic.com> adds:
mpm> No, I think we get to this on the non-NAPI route as well. The ->poll
mpm> check keeps us from filtering twice.
>> >> I'll have to take your word for it on this one, as I can't find a way
>> >> into this code for the non-napi case.  Would anyone care to give an
>> >> authoritative answer on this?
>> 
mpm> I could be mistaken, but that's my recollection from last summer.
mpm> Hopefully I'll have some spare cycles for this next week.
>> >> One other thing we might consider is adding a call to >>
>> touch_nmi_watchdog() to zap_completion_queue.
>> 
mpm> Not sure how I feel about that yet. If we can't get out of the guts of
mpm> netpoll in a timely fashion, then perhaps that's an indication that
mpm> the watchdog should indeed fire. Describe the scenario where you think
mpm> we should do this, please.
>> Alt-Sysrq-t from the keyboard on a heavily-loaded UP system.

mpm> Is it because we're spinning for too long waiting for skbs or is it
mpm> just because sysrq-t takes that long to dump its guts? How does the
mpm> watchdog get tickled in the sysrq-t over slow serial console case?

mpm> In other words, would this better be done between dumps in the sysrq-t
mpm> loop where we actually know we're making forward progress?

Good point.  I tend to center my thinking too much around netdump.  You're
right, if we're waiting too long for skb's, we probably should trigger the
NMI watchdog.  It also appears that show_state includes a call to
touch_nmi_watchdog in its loop.

-Jeff

      reply	other threads:[~2004-07-01 17:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 15:29 Jeff Moyer
2004-04-25 19:15 ` Matt Mackall
2004-04-28 12:44   ` Jeff Moyer
2004-04-28 14:03     ` Matt Mackall
2004-04-28 14:07       ` Jeff Moyer
2004-04-28 14:27         ` Matt Mackall
2004-04-28 18:23           ` Jeff Moyer
2004-05-20  2:20             ` klogd, netconsole without /dev/console? Tom Oehser
2004-06-25 15:50             ` netconsole hangs w/ alt-sysrq-t Jeff Moyer
2004-06-25 23:27               ` Matt Mackall
2004-06-28 14:48                 ` Jeff Moyer
2004-06-28 15:19                   ` Matt Mackall
2004-06-28 16:58                     ` Jeff Moyer
2004-06-29 12:36                       ` Jeff Moyer
2004-07-01 16:52                       ` Matt Mackall
2004-07-01 16:54                         ` Jeff Moyer
2004-07-01 17:05                           ` Matt Mackall
2004-07-01 17:53                             ` Jeff Moyer [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=16612.20364.397802.306245@segfault.boston.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.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

all inboxes | Powered by JetHome®