pcnet32: eth0: transmit timed out, status 97fb, resetting - NIC card problem solution

I've encountered this problem before and I believe it  may affect other drivers (I could test but I don't have time).  This was happening on my custom Linux system with the pcnet32 driver.

pcnet32: eth0: transmit timed out, status 97fb, resetting (and some other kernel module tracing in dmesg)

Basically it means the card is connected (it shows connected in full duplex etc.. and recognized if the cable is disconnected too) but no packets can be sent or received.  I've read people say they think it's a bad card (I've actually threw some of these cards away in the past, thining the same thing!, others commented they believed the card was dead/bad or that it wasn't seated properly in their situation but I think it is likely the IOAPIC issue they found) but it's a driver/IOAPIC issue.

This was tested with a VBOX/Virtualbox machine but it seems to apply equally to physical machines (based on what I've read elsewhere).  If you have IOAPIC enabled, this driver won't work until it's disabled.

Now, the tricky thing is that with some computers and in VBOX, Centos 5 and possibly other Linux/OS won't boot successfully.

So here are the solutions for this issue:

1.) Disable IOAPIC in the motherboard (but some OS's won't boot without IOAPIC enabled).

2.) Specify the kernel option "pci=noapic" and it will work.

I hope this helps others out as I believe I've run into this issue unknowingly in many situations over the years.

One more comment is that on the very same system, I changed the NIC to an Intel and this issue did not happen with the Intel NIC (even with IOAPIC enabled), so this appears to mean that the pcnet32 driver is garbage/has an issue with IOAPIC on systems.


Tags:

pcnet, eth, transmit, timed, fb, resetting, nic, solutioni, ve, encountered, drivers, custom, linux, kernel, module, tracing, dmesg, duplex, etc, disconnected, packets, thining, commented, wasn, seated, ioapic, vbox, virtualbox, equally, elsewhere, enabled, disabled, tricky, centos, os, successfully, solutions, disable, motherboard, specify, quot, pci, noapic, unknowingly, intel,

Latest Articles

  • Cloned VM/Server/Computer in Linux won't boot and goes to initramfs busybox Solution
  • How To Add Windows 7 8 10 11 to GRUB Boot List Dual Booting
  • How to configure OpenDKIM on Linux with Postfix and setup bind zonefile
  • Debian Ubuntu 10/11/12 Linux how to get tftpd-hpa server setup tutorial
  • efibootmgr: option requires an argument -- 'd' efibootmgr version 15 grub-install.real: error: efibootmgr failed to register the boot entry: Operation not permitted.
  • Apache Error Won't start SSL Cert Issue Solution Unable to configure verify locations for client authentication SSL Library Error: 151441510 error:0906D066:PEM routines:PEM_read_bio:bad end line SSL Library Error: 185090057 error:0B084009:x509 certif
  • Linux Debian Mint Ubuntu Bridge br0 gets random IP
  • redis requirements
  • How to kill a docker swarm
  • docker swarm silly issues
  • isc-dhcp-server dhcpd how to get longer lease
  • nvidia cannot resume from sleep Comm: nvidia-sleep.sh Tainted: Linux Ubuntu Mint Debian
  • zfs and LUKS how to recover in Linux
  • [error] (28)No space left on device: Cannot create SSLMutex Apache Solution Linux CentOS Ubuntu Debian Mint
  • Save money on bandwidth by disabling reflective rpc queries in Linux CentOS RHEL Ubuntu Debian
  • How to access a disk with bad superblock Linux Ubuntu Debian Redhat CentOS ext3 ext4
  • ImageMagick error convert solution - convert-im6.q16: cache resources exhausted
  • PTY allocation request failed on channel 0 solution
  • docker error not supported as upperdir failed to start daemon: error initializing graphdriver: driver not supported
  • Migrated Linux Ubuntu Mint not starting services due to broken /var/run and dbus - Failed to connect to bus: No such file or directory solution