system freeze, log shows eth1 error

loserboy02 · 12-02-2008, 04:19 PM

hey guys, I'm in a bit of a bind.. well a big bind.

I installed ubuntu hardy recently and got everything rolling pretty good, but then I noticed some random lockups and slow boot times. I checked my logs and the only thing that seemed out of place was tons of lines:

Code:

Nov 25 12:22:24 mike-work kernel: [  383.343214] eth1: (82593) System Error occurred (0)

also some lines of this:

Code:

Nov 25 12:18:25 mike-work kernel: [  141.692480] 0000:05:07.0: tulip_stop_rxtx() failed (CSR5 0xfc06c012 CSR6 0xff970111)

So I'm assuming my problems are coming from that. It freezes so often now that I can't even get to a desktop, but when I was still able to the only thing I knew to do was go to the graphical network settings and disable eth1 to no avail. Next I tried going to the interfaces file in /etc and commented out eth1... but that didn't help either.

So I'm stuck, I posted on UF, but no answer.

If it makes a difference eth1 is supposedly referring to my onboard LAN card and I even tried turning it off in bios.

this is what ifconfig says about it

Code:

eth1      Link encap:Ethernet  HWaddr 00:4c:69:6e:75:79  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:12320629 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:19 Base address:0xa400

any tips would be appreciated... and a fix would be awesome

Thanks
Mike

x_terminat_or_3 · 12-02-2008, 04:56 PM

dropped:12320629

That's something that would concern me. But if it really is your network card, you can just turn off your networking. Not sure How to do this in Ubuntu, but it definitely *is* possible. Also you can try booting up in runlevel 1.

To do this, when you see your boot loader (Grub), press the key to edit the boot instructions, and add a 1 at the end of your kernel line.

When you're in single user mode, do a

ethttool eth0

And check if it detects a link, what speed it has auto-negotiated and so.

From your output, it also shows that you have NO IP address.

Possible causes I see:

* bad cable
* bad switch/hub/router
* bad network card

I have not come across a system, by the way, that did not allow me to de-activate the internal network card in the system's setup (aka BIOS). I got a faulty internal network card in one of my Dell machines, and I just turned it off in the `BIOS'.

loserboy02 · 12-02-2008, 05:43 PM

I apologize, I should have included more information, I left some stuff out because it felt weird making a duplicate of my UF post.

this computer is connected to a network through wireless, but it also has the onboard lan card and a pci lan card (not in use atm). While I would like to be able to use a wired connection, my main concern is just isolating the issue of lockups and stopping it.

I also thought it was strange that I was still getting errors after turning lan off in bios and I'm starting to wonder if I have mixed the info about eth0 and eth1, so I'm gonna pull out the pci lan card and see where that gets me.

on a side note, out of desperation I googled the MAC on eth1 "00:4c:69:6e:75:79" and came across people having issues when they had multiple lan cards and they were conflicting, thus giving one of them that MAC address.

Thanks for the help so far.

loserboy02 · 12-03-2008, 12:41 PM

well, after removing the pci lan card, I don't seem to be getting the errors in the log.

Let's see how long it lasts *cross fingers*