From: jbradford@dial.pipex.com
To: rmk@arm.linux.org.uk (Russell King)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.x and 8250 UART problems
Date: Sat, 5 Oct 2002 22:12:02 +0100 (BST) [thread overview]
Message-ID: <200210052112.g95LC23B002031@darkstar.example.net> (raw)
In-Reply-To: <20021005205954.A1682@flint.arm.linux.org.uk> from "Russell King" at Oct 05, 2002 08:59:54 PM
> > The 486 SX-20 with 4 MB RAM, running 2.2.21 reliably achieves about 650
> > BPS download from another machine, with the port runnnig at 9600 bps.
> > With 2.5.40, many characters are lost at 9600, making, e.g. a ZModem
> > transfer retry for almost every block.
OK, first of all, I was wrong about it being an 8250 UART, I checked, and it is infact a 16540, not that it should make much difference, anyway :-)
> Ok, we need to find out where stuff is getting dropped. Dumping
> /proc/tty/driver/serial is always a good idea when reporting anything
> like this.
>
> The important thing is the change in the counters. Can you supply the
> port in question both before and after the zmodem run please?
OK, here goes, I used RZ on the command line instead of Minicom on the laptop, to maximize available memory.
---
Using 2.2.21 on the 486 laptop:
Laptop, (just booted):
0: uart:16450 port:3F8 irq:4 tx:0 rx:0 CTS|DTR|DSR
Desktop:
1: uart:16550A port:000002F8 irq:3 tx:946840 rx:5516126 RTS|CTS|DTR|DSR
Now transfer a 64K file using Z-modem.
Laptop:
0: uart:16450 port:3F8 irq:4 baud:9600 tx:104 rx:66050 CTS|DSR
Desktop:
1: uart:16550A port:000002F8 irq:3 tx:1012890 rx:5516209 RTS|DTR
---
Using 2.5.40 on the laptop:
Laptop, (just booted):
0: uart:16450 port:000003F8 irq:4 tx:0 rx:0 CTS|DSR
Desktop:
1: uart:16550A port:000002F8 irq:3 tx:1012890 rx:5516209 RTS|DTR
Now transfer a 64K file using Z-modem.
Contrary to what I originally thought, it did drop characters during disk access, but then it seemed to continue, only to drop characters again a second later.
Laptop:
0: uart:16450 port:000003F8 irq:4 tx:230 rx:73291 oe:45 CTS|DSR
Desktop:
1: uart:16550A port:000002F8 irq:3 tx:1086246 rx:5516439 RTS|DTR
---
I am begining to wonder whether it is something straightforward, like the newer kernel being more bloated, and therefore not being cached so well, causing the machine to run generally slower.
I remember seeing dropped characters with a bloated 2.2.13 kernel on that machine.
However, when I upgraded the other laptop from 2.2.x to 2.4.x, I saw an improvement in serial port performance, from an average of ~650 cps to ~950 cps. Although I also upgraded glibc at the same time. Seems like there are a lot of variables, sorry about that! :-)
Hope the above info is helpful. If you need me to do any more tests, or some with the other machine, let me know.
Cheers,
John.
next prev parent reply other threads:[~2002-10-05 20:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 15:06 2.5.x and 8250 UART problems jbradford
2002-10-05 15:07 ` bert hubert
2002-10-05 15:18 ` jbradford
2002-10-05 19:59 ` Russell King
2002-10-05 21:12 ` jbradford [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-05 19:43 Hell.Surfers
2002-10-05 20:01 ` jbradford
2002-10-05 15:05 jbradford
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=200210052112.g95LC23B002031@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@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