From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
netdev@vger.kernel.org
Subject: Re: Oops in fs_enet driver with preempt-rt
Date: Tue, 20 May 2008 11:21:20 -0500 [thread overview]
Message-ID: <4832FA80.7060807@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B046E73C6@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> Hmm.... ttyCPM1 output seems to be kinda garbled... Any ideas?
> Incomplete locking between printk and userland use of ttyCPM1 as
> console?
s/incomplete/nonexistent/ :-P
Try acquiring port->lock in cpm_uart_console_write.
-Scott
next prev parent reply other threads:[~2008-05-20 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 14:40 Oops in fs_enet driver with preempt-rt Rune Torgersen
2008-05-20 14:53 ` Rune Torgersen
2008-05-20 15:41 ` Scott Wood
2008-05-20 16:08 ` Rune Torgersen
2008-05-20 16:14 ` Rune Torgersen
2008-05-20 16:21 ` Scott Wood [this message]
2008-05-20 16:31 ` Rune Torgersen
2008-05-20 17:33 ` Kumar Gala
2008-05-20 18:53 ` Rune Torgersen
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=4832FA80.7060807@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=runet@innovsys.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;
as well as URLs for NNTP newsgroup(s).