From: Pascal CHAPPERON <pascal.chapperon@wanadoo.fr>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Andrew Hutchings <info@a-wing.co.uk>,
linux-kernel@vger.kernel.org, vinay kumar <b4uvin@yahoo.co.in>,
jgarzik@pobox.com
Subject: Re: sis190
Date: Mon, 13 Jun 2005 10:19:08 +0200 (CEST) [thread overview]
Message-ID: <18320560.1118650748703.JavaMail.www@wwinf1518> (raw)
> Message du 11/06/05 12:58
> De : "Francois Romieu" <romieu@fr.zoreil.com>
> Can you reproduce the tests (dhcp/no dhcp) with the patch linked below and
> add a tcpdump -x output taken at the server as an addition to the usual
> information ?
>
> http://www.fr.zoreil.com/people/francois/misc/20050611a-2.6.12-rc-sis190-test.patch
>
> If you are in a hurry and have any output, I'll look at it today (~18h).
>
> Thanks.
>
> --
> Ueimor
>
>
No, i am not in hurry, and many thanks for working on this driver.
The results :
# cat /var/log/messages
Jun 13 09:04:27 local kernel: sis190 Gigabit Ethernet driver 1.2 loaded
Jun 13 09:04:27 local kernel: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
Jun 13 09:04:27 local kernel: ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
Jun 13 09:04:27 local kernel: 0000:00:04.0: sis190 at ffffc20000004c00 (IRQ: 11), 00:11:2f:e9:42:70
Jun 13 09:04:27 local kernel: eth0: Enabling Auto-negotiation.
Jun 13 09:04:27 local kernel: eth0: status = 20000000
Jun 13 09:04:29 local last message repeated 155 times
Jun 13 09:04:29 local kernel: eth0: status = 20010000
Jun 13 09:04:29 local kernel: eth0: link change
Jun 13 09:04:29 local kernel: eth0: Link on unknown mode.
Jun 13 09:04:29 local kernel: eth0: status = 20000000
Jun 13 09:04:29 local last message repeated 4 times
Jun 13 09:04:29 local network: Bringing up interface eth0: succeeded
Jun 13 09:04:29 local kernel: eth0: status = 20000000
Jun 13 09:04:31 local last message repeated 147 times
Jun 13 09:04:31 local kernel: eth0: status = 2000000c
Jun 13 09:04:31 local kernel: eth0: status = 20000000
...
Jun 13 09:05:02 local kernel: eth0: Rx status = 40040040
Jun 13 09:05:02 local kernel: eth0: Rx PSize = 01010040
Jun 13 09:05:02 local kernel: eth0: Rx status = c0000000
Jun 13 09:05:03 local kernel: eth0: Rx status = 40040040
Jun 13 09:05:03 local kernel: eth0: Rx PSize = 01010040
Jun 13 09:05:03 local kernel: eth0: Rx status = c0000000
Jun 13 09:05:04 local kernel: eth0: Rx status = 40040040
Jun 13 09:05:04 local kernel: eth0: Rx PSize = 01010040
Jun 13 09:05:04 local kernel: eth0: Rx status = c0000000
Jun 13 09:05:05 local kernel: eth0: Rx status = 40040040
Jun 13 09:05:05 local kernel: eth0: Rx PSize = 01010040
Jun 13 09:05:05 local kernel: eth0: Rx status = c0000000
Jun 13 09:05:06 local kernel: eth0: Rx status = 40040040
Jun 13 09:05:06 local kernel: eth0: Rx PSize = 01010040
Jun 13 09:05:06 local kernel: eth0: Rx status = c0000000
Jun 13 09:05:07 local kernel: eth0: Rx status = 40040040
Jun 13 09:05:07 local kernel: eth0: Rx PSize = 01010040
Jun 13 09:05:07 local kernel: eth0: Rx status = c0000000
...
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:2F:E9:42:70
inet addr:10.169.21.20 Bcast:10.169.23.255 Mask:255.255.252.0
inet6 addr: fe80::211:2fff:fee9:4270/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:141 errors:0 dropped:0 overruns:0 frame:0
TX packets:144 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8460 (8.2 KiB) TX bytes:6104 (5.9 KiB)
Interrupt:11 Base address:0xbeef
NOTE : here is something strange about base address =>
dmesg : sis190 at ffffc20000004c00 (IRQ: 11)
ifconfig : Interrupt:11 Base address:0xbeef
# local tcpdump : ping server 10.169.21.1 from local 10.169.21.20
09:09:41.798748 arp who-has 10.169.21.1 tell 10.169.21.20
0x0000: 0001 0800 0604 0001 0011 2fe9 4270 0aa9 ........../.Bp..
0x0010: 1514 0000 0000 0000 0aa9 1501 ............
09:09:41.798920 4f:06:48:6e:08:06 null > 2f:e9:42:70:00:30 sap 08 I (s=3,r=2,C) len=42
0x0000: 0800 0604 0002 0030 4f06 486e 0aa9 1501 .......0O.Hn....
0x0010: 0011 2fe9 4270 0aa9 1514 0000 0000 0000 ../.Bp..........
0x0020: 0000 0000 0000 0000 0000 0000 0c15 ..............
09:09:42.798592 arp who-has 10.169.21.1 tell 10.169.21.20
0x0000: 0001 0800 0604 0001 0011 2fe9 4270 0aa9 ........../.Bp..
0x0010: 1514 0000 0000 0000 0aa9 1501 ............
09:09:42.798767 4f:06:48:6e:08:06 null > 2f:e9:42:70:00:30 sap 08 I (s=3,r=2,C) len=42
0x0000: 0800 0604 0002 0030 4f06 486e 0aa9 1501 .......0O.Hn....
0x0010: 0011 2fe9 4270 0aa9 1514 0000 0000 0000 ../.Bp..........
0x0020: 0000 0000 0000 0000 0000 0000 0c15 ..............
...
# server tcpdump : ping server 10.169.21.1 from local 10.169.21.20
09:27:40.749713 arp who-has 10.169.21.1 tell 10.169.21.20
0x0000: 0001 0800 0604 0001 0011 2fe9 4270 0aa9 ........../.Bp..
0x0010: 1514 0000 0000 0000 0aa9 1501 0000 0000 ................
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
09:27:40.749797 arp reply 10.169.21.1 is-at 00:30:4f:06:48:6e
0x0000: 0001 0800 0604 0002 0030 4f06 486e 0aa9 .........0O.Hn..
0x0010: 1501 0011 2fe9 4270 0aa9 1514 ..../.Bp....
09:27:41.749522 arp who-has 10.169.21.1 tell 10.169.21.20
0x0000: 0001 0800 0604 0001 0011 2fe9 4270 0aa9 ........../.Bp..
0x0010: 1514 0000 0000 0000 0aa9 1501 0000 0000 ................
0x0020: 0000 0000 0000 0000 0000 0000 0000 ..............
09:27:41.749605 arp reply 10.169.21.1 is-at 00:30:4f:06:48:6e
0x0000: 0001 0800 0604 0002 0030 4f06 486e 0aa9 .........0O.Hn..
0x0010: 1501 0011 2fe9 4270 0aa9 1514 ..../.Bp....
It seems that sis190 driver shifts 4 bytes...
further test about autoneg, probably silly:
be nice, as i know nothing to network drivers dev.
i do not understand what is LPA_SLCT...
modification :
# diff -puN sis190-20050611a.c sis190.c
--- sis190-20050611a.c 2005-06-13 08:54:56.000000000 +0200
+++ sis190.c 2005-06-13 09:41:29.000000000 +0200
@@ -630,7 +630,7 @@ static irqreturn_t sis190_interrupt(int
SIS_W32(IntrStatus, status);
- printk(KERN_INFO "%s: status = %08x\n", dev->name, status);
+ // printk(KERN_INFO "%s: status = %08x\n", dev->name, status);
if ((status & LinkChange) && netif_running(dev)) {
printk(KERN_INFO "%s: link change\n", dev->name);
@@ -823,18 +823,17 @@ static void sis190_phy_task(void * data)
u16 ctl;
const char *msg;
} reg31[] = {
- { _1000bpsF, 0x1c01, "1000 bps Full Duplex" },
- { _1000bpsH, 0x0c01, "1000 bps Half Duplex" },
- { _100bpsF, 0x1801, "100 bps Full Duplex" },
- { _100bpsH, 0x0801, "100 bps Half Duplex" },
- { _10bpsF, 0x1401, "10 bps Full Duplex" },
- { _10bpsH, 0x0401, "10 bps Half Duplex" },
+ { LPA_1000XFULL | LPA_SLCT, 0x1c01, "1000 bps Full Duplex" },
+ { LPA_1000XHALF | LPA_SLCT, 0x0c01, "1000 bps Half Duplex" },
+ { LPA_100FULL, 0x1801, "100 bps Full Duplex" },
+ { LPA_100HALF, 0x0901, "100 bps Half Duplex" },
+ { LPA_10FULL, 0x1401, "10 bps Full Duplex" },
+ { LPA_10HALF, 0x0401, "10 bps Half Duplex" },
{ 0, 0x0000, "unknown" }
}, *p;
- val = mdio_read(ioaddr, LPA_SLCT) & 0x1c; // bit 4:2
-
+ val = mdio_read(ioaddr, MII_LPA);
for (p = reg31; p->ctl; p++) {
- if (val == p->val)
+ if ((val & p->val) == p->val)
break;
}
if (p->ctl)
# dmesg
...
[ remote card forced in 10 half autoneg off ]
...
sis190 Gigabit Ethernet driver 1.2 loaded
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LNKD] -> GSI 11 (level, low) ->
IRQ 11
PCI: Setting latency timer of device 0000:00:04.0 to 64
0000:00:04.0: sis190 at ffffc20000004c00 (IRQ: 11), 00:11:2f:e9:42:70
eth0: Enabling Auto-negotiation.
eth0: Link on 10 bps Half Duplex mode.
eth0: no IPv6 routers present
...
[ remote card in 10 full autoneg off ]
[ I must restart the network to have (false) mode detection ]
...
eth0: Link on 10 bps Half Duplex mode.
eth0: Link on 10 bps Half Duplex mode.
...
[ remote card in 100 full autoneg on ]
[ no network restart ]
...
eth0: no IPv6 routers present
eth0: link change
eth0: PHY reset until link up
eth0: link change
eth0: Link on 100 bps Full Duplex mode.
eth0: Link on 100 bps Full Duplex mode.
...
Regards
Pascal
next reply other threads:[~2005-06-13 8:19 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 8:19 Pascal CHAPPERON [this message]
2005-06-13 21:39 ` sis190 Francois Romieu
-- strict thread matches above, loose matches on Subject: below --
2005-07-10 13:23 sis190 Pascal CHAPPERON
2005-07-09 13:25 sis190 Pascal CHAPPERON
2005-07-09 20:57 ` sis190 Francois Romieu
2005-07-06 15:58 sis190 Pascal CHAPPERON
2005-07-06 21:29 ` sis190 Francois Romieu
2005-07-02 10:52 sis190 Pascal CHAPPERON
2005-07-02 11:33 ` sis190 Francois Romieu
2005-07-04 23:30 ` sis190 Francois Romieu
2005-06-26 12:39 sis190 Pascal CHAPPERON
2005-06-30 23:37 ` sis190 Francois Romieu
2005-06-19 10:17 sis190 Pascal CHAPPERON
2005-06-21 23:02 ` sis190 Francois Romieu
2005-06-17 11:14 sis190 Pascal CHAPPERON
2005-06-17 18:22 ` sis190 Francois Romieu
2005-06-15 15:22 sis190 Pascal CHAPPERON
2005-06-16 22:34 ` sis190 Francois Romieu
2005-06-14 14:14 sis190 Pascal CHAPPERON
2005-06-14 20:04 ` sis190 Francois Romieu
2005-06-11 9:39 sis190 Pascal CHAPPERON
2005-06-11 10:56 ` sis190 Francois Romieu
2005-06-07 22:37 sis5513.c patch Andrew Hutchings
2005-06-07 22:57 ` Francois Romieu
2005-06-07 23:20 ` Andrew Hutchings
2005-06-08 22:51 ` sis190 (was: Re: sis5513.c patch) Francois Romieu
2005-06-09 4:54 ` sis190 Andrew Hutchings
2005-06-09 12:02 ` sis190 Andrew Hutchings
2005-06-09 21:18 ` sis190 Francois Romieu
2005-06-10 13:55 ` sis190 Andrew Hutchings
2005-06-10 23:41 ` sis190 Francois Romieu
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=18320560.1118650748703.JavaMail.www@wwinf1518 \
--to=pascal.chapperon@wanadoo.fr \
--cc=b4uvin@yahoo.co.in \
--cc=info@a-wing.co.uk \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.