Network Communication between "eth0" and "dhcp", only last for 1 minute. On NIC Vendor: Davicom Semiconductor, Inc. Device: 21x4x DEC-Tulip compatible 10/100 Ethernet. NIC Bus Type: PCI

[Joel Bryan Juliano]

My DHCP is up and running, I have no problems acquiring IP address during boot. I can connect to the internet, but for just under 1 minute.

I had experimented with the commands for reloading the network (ifdown eth0, ifup eth0, /etc/init.d/networking restart, dhclient), reacquiring DHCP and manually bringing it up, or use static IP to connect to my DSL modem.
My DSL modem is ZyXel Prestige 600 Series DSL Router. I even kill running dhclient, dhcbdb (NetworkManager), and NetworkManager. And route the gateway manually, but even without DHCP, my connection disconnects after 1 minute.

For the first few seconds, I can ping my Gateway/Router/DHCP server, until 1 minute elapse, then it disconnects. Then after 1 minute elapse I try to run dhclient and it does not work anymore this point.

To bring up the network again, I manually unplugging and re-plugging the network cable. Then it works again, for just 1 minute.

I fixed it using mii-diag, with -r option to resets autonegotiation,

This are the --help options

[help]
Usage: mii-diag [-aDfrRvVw] [-AF <speed+duplex>] [--watch] <interface>.

  This program configures and monitors the transceiver management registers
  for network interfaces. It uses the Media Independent Interface (MII)
  standard with additional Linux-specific controls to communicate with the
  underlying device driver. The MII registers control and report network
  link settings and errors. Examples are link speed, duplex, capabilities
  advertised to the link partner, status LED indications and link error
  counters.

   The common usage is
      mii-diag eth0

   The default interface is "eth0".
 Frequently used options are
   -A --advertise <speed|setting>
   -F --fixed-speed <speed>
 Speed is one of: 100baseT4, 100baseTx, 100baseTx-FD, 100baseTx-HD,
                  10baseT, 10baseT-FD, 10baseT-HD
   -s --status Return exit status 2 if there is no link beat.

 Less frequently used options are
   -a --all-interfaces Show the status all interfaces
              (Not recommended with options that change settings.)
   -D --debug
   -g --read-parameters Get driver-specific parameters.
   -G --set-parameters PARMS Set driver-specific parameters.
       Parameters are comma separated, missing elements retain existing value.
   -M --msg-level LEVEL Set the driver message bit map.
   -p --phy ADDR Set the PHY (MII address) to report.
   -r --restart Restart the link autonegotiation.
   -R --reset Reset the transceiver.
   -v --verbose Report each action taken.
   -V --version Emit version information.
   -w --watch Continuously monitor the transceiver and report changes.

   This command returns success (zero) if the interface information can be
   read. If the --status option is passed, a zero return means that the
   interface has link beat.
[/help]

This is my diagnostic when I am connected, without any parameters

[connected]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/connected]

Connected with -a (all interfaces) option.

[connected-a]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0003 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/connected-a]

connected with -a -D (for debug)

[connected-a-D]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/connected-a-D]

connected with -a -v (for verbose)

[connected-a-v]
mii-diag.c:v2.11 3/21/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
  Using the new SIOCGMIIPHY value on PHY 1 (BMCR 0x3100).
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.

libmii.c:v2.11 2/28/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   3100 782d 0181 b840 01e1 41e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 8018 7800 1000 0001 0002 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:6e:--:--:--, model 4 rev. 0.
   Vendor/Part: Davicom (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation completed.
  Davicom vendor specific registers: 0x0000 0x8018 0x7800.
[/connected-a-v]

connected with -a -v -D

[connected-a-v-D]
mii-diag.c:v2.11 3/21/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
  Using the new SIOCGMIIPHY value on PHY 1 (BMCR 0x3100).
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.

libmii.c:v2.11 2/28/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   3100 782d 0181 b840 01e1 41e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 8018 7800 1000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:6e:--:--:--, model 4 rev. 0.
   Vendor/Part: Davicom (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation completed.
  Davicom vendor specific registers: 0x0000 0x8018 0x7800.
[/connected-a-v-D]

Connected with -s (status)

[connected-s]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0003 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/connected-s]

here is my diagnostic when I get disconnected

without any parameters.

[disconnected]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/disconnected]

with -a

[disconnected-a]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/disconnected-a]

with -a -D

[disconnected-a-D]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/disconnected-a-D]

with -a -v

[disconnected-a-v]
mii-diag.c:v2.11 3/21/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
  Using the new SIOCGMIIPHY value on PHY 1 (BMCR 0x3100).
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.

libmii.c:v2.11 2/28/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   3100 782d 0181 b840 01e1 41e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 8018 7800 1000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:6e:--:--:--, model 4 rev. 0.
   Vendor/Part: Davicom (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation completed.
  Davicom vendor specific registers: 0x0000 0x8018 0x7800.
[/disconnected-a-v]

disconnected with -a-v-D

[disconnected-a-v-D]
mii-diag.c:v2.11 3/21/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
  Using the new SIOCGMIIPHY value on PHY 1 (BMCR 0x3100).
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
   This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.

libmii.c:v2.11 2/28/2005 Donald Becker (<email address hidden>)
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   3100 782d 0181 b840 01e1 41e1 0001 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 8018 7800 1000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x782d ... 782d.
   Link status: established.
   Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation complete.
 Vendor ID is 00:60:6e:--:--:--, model 4 rev. 0.
   Vendor/Part: Davicom (unknown type).
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Negotiation completed.
  Davicom vendor specific registers: 0x0000 0x8018 0x7800.
[/disconnected-a-v-D]

disconnected with -s

[disconnected-s]
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.
[/disconnected-s]

And now the watch interface

[watch-interfce]
Using the default interface 'eth0'.
Basic registers of MII PHY #1: 3100 782d 0181 b840 01e1 41e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner advertised 41e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   End of basic transceiver information.

Monitoring the MII transceiver status.
02:24:10.140 Baseline value of MII BMSR (basic mode status register) is 782d.
--comment --10 seconds -- joelbryan
02:24:28.500 MII BMSR now 7809: no link, NWay busy, No Jabber (0000).
--comment --unplugged cat45-- joelbryan
02:24:43.212 MII BMSR now 782d: Good link, NWay done, No Jabber (41e1).
   New link partner capability is 41e1 0003: 10/100 HD+FD switch.
--comment --replugged cat45-- joelbryan
--comment --still no link because interface being watched-- joelbryan
--comment --still no link after several seconds-- joelbryan
--comment --quitting watch session -- joelbryan
[/watch-interface]

As a solution, I use -r (Restart the link autonegotiation.) or
-R (Reset the transceiver.)

here's the difference

[reset-and-restart]
joelbryan@dhcppc0:~/devs/ethdebug$ sudo mii-diag -r
Using the default interface 'eth0'.
Restarting negotiation...
Basic registers of MII PHY #1: 1000 7809 0181 b840 01e1 0000 0000 0000.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   End of basic transceiver information.

joelbryan@dhcppc0:~/devs/ethdebug$ ping -c 5 www.google.com
PING www.l.google.com (66.102.7.104) 56(84) bytes of data.
64 bytes from 66.102.7.104: icmp_seq=1 ttl=243 time=226 ms
64 bytes from 66.102.7.104: icmp_seq=2 ttl=243 time=227 ms
64 bytes from 66.102.7.104: icmp_seq=3 ttl=243 time=226 ms
64 bytes from 66.102.7.104: icmp_seq=4 ttl=243 time=226 ms
64 bytes from 66.102.7.104: icmp_seq=5 ttl=243 time=226 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 226.681/226.865/227.254/0.365 ms
joelbryan@dhcppc0:~/devs/ethdebug$ sudo mii-diag -R
Using the default interface 'eth0'.
Resetting the transceiver...
Basic registers of MII PHY #1: 3100 7809 0181 b840 01e1 0000 0000 0000.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   End of basic transceiver information.

--comment-- wait for 1 minute to elapse -joelbryan
--comment-- disconnected -joelbryan

joelbryan@dhcppc0:~/devs/ethdebug$ ping -c 5 www.google.com
PING www.l.google.com (66.102.7.147) 56(84) bytes of data.
64 bytes from 66.102.7.147: icmp_seq=1 ttl=243 time=226 ms
64 bytes from 66.102.7.147: icmp_seq=2 ttl=243 time=227 ms
64 bytes from 66.102.7.147: icmp_seq=3 ttl=243 time=226 ms
64 bytes from 66.102.7.147: icmp_seq=4 ttl=243 time=226 ms
64 bytes from 66.102.7.147: icmp_seq=5 ttl=243 time=226 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 226.395/226.819/227.141/0.402 ms
joelbryan@dhcppc0:~/devs/ethdebug$

[/reset-and-restart]

I create a cron job to invoke "/usr/sbin/mii-diag -r" command recurrently every 1 minute.

* * * * * /usr/sbin/mii-diag -r >/dev/null 2> &1>

I hope I provide the details for reporting this bug. I believe that it's
the tulip driver's bug, not my hardware.

And I really want to get this fixed, because my university uses this particular NIC card (over 1 thousand computers) And I'm assigned to deploy Ubuntu Linux, and waiting for Dapper Drake to finalize. :-D

Good Day sir!

[Marc Higgins (mhiggins)]

Also found the same bug in the driver for Davicom DM9102AF network card in Dapper

Device manger reports it as Davicom 21x4x DEC-Tulip compatible 10/100

During installation it initially works & then subsequently fails as it downloads from the repositories.

If your pull the network cable out & put it back it seems to restart it & it will download a little more & then stop again.

Painful but I managed to do an install this way & an apt-get update, apt-get upgrade apt-get dist-upgrade.

dmesg shows tulip_stop_rxtx() failed errors

This fixes it

rmmod tulip
ifdown eth0
rmmod dmfe
modprobe dmfe
ifup eth0

http://www.ubuntuforums.org/showthread.php?t=63161&highlight=davicom

Strange! Anyway is this a bug? How/ where do I report this as a bug?

[d4ft (d4ft3d)]

try "sudo apt-get install dhcpcd"
then "sudo dhcpcd *eth0*"
# replace "*eth0*" with whatever your network
# interface is.
If it bombs out again then "sudo killall dhcpcd-bin"
then repeat "sudo dhcpcd *eth0*"
+++++++++++++++++++++++++++++
"Lead us in a few words of silent prayer."
                -- Bill Peterson, former Houston Oiler football coach

[Joel Bryan Juliano (joelbryan)]

Tried dhcpcd and still doesn't work

[Joel Bryan Juliano (joelbryan)]

I tried inserting dmfe in /etc/modules
and restarted, it now works.

[Carthik Sharma (carthik)]

See also bug #34219
https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/34219

[Carthik Sharma (carthik)]

Added link (bugwatch) to debian bug #326723:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326723

[Carthik Sharma (carthik)]

Confirming this since multiple folks have commented on reproducibility.

[Carthik Sharma (carthik)]

Filing this against linux-image-* since it seems most appropriate.

Maybe module-init-tools is the right package, but am not really sure. Please reassign if that is the case.

[Scott James Remnant (Canonical) (canonical-scott)]

This looks very much like a bug in the driver to me ... netbase is behaving (it's run dhclient for you)

[Felipe Lucero (flu0)]

(Sorry about my english, I'm form Chile)
Same problem here. The courious thing is that at install time, it works fine (downloaded the languaje-support packages for my languaje). Didn't have this prob. on Breezy.

[Fabio (fabiomb)]

Same problem.

If i unplug the network cable and reconnect, the network works again.!!!
When it fails. there's no output, only input (i used iptraf to see the packets, i tested sending packets from other computer, no response, but iptraf can see the incoming packet)

I asked for this on the forum and there are more like us:

http://www.ubuntuforums.org/showthread.php?t=182618&page=2

it's only a Dapper problem, Breezy, Hoary, other linuxes and Windows XP works properly.

I changed DHCP to Static IP address, but the problem continues, one minute (or less) and there's no more connection. If i want to renegotiate the DHCP, simply i can't.

Upgraded from Hoary to Dapper on 2006-05-27 (last update)

the Ethernet is an CNET Pro100

[Fabio (fabiomb)]

i used the "hack" from Marc Higgins and it worked, i will test this for a while, i will post again if something happens.

[Adam (adam-brady)]

I have the same issue with a broadcom NIC. Mine stays up for the most thirty seconds whether I am on the router or not. I also tried setting a static IP and I still have the same issue. If I run mii-diag -r the connection will come back up half of the time.

[trollord (trollenlord)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

[Alex Lowe (lengau)]

I haven't had any problems with this bug in the last year (perhaps more).

Is anyone still experiencing this?

If not, I move to close this bug.

[Carthik Sharma (carthik)]

I don't have access to the hardware anymore, so can't say eitherway. If one other person can confirm there is no problem, then this bug can be closed, I suppose.

[trollord (trollenlord)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the package name in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at [WWW] http://wiki.ubuntu.com/BugSquad/ManagingStatus . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

[Fabio (fabiomb)]

the problem with the tulip driver was fixed in Festy Fawn (7.04) so i'm
really happy
the version with this problem is the 6.06 LTS (the original CD-Rom install),
with the kernel installed in the default version. In 7.04 i haven't find
this problem.

Closed for me.

Fabio

On 8/22/07, trollord < <email address hidden>> wrote:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Thanks in advance.
>
> --
> Network Communication between "eth0" and "dhcp", only last for 1 minute.
> On NIC Vendor: Davicom Semiconductor, Inc. Device: 21x4x DEC-Tulip
> compatible 10/100 Ethernet. NIC Bus Type: PCI
> https://bugs.launchpad.net/bugs/31914
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Joel Bryan Juliano (joelbryan)]

I encountered this bug during Dapper and Edgy, upgrading to Feisty fixed the
bug.