From: jbradford@dial.pipex.com
To: tmolina@cox.net (Thomas Molina)
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5 Problem Report Status
Date: Sat, 12 Oct 2002 17:51:38 +0100 (BST) [thread overview]
Message-ID: <200210121651.g9CGpdXM010784@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0210120758420.4532-100000@dad.molina> from "Thomas Molina" at Oct 12, 2002 10:38:21 AM
> 2.5 Kernel Problem Reports as of 12 Oct
>
> Status Discussion Problem Title
> --------------------------------------------------------------------------
> open 05 Oct 2002 2.5.x and 8250 UART problems
>
> 22. http://marc.theaimsgroup.com/?l=linux-kernel&m=103383019409525&w=2
>
> --------------------------------------------------------------------------
2.5.41 didn't boot on the test machine.
2.5.42 does boot on the test machine, and exhibits the same problems
Typical scenario:
MMX-200 with plenty of RAM (128 MB), and a 16550A UART running 2.5.40
doing a 9600 bps Z-Modem transfer to
486 SX-20 with 4 MB RAM, and a 8250 UART, running 2.5.42
>From time to time, (every 4-8K or so), the Z-Modem protocol will
detect an error, and re-send blocks.
This does not occur with 2.2.13 or 2.2.21 on the 486.
Usually the errors occur at the same time as hard disk accesses, but
turning on IRQ unmasking does not prevent them. Also, sometimes the
hard disk is accessed, and no error occurs.
John.
next parent reply other threads:[~2002-10-12 16:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0210120758420.4532-100000@dad.molina>
2002-10-12 16:51 ` jbradford [this message]
2002-10-13 21:54 ` 2.5 Problem Report Status Stig Brautaset
2002-10-31 17:01 Kent Yoder
-- strict thread matches above, loose matches on Subject: below --
2002-10-23 2:26 Grover, Andrew
2002-10-23 2:07 Thomas Molina
2002-10-23 2:28 ` Ben Collins
2002-10-23 2:43 ` Ben Collins
2002-10-23 7:58 ` Russell King
2002-10-23 9:53 ` jbradford
2002-10-23 10:35 ` Vojtech Pavlik
2002-10-23 12:21 ` jbradford
2002-10-23 12:26 ` jbradford
2002-10-23 13:09 ` Alan Cox
2002-10-23 14:14 ` jbradford
2002-10-23 15:25 ` Alan Cox
2002-10-23 15:31 ` jbradford
2002-10-23 17:03 ` Patrick Mochel
2002-10-23 17:34 ` Alan Cox
2002-10-26 14:18 ` Toon van der Pas
2002-10-26 19:06 ` Patrick Mochel
2002-10-23 14:29 ` erik
2002-10-23 13:41 ` caligula
2002-10-31 15:16 ` caligula
2002-10-05 20:21 Mikael Pettersson
2002-10-05 22:10 ` Thomas Molina
2002-10-05 23:19 ` John Levon
2002-10-05 18:18 Steven Cole
2002-10-05 16:57 Thomas Molina
2002-10-05 17:19 ` Bjoern A. Zeeb
2002-10-05 17:38 ` Thomas Molina
2002-10-05 18:05 ` Robert Love
2002-10-06 20:13 ` Gcc k6 testing account
2002-09-21 22:52 Thomas Molina
2002-09-21 22:52 ` William Lee Irwin III
2002-09-21 23:26 ` Axel Siebenwirth
2002-09-18 8:39 Thomas Molina
2002-09-17 1:57 Thomas Molina
2002-09-17 12:37 ` Helge Hafting
2002-09-17 20:58 ` Thomas Molina
2002-09-17 20:48 ` William Lee Irwin III
2002-09-04 3:26 Thomas Molina
2002-09-04 3:43 ` Andre Hedrick
2002-09-04 3:52 ` Robert Love
2002-09-04 8:08 ` Axel H. Siebenwirth
2002-09-04 10:16 ` Thomas Molina
2002-08-19 0:25 2.5 Problem Report status Thomas Molina
2002-08-10 18:09 2.5 Problem Report Status Thomas Molina
2002-08-22 19:29 ` James Simmons
2002-07-26 15:18 Thomas Molina
2002-07-27 20:04 ` James Simmons
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=200210121651.g9CGpdXM010784@darkstar.example.net \
--to=jbradford@dial.pipex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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