LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu
Reload this Page Hardy Heron kept dropping network connection (both wired and wireless)
User Name
Password
Ubuntu This forum is for the discussion of Ubuntu Linux.

Notices


Reply
  Search this Thread
Old 04-30-2010, 06:43 AM   #1
sirpelidor
Member
 
Registered: Oct 2003
Location: Madison
Distribution: mdk 8.2, 9.0, 9.2, slack 9.1
Posts: 403

Rep: Reputation: 30
Angry Hardy Heron kept dropping network connection (both wired and wireless)

Hi, I'm using Hardy Heron on a old Thinkpad T41.

This is a fresh install system and I noticed it kept dropping wireless connection. After google around, seems like this is a common problem? Then I switched to wired network, and turned out the same thing happens again. Looks like doesn't matter wired or wireless, it kept dropping itself from time to time.

After checking syslog, I found something interesting...it kept complain eth0 is invalid, then it said it found a better connection???

I found that extremely weird...

Code:
Apr 30 06:24:32 support kernel: [  961.236895] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Apr 30 06:24:32 support kernel: [  961.236902]   Tx Queue             <0>
Apr 30 06:24:32 support kernel: [  961.236905]   TDH                  <20>
Apr 30 06:24:32 support kernel: [  961.236908]   TDT                  <22>
Apr 30 06:24:32 support kernel: [  961.236911]   next_to_use          <22>
Apr 30 06:24:32 support kernel: [  961.236914]   next_to_clean        <20>
Apr 30 06:24:32 support kernel: [  961.236917] buffer_info[next_to_clean]
Apr 30 06:24:32 support kernel: [  961.236919]   time_stamp           <69b61>
Apr 30 06:24:32 support kernel: [  961.236922]   next_to_watch        <21>
Apr 30 06:24:32 support kernel: [  961.236925]   jiffies              <69c62>
Apr 30 06:24:32 support kernel: [  961.236928]   next_to_watch.status <0>
Apr 30 06:24:34 support kernel: [  963.236418] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Apr 30 06:24:34 support kernel: [  963.236424]   Tx Queue             <0>
Apr 30 06:24:34 support kernel: [  963.236428]   TDH                  <20>
Apr 30 06:24:34 support kernel: [  963.236431]   TDT                  <22>
Apr 30 06:24:34 support kernel: [  963.236433]   next_to_use          <22>
Apr 30 06:24:34 support kernel: [  963.236436]   next_to_clean        <20>
Apr 30 06:24:34 support kernel: [  963.236439] buffer_info[next_to_clean]
Apr 30 06:24:34 support kernel: [  963.236442]   time_stamp           <69b61>
Apr 30 06:24:34 support kernel: [  963.236444]   next_to_watch        <21>
Apr 30 06:24:34 support kernel: [  963.236447]   jiffies              <69e56>
Apr 30 06:24:34 support kernel: [  963.236450]   next_to_watch.status <0>
Apr 30 06:24:36 support kernel: [  965.368638] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Apr 30 06:24:36 support kernel: [  965.368646]   Tx Queue             <0>
Apr 30 06:24:36 support kernel: [  965.368649]   TDH                  <20>
Apr 30 06:24:36 support kernel: [  965.368652]   TDT                  <22>
Apr 30 06:24:36 support kernel: [  965.368655]   next_to_use          <22>
Apr 30 06:24:36 support kernel: [  965.368657]   next_to_clean        <20>
Apr 30 06:24:36 support kernel: [  965.368660] buffer_info[next_to_clean]
Apr 30 06:24:36 support kernel: [  965.368663]   time_stamp           <69b61>
Apr 30 06:24:36 support kernel: [  965.368666]   next_to_watch        <21>
Apr 30 06:24:36 support kernel: [  965.368669]   jiffies              <6a04a>
Apr 30 06:24:36 support kernel: [  965.368671]   next_to_watch.status <0>
Apr 30 06:24:38 support kernel: [  967.368162] e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Apr 30 06:24:38 support kernel: [  967.368169]   Tx Queue             <0>
Apr 30 06:24:38 support kernel: [  967.368172]   TDH                  <20>
Apr 30 06:24:38 support kernel: [  967.368175]   TDT                  <22>
Apr 30 06:24:38 support kernel: [  967.368178]   next_to_use          <22>
Apr 30 06:24:38 support kernel: [  967.368181]   next_to_clean        <20>
Apr 30 06:24:38 support kernel: [  967.368183] buffer_info[next_to_clean]
Apr 30 06:24:38 support kernel: [  967.368186]   time_stamp           <69b61>
Apr 30 06:24:38 support kernel: [  967.368189]   next_to_watch        <21>
Apr 30 06:24:38 support kernel: [  967.368192]   jiffies              <6a23e>
Apr 30 06:24:38 support kernel: [  967.368194]   next_to_watch.status <0>
Apr 30 06:24:39 support kernel: [  968.367821] NETDEV WATCHDOG: eth0: transmit timed out
Apr 30 06:24:39 support NetworkManager: <info>  SWITCH: terminating current connection 'eth0' because it's no longer valid. 
Apr 30 06:24:39 support NetworkManager: <info>  Deactivating device eth0. 
Apr 30 06:24:39 support dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 6485
Apr 30 06:24:39 support dhclient: killed old client process, removed PID file
Apr 30 06:24:39 support dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
Apr 30 06:24:39 support avahi-daemon[4967]: Withdrawing address record for 192.168.0.65 on eth0.
Apr 30 06:24:39 support avahi-daemon[4967]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.65.
Apr 30 06:24:39 support avahi-daemon[4967]: Interface eth0.IPv4 no longer relevant for mDNS.
Apr 30 06:24:40 support avahi-daemon[4967]: Withdrawing address record for fe80::211:25ff:fe30:363f on eth0.
Apr 30 06:24:40 support NetworkManager: nm_device_is_802_3_ethernet: assertion `dev != NULL' failed
Apr 30 06:24:40 support NetworkManager: nm_device_is_802_11_wireless: assertion `dev != NULL' failed
Apr 30 06:24:40 support kernel: [  970.643269] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
Apr 30 06:24:40 support NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link. 
Apr 30 06:24:40 support NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'. 
Apr 30 06:24:40 support kernel: [  970.647676] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Apr 30 06:24:40 support NetworkManager: <info>  Will activate connection 'eth0'. 
Apr 30 06:24:40 support NetworkManager: <info>  Device eth0 activation scheduled... 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) started... 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
Apr 30 06:24:40 support NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
Apr 30 06:24:41 support NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction. 
Apr 30 06:24:41 support dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Apr 30 06:24:41 support NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
Apr 30 06:24:41 support NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0 
Apr 30 06:24:42 support avahi-daemon[4967]: Registering new address record for fe80::211:25ff:fe30:363f on eth0.*.
Apr 30 06:24:42 support NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0 
Apr 30 06:24:45 support dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
Apr 30 06:24:45 support dhclient: DHCPOFFER of 192.168.0.65 from 192.168.0.1
Apr 30 06:24:45 support dhclient: DHCPREQUEST of 192.168.0.65 on eth0 to 255.255.255.255 port 67
Apr 30 06:24:45 support dhclient: DHCPACK of 192.168.0.65 from 192.168.0.1
Apr 30 06:24:45 support avahi-daemon[4967]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.65.
Apr 30 06:24:45 support avahi-daemon[4967]: New relevant interface eth0.IPv4 for mDNS.
Apr 30 06:24:45 support avahi-daemon[4967]: Registering new address record for 192.168.0.65 on eth0.IPv4.
Apr 30 06:24:45 support NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth0 
Apr 30 06:24:45 support NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... 
Apr 30 06:24:45 support NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started... 
Apr 30 06:24:45 support dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Apr 30 06:24:45 support dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers
Apr 30 06:24:45 support NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon: 
Apr 30 06:24:45 support NetworkManager: <info>    address 192.168.0.65 
Apr 30 06:24:45 support NetworkManager: <info>    netmask 255.255.255.0 
Apr 30 06:24:45 support NetworkManager: <info>    broadcast 192.168.0.255 
Apr 30 06:24:45 support NetworkManager: <info>    gateway 192.168.0.1 
Apr 30 06:24:45 support NetworkManager: <info>    nameserver 192.168.0.1 
Apr 30 06:24:45 support NetworkManager: <info>    nameserver 205.171.3.25 
Apr 30 06:24:45 support NetworkManager: <info>    hostname 'tux' 
Apr 30 06:24:45 support NetworkManager: <info>    domain name 'domain.tux' 
Apr 30 06:24:45 support dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.interface_mtu
Apr 30 06:24:45 support NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... 
Apr 30 06:24:45 support NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. 
Apr 30 06:24:45 support NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... 
Apr 30 06:24:45 support dhclient: bound to 192.168.0.65 -- renewal in 37746 seconds.
Apr 30 06:24:45 support avahi-daemon[4967]: Withdrawing address record for 192.168.0.65 on eth0.
Apr 30 06:24:45 support avahi-daemon[4967]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.65.
Apr 30 06:24:45 support avahi-daemon[4967]: Interface eth0.IPv4 no longer relevant for mDNS.
Apr 30 06:24:45 support avahi-daemon[4967]: Withdrawing address record for fe80::211:25ff:fe30:363f on eth0.
Apr 30 06:24:45 support avahi-daemon[4967]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.0.65.
Apr 30 06:24:45 support avahi-daemon[4967]: New relevant interface eth0.IPv4 for mDNS.
Apr 30 06:24:45 support avahi-daemon[4967]: Registering new address record for 192.168.0.65 on eth0.IPv4.
Apr 30 06:24:46 support NetworkManager: <info>  Clearing nscd hosts cache. 
Apr 30 06:24:46 support NetworkManager: <WARN>  nm_spawn_process(): nm_spawn_process('/usr/sbin/nscd -i hosts'): could not spawn process. (Failed to execute child process "/usr/sbin/nscd" (No such file or directory))  
Apr 30 06:24:46 support NetworkManager: <info>  Activation (eth0) successful, device activated. 
Apr 30 06:24:46 support NetworkManager: <info>  Activation (eth0) Finish handler scheduled. 
Apr 30 06:24:46 support NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. 
Apr 30 06:24:46 support ntpdate[14625]: adjust time server 91.189.94.4 offset -0.018862 sec
Apr 30 06:24:47 support avahi-daemon[4967]: Registering new address record for fe80::211:25ff:fe30:363f on eth0.*.
Apr 30 06:24:56 support kernel: [  990.344584] eth0: no IPv6 routers present
Apr 30 06:25:01 support /USR/SBIN/CRON[14929]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Apr 30 06:27:29 support anacron[5386]: Job `cron.monthly' terminated
Apr 30 06:27:29 support anacron[5386]: Normal exit (3 jobs run)
 
Old 05-02-2010, 10:43 AM   #2
tommcd
Senior Member
 
Registered: Jun 2006
Location: Philadelphia PA USA
Distribution: Lubuntu, Slackware
Posts: 2,230

Rep: Reputation: 293Reputation: 293Reputation: 293
Since nobody has of yet answered your thread, I would suggest upgrading to, or doing a clean reinstall of, Ubuntu 10.04. If your internet connection is unreliable then you should probably just do a clean install of 10.04.
Since both 8.04 and 10.04 are LTS versions, it is possible to do a dist-upgrade directly from 8.04 --> 10.04:
https://help.ubuntu.com/community/UpgradeNotes
Since 10.04 will have a much newer kernel and apps, it is likely that 10.04 will have better support for your wired and wireless connections. Ubuntu 8.04 is getting to be rather old and outdated anyway.
Last edited by tommcd; 05-02-2010 at 10:44 AM.
 
  


Reply

Tags
connection, drop, ubuntu, wired, wireless



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
halp, hardy heron without an internet connection Falcon_of_Storms Linux - Software 5 02-08-2009 02:58 PM
ubuntu hardy heron no wifi connection chrisbobbrown Linux - Software 1 05-13-2008 12:36 AM
Ubuntu 8.04 hardy heron recommended wireless network card? fyoder Linux - Wireless Networking 9 05-04-2008 10:55 PM
Wireless PCI in Hardy Heron 8.04 frascelly Linux - Wireless Networking 9 04-27-2008 10:52 PM
Wireless Network Connection Dropping _Ronnie_ Linux - Wireless Networking 0 01-23-2006 08:04 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Ubuntu

All times are GMT -5. The time now is 08:55 PM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration