From: Paul Mackerras <paulus@cs.anu.edu.au>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: toe@unlserve.unl.edu, puetzk@iastate.edu,
iweiny@falcon.csc.calpoly.edu, lambert@jeol.com,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Communicator Crashes X II
Date: Tue, 31 Aug 1999 11:48:26 +1000 [thread overview]
Message-ID: <199908310148.LAA14647@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.LNX.4.10.9908301823010.27650-100000@mercator.cs.kuleuven.ac.be> (message from Geert Uytterhoeven on Mon, 30 Aug 1999 18:23:48 +0200 (CEST))
Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:
> Perhaps the kernel spends too much time in the interrupt handling section of
> the IDE driver? We saw similar things on m68k.
Or the SCSI code. I recently converted the mesh and mac53c94 drivers
to use the `new-style' error handling (it didn't take as much hacking
as I had expected). One result is that the command-done processing in
the scsi mid-layer gets done in a BH handler rather than in an
interrupt handler with interrupts disabled. I noticed that I got far
fewer serial overruns with the new code during disk activity.
I don't see the FB. overflow messages, but then I don't run the serial
port at 115200, only at 57600. Is it a common feature that people who
see the FB. overflow message are running the serial port at 115200 or
230400 baud?
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-31 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 13:16 Communicator Crashes X II Kevin Puetz
1999-08-30 16:20 ` Takashi Oe
1999-08-30 16:23 ` Geert Uytterhoeven
1999-08-31 1:48 ` Paul Mackerras [this message]
1999-08-31 13:08 ` Improving gatwick interrupts Benjamin Herrenschmidt
1999-08-31 17:20 ` A few sleep patches Benjamin Herrenschmidt
1999-09-08 18:45 ` Communicator Crashes X II Jerry Quinn
-- strict thread matches above, loose matches on Subject: below --
1999-08-30 5:07 Ira K Weiny
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=199908310148.LAA14647@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=iweiny@falcon.csc.calpoly.edu \
--cc=lambert@jeol.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=puetzk@iastate.edu \
--cc=toe@unlserve.unl.edu \
/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).