Pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
-
Indeed that looks like the correct, so it's not that. :( But at least that's one thing eliminated. :)
Really hard to know what the exact cause of this is at this point. I would have to guess that it's some ACPI interaction that was introduced by the upgrade from FreeBSD 8.3 to 10.1. Assuming that I would try using the various ACPI debug options decsribed here: https://www.freebsd.org/cgi/man.cgi?query=acpi&sektion=4
That is likely to be a long and tedious process that may not in the end actually produce any useful results. :-\Steve
-
I wish some how some way it would start working.
-
This is not a specific pfSense problem. You may have more luck asking for help on the FreeBSD forums. Perhaps someone there has worked around this issue before.
Steve
-
Yes, I found it was since I tried freebsd 10.1 but I did post in forum and nothing back yet.. seems they not as active as pfsense is.. glad you are. I wish I knew way to resinstall drivers
-
https://svnweb.freebsd.org/base?view=revision&revision=269196
This is where they updated the EM driver .. talks about shared code in the update.. Also submitted a bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501
Now the question is. If they fix it in freebsd10.1 will it get into Pfsense and how fast?
Is there a way to downgrade to the driver used in 8.1 till they fix maybe?
I got the older driver but MAKE and PKG_Add are not part of pfense.. PKG_add use to be.. really starting to hate PFSENSE
http://doc.pfsense.org/index.php/Add_Packages_HOWTO_Add_Packages_from_a_shell
-
Drivers are not FreeBSD packages that you can add.
There are no build tools at all in pfSense, including them would only be a security risk.
FreeBSD 10 moved to the pkgng package system.
The driver subsystems changed a lot between 8.3 and 10.1, i'd be surprised if you're able to compile an 8.3 driver against 10.1 source.
It's my belief that it's not the driver anyway but some resource management component.You might try to find exactly which FreeBSD version introduced the issue. Looking at the other bug reports we've referenced in this thread it may have been 9.0 or 9.1.
Steve
-
Solved!
hint.agp.0.disabled=1
in loader.conf fixes the problem. :) -
Huh, how did you find that? Well done. :)
Steve
-
I found by submitting a bug to Intel and someone gave me that to try.. that fixed it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196501
-
Ah. Importantly that person was John Baldwin. I'm not going to feel bad not knowing something he does. ;)
Anyway I'm happy a workaround exists and that key FreeBSD people are aware of it.Steve
-
Interestingly, this isn't a em driver bug (as upthread wanted to pursue), but rather a PCI bus issue.
