public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: linux-kernel@vger.kernel.org, ltt-dev@shafik.org
Subject: Re: Interrupts disabled for too long in printk
Date: Wed, 7 Jun 2006 22:31:02 -0400	[thread overview]
Message-ID: <20060608023102.GA22022@Krystal> (raw)
In-Reply-To: <9e4733910606071837l4e81c975t8d531ed9810af60f@mail.gmail.com>

* Jon Smirl (jonsmirl@gmail.com) wrote:
> You can look at this problem from the other direction too. Why is it
> taking 15ms to get between the two points? If IRQs are off how is the
> serial driver getting interrupts to be able to display the message? It
> is probably worthwhile to take a look and see what the serial console
> driver is doing.

Hi John,

The serial port is configured at 38000 bauds. It can therefore transmit 4800
bytes per seconds, for 72 characters in 15 ms. So the console driver would be
simply busy sending characters to the serial port during that interrupt
disabling period.

Mathieu

OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 

  reply	other threads:[~2006-06-08  2:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-03 11:19 Interrupts disabled for too long in printk Mathieu Desnoyers
2006-06-03 21:43 ` Steven Rostedt
2006-06-08  1:09   ` Mathieu Desnoyers
2006-06-08  1:37 ` Jon Smirl
2006-06-08  2:31   ` Mathieu Desnoyers [this message]
2006-06-08  2:35     ` Jon Smirl
2006-06-08 10:24       ` linux-os (Dick Johnson)
2006-06-08 14:38         ` Jon Smirl
2006-06-08 15:17           ` linux-os (Dick Johnson)
2006-06-08 15:45             ` Jon Smirl
2006-06-08 18:34               ` Miquel van Smoorenburg

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=20060608023102.GA22022@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox