OpenBSD 5.0 upgrade: em interface status "no carrier"

2011-11-17 Thread Sam Vaughan
Hi,

After upgrading from OpenBSD 4.9 to OpenBSD 5.0, the "Intel 82579LM" and
"Intel PRO/1000 MT (82574L)" devices on one of my servers no longer come up.
The ifconfig output simply shows "status: no carrier".  Without network access
I can't copy and paste an entire dmesg, so here's some cherry-picked info:

# uname -mrsv
OpenBSD 5.0 GENERIC.MP#63 amd64
# dmesg | head -2
OpenBSD 5.0 (GENERIC.MP) #63: Wed Aug 17 10:14:30 MDT 2011
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
# dmesg | grep em[01]
em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x05: msi, address
00:25:90:52:b2:c1
em1 at pci2 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: msi,
address 00:25:90:52:b2:c0
# ifconfig em0
em0: flags=8843 mtu 1500
lladdr 00:25:90:52:b2:c1
priority: 0
groups: egress
media: Ethernet autoselect (none)
status: no carrier
inet 10.0.2.7 netmask 0xff00 broadcast 10.255.255.255
inet6 fe80::225:90ff:fe52:b2c1%em0 prefixlen 64 scopeid 0x1

Running ifconfig down/up, manually choosing media types from the supported
list and rebooting all have no effect.  I've tried em1 as well without
success.  The connected switch is a Netgear GS116E and I've tried different
cables and also a Netgear GS105E.  I don't think it's the cable or switch
though because rebooting back into 4.9 immediately brings the interface back
to life.

This is the hardware I'm having the problem on:

http://www.supermicro.com/products/motherboard/Xeon/C202_C204/X9SCL-F.cfm

I'm wondering if it's related to OpenBSD 5.0's new MSI interrupt code?

Below is the dmesg when it's all up and working on 4.9.

Is there anything I can try to narrow the problem down a bit further?

Regards,

Sam


OpenBSD 4.9 (GENERIC.MP) #819: Wed Mar  2 06:57:49 MST 2011
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 3210297344 (3061MB)
avail mem = 3110817792 (2966MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xeadc0 (105 entries)
bios0: vendor American Megatrends Inc. version "4.6.4" date 06/30/2011
bios0: Supermicro X9SCL/X9SCM
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP APIC SSDT MCFG HPET SPMI SPCR DMAR EINJ ERST HEST
BERT
acpi0: wakeup devices PS2K(S1) PS2M(S1) UAR1(S4) UAR2(S4) BR20(S1) EUSB(S4)
USBE(S4) PEX0(S4) PEX4(S4) PEX6(S4) GBE_(S4) P0P1(S4) P0P2(S4) P0P3(S4)
P0P4(S4) SLPB(S0) PWRB(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.48 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 99MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.01 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG
cpu1: 256KB 64b/line 8-way L2 cache
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.02 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG
cpu2: 256KB 64b/line 8-way L2 cache
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Xeon(R) CPU E31220L @ 2.20GHz, 2195.01 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,PCLMUL,MWAIT,DS-CPL,VMX,SMX,ES
T,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,POPCNT,XSAVE,AVX,NXE,LONG
cpu3: 256KB 64b/line 8-way L2 cache
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (BR20)
acpiprt2 at acpi0: bus 1 (PEX0)
acpiprt3 at acpi0: bus 2 (PEX4)
acpiprt4 at acpi0: bus -1 (PEX6)
acpiprt5 at acpi0: bus -1 (P0P1)
acpiprt6 at acpi0: bus -1 (P0P2)
acpiprt7 at acpi0: bus -1 (P0P3)
acpiprt8 at acpi0: bus -1 (P0P4)
acpicpu0 at acpi0: C3, C1, PSS
acpicpu1 at acpi0: C3, C1, PSS
acpicpu2 at acpi0: C3, C1, PSS
acpicpu3 at acpi0: C3, C1, PSS
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
ipmi at mainbus0 not configured
cpu0: unknown i686 model 0x2a, can't get bus clock
cpu0: Enhanced SpeedStep 2195 MHz: speeds: 2201, 2200, 2100, 2000, 1900, 1800,
1700, 1600 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 vendor "Intel", unk

Re: OpenBSD 5.0 upgrade: em interface status "no carrier"

2011-11-17 Thread Sam Vaughan
On 18/11/2011, at 12:59 PM, Sam Vaughan wrote:

> Hi,
>
> After upgrading from OpenBSD 4.9 to OpenBSD 5.0, the "Intel 82579LM" and
"Intel PRO/1000 MT (82574L)" devices on one of my servers no longer come up.



If I'd bothered to compare those two dmesg outputs more closely I'd have
noticed that OpenBSD 5.0 is simply enumerating the two interfaces in the
opposite order.  What was em0 in 4.9 is now em1 in 5.0 and vice versa.  Simply
swapping the cable to the other port and _not_ moving the settings in ifconfig
to em1 fixes the problem.  Sorry for the noise.

By the way, is there any reason why I should prefer the 82579LM to the 82574L
or vice versa?

Thanks,

Sam



Re: OpenBSD 5.0 upgrade: em interface status "no carrier"

2011-11-20 Thread Mike Belopuhov
On Fri, Nov 18, 2011 at 4:01 AM, Sam Vaughan 
wrote:
> On 18/11/2011, at 12:59 PM, Sam Vaughan wrote:
>
>> Hi,
>>
>> After upgrading from OpenBSD 4.9 to OpenBSD 5.0, the "Intel 82579LM" and
> "Intel PRO/1000 MT (82574L)" devices on one of my servers no longer come
up.
>
> 
>
> If I'd bothered to compare those two dmesg outputs more closely I'd have
> noticed that OpenBSD 5.0 is simply enumerating the two interfaces in the
> opposite order.  What was em0 in 4.9 is now em1 in 5.0 and vice versa.
 Simply
> swapping the cable to the other port and _not_ moving the settings in
ifconfig
> to em1 fixes the problem.  Sorry for the noise.
>
> By the way, is there any reason why I should prefer the 82579LM to the
82574L
> or vice versa?
>
> Thanks,
>
> Sam
>
>

there's no reason you should consider either of them for any serious
task as both of them are desktop low performance versions.

82576EB is known to be a very good one for routing workloads.

http://www.intel.com/content/dam/doc/brochure/ethernet-controllers-phys-broch
ure.pdf