pfSense Support Subscription

Author Topic: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic  (Read 10750 times)

0 Members and 1 Guest are viewing this topic.

Offline Topper727

  • Full Member
  • ***
  • Posts: 245
  • Karma: +25/-0
    • View Profile
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #60 on: January 05, 2015, 12:04:48 am »
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
« Last Edit: January 05, 2015, 03:09:41 am by Topper727 »
Dell 2950 g3 server
Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
Current: 2000 MHz, Max: 2667 MHz
8 CPUs: 2 package(s) x 4 core(s)
8152 MiB and 600meg 10k drive
Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11914
  • Karma: +468/-15
    • View Profile
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #61 on: January 05, 2015, 09:02:16 am »
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

Offline Topper727

  • Full Member
  • ***
  • Posts: 245
  • Karma: +25/-0
    • View Profile
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #62 on: January 14, 2015, 03:08:39 am »
Solved!


hint.agp.0.disabled=1
in loader.conf fixes the problem. :)
Dell 2950 g3 server
Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
Current: 2000 MHz, Max: 2667 MHz
8 CPUs: 2 package(s) x 4 core(s)
8152 MiB and 600meg 10k drive
Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11914
  • Karma: +468/-15
    • View Profile
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #63 on: January 14, 2015, 05:38:58 am »
Huh, how did you find that? Well done.  :)

Steve

Offline Topper727

  • Full Member
  • ***
  • Posts: 245
  • Karma: +25/-0
    • View Profile
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #64 on: January 14, 2015, 05:41:45 am »
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
« Last Edit: January 14, 2015, 06:01:36 am by Topper727 »
Dell 2950 g3 server
Intel(R) Xeon(R) CPU E5430 @ 2.66GHz
Current: 2000 MHz, Max: 2667 MHz
8 CPUs: 2 package(s) x 4 core(s)
8152 MiB and 600meg 10k drive
Pfsense 2.4 .. Hoping to get the phpvirtualbox going again.

Offline stephenw10

  • Administrator
  • Hero Member
  • *****
  • Posts: 11914
  • Karma: +468/-15
    • View Profile
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #65 on: January 14, 2015, 06:25:37 am »
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

gonzopancho

  • Guest
Re: pdsbm-ln2 1U server Lan Ports fail in RC canidate. Using Intel 82573 nic
« Reply #66 on: February 07, 2015, 10:39:13 pm »
Interestingly, this isn't a em driver bug (as upthread wanted to pursue), but rather a PCI bus issue.