Computer freaks out, network dies.

[Dillius]

So like the title says... all of a sudden my computer freaked out. It was having hard drive errors and etc until finally i restarted it again and it restored itself with journaling.

Ever since, my network has no been working correctly.

I'm using forcedeth to run my mobo's built in Nforce gigabit ethernet. It's been working up until now just fine.

Now, if i try to connect to my router with DHCP, it just sticks and nothing ever happens. If I try to manually set everything, the following error occurs:

Bringing eth1 up (192.168.0.2)...
SIOCSIFADDR: No such device
eth1: unknown interface: No such device
SIOCSIFBRADDR: No such device
eth1: unknown interface: No such device
SCIOCSIFNETMASK: No such device

Followed by a number of errors that are from services that can not be started without internet.

Has anyone encountered this problem before?

[Dillius]

Upon doing some work I was able to get it working a little better. Now, strangely, it appears as if the interface eth0 is up, and it is receiving some kinds of packets.

However, ifconfig shows that all sent packets are being dropped. no bytes have been sent, however some have been received.

[Dillius]

Ok, so after working far into the night all i've accomplished is that I know from dmesg that the module is loading and being assigned eth0, and the other onboard (which hasn't worked in a while, r8169) is also finding it's module and loading properly.

I've been making them both try to start up with set IP addresses and the gateway set, however it appears that the gateway settings may be the problem.

Whenever I start it up and type "route" nothing ever happens. it loads the titles of each column, but never actually displays the routing information.

EDIT: I also believe I know how all of this came about.

I have 2 linux computers behind a router. The desktop that is having the problems and an old laptop I use for hosting a website. I use this website as a fileserver for my friends. Well the files are actually on the Desktop, so I have just been using samba to mount them on the laptop and have them accessed that way.

Well, when the problem occured, I was restarting the desktop but the laptop was still on. And I believe one of my friends was trying to download data from the site while the computer with the actual data was being restarted.

As strange as this seems, it would explain why most of the hard drive corruption that had to be fixed occured on the hard drive and partition that the files he was accessing were on.

[Dillius]

Man I hate to keep replaying over and over to my own post, but I've been working on this problem and researching constantly so I keep finding new things.

I've got it back basically to the stage it was at in my 2nd post. receiving packets but dropping all sent packets.

dmesg shows that:

NETDEV WATCHDOG: eth0: transmit timed out
nv_stop_tx: TransmitterStatus remained busy<7>eth0: tx_timeout: dead entries!

so after researching the forums a bit all I could really find were issues in which you needed to add kernel load options such as acpi=off, pci=noacpi, noapic.

Well, i've always had apci=off, and always needed it before before this thing freaked out. Adding either pci=noapci, or noapic simply makes it so that I do not even receive packets or drop transmitted ones. The entire ethernet line appears dead if either of those are added.

EDIT: also, trying to ping anything causes:

ping: sendmsg: No buffer space available

[astrohm]

I might be having the same problem:

NETDEV WATCHDOG: eth1: transmit timed out
nv_stop_tx: TransmitterStatus remained busy<7>eth1: tx_timeout: dead entries!

Powering the computer off completely (so the lights on the ethernet port turn off) and rebooting seems to temporarily fix it.

However, it has come back twice, once a day for the last couple of days. I haven't been able to pin down if I was always doing the same thing when it came back.

What really concerns me is that the light on the ethernet port that is always green is now red, which makes me wonder if, my problem anyway might, be hardware and not software.

Do you see this too?

Also you mentioned that the NIC you were having this problem on was your mobos Nforce gigabit, what mobo do you have exactly? I have a MSI K8N Neo Platinum with nForce3.

I'd like to make sure that it isn't hardware

[Deathwing00]

Moved to Duplicate Threads in favor of http://forums.gentoo.org/viewtopic-t-320241.html