Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: Thomas Marteau <marteaut@esiee.fr>
Cc: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: 2-way A500
Date: Tue, 27 Feb 2001 13:58:46 -0800	[thread overview]
Message-ID: <200102272158.NAA25485@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Tue, 27 Feb 2001 22:05:47 PST." <3A9C16AB.A3BBCB51@esiee.fr>

Thomas,

Please send full console output, lspci, and /proc/interrupt output.
I can provide pciutils binaries if you can't otherwise find/build them.

Thomas Marteau wrote:
> Hi Grant,
> 
> 	I noticed that if we put init=/bin/bash, we see this message:
> IRQ No handler for IRQ 128!

64-bit on A500?

If so, IRQ128 is IRQ0 in IRQ region 2 - ie first iosapic/PCI bus.
A device may have that line asserted for some reason.
I do expect that all drivers for boot devices have registered/claimed
the devices they should *before* init (/bin/bash) is invoked.

> It is true that in /proc/interrupts, no device is reported for this IRQ. The
> problem is that you do not have this problem with /bin/sh, afaik.

Interesting. Perhaps bash RC scripts is doing something different?
I don't see how bash or sh could otherwise generate IO interrupts.

> Also, I will appreciate if you could explain how works this file when it is a
> SMP kernel because I am a little lost :) (Everything is reported to CPU00 here!)

All IO interrupts are routed to the "monarch" (CPU 0) at the moment.
When things stabilize, I'll change the code so both processors share
the IO IRQ load.

ciao!
grant

Grant Grundler
parisc-linux {PCI|IOMMU|SMP} hacker
+1.408.447.7253

       reply	other threads:[~2001-02-27 21:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A9C16AB.A3BBCB51@esiee.fr>
2001-02-27 21:58 ` Grant Grundler [this message]
2001-02-27 23:49   ` [parisc-linux] Re: 2-way A500 Thomas Marteau
2001-02-28  5:22     ` Grant Grundler

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=200102272158.NAA25485@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=marteaut@esiee.fr \
    --cc=parisc-linux@lists.parisc-linux.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