From: Juergen Beisert <jbe@pengutronix.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-rt-users" <linux-rt-users@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Serieal console on Samsung S3C6410 ARM11 CPU (Was [ANNOUNCE] 3.0.6-rt17)
Date: Sat, 8 Oct 2011 13:26:58 +0200 [thread overview]
Message-ID: <201110081326.58731.jbe@pengutronix.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1110070046270.3240@ionos>
Thomas Gleixner wrote:
> I'm pleased to announce the 3.0.6-rt17 release.
I have no idea where to search, but when I'm using the 3.0.6-rt17 on my
Samsung S3C6410 ARM based system, the UART (serial console) does not work as
expected. Typing only one char at a time is okay. Typing two chars
immediately makes the system using 100 % CPU load and takes about 2 seconds
to respond. It seems the interrupt handling is broken in the UART driver, but
I don't know how to fix it.
This with a simple cursor up (one char to get the last command) and a small
pause to the next "ENTER" char:
root@mini6410:~ cat /proc/interrupts | grep 18:
18: 5739107 s3c-uart s3c6400-uart
Same again:
root@mini6410:~ cat /proc/interrupts | grep 18:
18: 5739113 s3c-uart s3c6400-uart
6 interrupts seems reasonable.
Now with cursor up and SPACE immediately, then a pause for ENTER:
root@mini6410:~ cat /proc/interrupts | grep 18:
18: 5923815 s3c-uart s3c6400-uart
184702 interrupts looks strange.
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-10-08 11:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 1:15 [ANNOUNCE] 3.0.6-rt17 Thomas Gleixner
2011-10-07 1:20 ` Madovsky
2011-10-07 1:52 ` Luis Claudio R. Goncalves
2011-10-07 4:13 ` Frank Rowand
2011-10-07 8:10 ` Rolando Martins
2011-10-07 17:25 ` Fernando Lopez-Lezcano
2011-10-07 19:54 ` Fernando Lopez-Lezcano
2011-10-07 22:02 ` Thomas Gleixner
2011-10-07 23:05 ` Fernando Lopez-Lezcano
2011-10-13 7:52 ` [PATCH -rt] hrtimer: Add missing debug_activate() aid [Was: Re: [ANNOUNCE] 3.0.6-rt17] Yong Zhang
[not found] ` <b11eac52-79af-40ea-a53b-6f77581be035@email.android.com>
2011-10-07 23:14 ` PEBTAO [ was Re: [ANNOUNCE] 3.0.6-rt17 ] Thomas Gleixner
2011-10-07 23:25 ` Steven Rostedt
2011-10-07 23:30 ` Thomas Gleixner
2011-10-08 0:26 ` Valdis.Kletnieks
2011-10-08 7:56 ` octoploid
2011-10-08 11:26 ` Juergen Beisert [this message]
2011-10-08 13:29 ` Serieal console on Samsung S3C6410 ARM11 CPU (Was [ANNOUNCE] 3.0.6-rt17) Thomas Abraham
2011-10-08 18:15 ` Juergen Beisert
2011-10-08 19:01 ` Thomas Abraham
2011-10-08 20:56 ` [ANNOUNCE] 3.0.6-rt17 Maarten Lankhorst
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=201110081326.58731.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).