LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices


Reply
  Search this Thread
Old 12-28-2010, 09:26 AM   #1
chemicstry
LQ Newbie
 
Registered: Dec 2010
Posts: 2

Rep: Reputation: 0
Debian network issues


Hi, i have linux network issues. It happens almost everyday and lasts from 5minutes to few hours, huge ping spikes, disconnects etc. I think logs are self explaining:

messages log:
full: http://pastebin.com/vgACq91n
Code:
Dec 25 16:28:47 debian kernel: [1725676.021403] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:28:47 debian kernel: [1725676.040580] r8169: eth0: link up
Dec 25 16:28:59 debian kernel: [1725689.257009] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:28:59 debian kernel: [1725689.277292] r8169: eth0: link up
Dec 25 16:29:23 debian kernel: [1725714.639316] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:29:23 debian kernel: [1725714.656418] r8169: eth0: link up
Dec 25 16:29:41 debian kernel: [1725733.329948] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:29:41 debian kernel: [1725733.346743] r8169: eth0: link up
Dec 25 16:30:05 debian kernel: [1725759.372519] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:30:05 debian kernel: [1725759.390393] r8169: eth0: link up
Dec 25 16:30:17 debian kernel: [1725772.136114] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:30:17 debian kernel: [1725772.152805] r8169: eth0: link up
Dec 25 16:31:53 debian kernel: [1725873.259547] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:31:53 debian kernel: [1725873.277439] r8169: eth0: link up
Dec 25 16:32:11 debian kernel: [1725892.124006] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:32:11 debian kernel: [1725892.139394] r8169: eth0: link up
Dec 25 16:32:23 debian kernel: [1725904.798311] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:32:23 debian kernel: [1725904.815015] r8169: eth0: link up
Dec 25 16:32:47 debian kernel: [1725929.659319] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:32:47 debian kernel: [1725929.675787] r8169: eth0: link up
Dec 25 16:33:11 debian kernel: [1725954.638239] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:33:11 debian kernel: [1725954.654306] r8169: eth0: link up
Dec 25 16:35:11 debian kernel: [1726083.286877] NETDEV WATCHDOG: eth0: transmit timed out
Dec 25 16:35:11 debian kernel: [1726083.304676] r8169: eth0: link up
Today i was lucky to get this:
Code:
Dec 28 15:14:53 debian kernel: [175485.658214] NETDEV WATCHDOG: eth2: transmit timed out
Dec 28 15:14:53 debian kernel: [175485.658221] ------------[ cut here ]------------
Dec 28 15:14:53 debian kernel: [175485.658223] WARNING: at net/sched/sch_generic.c:222 dev_watchdog+0xa6/0xfb()
Dec 28 15:14:53 debian kernel: [175485.658224] Modules linked in: ipt_MASQUERADE iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack ip_tables x_tables ppdev parport_pc lp parport ipv6 sbp2 loop snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device serio_raw snd i2c_i801 soundcore button psmouse wmi i2c_core snd_page_alloc pcspkr evdev joydev ext3 jbd mbcache sd_mod ata_generic usbhid hid ff_memless ata_piix ahci libata scsi_mod ohci1394 dock r8169 ieee1394 jmicron ide_pci_generic ide_core ehci_hcd uhci_hcd thermal processor fan thermal_sys [last unloaded: scsi_wait_scan]
Dec 28 15:14:53 debian kernel: [175485.658250] Pid: 0, comm: swapper Not tainted 2.6.26-2-amd64 #1
Dec 28 15:14:53 debian kernel: [175485.658251] 
Dec 28 15:14:53 debian kernel: [175485.658252] Call Trace:
Dec 28 15:14:53 debian kernel: [175485.658253]  <IRQ>  [<ffffffff80234958>] warn_on_slowpath+0x51/0x7a
Dec 28 15:14:53 debian kernel: [175485.658260]  [<ffffffff803cca86>] dev_watchdog+0x0/0xfb
Dec 28 15:14:53 debian kernel: [175485.658262]  [<ffffffff802353f3>] printk+0x4e/0x56
Dec 28 15:14:53 debian kernel: [175485.658265]  [<ffffffff80212507>] read_tsc+0x9/0x20
Dec 28 15:14:53 debian kernel: [175485.658268]  [<ffffffff8023cf15>] lock_timer_base+0x26/0x4b
Dec 28 15:14:53 debian kernel: [175485.658271]  [<ffffffff8023d0a4>] __mod_timer+0xbd/0xcc
Dec 28 15:14:53 debian kernel: [175485.658275]  [<ffffffff80243847>] queue_delayed_work_on+0xb8/0xc8
Dec 28 15:14:53 debian kernel: [175485.658278]  [<ffffffff803cca86>] dev_watchdog+0x0/0xfb
Dec 28 15:14:53 debian kernel: [175485.658280]  [<ffffffff803ccb2c>] dev_watchdog+0xa6/0xfb
Dec 28 15:14:53 debian kernel: [175485.658282]  [<ffffffff803cca86>] dev_watchdog+0x0/0xfb
Dec 28 15:14:53 debian kernel: [175485.658284]  [<ffffffff8023c9d5>] run_timer_softirq+0x16a/0x1e2
Dec 28 15:14:53 debian kernel: [175485.658288]  [<ffffffff802393a1>] __do_softirq+0x5c/0xd1
Dec 28 15:14:53 debian kernel: [175485.658291]  [<ffffffff8020d2dc>] call_softirq+0x1c/0x28
Dec 28 15:14:53 debian kernel: [175485.658293]  [<ffffffff8020f3e8>] do_softirq+0x3c/0x81
Dec 28 15:14:53 debian kernel: [175485.658295]  [<ffffffff802392ff>] irq_exit+0x3f/0x85
Dec 28 15:14:53 debian kernel: [175485.658298]  [<ffffffff8021aaab>] smp_apic_timer_interrupt+0x8c/0xa4
Dec 28 15:14:53 debian kernel: [175485.658300]  [<ffffffff80212b57>] mwait_idle+0x0/0x4d
Dec 28 15:14:53 debian kernel: [175485.658302]  [<ffffffff8020cd02>] apic_timer_interrupt+0x72/0x80
Dec 28 15:14:53 debian kernel: [175485.658304]  <EOI>  [<ffffffff80212b98>] mwait_idle+0x41/0x4d
Dec 28 15:14:53 debian kernel: [175485.658310]  [<ffffffff8020ad04>] cpu_idle+0x8e/0xb8
Dec 28 15:14:53 debian kernel: [175485.658316] 
Dec 28 15:14:53 debian kernel: [175485.658317] ---[ end trace 63b0b81ec9dd0a5d ]---
dmesg: http://pastebin.com/qUiLtRfF

Pinging from other network:
Code:
Pinging 84.240.24.209 with 32 bytes of data:
Reply from 84.240.24.209: bytes=32 time=12ms TTL=63
Request timed out.
Reply from 84.240.24.209: bytes=32 time=1800ms TTL=63
Reply from 84.240.24.209: bytes=32 time=11ms TTL=63
Reply from 84.240.24.209: bytes=32 time=601ms TTL=63
Request timed out.
Reply from 84.240.24.209: bytes=32 time=13ms TTL=63
Kernel: Linux debian 2.6.26-2-amd64 #1 SMP Thu Nov 25 04:30:55 UTC 2010 x86_64 GNU/Linux

This is happening for more than 3 months and I just don't know what to do. Maybe it is ISP issue, I don't know. I tried switching network adapter but with no luck.

This is server PC and I'm holding wow and few counter strike servers.
 
Old 12-28-2010, 09:44 AM   #2
AlucardZero
Senior Member
 
Registered: May 2006
Location: USA
Distribution: Debian
Posts: 4,824

Rep: Reputation: 615Reputation: 615Reputation: 615Reputation: 615Reputation: 615Reputation: 615
Some things to try:
- Make sure your kernel is up to date for Lenny
- A different network cable
- A third NIC from a different manufacturer
- Booting with pci=nommconf, noapic or nomsi

Sources:
http://kerneltrap.org/mailarchive/li...8/6/13/2121634
http://kerneltrap.org/mailarchive/li...8/6/14/2125594
 
Old 01-01-2011, 02:45 PM   #3
chemicstry
LQ Newbie
 
Registered: Dec 2010
Posts: 2

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by AlucardZero View Post
Some things to try:
- Make sure your kernel is up to date for Lenny
- A different network cable
- A third NIC from a different manufacturer
- Booting with pci=nommconf, noapic or nomsi

Sources:
http://kerneltrap.org/mailarchive/li...8/6/13/2121634
http://kerneltrap.org/mailarchive/li...8/6/14/2125594
1. kernel is up to date
2. Cable comes directly from isp so i can't change it
3. Tried, same problem
4. don't know how to do that

But is it pure hardware./software problem or it can be related to ISP ?

It seems that only TX packets are dropped:
Code:
eth2      Link encap:Ethernet  HWaddr 00:07:e9:46:56:24
          inet addr:84.240.24.209  Bcast:84.240.24.223  Mask:255.255.255.224
          inet6 addr: fe80::207:e9ff:fe46:5624/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:285966581 errors:0 dropped:0 overruns:0 frame:0
          TX packets:306847785 errors:0 dropped:322 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:31895838353 (29.7 GiB)  TX bytes:57676051076 (53.7 GiB)
          Interrupt:17 Base address:0xc000
EDIT: It seems that it was my friend's cs 1.6 servers what caused lag. Need more time to test it.

Last edited by chemicstry; 01-01-2011 at 02:46 PM.
 
  


Reply



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
Debian installation network issues robbow52 Debian 4 07-21-2009 08:06 PM
Debian: Wireless network and fstab issues NannoBot Linux - Newbie 8 03-04-2009 04:33 PM
Dell m1210 Linux issues (having issues getting network working under Ubuntu) thebert Linux - Newbie 4 03-14-2008 03:47 PM
grub issues: dual boot Debian i386 & Debian amd64 ErrorBound Debian 1 03-09-2007 07:41 PM
Debian laptop/network issues Levitate Debian 6 08-03-2004 03:20 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking

All times are GMT -5. The time now is 03:03 AM.

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