From: Sebastian Heutling <sheutlin@gmx.de>
To: Marc Dietrich <marvin24@gmx.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [FYI] linux 2.6 still not working with PReP (ppc32)
Date: Mon, 10 Jan 2005 00:17:54 +0100 [thread overview]
Message-ID: <41E1BBA2.30008@gmx.de> (raw)
In-Reply-To: <200501052157.25302.marvin24@gmx.de>
Marc Dietrich wrote:
>Hi all,
>
>I didn't recognise that the kernel from Sebastian - which was working fine
>here - was build from the debian sources (no hint in the kernel version).
>So I build everything again from debian source and fixed the irq's in
>prep_pci.c.
>
>
Erm ... well ... yes - it's a debian kernel ;).
>I can confirm now, that this debian+irq_fix kernel 2.6.8 runs fine and
>produces no scsi timeouts!
>
>Something happend in kernels >= 2.6.9 which makes the scsi unusable. Also it
>seems, that even in 2.6.8 kernels and with ide hard disks (Sebastians setup)
>the scsi controller timeouts, but continues to operate - correct?
>
>
Yep correct.
I also tried the 2.6.10 and found out that it doesn't work here as well.
First I get a lot of lost interrupts from the IDE driver and after that
I also get the SCSI timeouts. It must have something to do with the prep
changes in 2.6.9. One difference in IRQ setup I noticed is in
prep_pcibios_fixup(). If I remember correctly before 2.6.9 at least on
this Utah machine the IRQs are assigned from Motherboard_routes[]
without doing anything else. Now additionally the IRQ is also written
into the devices pci config space which might not work on the
PowerstackII Utah.
It's only a guess and I haven't had the time yet to test it.
Sebastian
next prev parent reply other threads:[~2005-01-09 23:18 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 13:35 [FYI] linux 2.6 still not working with PReP (ppc32) Marc Dietrich
2004-12-27 2:47 ` Christian
2004-12-27 21:37 ` Marc Dietrich
2005-01-02 0:31 ` Sebastian Heutling
2005-01-03 12:26 ` Marc Dietrich
2005-01-04 0:54 ` evilninja
2005-01-04 11:31 ` Sebastian Heutling
2005-01-04 14:04 ` Marc Dietrich
2005-01-04 14:42 ` Sebastian Heutling
[not found] ` <1104850036.6164.25.camel@weizen.left.earth>
2005-01-05 11:33 ` Marc Dietrich
2005-01-05 15:47 ` Sven Luther
2005-01-05 17:10 ` Christian
2005-01-05 17:39 ` Sven Luther
2005-01-06 16:00 ` Christian
2005-01-06 16:27 ` Sven Luther
2005-01-06 20:27 ` Christian
2005-01-06 21:07 ` Sven Luther
2005-01-06 21:21 ` Christian
2005-01-06 21:49 ` Sven Luther
2004-12-31 9:55 ` Sven Luther
2004-12-31 15:00 ` Sebastian Heutling
2004-12-31 22:28 ` Sven Luther
2005-01-01 23:56 ` Sebastian Heutling
2005-01-02 9:39 ` Sven Luther
2005-01-02 21:33 ` Sebastian Heutling
[not found] ` <200501051733.06350.marvin24@gmx.de>
[not found] ` <20050105165551.GA29287@pegasos>
2005-01-05 20:57 ` Marc Dietrich
2005-01-09 23:17 ` Sebastian Heutling [this message]
2005-01-10 6:34 ` Sven Luther
2005-01-10 15:19 ` Sebastian Heutling
2005-01-10 6:54 ` Sven Luther
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 2:12 Christian
2005-01-04 13:23 ` Marc Dietrich
2005-01-04 15:08 ` Christian
2004-12-04 22:45 Christian Kujau
2004-12-05 0:41 ` Sebastian Heutling
2004-12-05 17:41 ` Christian Kujau
2004-12-06 1:46 ` Sebastian Heutling
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=41E1BBA2.30008@gmx.de \
--to=sheutlin@gmx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=marvin24@gmx.de \
/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).