From: Bill Davidsen <davidsen@tmr.com>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: tickle NMI watchdog on serial output.
Date: Tue, 01 Aug 2006 16:12:17 -0400 [thread overview]
Message-ID: <44CFB5A1.8080904@tmr.com> (raw)
In-Reply-To: <20060801182529.GJ22240@redhat.com>
http://newsvote.bbc.co.uk/mpapps/pagetools/print/news.bbc.co.uk/2/hi/health/5232150.stmDave
Jones wrote:
> Serial is _slow_ sometimes. So slow, that the NMI watchdog kicks in.
> I initially did the patch below a year ago for the Fedora kernel, and have
> been keeping it up to date since. I recently got the same thing happening
> on a vanilla kernel, so figured it was time to repost this.
Hopefully this will get picked up for mainline. In case of a real hung
it should still trigger NMI in some reasonable time.
>
> Signed-off-by: Dave Jones <davej@redhat.com>
>
> --- linux-2.6/drivers/serial/8250.c~ 2005-05-14 02:49:02.000000000 -0400
> +++ linux-2.6/drivers/serial/8250.c 2005-05-14 02:54:30.000000000 -0400
> @@ -2098,9 +2098,11 @@ static inline void wait_for_xmitr(struct
> /* Wait up to 1s for flow control if necessary */
> if (up->port.flags & UPF_CONS_FLOW) {
> tmout = 1000000;
> - while (--tmout &&
> - ((serial_in(up, UART_MSR) & UART_MSR_CTS) == 0))
> + while (!(serial_in(up, UART_MSR) & UART_MSR_CTS) && --tmout) {
> udelay(1);
> + if ((tmout % 1000) == 0)
> + touch_nmi_watchdog();
> + }
> }
> }
>
>
--
Bill Davidsen <davidsen@tmr.com>
Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one errors occurs during
wildcard (glob) expansion.
next prev parent reply other threads:[~2006-08-01 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 18:25 tickle NMI watchdog on serial output Dave Jones
2006-08-01 20:12 ` Bill Davidsen [this message]
2006-08-01 22:00 ` Alan Cox
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=44CFB5A1.8080904@tmr.com \
--to=davidsen@tmr.com \
--cc=davej@redhat.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.