Watchdog timeout
-
The card was fully inserted and it didn't move (I admit that it is insecure without the bracket, unfortunatly I don't have a half bracket for it) after taking the picture ( and reinstalling the card) I still have the problem.
The card is not new so it is possible it developed a fault but since it manifested after an update, it was my first thought to blame the update :)Possible, though hardware problems manifest themselves after a reboot more than you'd probably think (or at least more than I used to think), we've seen others hit that a ton here.
What version did you upgrade from? Only see the version you're on now.
-
Not exactly sure but I think it was the build from 21.nov.
-
Ah ok, if you were already on 2.1 from any time this year, then nothing in that re driver has changed. That definitely makes suspect hardware more likely.
-
Ok, thanks.
-
Is there a list of pfsense/freebsd supported/compatible network interfaces?
-
Is there a list of pfsense/freebsd supported/compatible network interfaces?
See http://www.freebsd.org/releases/8.3R/hardware.html Change the 8.3 in the URL for the FreeBSD version in which you are interested.
-
Some quick googling on this shows a number of generic possible causes but one caught my eye, a possible comflict when used in an Asus motherboard. I assume that's what you're using from your other PCI device information? A workaround for that problem (a few years ago now) was to boot with acpi disabled. Not ideal but it would be an easy and zero cost test.
I would also try, but not at the same time, disabling MSI/MSI-X since that seems to cause problems with some cards. Add to /boot/loader.conf.local:
hw.re.msi_disable=1 hw.re.msix_disable=1Since that is also a zero cost test. ;)
It will however effect all three of your re interfaces.Steve
-
I am using e35m1-m pro. I have been using the current setup for aprox 1/2 year and so far I didn't have any issues. I'll try disabling msi/msi-x and/or acpi to see if it works. If I disable ACPI will it disable cpu frequency switching or is it not related?
I think I'll order this NIC - http://www.edimax.com/en/produce_detail.php?pd_id=315&pl1_id=2&pl2_id=9
Chipset seems to be supported and it's cheap. -
If you're buying another NIC I would always buy Intel. That card you linked to looks to be Realtek based?
Steve
-
From specs: Realtek RTL8168E Single Chip
Intel is sure to be better but I would guess a few times more expensive. The above card costs ~14€ and the router is for home use otherwise I would use better components. It does still get on my nerves if it doesn't work though ;D
-
Do you need Gigabit for home use? Even on WAN? If so, lucky you! ;D
You can pick up an Intel pro 100 card for less than €14 these days.For example: http://www.ebay.co.uk/itm/Intel-R-Network-Card-EXP19301CTBLK-/321044815334?pt=UK_Computing_Other_Computing_Networking&hash=item4abfc31de6
Steve
-
Well, I am a bit impatient when moving gigabytes of stuff between computers at home hence my need for gigabit lan. For wan I'll hopefully need gigabit one day when I get the fibre and 100/10 :)
And now the funny development regarding the problem, it dissapeared. I wasn't home much for the past few days so I couldn't try what was suggested, yday I downloaded ~7gb for test and no problems so far. I'll update pfsense to the latest version after work to see if it will make the problem reappear.
-
Replacing the NIC fixed the problem. Thanks for the help.
