linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: "LinuxPPC-Dev Liste" <linuxppc-dev@lists.linuxppc.org>,
	"Albrecht Dreß" <ad@mpifr-bonn.mpg.de>
Subject: Re: Strange PMAC IDE performance problem
Date: Wed, 6 Jan 1999 11:02:56 +0100	[thread overview]
Message-ID: <19990106110256.031920@mail.mipsys.com> (raw)
In-Reply-To: <36932B99.20AE3AA4@mpifr-bonn.mpg.de>


On Wed, Jan 6, 1999, Albrecht Dreß <ad@mpifr-bonn.mpg.de> wrote:

>I use the latest test kernel form your web page (2.1.130 with patches; btw.
>the
>trackpad patch is REALLY great!!) and boot with BootX 1.0.1. Bogus interrupts
>appear both with nothing attached to external SCSI and with a tape drive. I
>get
>very few bogus irq's from via_pmu_interrupt (c01d43fc, c01d4410) and
LOTS from
>do_IRQ (c0005518) in both cases. According to /proc/interrupts, doing a dd of
>200 MBytes form /dev/zero to the internal hd resulted in 31 bad irq's from
>do_IRQ (and a transfer rate of 1.71 MB/s).

By curiousity, did someone tried to locate the exact instruction in
do_IRQ when those bogus interrupt happens ? Looks it's always the same...
On MacOS, CodeWarrior has a useful disassembly tool that mixes C and asm
output for that, but I guess there is probably something 1000 times
better on Linux, I just need to know the command line ;-)


-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>





[[ 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 10:02 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
1999-01-06  9:59         ` Benjamin Herrenschmidt
1999-01-06  9:23       ` Albrecht Dreß
1999-01-06 10:02         ` Benjamin Herrenschmidt [this message]
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=19990106110256.031920@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=ad@mpifr-bonn.mpg.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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).