LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 04-18-2008, 01:31 AM   #1
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 924

Rep: Reputation: 43
Hardware or software problem ?


Distro: Slackware 9.1.0
Kernel: 2.4.22 (recompiled)
2x NIC 8139too (eth0 = Internet eth1 = LAN)
Destination: NAT server with DHCPd on eth1

The problem appeared yesterday. I have lost connection to Internet as well as users from LAN were not able to get local IP form DHCP (DHCPd listen on eth1). Users were able to get IP for 2-3 sec then lose it.

Finally I have solved problem by changing one of NICs and putting another to other PCI slot. Also found that one of users were connected with some PLANNET router - disconnected him.

Here is what I fouind in syslog and what I still dont know what does it mean:
Code:
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 19 times
Apr 17 22:44:22 NATsrv kernel: eth0: Too much work at interrupt, IntrStatus=0x8000.
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 2290.
Apr 17 22:44:22 NATsrv last message repeated 13 times
Apr 17 22:44:22 NATsrv kernel: eth0: PCI Bus error 0290.
Apr 17 22:44:50 NATsrv dhcpd: Abandoning IP address 192.168.1.126: pinged before offer
Apr 17 22:45:33 NATsrv dhcpd: Abandoning IP address 192.168.1.144: declined.
Apr 17 22:45:46 NATsrv dhcpd: Abandoning IP address 192.168.1.114: declined.
Apr 17 22:45:59 NATsrv dhcpd: Abandoning IP address 192.168.1.112: declined.
Apr 17 22:46:10 NATsrv dhcpd: Abandoning IP address 192.168.1.108: declined.
Apr 17 22:46:21 NATsrv dhcpd: Abandoning IP address 192.168.1.107: declined.
Apr 17 22:46:33 NATsrv dhcpd: Abandoning IP address 192.168.1.106: declined.
Apr 17 22:46:46 NATsrv dhcpd: Abandoning IP address 192.168.1.105: declined.
Apr 17 22:46:59 NATsrv dhcpd: Abandoning IP address 192.168.1.104: declined.
Apr 17 22:47:10 NATsrv dhcpd: Abandoning IP address 192.168.1.99: declined.
Apr 17 22:47:23 NATsrv dhcpd: Abandoning IP address 192.168.1.98: declined.
Apr 17 22:47:36 NATsrv dhcpd: Abandoning IP address 192.168.1.97: declined.
Apr 17 22:47:49 NATsrv dhcpd: Abandoning IP address 192.168.1.96: declined.
Apr 17 22:48:00 NATsrv dhcpd: Abandoning IP address 192.168.1.95: declined.
Apr 17 22:48:13 NATsrv dhcpd: Abandoning IP address 192.168.1.94: declined.
Apr 17 22:48:26 NATsrv dhcpd: Abandoning IP address 192.168.1.93: declined.
Apr 17 22:48:39 NATsrv dhcpd: Abandoning IP address 192.168.1.91: declined.
Apr 17 22:48:42 NATsrv dhcpd: Abandoning IP address 192.168.1.90: declined.
Apr 17 22:48:59 NATsrv dhcpd: Abandoning IP address 192.168.1.89: declined.
Apr 17 22:49:10 NATsrv dhcpd: Abandoning IP address 192.168.1.88: declined.
Apr 17 22:49:23 NATsrv dhcpd: Abandoning IP address 192.168.1.87: declined.
Apr 17 22:49:36 NATsrv dhcpd: Abandoning IP address 192.168.1.86: declined.
Apr 17 22:49:49 NATsrv dhcpd: Abandoning IP address 192.168.1.85: declined.
Apr 17 22:50:00 NATsrv dhcpd: Abandoning IP address 192.168.1.84: declined.
Apr 17 22:50:13 NATsrv dhcpd: Abandoning IP address 192.168.1.83: declined.
Apr 17 22:50:26 NATsrv dhcpd: Abandoning IP address 192.168.1.82: declined.
Apr 17 22:50:40 NATsrv dhcpd: Abandoning IP address 192.168.1.81: declined.
Apr 17 22:54:25 NATsrv dhcpd: Abandoning IP address 192.168.1.80: declined.
Apr 17 22:54:36 NATsrv dhcpd: Abandoning IP address 192.168.1.79: declined.
Apr 17 22:54:49 NATsrv dhcpd: Abandoning IP address 192.168.1.78: declined.
Apr 17 22:55:02 NATsrv dhcpd: Abandoning IP address 192.168.1.77: declined.
Apr 17 22:55:15 NATsrv dhcpd: Abandoning IP address 192.168.1.76: declined.
Apr 17 22:55:26 NATsrv dhcpd: Abandoning IP address 192.168.1.75: declined.
Apr 17 22:55:37 NATsrv dhcpd: Abandoning IP address 192.168.1.74: declined.
Apr 17 22:55:51 NATsrv dhcpd: Abandoning IP address 192.168.1.73: declined.
Apr 17 22:56:04 NATsrv dhcpd: Abandoning IP address 192.168.1.72: declined.
Apr 17 22:56:15 NATsrv dhcpd: Abandoning IP address 192.168.1.71: declined.
Just in case here is my DHCPd conf. Wonder would it be problem that someone have another DHCP server on LAN - if Im right then how to make my server to be more authoritative ?

Code:
ddns-update-style none;
authoritative;

    subnet 192.168.1.0 netmask 255.255.255.0
  {
    default-lease-time 72000;
    max-lease-time 144000;
    option subnet-mask 255.255.255.0;
    option broadcast-address 192.168.1.255;
    option routers 192.168.1.1;
    option domain-name-servers 217.98.63.164, 194.204.159.1;
    option domain-name "local";
    range 192.168.1.21 192.168.1.254;
  }

Last edited by czezz; 04-18-2008 at 01:51 AM.
 
Old 04-18-2008, 08:24 AM   #2
MS3FGX
LQ Guru
 
Registered: Jan 2004
Location: NJ, USA
Distribution: Slackware, Debian
Posts: 5,852

Rep: Reputation: 361Reputation: 361Reputation: 361Reputation: 361
Well the kernel errors would indicate, and changing the hardware would confirm, that there was a problem with that particular NIC (or perhaps that PCI slot itself, since you changed slots and cards).
 
Old 04-18-2008, 09:33 AM   #3
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 924

Original Poster
Rep: Reputation: 43
well... im not 100% sure because after I changed slots and one of NIC errors still appeared.
It stopped after I disconnected that router I mentioned above.
That is why Im thinking also about DHCP server.
 
Old 04-18-2008, 11:10 AM   #4
TB0ne
LQ Guru
 
Registered: Jul 2003
Location: Birmingham, Alabama
Distribution: SuSE, RedHat, Slack,CentOS
Posts: 26,622

Rep: Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963Reputation: 7963
Quote:
Originally Posted by czezz View Post
well... im not 100% sure because after I changed slots and one of NIC errors still appeared.
It stopped after I disconnected that router I mentioned above.
That is why Im thinking also about DHCP server.
Or that router had a flaky port, or wasn't configured right, since the errors went away after you disconnected that router.
 
  


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
Burning cd trouble: hardware problem or software problem argt Linux - Hardware 2 04-20-2005 05:27 PM
Is the problem exactly hardware or software related? vmuralikrishnan Linux - Software 1 03-24-2005 03:39 AM
Internet and LAN access is unstable-is this a hardware problem or a software problem? soren625 Linux - Networking 1 06-07-2004 06:43 AM
software/hardware problem ? astrobase Linux - General 4 11-04-2003 07:42 AM
Opinion Wanted: Hardware or Software problem?? Manuel-H Linux - General 3 07-18-2003 08:58 AM

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

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