LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 03-02-2015, 08:51 PM   #1
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Rep: Reputation: Disabled
Debian dropping packets, killing home router and 100% CPU utilization


Hi folks, right up front - total Linux noob (or newb?) here, first post. I've tried to research this on my own as much as possible but I'm out of ideas and could use some expert opinion on possible causes or things to try.

Issue: My Debian workstation was running fine, unsure of what the actual trigger was for my issues. My Comcast ISP had some issues with their node in the neighborhood and I also did some standard Linux updates. Not sure either of those are responsible but now my system drops packets, drives crazy-high CPU utilization and overloads/crashes my home router.

Symptom: Intel DZ77SL-50K mboard with Intel Core i7-3770 with 82579V gigabit controller running Debian 7.1 has a wired 100 mbit connection to my home Netgear router. Shortly after booting all 8 cores of the processor each go to 100% utilization for about 20 seconds from a weirdly-named (string of random letters) root process (I'm using "top" and the graphical resource monitor). At this point my Netgear router drops it's wifi connections with other devices in the home. The system then returns to normal, the router then reconnects with wifi devices and about 2 minutes go by before the cycle starts all over again. (Logs on the router - which are minimal - show nothing). Also Network traffic on the resource monitor oddly shows nothing). Running mtr and ping (to 8.8.8.8) shows major packet loss during the 800% utilization cycle and then when the spike is over packet loss returns to zero. Running "dmesg | grep eth" shows the adapter sometimes resetting during the 800% period.

Killing the process (sudo kill pid XXXX) simply causes a new root process with a new (weird) name and PID to be generated almost immediately and the cycle starts over.

I googled and found some old issues with the e1000e driver on the Intel 82579V LAN controller and was (painfully) able to download the latest driver, compile and install it but nothing changed. I also used ethtools to turn off tso (tcp segmentation offload) but that had no effect. I also tried acpi=off in grub with no effect. I also am running the latest BIOS update and the Netgear has the latest firmware. This is a dual-boot machine and there are no issues whatsoever with the box when running Win 7.

Also, weirdly, if I use "ifdown eth0" then 1 core (of 8) runs at 100% utilization all the time. (More specifically the single core appears to drop to 0% after ~10 sec however another core picks up immediately to 100% so basically there is always 1 core running at 100%.).

I'm using DHCP and resolve.conf has a single entry to 192.168.1.1.

Any thoughts/suggestions greatly appreciated. Also keep in mind I'm a noob so re-building the kernel and suggestions like that are a stretch for me although I could try.
 
Old 03-02-2015, 11:08 PM   #2
ceyx
Member
 
Registered: May 2009
Location: Fort Langley BC
Distribution: Kubuntu,Free BSD,OSX,Windows
Posts: 342

Rep: Reputation: 59
Okay, I'll bite.

What is the make and model of your router ?

What is the output of 'ifconfig' ?

How do you know your system is dropping packets ?
 
Old 03-02-2015, 11:52 PM   #3
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,188

Rep: Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131
Let's see what those tasks are - during a bad period, do this from a terminal and post the output
Code:
top -b -n 1 | head -n 25
 
Old 03-03-2015, 01:51 PM   #4
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Original Poster
Rep: Reputation: Disabled
Thanks for the response, a couple of updates and comments in addition to your requests.

1) After a week+ straight of having this issue the behaviour is different today: So far after two cold boots it did not have any of the 800% (all 8 cores) CPU utilization cycle and everything appeared & acted normal. However I ran "mtr" (see #2 below) which hosed my internet connect so I did a "ifdown eth0" and I did get the previously described signle-thread 100% utilization (see "top" data below).

2) With everything running fine i ran "mtr 8.8.8.8" and it showed massive packet loss again HOWEVER I dug into my limited router logs and found:

"[DoS attack: STORM] attack packets in last 20 sec from ip [192.168.1.19], Tuesday, Mar 03,2015 12:00:45"

so I'm wondering if the "packet loss" is actually my router's fault (maybe overwhelming it's CPU causing it to drop wifi, etc).



Quote:
What is the make and model of your router ?

What is the output of 'ifconfig' ?

How do you know your system is dropping packets ?

The router is a Netgear N600 WNDR3700v3 with most recent firmware. I believe it's dropping packets because 1) "mtr" show packet loss during that period and "ping" hangs, then gives some kind of error until the CPU burst is over and then works normally. "ifconfig" is as follows:

steve@debian:~$ sudo ifconfig -a
eth0 Link encap:Ethernet HWaddr 4c:72:b9:43:e2:0e
inet addr:192.168.1.19 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::4e72:b9ff:fe43:e20e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8757 errors:0 dropped:0 overruns:0 frame:0
TX packets:171620 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5749751 (5.4 MiB) TX bytes:175615191 (167.4 MiB)
Interrupt:20 Memory:f7c00000-f7c20000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:11163456 errors:0 dropped:0 overruns:0 frame:0
TX packets:11163456 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:558172880 (532.3 MiB) TX bytes:558172880 (532.3 MiB)



When I run "ifdown eth0" and the single core goes to 100% this is the process list:

steve@debian:~$ top -b -n 1 | head -n 25
top - 14:10:37 up 7 min, 2 users, load average: 0.19, 0.71, 0.52
Tasks: 174 total, 1 running, 173 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.6 us, 4.7 sy, 0.0 ni, 87.9 id, 1.7 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem: 16367004 total, 1073080 used, 15293924 free, 34908 buffers
KiB Swap: 33342460 total, 0 used, 33342460 free, 538796 cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2294 root 20 0 66512 504 192 S 98.2 0.0 4:31.42 wvbhgntrsa
3881 steve 20 0 1001m 126m 39m S 19.6 0.8 0:11.39 gnome-shell
4043 steve 20 0 378m 16m 11m S 6.5 0.1 0:00.68 gnome-terminal
1 root 20 0 10648 828 692 S 0.0 0.0 0:01.14 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
6 root rt 0 0 0 0 S 0.0 0.0 0:00.09 migration/0
7 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
8 root rt 0 0 0 0 S 0.0 0.0 0:00.09 migration/1
10 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
11 root 20 0 0 0 0 S 0.0 0.0 0:00.12 kworker/0:1
12 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
13 root rt 0 0 0 0 S 0.0 0.0 0:00.02 migration/2
15 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/2
16 root rt 0 0 0 0 S 0.0 0.0 0:00.03 watchdog/2
17 root rt 0 0 0 0 S 0.0 0.0 0:00.09 migration/3
19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/3
20 root rt 0 0 0 0 S 0.0 0.0 0:00.00 watchdog/3

The "wvbhgntrsa" appears to be the offender; note that: 1) when I do have the 800% CPU utilization it has a very similar process name/PID and 2) if I kill that it simply respawns with a different (but similar weird format) name and different PID number.

At this point I'm guessing mtr doesn't work correctly because my router is getting overwhelmed or doesn't understand the IP packet type or something. However the rest of the behaviour still seems eratic. Thanks.
 
Old 03-03-2015, 11:43 PM   #5
ceyx
Member
 
Registered: May 2009
Location: Fort Langley BC
Distribution: Kubuntu,Free BSD,OSX,Windows
Posts: 342

Rep: Reputation: 59
Quote:
The router is a Netgear N600 WNDR3700v3
You might be interested in this DDWRT firmware for your router : http://www.dd-wrt.com/wiki/index.php/Netgear_WNDR3700
but maybe after you fix this problem

Quote:
RX packets:8757 errors:0 dropped:0 overruns:0 frame:0
TX packets:171620 errors:0 dropped:0 overruns:0 carrier:0
It is interesting that there are no errors reported above.

Quote:
2294 root 20 0 66512 504 192 S 98.2 0.0 4:31.42 wvbhgntrsa
You can get more info on what this process is by using 'strace -p2294', or whatever PID shows up next time.

The best place to get fast info on what is going on is in /var/log.
For example run 'tail -f /var/log/syslog' and something should jump out at you.
You can also run 'tail -100 /var/log/syslog' to get the last 100 lines (or 1000) if you are not that fast after your computer boots.
Also look at the other log files in that location - some indication is almost guaranteed to be there.

Where is your
Quote:
mtr 8.8.8.8
failing ? on the first hop ?

Also, if you want to narrow things down, if possible, just have the 192.168.1.19 machine and the router on the lan. Leave the other clients off. I have seen Windows network discovery go apeshit trying to figure out who the new client is when it comes up.

What does Comcast give you ? a modem or a modem/router ? Or asked another way, what is between your 192.168.1.1 router and the net ?

Good luck, and let us know what you find out
 
Old 03-04-2015, 06:45 PM   #6
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Original Poster
Rep: Reputation: Disabled
Hi,

Well I booted this morning and the exact same thing came back. So some additional notes:

1) The LAN config is Comcast cable -> Arris 722 modem (single port) -> Netgear Router (WiFi + 4 LAN)

2) The mtr fails across all hops, and I've seen it fail on hop #1 (my Netgear 192.168.1.1)

3) Recalling the single core (out of 8) 100% utilization which happens when I take eth0 down the top info is:

steve@debian:~$ top -b -n 1 | head -n 25
top - 14:10:37 up 7 min, 2 users, load average: 0.19, 0.71, 0.52
Tasks: 174 total, 1 running, 173 sleeping, 0 stopped, 0 zombie
%Cpu(s): 5.6 us, 4.7 sy, 0.0 ni, 87.9 id, 1.7 wa, 0.0 hi, 0.1 si, 0.0 st
KiB Mem: 16367004 total, 1073080 used, 15293924 free, 34908 buffers
KiB Swap: 33342460 total, 0 used, 33342460 free, 538796 cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2294 root 20 0 66512 504 192 S 98.2 0.0 4:31.42 wvbhgntrsa
3881 steve 20 0 1001m 126m 39m S 19.6 0.8 0:11.39 gnome-shell
4043 steve 20 0 378m 16m 11m S 6.5 0.1 0:00.68 gnome-terminal
1 root 20 0 10648 828 692 S 0.0 0.0 0:01.14 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
6 root rt 0 0 0 0 S 0.0 0.0 0:00.09 migration/0


So I decided to remove the Netgear completely - Debian is now hardwired directly into the Arris modem. After booting the same cycle begins again - ~2 min 24 sec of normalcy, then ~26 seconds of 800% (all 8 CPU cores) CPU utilization. This period repeats just like clockwork. During the 800% utilization:

steve@debian:~$ top -b -n 1
top - 19:07:18 up 1 min, 2 users, load average: 4.48, 1.24, 0.43
Tasks: 175 total, 2 running, 173 sleeping, 0 stopped, 0 zombie
%Cpu(s): 12.8 us, 12.8 sy, 0.0 ni, 68.3 id, 5.7 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem: 16367004 total, 743496 used, 15623508 free, 28640 buffers
KiB Swap: 33342460 total, 0 used, 33342460 free, 375620 cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2297 root 20 0 156m 4416 184 S 726.2 0.0 3:31.03 izsobvefdj
1 root 20 0 10648 828 692 S 0.0 0.0 0:01.12 init
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.08 ksoftirqd/0
4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/0:0
5 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kworker/u:0
6 root rt 0 0 0 0 S 0.0 0.0 0:00.04 migration/0


Note that during this 800% CPU utilization mtr fails hop 2 - 10. (Hop #1 is "???"). Ping also fails. (This is also the time when my Netgear would drop wireless connections and also report a DOS attack).

I ran strace - there's a ton of data generated, not sure what is relevant but I can't even post 5 seconds worth. Any guidance in what to look for is appreciated.

Per your suggestion (BTW thanks I'm learning a lot) I looked at some log files - I could use your help on if there's anything meaningful here:

steve@debian:~$ sudo tail -100 /var/log/syslog
Mar 4 16:25:39 debian anacron[2421]: Job `cron.daily' terminated
Mar 4 16:25:39 debian anacron[2421]: Normal exit (1 job run)
Mar 4 16:27:01 debian /USR/SBIN/CRON[5473]: (root) CMD (/etc/cron.hourly/cron.sh)
Mar 4 16:27:41 debian kernel: [ 449.761425] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:27:41 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:27:44 debian kernel: [ 453.234854] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:27:44 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)
Mar 4 16:30:01 debian /USR/SBIN/CRON[6048]: (root) CMD (/etc/cron.hourly/cron.sh)
Mar 4 16:30:30 debian kernel: [ 618.271605] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:30:30 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:30:33 debian kernel: [ 621.788899] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:30:33 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)
Mar 4 16:33:01 debian /USR/SBIN/CRON[6625]: (root) CMD (/etc/cron.hourly/cron.sh)


steve@debian:/var/log$ sudo tail -15 daemon.log
Mar 4 16:21:54 debian minissdpd[3385]: 3 new devices added
Mar 4 16:21:54 debian minissdpd[3385]: 12 new devices added
Mar 4 16:21:58 debian minissdpd[3385]: 6 new devices added
Mar 4 16:24:22 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:24:25 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)
Mar 4 16:27:41 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:27:44 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)
Mar 4 16:30:30 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:30:33 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)
Mar 4 16:33:09 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:33:12 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)
Mar 4 16:34:19 debian minissdpd[3385]: 10 new devices added
Mar 4 16:34:20 debian minissdpd[3385]: 4 new devices added
Mar 4 16:36:48 debian NetworkManager[3022]: <info> (eth0): carrier now OFF (device state 10)
Mar 4 16:36:51 debian NetworkManager[3022]: <info> (eth0): carrier now ON (device state 10)



steve@debian:/var/log$ sudo tail -15 kern.log
Mar 4 16:21:18 debian kernel: [ 67.813609] [<ffffffff81356a5e>] ? apic_timer_interrupt+0x6e/0x80
Mar 4 16:21:18 debian kernel: [ 67.813610] <EOI> [<ffffffff81358844>] ? ia32_syscall+0x14/0x60
Mar 4 16:21:18 debian kernel: [ 67.813614] ---[ end trace d4b06df8bb5b2d31 ]---
Mar 4 16:21:18 debian kernel: [ 67.813619] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:21:21 debian kernel: [ 71.298894] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:24:22 debian kernel: [ 251.324795] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:24:25 debian kernel: [ 254.818186] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:27:41 debian kernel: [ 449.761425] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:27:44 debian kernel: [ 453.234854] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:30:30 debian kernel: [ 618.271605] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:30:33 debian kernel: [ 621.788899] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:33:09 debian kernel: [ 776.826221] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:33:12 debian kernel: [ 780.299666] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar 4 16:36:48 debian kernel: [ 995.193863] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar 4 16:36:51 debian kernel: [ 998.707

I've attached a screenshot of the resource monitor during the 800% CPU utilization period.

Thanks again.
Attached Thumbnails
Click image for larger version

Name:	Screenshot from 2015-03-04 16:53:16.png
Views:	40
Size:	83.1 KB
ID:	17733  
 
Old 03-04-2015, 07:47 PM   #7
Miati
Member
 
Registered: Dec 2014
Distribution: Linux Mint 17.*
Posts: 326

Rep: Reputation: 106Reputation: 106
Hi - wrapping code output in code tags helps make reading it a lot easier
(You can find it represented by the # symbol in the toolbar)


top - 19:07:18 up 1 min, 2 users, load average: 4.48, 1.24, 0.43
Tasks: 175 total, 2 running, 173 sleeping, 0 stopped, 0 zombie
%Cpu(s): 12.8 us, 12.8 sy, 0.0 ni, 68.3 id, 5.7 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem: 16367004 total, 743496 used, 15623508 free, 28640 buffers
KiB Swap: 33342460 total, 0 used, 33342460 free, 375620 cached

vs.

Code:
top - 19:07:18 up 1 min, 2 users, load average: 4.48, 1.24, 0.43
Tasks: 175 total, 2 running, 173 sleeping, 0 stopped, 0 zombie
%Cpu(s): 12.8 us, 12.8 sy, 0.0 ni, 68.3 id, 5.7 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem: 16367004 total, 743496 used, 15623508 free, 28640 buffers
KiB Swap: 33342460 total, 0 used, 33342460 free, 375620 cached
 
1 members found this post helpful.
Old 03-04-2015, 09:29 PM   #8
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Original Poster
Rep: Reputation: Disabled
Found it - awesome, thanks for the pointer!
 
Old 03-04-2015, 09:42 PM   #9
ceyx
Member
 
Registered: May 2009
Location: Fort Langley BC
Distribution: Kubuntu,Free BSD,OSX,Windows
Posts: 342

Rep: Reputation: 59
All three of the logs you posted show the ethernet card bouncing up and down like crazy !

Quote:
I googled and found some old issues with the e1000e driver on the Intel 82579V LAN controller
Those problems aren't so old. Some were dated 2015. (The only reason I revert back to google is because you can select a time frame for a query easily.)

Do you have the Debian 'non-free' repositories selected ? Sometimes there are 'copyrighted' drivers available which are not included by default. There may be a non-free driver for this card.

See: https://wiki.debian.org/SourcesList
and look for non-free.
If you do enable the non-free repository, do an update immediately after.

If that doesn't do the trick, I suggest (just for trouble shooting purposes) disable the onboard lan and fire in whatever spare ethernet board you have around. This will very quickly confirm the problem and we can look for a solution based on that knowledge.

It sure looks like a card/driver issue.

Regards
 
Old 03-04-2015, 10:21 PM   #10
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Original Poster
Rep: Reputation: Disabled
I do not have the "non-free" sources selected; I recently discovered this option as I was investigating going from my version (7.1) to the latest (I think 7.6); I wasn't sure exactly where to add and/or replace with the non-free (there were 3 sections to the sources file if I recall) but I will spend some time with it in the morning and try it. Thanks.
 
Old 03-05-2015, 01:04 AM   #11
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,188

Rep: Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131
Quote:
Originally Posted by ybl84f1 View Post
steve@debian:/var/log$ sudo tail -15 kern.log
Mar 4 16:21:18 debian kernel: [ 67.813609] [<ffffffff81356a5e>] ? apic_timer_interrupt+0x6e/0x80
Mar 4 16:21:18 debian kernel: [ 67.813610] <EOI> [<ffffffff81358844>] ? ia32_syscall+0x14/0x60
Mar 4 16:21:18 debian kernel: [ 67.813614] ---[ end trace d4b06df8bb5b2d31 ]---
That looks a little bit serious - looks like the end of a kernel oops. Go back further in the log.

Bad driver is looking a real good candidate.
 
Old 03-05-2015, 07:28 PM   #12
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Original Poster
Rep: Reputation: Disabled
Quote:
That looks a little bit serious - looks like the end of a kernel oops. Go back further in the log.
After cold boot and two 800% CPU utilization cycles:

Code:
steve@debian:/var/log$ sudo tail -n 40 kern.log
Mar  5 20:11:24 debian kernel: [   87.788354] Hardware name:         
Mar  5 20:11:24 debian kernel: [   87.788355] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
Mar  5 20:11:24 debian kernel: [   87.788356] Modules linked in: parport_pc ppdev lp parport bnep rfcomm bluetooth rfkill binfmt_misc nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc loop snd_hda_codec_hdmi snd_hda_codec_realtek joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer snd evdev coretemp crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 aes_generic i915 cryptd drm_kms_helper i2c_i801 drm i2c_algo_bit acpi_cpufreq i2c_core mperf iTCO_wdt iTCO_vendor_support psmouse serio_raw pcspkr processor video button soundcore ext4 crc16 jbd2 mbcache usbhid hid sg sr_mod sd_mod cdrom crc_t10dif xhci_hcd fan thermal thermal_sys ahci libahci libata scsi_mod ehci_hcd e1000e usbcore usb_common [last unloaded: scsi_wait_scan]
Mar  5 20:11:24 debian kernel: [   87.788401] Pid: 4166, comm: izsobvefdj Not tainted 3.2.0-4-amd64 #1 Debian 3.2.65-1+deb7u2
Mar  5 20:11:24 debian kernel: [   87.788402] Call Trace:
Mar  5 20:11:24 debian kernel: [   87.788404]  <IRQ>  [<ffffffff81046d81>] ? warn_slowpath_common+0x78/0x8c
Mar  5 20:11:24 debian kernel: [   87.788411]  [<ffffffff81046e2d>] ? warn_slowpath_fmt+0x45/0x4a
Mar  5 20:11:24 debian kernel: [   87.788414]  [<ffffffff812a8995>] ? netif_tx_lock+0x40/0x75
Mar  5 20:11:24 debian kernel: [   87.788419]  [<ffffffff812a8b05>] ? dev_watchdog+0xf2/0x151
Mar  5 20:11:24 debian kernel: [   87.788422]  [<ffffffff810525a0>] ? run_timer_softirq+0x19a/0x261
Mar  5 20:11:24 debian kernel: [   87.788425]  [<ffffffff812a8a13>] ? netif_tx_unlock+0x49/0x49
Mar  5 20:11:24 debian kernel: [   87.788427]  [<ffffffff8104c416>] ? __do_softirq+0xb9/0x177
Mar  5 20:11:24 debian kernel: [   87.788431]  [<ffffffff813581ec>] ? call_softirq+0x1c/0x30
Mar  5 20:11:24 debian kernel: [   87.788432]  <EOI>  [<ffffffff8100fa91>] ? do_softirq+0x3c/0x7b
Mar  5 20:11:24 debian kernel: [   87.788437]  [<ffffffff8104c341>] ? _local_bh_enable_ip.isra.11+0x76/0x88
Mar  5 20:11:24 debian kernel: [   87.788440]  [<ffffffff812993b5>] ? __neigh_event_send+0x18c/0x198
Mar  5 20:11:24 debian kernel: [   87.788443]  [<ffffffff8129ac00>] ? neigh_resolve_output+0x4d/0x159
Mar  5 20:11:24 debian kernel: [   87.788446]  [<ffffffff812bb8f8>] ? ip_finish_output2+0x1ca/0x1f9
Mar  5 20:11:24 debian kernel: [   87.788449]  [<ffffffff812d61e8>] ? raw_sendmsg+0x603/0x7ca
Mar  5 20:11:24 debian kernel: [   87.788452]  [<ffffffff812ded7c>] ? inet_sendmsg+0x1d/0x6b
Mar  5 20:11:24 debian kernel: [   87.788455]  [<ffffffff81280851>] ? sock_sendmsg+0xc1/0xde
Mar  5 20:11:24 debian kernel: [   87.788459]  [<ffffffff81039adc>] ? finish_task_switch+0x88/0xb9
Mar  5 20:11:24 debian kernel: [   87.788461]  [<ffffffff8134fb09>] ? __schedule+0x5f9/0x610
Mar  5 20:11:24 debian kernel: [   87.788464]  [<ffffffff81036638>] ? should_resched+0x5/0x23
Mar  5 20:11:24 debian kernel: [   87.788466]  [<ffffffff8134fb64>] ? _cond_resched+0x7/0x1c
Mar  5 20:11:24 debian kernel: [   87.788469]  [<ffffffff8127f29f>] ? copy_from_user+0x18/0x30
Mar  5 20:11:24 debian kernel: [   87.788472]  [<ffffffff81282138>] ? sys_sendto+0xf7/0x137
Mar  5 20:11:24 debian kernel: [   87.788474]  [<ffffffff8100d039>] ? load_gs_index+0x7/0xa
Mar  5 20:11:24 debian kernel: [   87.788476]  [<ffffffff8100d039>] ? load_gs_index+0x7/0xa
Mar  5 20:11:24 debian kernel: [   87.788479]  [<ffffffff8100d71b>] ? __switch_to+0x1b0/0x265
Mar  5 20:11:24 debian kernel: [   87.788481]  [<ffffffff8134fb09>] ? __schedule+0x5f9/0x610
Mar  5 20:11:24 debian kernel: [   87.788483]  [<ffffffff81039adc>] ? finish_task_switch+0x88/0xb9
Mar  5 20:11:24 debian kernel: [   87.788485]  [<ffffffff8134fb09>] ? __schedule+0x5f9/0x610
Mar  5 20:11:24 debian kernel: [   87.788488]  [<ffffffff812a6a90>] ? compat_sys_socketcall+0x106/0x1ba
Mar  5 20:11:24 debian kernel: [   87.788491]  [<ffffffff813588a3>] ? ia32_do_call+0x13/0x13
Mar  5 20:11:24 debian kernel: [   87.788493] ---[ end trace 4a4b7ef85f8a2b2c ]---
Mar  5 20:11:24 debian kernel: [   87.788498] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar  5 20:11:27 debian kernel: [   91.249790] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Mar  5 20:14:28 debian kernel: [  271.263547] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
Mar  5 20:14:31 debian kernel: [  274.752939] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
and also:

Code:
steve@debian:/var/log$ dmesg | grep eth0
[    1.680386] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 4c:72:b9:43:e2:0e
[    1.680388] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[    1.680425] e1000e 0000:00:19.0: eth0: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF
[   10.443275] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.830107] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[   12.831167] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   23.508216] eth0: no IPv6 routers present
[   87.788355] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out
[   87.788498] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
[   91.249790] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  271.263547] e1000e 0000:00:19.0: eth0: Reset adapter unexpectedly
[  274.752939] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

During 800% CPU Utilization cycle:


Code:
steve@debian:/var/log$ ping -c 25 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 192.168.1.19 icmp_seq=15 Destination Host Unreachable
From 192.168.1.19 icmp_seq=16 Destination Host Unreachable
From 192.168.1.19 icmp_seq=17 Destination Host Unreachable
From 192.168.1.19 icmp_seq=18 Destination Host Unreachable
From 192.168.1.19 icmp_seq=19 Destination Host Unreachable
From 192.168.1.19 icmp_seq=20 Destination Host Unreachable
From 192.168.1.19 icmp_seq=21 Destination Host Unreachable
From 192.168.1.19 icmp_seq=22 Destination Host Unreachable
From 192.168.1.19 icmp_seq=23 Destination Host Unreachable

--- 8.8.8.8 ping statistics ---
25 packets transmitted, 0 received, +9 errors, 100% packet loss, time 30999ms
pipe 4

Quote:
Do you have the Debian 'non-free' repositories selected ? Sometimes there are 'copyrighted' drivers available which are not included by default. There may be a non-free driver for this card.
I'm going to try that tonight. Note however I did download the latest e1000e ethernet driver from Intel and installed it.

Thanks.
 
Old 03-05-2015, 07:58 PM   #13
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,188

Rep: Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131
Quote:
Originally Posted by ybl84f1 View Post
Note however I did download the latest e1000e ethernet driver from Intel and installed it.
Latest doesn't always mean greatest (hopefully it does, but ...), bugs get introduced occasionally.
You just missed the start of the messages - try this
Code:
sed -n '/^[[:space:]]*---/,/^[[:space:]]*----/p' kern.log
(if you get more than one listed, just post the first).
 
Old 03-05-2015, 08:10 PM   #14
ybl84f1
LQ Newbie
 
Registered: Mar 2015
Location: CT
Distribution: Debian
Posts: 19

Original Poster
Rep: Reputation: Disabled
I tried
Quote:
steve@debian:/var/log$ sudo sed -n '/^[[:space:]]*---/,/^[[:space:]]*----/p' kern.log
steve@debian:/var/log$
but just a blank. I tried to decipher & fix it but its a little past my level.

Last edited by ybl84f1; 03-05-2015 at 08:11 PM.
 
Old 03-05-2015, 08:46 PM   #15
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,188

Rep: Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131Reputation: 4131
My bad, trying to be too specific - try this
Code:
sed -n '/[[:space:]]*---/,/[[:space:]]*---/p' kern.log
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
100% CPU utilization linuxandtsm Linux - Newbie 6 05-31-2012 01:38 AM
CPU utilization on a busy traffic shaping router robel Linux - Networking 8 09-28-2010 03:25 AM
Dragging and dropping causes 100% cpu spike? DragonM15 Linux - Software 4 01-22-2009 12:37 PM
CPU 100 % Utilization rajaniyer123 Solaris / OpenSolaris 1 09-20-2007 11:31 AM
100 % CPU utilization Ganesh Kamat Linux - General 14 04-18-2003 01:34 PM

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

All times are GMT -5. The time now is 11:59 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