Network problem with chip RTL8168D/8111D
Added by Gilles Ribaud about 1 year ago
Hello,
I use Nexenta since two months with release 3.0.0. I encounter, only sometimes, a problem when rebooting : the system cannot be pinged. The only way to recover the network is to put the system off, then to disconnect the power supply, in order to really cut all power supplies and turn completly off all motherboard's components. It is an amd64 motherboard, with an integrated network chip RTL8168D/8111D on chipset AMD785G / SB710. This motherboard had no problem with an opensolaris snv128 thru snv134.
The error messages found in /var/adm/messages is, when it fails:
... May 9 13:22:32 nasappliance gani: [ID 716252 kern.info] gani0: resetting PHY
May 9 13:22:32 nasappliance gani: [ID 813759 kern.info] gani0: ganiinitchip: called
May 9 13:22:32 nasappliance gani: [ID 813759 kern.info] gani0: ganiinit8168: called
May 9 13:22:32 nasappliance gani: [ID 353514 kern.info] gani0: RMS 1523
May 9 13:22:32 nasappliance gani: [ID 563436 kern.info] gani0: ganiinit8168: rcr:8700<128INT>, tcr:2b3007c0
May 9 13:22:32 nasappliance gani: [ID 813759 kern.info] gani0: ganistopchip: called
May 9 13:22:32 nasappliance gani: [ID 813759 kern.info] gani0: ganiresetchip: called
May 9 13:22:32 nasappliance mac: [ID 469746 kern.info] NOTICE: softmac1000 registered
May 9 13:22:32 nasappliance gani: [ID 813759 kern.info] gani0: ganiinitchip: called
May 9 13:22:32 nasappliance gani: [ID 813759 kern.info] gani0: ganiinit8168: called
May 9 13:22:32 nasappliance gani: [ID 353514 kern.info] gani0: RMS 1523
May 9 13:22:32 nasappliance gani: [ID 563436 kern.info] gani0: ganiinit8168: rcr:8700<128INT>, tcr:2b3007c0
May 9 13:22:32 nasappliance pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
May 9 13:22:32 nasappliance genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0
May 9 13:22:33 nasappliance gani: [ID 779564 kern.warning] WARNING: gani0: ganimiiread_raw: timeout, reg:0
May 9 13:22:33 nasappliance gani: [ID 779564 kern.warning] WARNING: gani0: ganimiiread_raw: timeout, reg:4
May 9 13:22:33 nasappliance gani: [ID 831844 kern.info] gani0: auto-negotiation started
May 9 13:22:33 nasappliance gani: [ID 779564 kern.warning] WARNING: gani0: ganimiiread_raw: timeout, reg:0
. . . May 9 13:22:34 nasappliance gani: [ID 779564 kern.warning] WARNING: gani0: ganimiiread_raw: timeout, reg:1
May 9 13:22:34 nasappliance rootnex: [ID 349649 kern.info] iscsi0 at root
May 9 13:22:34 nasappliance genunix: [ID 936769 kern.info] iscsi0 is /iscsi
May 9 13:22:34 nasappliance gani: [ID 779564 kern.warning] WARNING: gani0: ganimiiread_raw: timeout, reg:1
May 9 13:22:38 nasappliance last message repeated 36 times
May 9 13:22:38 nasappliance gani: [ID 503627 kern.warning] WARNING: gani0: auto-negotiation failed: timeout
May 9 13:22:38 nasappliance gani: [ID 779564 kern.warning] WARNING: gani0: ganimiiread_raw: timeout, reg:0
...
When the network card is correctly initialised (after a "very" cold start), the /var/adm/messages contains this:
May 9 13:52:18 nasappliance gani: [ID 716252 kern.info] gani0: resetting PHY
May 9 13:52:18 nasappliance gani: [ID 813759 kern.info] gani0: ganiinitchip: called
May 9 13:52:18 nasappliance gani: [ID 813759 kern.info] gani0: ganiinit8168: called
May 9 13:52:18 nasappliance gani: [ID 353514 kern.info] gani0: RMS 1523
May 9 13:52:18 nasappliance gani: [ID 563436 kern.info] gani0: ganiinit8168: rcr:8700<128INT>, tcr:2b3007c0
May 9 13:52:18 nasappliance gani: [ID 813759 kern.info] gani0: ganistopchip: called
May 9 13:52:18 nasappliance gani: [ID 813759 kern.info] gani0: ganiresetchip: called
May 9 13:52:18 nasappliance mac: [ID 469746 kern.info] NOTICE: softmac1000 registered
May 9 13:52:18 nasappliance gani: [ID 813759 kern.info] gani0: ganiinitchip: called
May 9 13:52:18 nasappliance gani: [ID 813759 kern.info] gani0: ganiinit8168: called
May 9 13:52:18 nasappliance gani: [ID 353514 kern.info] gani0: RMS 1523
May 9 13:52:18 nasappliance gani: [ID 563436 kern.info] gani0: ganiinit8168: rcr:8700<128INT>, tcr:2b3007c0
May 9 13:52:18 nasappliance pseudo: [ID 129642 kern.info] pseudo-device: devinfo0
.
.
.
May 9 13:52:21 nasappliance gani: [ID 455749 kern.info] gani0: auto-negotiation done, advert:1e1<100BASETXFD,100BASETX,10BASETFD,10BASET>, lpable:cde1
May 9 13:52:21 nasappliance gani: [ID 479110 kern.info] MII1000TC:300
May 9 13:52:21 nasappliance gani: [ID 155113 kern.info] gani0: ganisetmedia: phys: 93
May 9 13:52:21 nasappliance gani: [ID 103695 kern.info] gani0: Link up: 1000 Mbps full duplex without flow control
May 9 13:52:21 nasappliance gani: [ID 813759 kern.info] gani0: ganistartchip: called
...
Is this a reset problem of chip ? Looks like a driver problem ? Does anyone got this problem ? And how solved it ?by correcting driver code ?
Thank you very much for your help,
Gilles
Replies
RE: Network problem with chip RTL8168D/8111D - Added by Christian o about 1 year ago
There are other driver versions available that work better.
http://www.nexenta.org/boards/1/topics/224#message-234
RE: Network problem with chip RTL8168D/8111D - Added by Gilles Ribaud about 1 year ago
Yes, I have read the message 234. And yes, this network card was not recognized as "gani" with Opensolaris, but as an rge0 if I remember. I will see that next week (no time now). I'll boot with a live Opensolaris, to see which driver it uses.
Thank you for the idea. Results in a very near future.