From: Christian Kujau <evil@g-house.de>
To: Remco Post <r.post@sara.nl>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.6 PReP issues, still freezing
Date: Tue, 02 Dec 2003 00:17:30 +0100 [thread overview]
Message-ID: <3FCBCC0A.5060107@g-house.de> (raw)
In-Reply-To: <3318B418-244D-11D8-A10A-000393911DE2@sara.nl>
Remco Post wrote:
> flops:~# ping 172.16.5.1
> PING 172.16.5.1 (172.16.5.1): 56 data bytes
>
> --- 172.16.5.1 ping statistics ---
> 2 packets transmitted, 0 packets received, 100% packet loss
> flops:~# eth0: link down
> eth0: timeout expired stopping DMA
> kernel BUG in de_set_media at drivers/net/tulip/de2104x.c:926!
so you really have a de2104x card. and your problems differ from mine,
as i never got any Oopses.
did you try Jeff Garzik's fixes for this driver?
http://marc.theaimsgroup.com/?l=linux-kernel&m=106950312306991&w=2
they were for some -test9-bk tree, but neither the -test10 nor the
-test11 ChangeLog says something about the fixes, so i think they are
still pending.
> CONFIG_PPC_CHRP=y
> CONFIG_PPC_PMAC=y
> CONFIG_PPC_PREP=y
> CONFIG_PPC_OF=y
how many archs do you want to boot at once? :-)
Thanks,
Christian.
--
BOFH excuse #233:
TCP/IP UDP alarm threshold is set too low.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-12-01 23:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 13:21 2.6 PReP issues, still freezing Christian Kujau
2003-12-01 11:11 ` Remco Post
2003-12-01 14:23 ` Christian Kujau
2003-12-01 14:52 ` Remco Post
2003-12-01 19:16 ` Tom Rini
2003-12-01 21:05 ` Remco Post
2003-12-01 22:24 ` Remco Post
2003-12-01 22:47 ` Remco Post
2003-12-01 23:17 ` Christian Kujau [this message]
2003-12-02 0:26 ` Remco Post
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=3FCBCC0A.5060107@g-house.de \
--to=evil@g-house.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=r.post@sara.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.