From: Christian Kujau <evil@g-house•de>
To: sheutlin@gmx•de
Cc: linuxppc-dev@ozlabs•org, Sven Hartge <hartge@ds9•argh.org>
Subject: Re: [FYI] linux 2.6 still not^Wnow working with PReP (ppc32)
Date: Mon, 06 Dec 2004 05:15:19 +0100 [thread overview]
Message-ID: <41B3DCD7.3020503@g-house.de> (raw)
In-Reply-To: <1102297574.7138.17.camel@weizen.left.earth>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sebastian Heutling schrieb:
>
> Pure trial and error in the first time. When realising that something is
> wrong with the assigned interrupts (looking at the kernel output) we
> tried to set the ones that were working in a 2.4 kernel. When the
> machine finally booted a "lspci" showed that the slot number changed.
lspci, sounds easy ;-)
but i never would have looked at slot numbering....
>
> Is it that onboard network tulip kind of thingy? Do you have some other
> PCI cards installed?
the card is onboard. since i had some issues with this card in early 2.4
kernels too, i used to have another NIC. in fact, very often i only
compiled with 3c59x enabled - OF cared about the onboard NIC (tulip) and
once the kernel is loaded, the tulip is not needed any more and 3c59x
takes over.
http://nerdbynature.de/bits/sheep/2.6.10-rc3/ has some details.
> I used to have an extra symbios logic scsi-host-adapter installed.
> On high network load and loading/writing to a HD (using onboard scsi), I
> noticed a lot of problems: either the scsi-host-adapter lost the
> interrupt or the network driver lost some packets or both. After having
> removed the extra scsi-host-adapter it works fine now.
hm, when i had 3 scsi-disks in this machine (fine IBM ones, hmmmm..) i
only used the on-board scsi-bus. there was no other scsi-host-adapter
inside, but i noticed the very same problems: upon massive i/o, the
machine got stuck for 30sec, sometimes longer, load increased to 30..40 or
so, then the machine got back, with a syslog full of scsi errors.
it's still so incredible that a 3-liner solved this issue. the bug-report
was opened over a year ago...
thanks again,
Christian.
- --
BOFH excuse #13:
we're waiting for [the phone company] to fix that line
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBs9zX+A7rjkF8z0wRArwBAKDZ2ywiukQl/b/uPTG1/1jWHrIsxQCeIcKb
ltnS8407uSUM+J6jiJABxxc=
=Ts4X
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-12-06 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 22:45 [FYI] linux 2.6 still not working with PReP (ppc32) Christian Kujau
2004-12-05 0:41 ` Sebastian Heutling
2004-12-05 17:41 ` Christian Kujau
2004-12-06 1:46 ` Sebastian Heutling
2004-12-06 4:15 ` Christian Kujau [this message]
2004-12-05 19:57 ` [PATCH] linux 2.6 not^Wnow " Christian Kujau
2004-12-06 18:49 ` Tom Rini
2004-12-06 19:33 ` Christian
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=41B3DCD7.3020503@g-house.de \
--to=evil@g-house$(echo .)de \
--cc=hartge@ds9$(echo .)argh.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=sheutlin@gmx$(echo .)de \
/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