From: Tom Rini <trini@kernel•crashing.org>
To: Sven Luther <sven.luther@wanadoo•fr>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch ...
Date: Tue, 5 Apr 2005 07:38:02 -0700 [thread overview]
Message-ID: <20050405143802.GS25923@smtp.west.cox.net> (raw)
In-Reply-To: <20050405053930.GD4604@pegasos>
On Tue, Apr 05, 2005 at 07:39:31AM +0200, Sven Luther wrote:
> On Tue, Apr 05, 2005 at 02:03:06AM +0200, Christian wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Sven Luther wrote:
> > >>># This is a BitKeeper generated diff -Nru style patch.
> > >>>#
> > >>># ChangeSet
> > >>># 2004/08/16 10:35:18-07:00 trini@kernel•crashing.org
> > >>># ppc32: On PReP, use residual data for PCI dev -> IRQ, and use it.
> > >
> > > I got through all the changesets one by one, and it is most definitively this
> > > one. i unapply it and it works, i apply it and it breaks.
> >
> > i can confirm this one.
> >
> > the changesets are listed here:
> > http://linux.bkbits.net:8080/linux-2.6/patch@1.1803.125.6
> >
> > ...and because i had some troubles getting a GNU diff-style patch with
> > /usr/bin/bk, i made one against 2.6.11.6:
> >
> > http://nerdbynature.de/bits/hal/2.6.11.6/1.1803.125.6.diff
> >
> > more info and dmesg under:
> >
> > http://nerdbynature.de/bits/hal/2.6.11.6/
> >
> > to summarize: i don't know exactly which changes, but *some* changes had
> > to be made to arch/ppc/platforms/prep_pci.c to get the network card
> > working [1] again (network code kept locking up the machine). after this
> > issue was resolved, i too noticed the scsi errors [2] others were
> > complaing about.
>
> The issue seems obvious, the patch adds some different way of setting the
> irqs, based on the residual data, which fails to do what it should on the
> powerstack, and thus the irqs are fully left uninitialized.
Can either of you verify that say 2.6.11.6 w/ "noresidual" on the
command-line works? Thanks.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-04-05 14:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 23:23 PREP sym53c8xx sym53c8xx brokeness due to 2.6.9-rc1-bk1 introduced residual data patch Sven Luther
2005-03-31 14:28 ` Tom Rini
2005-03-31 18:45 ` Sven Luther
2005-04-05 0:03 ` Christian
2005-04-05 5:39 ` Sven Luther
2005-04-05 14:38 ` Tom Rini [this message]
2005-04-05 15:23 ` Sven Luther
2005-04-05 15:47 ` Tom Rini
2005-04-06 1:47 ` Christian
2005-04-06 1:58 ` Christian
2005-04-06 18:50 ` Tom Rini
2005-04-08 11:36 ` Leigh Brown
2005-04-08 14:54 ` Tom Rini
2005-04-08 15:51 ` Christian
2005-04-08 15:57 ` Tom Rini
2005-04-09 11:33 ` [PATCH 2.6.11+] ppc32: Make the Powerstack II Pro4000 boot again Leigh Brown
2005-04-13 5:18 ` Greg KH
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=20050405143802.GS25923@smtp.west.cox.net \
--to=trini@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sven.luther@wanadoo$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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