From: "Jon Smirl" <jonsmirl@gmail.com>
To: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: solution to printk() blocking interrupts?
Date: Sun, 21 Sep 2008 16:53:24 -0400 [thread overview]
Message-ID: <9e4733910809211353k1f06fb5bi219c124d0c44b47a@mail.gmail.com> (raw)
Does anyone have a solution to the problem of printk() to a serial
console blocking interrupts for too long? I'm losing interrupts I need
because my hardware is getting overrun.
--
Jon Smirl
jonsmirl@gmail.com
next reply other threads:[~2008-09-21 20:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 20:53 Jon Smirl [this message]
2008-09-21 21:43 ` solution to printk() blocking interrupts? Jon Smirl
2008-09-21 22:21 ` Sergei Shtylyov
2008-09-21 23:34 ` Jon Smirl
2008-09-22 5:17 ` Benjamin Herrenschmidt
2008-09-22 11:04 ` Sergei Shtylyov
2008-09-22 11:11 ` Sergei Shtylyov
2008-09-22 14:39 ` Sergei Shtylyov
2008-09-22 14:45 ` Jon Smirl
2008-09-22 14:59 ` Sergei Shtylyov
2008-09-22 21:27 ` Benjamin Herrenschmidt
2008-09-22 10:03 ` Sergei Shtylyov
2008-09-22 11:01 ` Sergei Shtylyov
2008-09-22 11:21 ` Sergei Shtylyov
2008-09-22 13:45 ` Jon Smirl
2008-09-23 5:46 ` Benjamin Herrenschmidt
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=9e4733910809211353k1f06fb5bi219c124d0c44b47a@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).