Message-ID: <20070301095711.GC22482@venus.synerway.com>
Date:	Thu, 1 Mar 2007 10:57:11 +0100
From:	pgs@...erway.com
To:	netdev@...r.kernel.org
Subject: Re: need some help on a backport of r8169

Hello Ueimor,

I succeeded to make the MII ioctls work in the r1000 driver. It seems
to be a solution for my problem.
Thank you a lot, it wouldn't have been possible without your help. You
allowed me to place some debug in the r8169 driver and look at it with
an up interface so I could compare some values.
I will send you my patch for r1000, if it can be of any use for you,
however I don't think I can do it before next week.

Though I continue to send you the interesting informations. See
further.
 

Francois Romieu a écrit, le Thu 01 Mar 2007 à 12:08:07AM :
> pgs@...erway.com <pgs@...erway.com> :
> [...]
> > The problem comes here, I do a ping and it seems to have just the time
> > to make the DNS resolution but not further. When I do a new ifconfig,
> > the TX dropped is not 0 anymore. Then I can turn up and down my
> > interface, I won't be able to ping anything.
> 
> Ok, almost perfect for a first try. :o)
> 
> If you can issue 'ifconfig' and do an ethtool dump of the registers at
> the interesting points in time, it could surely help.
eth0      Link encap:Ethernet  HWaddr 00:16:EC:8F:2F:AF  
          inet addr:172.16.39.95  Bcast:172.16.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1523 errors:0 dropped:0 overruns:0 frame:0
          TX packets:154 errors:0 dropped:43 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:138174 (134.9 Kb)  TX bytes:14386 (14.0 Kb)
          Interrupt:10 

Offset	Value
--------	-----
00	0x00
01	0x16
02	0xec
03	0x8f
04	0x2f
05	0xaf
06	0x00
07	0x00
08	0xff
09	0xff
10	0xff
11	0xff
12	0xff
13	0xff
14	0xff
15	0xff
16	0x80
17	0x81
18	0x32
19	0xf7
20	0xc4
21	0x81
22	0x32
23	0xf7
24	0x00
25	0x00
26	0x00
27	0x00
28	0x00
29	0x00
30	0x00
31	0x00
32	0x00
33	0x60
34	0x7b
35	0x17
36	0x00
37	0x00
38	0x00
39	0x00
40	0x00
41	0x81
42	0x32
43	0xf7
44	0xc4
45	0x81
46	0x32
47	0xf7
48	0x00
49	0x00
50	0x00
51	0x00
52	0x00
53	0x00
54	0x00
55	0x0c
56	0x00
57	0x00
58	0x00
59	0x00
60	0x7f
61	0x80
62	0x00
63	0x00
64	0x00
65	0x06
66	0x00
67	0x3b
68	0x0e
69	0xe6
70	0x00
71	0x00
72	0xa9
73	0xcf
74	0xfa
75	0xc5
76	0x00
77	0x00
78	0x00
79	0x00
80	0x00
81	0x05
82	0x0f
83	0x30
84	0x20
85	0x00
86	0x01
87	0x00
88	0x00
89	0x00
90	0x00
91	0x00
92	0x00
93	0x00
94	0x00
95	0x00
96	0x00
97	0x10
98	0x00
99	0x80
100	0xc4
101	0x81
102	0x32
103	0xf7
104	0x7f
105	0xab
106	0x00
107	0x00
108	0x73
109	0x02
110	0x01
111	0x00
112	0x00
113	0x00
114	0x00
115	0x00
116	0x00
117	0x00
118	0x00
119	0x00
120	0x00
121	0x00
122	0xff
123	0xff
124	0x00
125	0x00
126	0x00
127	0x00
128	0x93
129	0x1b
130	0x01
131	0x80
132	0xc4
133	0x81
134	0x32
135	0xf7
136	0xc4
137	0x81
138	0x32
139	0xf7
140	0xc4
141	0x81
142	0x32
143	0xf7
144	0xc4
145	0x81
146	0x32
147	0xf7
148	0xc4
149	0x81
150	0x32
151	0xf7
152	0xc4
153	0x81
154	0x32
155	0xf7
156	0xc4
157	0x81
158	0x32
159	0xf7
160	0xc4
161	0x81
162	0x32
163	0xf7
164	0xc4
165	0x81
166	0x32
167	0xf7
168	0xc4
169	0x81
170	0x32
171	0xf7
172	0xc4
173	0x81
174	0x32
175	0xf7
176	0xc4
177	0x81
178	0x32
179	0xf7
180	0xc4
181	0x81
182	0x32
183	0xf7
184	0xc4
185	0x81
186	0x32
187	0xf7
188	0xc4
189	0x81
190	0x32
191	0xf7
192	0xc4
193	0x81
194	0x32
195	0xf7
196	0xc4
197	0x81
198	0x32
199	0xf7
200	0xc4
201	0x81
202	0x32
203	0xf7
204	0xc4
205	0x81
206	0x00
207	0x00
208	0x00
209	0x00
210	0x00
211	0x00
212	0x00
213	0x00
214	0x00
215	0x00
216	0x00
217	0x00
218	0xff
219	0x3f
220	0x00
221	0x00
222	0x00
223	0x00
224	0x28
225	0x20
226	0x00
227	0x00
228	0x00
229	0x90
230	0x74
231	0x17
232	0x00
233	0x00
234	0x00
235	0x00
236	0x3f
237	0x00
238	0x00
239	0x00
240	0x00
241	0x00
242	0x00
243	0x00
244	0x00
245	0x00
246	0x00
247	0x00
248	0x00
249	0x00
250	0x00
251	0x00
252	0x00
253	0x00
254	0x00
255	0x00

I'm so sorry I couldn't give you a better dump, ethtool 5 told me
"Unknown Realtek chipset".

FYI: I noticed that ethtool -d eth0 is not supported with the r1000 driver.

> 
> [...]
> > Ah... poor me who thought that the RTL8168 was just like the RTL8169 with
> > a pci express interface... It seems that a PCI-Express RTL8169 also
> > exist right?
> 
> Remind me to check it later.
If I don't forget.

> 
> [...]
> > Do you think my problem is the one you mentionned above, without the
> > experimental patches?
> 
> It is possible. I should review the diffs too.
> 
> Once you have logged the ifconfig/ethtool dump, you can try the serie
> or the patch at:
> 
> http://www.fr.zoreil.com/people/francois/backport/r8169/20070228-00
Hum... ok I might have enough time to check it, not sure though, I
have a point with my boss this morning.

> 
> Btw:
> 
> [...dmesg dump...]
> > Enabling fast FPU save and restore... done.
> > Enabling unmasked SIMD FPU exception support... done.
> > Checking 'hlt' instruction... OK.
> > ACPI: setting ELCR to 0200 (from 0c08)
> > NET: Registered protocol family 16
> > PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=2
> > PCI: Using MMCONFIG
> 
> Please disable MMCONFIG.
In the BIOS?

> 
> If you have any PCI latency option in your bios, set it to 64.
I'm not the BIOS-master, I'll suggest it.

> 
> -- 
> Ueimor

Sigerg
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists