From: Jon Mason <jdmason@us.ibm.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Hans-Frieder Vogt <hfvogt@arcor.de>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com,
netdev@oss.sgi.com
Subject: Re: 2.6.9-rc1-bk11+ and 2.6.9-rc1-mm3,4 r8169: freeze during boot (FIX included)
Date: Thu, 16 Sep 2004 13:20:16 -0500 [thread overview]
Message-ID: <200409161320.16526.jdmason@us.ltcfwd.linux.ibm.com> (raw)
In-Reply-To: <20040916070211.GA32592@electric-eye.fr.zoreil.com>
> Jon, if your ppc64 box offers 64 bits wide PCI slots, it would be nice if
> you could ttry 2.6.9-rc2-bkX, apply
> http://www.fr.zoreil.com/people/francois/misc/r8169-xx0.patch
> and report the content of the "Config2" line in the logs of the kernel.
Here is the info you requested:
r8169 Gigabit Ethernet driver 1.6LK loaded
eth8: Identified chip type is 'RTL8169s/8110s'.
eth8: RTL8169 at 0xa0000000800b7000, 00:40:f4:96:fc:3f, IRQ 131
r8169: eth8: Config2 = 0x01
r8169: eth8: link up
My p630 has 64bit PCI-X slots, but my r8169 adapter is a 32bit adapter. See
lspci output below (with a 64bit PCI-X e1000 adapter as a comparison).
.....
0001:61:01.1 Ethernet controller: Intel Corp. 82546GB Gigabit Ethernet
Controller (rev 03)
Subsystem: IBM: Unknown device 0289
Flags: bus master, 66Mhz, medium devsel, latency 144, IRQ 122
Memory at cc100000 (64-bit, non-prefetchable) [size=cc000000]
Memory at cc040000 (64-bit, non-prefetchable) [size=256K]
I/O ports at 12ec00 [size=64]
Expansion ROM at 00040000 [disabled]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] Capabilities: [f0] Message Signalled
Interrupts: 64bit+ Queue=0/0 Enable-
......
0002:01:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169
Gigabit Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet
Flags: bus master, 66Mhz, medium devsel, latency 74, IRQ 131
I/O ports at 20fc00 [size=e0000000]
Memory at e0020000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at 00020000 [disabled]
Capabilities: [dc] Power Management version 2
I think my AMD64 system at home has a 64bit integrated adapter, as the
performance on it is 2.5x faster (either that or r8169 and ppc don't play
well together). I will verify this when I get home.
--
Jon Mason
jdmason@us.ibm.com
next prev parent reply other threads:[~2004-09-16 18:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200409130035.50823.hfvogt@arcor.de>
[not found] ` <20040912232604.GC27282@electric-eye.fr.zoreil.com>
2004-09-13 12:43 ` 2.6.9-rc1-bk11+ and 2.6.9-rc1-mm3,4 r8169: freeze during boot (FIX included) Hans-Frieder Vogt
2004-09-13 22:02 ` Francois Romieu
2004-09-13 23:31 ` Hans-Frieder Vogt
2004-09-15 22:40 ` Hans-Frieder Vogt
2004-09-15 23:09 ` Francois Romieu
2004-09-15 23:32 ` Hans-Frieder Vogt
2004-09-16 7:02 ` Francois Romieu
2004-09-16 18:20 ` Jon Mason [this message]
2004-09-17 15:43 ` Jon Mason
2004-09-17 16:01 ` Francois Romieu
2004-09-19 21:17 ` Andy Lutomirski
2004-09-19 21:39 ` Francois Romieu
2004-09-19 23:51 ` Andy Lutomirski
2004-09-20 2:56 ` Jeff Garzik
2004-09-20 7:17 ` Francois Romieu
2004-09-20 17:59 ` Jeff Garzik
2004-09-20 21:15 ` Francois Romieu
2004-09-20 16:06 ` Jon Mason
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=200409161320.16526.jdmason@us.ltcfwd.linux.ibm.com \
--to=jdmason@us.ibm.com \
--cc=hfvogt@arcor.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.com \
/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).