mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: real time hang w/ latency tracing
Date: Wed, 04 Apr 2007 08:57:57 -0700	[thread overview]
Message-ID: <1175702277.15973.17.camel@imap.mvista.com> (raw)
In-Reply-To: <20070404154249.GA31171@elte.hu>

On Wed, 2007-04-04 at 17:42 +0200, Ingo Molnar wrote:

> i mean non-printk related breakages to the normal serial driver - which 
> is now surprised by this raw lock in an -rt kernel.
> 
> this is a hard issue and there's no easy solution i can see. neither 
> having it as a raw lock is a good solution, nor having it as a 
> preemptible lock is a good solution.

The machine that I'm using is relatively fast, but on slower machine
it's possible to reproduce this same hang just by running,

echo 0 > /proc/sys/kernel/preempt_max_latency

then pressing enter a few times .. Which would be a fairly common
happening with people using latency tracing an a serial port I would
imagine..

The other fix I test was using the hack for sysrq,

        if (up->port.sysrq || oops_in_progress)

in serial8250_console_write to then also check "irqs_disabled()" , but
I'm sure mass usage of the serial port would cause some issues with
that.. Although both fixes I tested resulted in the serial port becoming
garbled after about 10 min. with the preempt_thresh at 1 .

Daniel


      reply	other threads:[~2007-04-04 15:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-03 18:57 Daniel Walker
2007-04-04  1:41 ` Daniel Walker
2007-04-04  8:51   ` Ingo Molnar
2007-04-04 15:36     ` Daniel Walker
2007-04-04 15:42       ` Ingo Molnar
2007-04-04 15:57         ` Daniel Walker [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=1175702277.15973.17.camel@imap.mvista.com \
    --to=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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®