From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Danny ter Haar <dth@ncc1701.cistron.net>, linux-kernel@vger.kernel.org
Subject: Re: Linux serial console patch
Date: Mon, 06 Sep 2004 16:45:22 +0100 [thread overview]
Message-ID: <413C8612.4010806@superbug.demon.co.uk> (raw)
In-Reply-To: <20040906114321.A26906@flint.arm.linux.org.uk>
Russell King wrote:
> On Mon, Sep 06, 2004 at 10:32:27AM +0000, Danny ter Haar wrote:
>
>>James Courtier-Dutton <James@superbug.demon.co.uk> wrote:
>>
>>>>I have read your posts to lkml containing your serial console flow control
>>>>patches firstly for 2.4.x and then for 2.6.x kernels.
>>>
>>>Does this fix junk being output from the serial console?
>>>If one is using Pentium 4 HT, it seems that both CPU cores try to send
>>>characters to the serial port at the same time, resulting in lost
>>>characters as one CPU over writes the output from the other.
>>
>>We have multiple P4-HT enabled servers with debian installed & serial
>>console enabled (RPB++ ;-) and _i_ have never seen this behaviour.
>
>
> I don't think this is a serial problem as such, but a problem with the
> kernel console subsystem (printk) itself. Maybe James can provide an
> example output to confirm exactly what he's seeing.
>
http://www.superbug.demon.co.uk/latency/
There are 2 oops traces there. At about line 176, the corruption starts.
next prev parent reply other threads:[~2004-09-06 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 17:24 Linux serial console patch Alex Owen
2004-09-05 23:38 ` James Courtier-Dutton
2004-09-06 10:32 ` Danny ter Haar
2004-09-06 10:43 ` Russell King
2004-09-06 15:45 ` James Courtier-Dutton [this message]
2004-09-06 15:52 ` Russell King
2004-09-06 16:46 ` Randy.Dunlap
2004-09-11 20:58 ` Herbert Poetzl
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=413C8612.4010806@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=dth@ncc1701.cistron.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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