public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Heutling <sheutlin@gmx.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Tom Rini <trini@kernel.crashing.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org, Christian Kujau <evil@g-house.de>,
	Sven Hartge <hartge@ds9.gnuu.de>
Subject: Re: [PATCH 2.6.10-rc3][PPC32] Fix Motorola PReP (PowerstackII Utah) PCI IRQ map
Date: Tue, 22 Feb 2005 13:01:22 +0100	[thread overview]
Message-ID: <421B1F12.7050601@gmx.de> (raw)
In-Reply-To: <Pine.SOC.4.61.0502221031230.6097@math.ut.ee>

Meelis Roos wrote:

>> The PCI IRQ map for the old Motorola PowerStackII (Utah) boards was
>> incorrect, but this breakage wasn't exposed until 2.5, and finally fixed
>> until recently by Sebastian Heutling <sheutlin@gmx.de>.
>
>
> Yesterday I finally got around to testing it. It seems the patch has 
> been applied in Linus's tree so I downloaded the latest BK and tried it.
>
> Still does not work for me but this time it's different. Before the 
> patch SCSI worked fine but PCI NICs caused hangs. Now I can't test PCI 
> NICs because even the onboard 53c825 SCSI hangs - seems it gets no 
> interrupts.
>
> It detects the HBA, tries device discovery, gets a timeout, ABORT, 
> timeout, TARGET RESET, timeout, BUS RESET, timeout, HOST RESET and 
> there it hangs.
>
> Does it work for anyone else on Powerstack II Pro4000 (Utah)?
>
It does work in 2.6.8 using backported patches (e.g. the debian 2.6.8 
kernel). But it doesn't work above that version because of other patches 
in arch/ppc/platforms/prep_pci.c and arch/ppc/platforms/prep_setup.c 
(made by Tom Rini?). I couldn't find out what exactly is causing this 
problem yet (because lack of time and the fact that my Powerstack is 
used as a router).

Basti

  reply	other threads:[~2005-02-22 12:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 18:54 [PATCH 2.6.10-rc3][PPC32] Fix Motorola PReP (PowerstackII Utah) PCI IRQ map Tom Rini
2005-02-22  8:36 ` Meelis Roos
2005-02-22 12:01   ` Sebastian Heutling [this message]
2005-02-22 12:23     ` Leigh Brown
2005-02-22 16:27       ` Christian Kujau
2005-02-22 18:27       ` Sebastian Heutling
2005-02-24  7:47   ` Sven Luther
2005-02-24 15:47     ` Meelis Roos
2005-02-24 16:06       ` Sven Luther
2005-02-24 16:34         ` Meelis Roos
2005-02-24 17:01           ` Sven Luther
2005-02-24 20:51             ` Meelis Roos
2005-02-25  0:24         ` Christian Kujau
2005-02-25  6:36           ` Sven Luther
2005-02-25 11:59             ` Christian
2005-02-25 12:15               ` Sven Luther
2005-02-26  3:39                 ` Christian
2005-02-26  6:04                   ` Sven Luther

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=421B1F12.7050601@gmx.de \
    --to=sheutlin@gmx.de \
    --cc=evil@g-house.de \
    --cc=hartge@ds9.gnuu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mroos@linux.ee \
    --cc=trini@kernel.crashing.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