linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dmalek@jlc.net>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: linuxppc-dev@lists.linuxppc.org,
	"Timothy A. Seufert" <tas@mindspring.com>
Subject: Re: Strange PMAC IDE performance problem
Date: Wed, 06 Jan 1999 00:56:40 -0500	[thread overview]
Message-ID: <3692FB17.A3A22B55@jlc.net> (raw)
In-Reply-To: 19990105234815.008275@smtp.calvacom.fr


Benjamin Herrenschmidt wrote:

> I remember Cort having tons of them initially with his PowerBook and they
> disappeared, I don't know if it was after a kernel change however.

I am still running 2.1.125 on my PowerBook G3, and get tons
of bogus interrupts.  I am trying to upgrade to 2.1.130 (or the
latest vger tree).  When I run 2.1.130, I don't see the problems.
The major difference is I run the IDE DMA on 2.1.130 and not
on other kernels..........I can't point to anything else.  My other
thought was something wrong with power management.


> I never experienced the slowdown+crash on heavy i/os, even when copying
> full kernel trees locally, over NFS and both at the same time.

Mine will when running 2.1.125.....not with 2.1.130.


> ........ Also, are
> the problem similar when booting with OF and BootX or are there any
> differences ?

I boot with OF (either floppy or enet) because I don't have an
easy way to get the kernel into the MacOS system folder.  I have
hacked the atyfb to force G3 resolution and depth regardless of what
it finds automatically.


    -- Dan



[[ 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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-01-06  5:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-05  8:52 Strange PMAC IDE performance problem Timothy A. Seufert
1999-01-05 11:33 ` Albrecht Dreß
1999-01-05 17:52   ` Marcus H. Mendenhall
1999-01-05 18:49   ` Timothy A. Seufert
1999-01-05 22:48     ` Benjamin Herrenschmidt
1999-01-06  5:56       ` Dan Malek [this message]
1999-01-06  9:59         ` Benjamin Herrenschmidt
1999-01-06  9:23       ` Albrecht Dreß
1999-01-06 10:02         ` Benjamin Herrenschmidt
1999-01-06 23:22           ` Paul Mackerras
1999-01-07  9:11             ` Benjamin Herrenschmidt
1999-01-05 22:39 ` Paul Mackerras
1999-01-06  6:01   ` Paul Mackerras
1999-01-06 11:51     ` Benjamin Herrenschmidt
1999-01-06 16:02     ` Great IDE perf (WAS: Strange PMAC IDE performance) Benjamin Herrenschmidt
1999-01-07 11:12       ` Timothy A. Seufert
1999-01-07 11:32         ` Paul Mackerras
1999-01-07 18:59           ` Timothy A. Seufert
1999-01-07 11:59         ` Benjamin Herrenschmidt
1999-01-07 18:59           ` Timothy A. Seufert
1999-01-07 20:15             ` Benjamin Herrenschmidt
1999-01-08  2:06           ` Paul Mackerras
1999-01-08  3:30             ` Benjamin Herrenschmidt

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=3692FB17.A3A22B55@jlc.net \
    --to=dmalek@jlc.net \
    --cc=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tas@mindspring.com \
    /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).