Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-07-01 Thread Frédéric URBAN

Le 29/06/2010 20:46, Fridiric URBAN a icrit :
4.7, but it only fix the hardware initialization. I've got all 
interface available in ifconfig and known by the kernel but thoses who 
useally don't get initialized doesn't work when you plug the cable, 
there must be a similar problem when bringing up the link.


The problem, I fixed on hw_init was simply a failing mutex (in 
if_em_hw.c) . When interrogating the PHY registers at the end of 
em_setup_copper_link(), if the PHY is busy, the function 
em_read_phy_reg() return an error (E1000_ERR_PHY) which is brought on 
the function stack and lead to hardware initialization failure... So i 
took the code from e1000_82575.c of the freebsd project and this is 
over. Now this is uglyly coded, it need to be rewritten to feet with 
the OpenBSD em(4) philosophy which is totaly different from freebsd 
em/igb code. I will be busy at work but i'll try to keep on working on 
that during my free time. If somebody wants to help/go on, mail me ;)


PS: I'll have fiber card soon, we'll see they have the same problem.

Fred

Ok it's confirmed, the PHY used on the card has a strange behavior. Each 
time that the function em_read_phy_reg() is used there is a  risk of 
failure, The PHY is more often busy than useall. I added some debug 
information in the code which show the return code of em_read_phy_reg() 
and sometimes E1000_ERR_PHY is returned.This function is called very 
very often (which is obvious). When it happends the interface won't work.


I partially fixed the hardware initialization by adding a timed retry 
when the PHY is busy (in em_setup_copper_link()), but there is still 
lots of occurrence of em_read_phy_reg() that need to be modified (ie: I 
already had error in em_copper_link_autoneg()) and it's the first time I 
put my finger inside a device driver :E So maybe there is a better way 
to fix it ! We need a kernel guru !!! :D


Fred

Btw, I took the idea of the timed retry of em_read_phy_reg()  from 
FreeBSD igb driver, in their equivalent of em_setup_copper_link(), they 
use it.




Le 29/06/2010 18:29, w...@wootsie.com a icrit :

4.6 or 4.7 code?

-Bill

On Tue, Jun 29, 2010 at 10:48 AM, Fridiric URBAN
frederic.ur...@ircad.u-strasbg.fr  wrote:

Le 29/06/2010 14:16, uhu a C)crit :

FrC)dC)ric URBANfrederic.urbanat   ircad.u-strasbg.fr   writes:



.
I didn't find any bug report yet on the OpenBSD official Website, 
this

is a different case than the one  reported here:
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301 



Can somebody report it with a dmesg on 4.7 ?




I reported it some days ago, got an error message, but the bug report
seems to be here since 07/23:

http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6408

Uwe



Hello again,

Maybe i got a fix, I modified some lines of code inside the driver... I
booted 4x times without nics that has failed... But i'll try it more 
before

saying victory ;)

Fred




Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-29 Thread uhu
FrC)dC)ric URBAN frederic.urban at ircad.u-strasbg.fr writes:

 
 .
 I didn't find any bug report yet on the OpenBSD official Website, this 
 is a different case than the one  reported here:
 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301 
 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301
 
 Can somebody report it with a dmesg on 4.7 ?
 
 


I reported it some days ago, got an error message, but the bug report
seems to be here since 07/23:

http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6408

Uwe



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-29 Thread Frédéric URBAN

Le 29/06/2010 14:16, uhu a C)crit :

FrC)dC)ric URBANfrederic.urbanat  ircad.u-strasbg.fr  writes:

   

.
I didn't find any bug report yet on the OpenBSD official Website, this
is a different case than the one  reported here:
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301

Can somebody report it with a dmesg on 4.7 ?


 


I reported it some days ago, got an error message, but the bug report
seems to be here since 07/23:

http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6408

Uwe

   

Hello again,

Maybe i got a fix, I modified some lines of code inside the driver... I 
booted 4x times without nics that has failed... But i'll try it more 
before saying victory ;)


Fred



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-29 Thread wrh
4.6 or 4.7 code?

-Bill

On Tue, Jun 29, 2010 at 10:48 AM, Fridiric URBAN
frederic.ur...@ircad.u-strasbg.fr wrote:
 Le 29/06/2010 14:16, uhu a C)crit :

 FrC)dC)ric URBANfrederic.urbanat  ircad.u-strasbg.fr  writes:



 .
 I didn't find any bug report yet on the OpenBSD official Website, this
 is a different case than the one  reported here:
 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301
 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301

 Can somebody report it with a dmesg on 4.7 ?




 I reported it some days ago, got an error message, but the bug report
 seems to be here since 07/23:

 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6408

 Uwe



 Hello again,

 Maybe i got a fix, I modified some lines of code inside the driver... I
 booted 4x times without nics that has failed... But i'll try it more before
 saying victory ;)

 Fred



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-29 Thread Frédéric URBAN
4.7, but it only fix the hardware initialization. I've got all interface 
available in ifconfig and known by the kernel but thoses who useally 
don't get initialized doesn't work when you plug the cable, there must 
be a similar problem when bringing up the link.


The problem, I fixed on hw_init was simply a failing mutex (in 
if_em_hw.c) . When interrogating the PHY registers at the end of 
em_setup_copper_link(), if the PHY is busy, the function 
em_read_phy_reg() return an error (E1000_ERR_PHY) which is brought on 
the function stack and lead to hardware initialization failure... So i 
took the code from e1000_82575.c of the freebsd project and this is 
over. Now this is uglyly coded, it need to be rewritten to feet with the 
OpenBSD em(4) philosophy which is totaly different from freebsd em/igb 
code. I will be busy at work but i'll try to keep on working on that 
during my free time. If somebody wants to help/go on, mail me ;)


PS: I'll have fiber card soon, we'll see they have the same problem.

Fred

Le 29/06/2010 18:29, w...@wootsie.com a icrit :

4.6 or 4.7 code?

-Bill

On Tue, Jun 29, 2010 at 10:48 AM, Fridiric URBAN
frederic.ur...@ircad.u-strasbg.fr  wrote:
   

Le 29/06/2010 14:16, uhu a C)crit :
 

FrC)dC)ric URBANfrederic.urbanat   ircad.u-strasbg.fr   writes:


   

.
I didn't find any bug report yet on the OpenBSD official Website, this
is a different case than the one  reported here:
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301

Can somebody report it with a dmesg on 4.7 ?



 

I reported it some days ago, got an error message, but the bug report
seems to be here since 07/23:

http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6408

Uwe


   

Hello again,

Maybe i got a fix, I modified some lines of code inside the driver... I
booted 4x times without nics that has failed... But i'll try it more before
saying victory ;)

Fred




Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-28 Thread wrh
sendbug submitted with 4.7-current.

http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6411


-Bill

On Thu, Jun 24, 2010 at 4:14 AM, Fridiric URBAN
frederic.ur...@ircad.u-strasbg.fr wrote:
 Le 23/06/2010 12:08, rh...@hushmail.com a C)crit :

 Thank you for the messages regarding /var/run/dmesg.boot. I bow
 to your combined superior wisdoms !

 Hope this is of assistance :   ;-)

 OpenBSD 4.7 (GENERIC.MP) #0: Sat Jan 10 10:10:10 GMT 2010
 r...@example.com:/usr/src/sys/arch/i386/compile/GENERIC.MP
 cpu0: Intel(R) Xeon(R) CPU E5502 @ 1.87GHz (GenuineIntel 686-
 class) 1.87 GHz
 cpu0:
 ...
 em0 at pci3 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev
 0x06: apic 0 int 6 (irq 7), address 00:15:17:00:00:00
 em1 at pci3 dev 0 function 1 Intel PRO/1000 PT (82571EB) rev
 0x06: apic 0 int 13 (irq 11), address 00:15:17:00:00:01
 ...

 This is working well in your case because you are using Intel Pro Server PT
 cards that is running 82571EB Chip which is supported since a long time
now.
 We've some of thoses in production here.
 The problem happend on:
 - Intel Pro Server ET Dual Port Card.
 - Intel Pro Server ET Quad Port Card.
 - All on-motherboard NIC which are based on Intel 82576EB,
 It remains untested on:
 - Intel Pro Server EF Dual Port Card.
 - Intel Pro Server EF Quad Port Card.
  I'll be able to test the Dual Port EF Card in a few days but I already
 think it will fail since both are based on 82576EB...

 I didn't find any bug report yet on the OpenBSD official Website, this is a
 different case than the one  reported here:
 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301
 http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301

 Can somebody report it with a dmesg on 4.7 ?



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-24 Thread Frédéric URBAN

Le 23/06/2010 12:08, rh...@hushmail.com a C)crit :

Thank you for the messages regarding /var/run/dmesg.boot. I bow
to your combined superior wisdoms !

Hope this is of assistance :   ;-)

OpenBSD 4.7 (GENERIC.MP) #0: Sat Jan 10 10:10:10 GMT 2010
 r...@example.com:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(R) CPU E5502 @ 1.87GHz (GenuineIntel 686-
class) 1.87 GHz
cpu0:
...
em0 at pci3 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev
0x06: apic 0 int 6 (irq 7), address 00:15:17:00:00:00
em1 at pci3 dev 0 function 1 Intel PRO/1000 PT (82571EB) rev
0x06: apic 0 int 13 (irq 11), address 00:15:17:00:00:01
...
This is working well in your case because you are using Intel Pro Server 
PT cards that is running 82571EB Chip which is supported since a long 
time now. We've some of thoses in production here.

The problem happend on:
- Intel Pro Server ET Dual Port Card.
- Intel Pro Server ET Quad Port Card.
- All on-motherboard NIC which are based on Intel 82576EB,
It remains untested on:
- Intel Pro Server EF Dual Port Card.
- Intel Pro Server EF Quad Port Card.
 I'll be able to test the Dual Port EF Card in a few days but I already 
think it will fail since both are based on 82576EB...


I didn't find any bug report yet on the OpenBSD official Website, this 
is a different case than the one  reported here:
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301 
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301


Can somebody report it with a dmesg on 4.7 ?



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-23 Thread rhsv6
 Somebody knows if this problem only happends on Intel 
X58/5500/5600 
chipsets ? Did somebody tried the i386 version of OpenBSD 4.7 ?


I am running 4.7 i386 release (+ errata patches) on a Intel 5500 
platform with the following Intel NIC.  Seems to be behaving itself 
so far.  

(Sorry no dmesg, it got overwritten by system events, so you'll 
have to wait until I get a chance to reboot).

 10:0:0: Intel PRO/1000 PT (82571EB)
0x: Vendor ID: 8086 Product ID: 105e
0x0004: Command: 0047 Status ID: 0010
0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 06
0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache 
Line Size: 10
0x0010: BAR mem 32bit addr: 0xfbfe
0x0014: BAR mem 32bit addr: 0xfbfc
0x0018: BAR io addr: 0x4000
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 8086 Product ID: 115e
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
0x00c8: Capability 0x01: Power Management
0x00d0: Capability 0x05: Message Signaled Interrupts (MSI)
0x00e0: Capability 0x10: PCI Express
 10:0:1: Intel PRO/1000 PT (82571EB)
0x: Vendor ID: 8086 Product ID: 105e
0x0004: Command: 0047 Status ID: 0010
0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 06
0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache 
Line Size: 10
0x0010: BAR mem 32bit addr: 0xfbfa
0x0014: BAR mem 32bit addr: 0xfbf8
0x0018: BAR io addr: 0x4020
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 8086 Product ID: 115e
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 02 Line: 0b Min Gnt: 00 Max Lat: 00
0x00c8: Capability 0x01: Power Management
0x00d0: Capability 0x05: Message Signaled Interrupts (MSI)
0x00e0: Capability 0x10: PCI Express



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-23 Thread Otto Moerbeek
On Wed, Jun 23, 2010 at 10:02:14AM +0100, rh...@hushmail.com wrote:

  Somebody knows if this problem only happends on Intel 
 X58/5500/5600 
 chipsets ? Did somebody tried the i386 version of OpenBSD 4.7 ?
 
 
 I am running 4.7 i386 release (+ errata patches) on a Intel 5500 
 platform with the following Intel NIC.  Seems to be behaving itself 
 so far.  
 
 (Sorry no dmesg, it got overwritten by system events, so you'll 
 have to wait until I get a chance to reboot).

There's always /var/run/dmesg.boot

-Otto



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-23 Thread rhsv6
Thank you for the messages regarding /var/run/dmesg.boot. I bow 
to your combined superior wisdoms !

Hope this is of assistance :   ;-)

OpenBSD 4.7 (GENERIC.MP) #0: Sat Jan 10 10:10:10 GMT 2010
r...@example.com:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Xeon(R) CPU E5502 @ 1.87GHz (GenuineIntel 686-
class) 1.87 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PS
E36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-
CPL,VMX,EST,TM2,CX16,xTPR
real mem  = 3881558016 (3701MB)
avail mem = 3779342336 (3604MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 
0xf, SMBIOS rev. 2.6 @ 0xe77fe000 (134 entries)
bios0: vendor HP version W07 date 07/24/2009
bios0: HP ProLiant DL320 G6
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP SPCR MCFG HPET  SPMI ERST APIC SRAT 
 BERT HEST DMAR SSDT SSDT SSDT SSDT
acpi0: wakeup devices PCI0(S4)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 16 (boot processor)
cpu0: unknown i686 model 0x1a, can't get bus clock (0x0)
cpu0: apic clock running at 133MHz
cpu1 at mainbus0: apid 20 (application processor)
cpu1: Intel(R) Xeon(R) CPU E5502 @ 1.87GHz (GenuineIntel 686-
class) 1.87 GHz
cpu1: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PS
E36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-
CPL,VMX,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 0 pa 0xfec8, version 20, 24 pins
acpiprt0 at acpi0: bus 1 (IP2P)
acpiprt1 at acpi0: bus 3 (NIB1)
acpiprt2 at acpi0: bus 4 (IPT5)
acpiprt3 at acpi0: bus 0 (PRB2)
acpiprt4 at acpi0: bus 10 (PT07)
acpiprt5 at acpi0: bus 7 (PT03)
acpiprt6 at acpi0: bus 13 (PT01)
acpiprt7 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C3, C3, C1
acpicpu1 at acpi0: C3, C3, C1
acpitz0 at acpi0: critical temperature 31 degC
bios0: ROM list: 0xc/0xb000 0xcb000/0x1a00 0xcca00/0x2600!
ipmi at mainbus0 not configured
cpu0: EST: PSS not yet available for this processor
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 Intel 5500 Host rev 0x13
ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x13
pci1 at ppb0 bus 13
ppb1 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x13
pci2 at ppb1 bus 7
ppb2 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x13
pci3 at ppb2 bus 10
em0 at pci3 dev 0 function 0 Intel PRO/1000 PT (82571EB) rev 
0x06: apic 0 int 6 (irq 7), address 00:15:17:00:00:00
em1 at pci3 dev 0 function 1 Intel PRO/1000 PT (82571EB) rev 
0x06: apic 0 int 13 (irq 11), address 00:15:17:00:00:01
pchb1 at pci0 dev 13 function 0 vendor Intel, unknown product 
0x343a rev 0x13
pchb2 at pci0 dev 13 function 1 vendor Intel, unknown product 
0x343b rev 0x13
pchb3 at pci0 dev 13 function 2 vendor Intel, unknown product 
0x343c rev 0x13
pchb4 at pci0 dev 13 function 3 vendor Intel, unknown product 
0x343d rev 0x13
pchb5 at pci0 dev 13 function 4 Intel 5520/X58 QuickPath rev 0x13
pchb6 at pci0 dev 13 function 5 Intel 5520 QuickPath rev 0x13
pchb7 at pci0 dev 13 function 6 vendor Intel, unknown product 
0x341a rev 0x13
pchb8 at pci0 dev 14 function 0 vendor Intel, unknown product 
0x341c rev 0x13
pchb9 at pci0 dev 14 function 1 vendor Intel, unknown product 
0x341d rev 0x13
pchb10 at pci0 dev 14 function 2 vendor Intel, unknown product 
0x341e rev 0x13
pchb11 at pci0 dev 14 function 3 vendor Intel, unknown product 
0x341f rev 0x13
pchb12 at pci0 dev 14 function 4 vendor Intel, unknown product 
0x3439 rev 0x13
Intel X58 Misc rev 0x13 at pci0 dev 20 function 0 not configured
Intel X58 GPIO rev 0x13 at pci0 dev 20 function 1 not configured
Intel X58 RAS rev 0x13 at pci0 dev 20 function 2 not configured
uhci0 at pci0 dev 26 function 0 Intel 82801JI USB rev 0x00: apic 
8 int 20 (irq 5)
uhci1 at pci0 dev 26 function 1 Intel 82801JI USB rev 0x00: apic 
8 int 23 (irq 7)
uhci2 at pci0 dev 26 function 2 Intel 82801JI USB rev 0x00: apic 
8 int 22 (irq 10)
ehci0 at pci0 dev 26 function 7 Intel 82801JI USB rev 0x00: apic 
8 int 22 (irq 10)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1
ppb3 at pci0 dev 28 function 0 Intel 82801JI PCIE rev 0x00
pci4 at ppb3 bus 2
ppb4 at pci4 dev 0 function 0 ServerWorks PCIE-PCIX rev 0xb5
pci5 at ppb4 bus 3
bge0 at pci5 dev 4 function 0 Broadcom BCM5715 rev 0xa3, BCM5715 
A3 (0x9003): apic 8 int 16 (irq 7), address 18:a9:05:00:00:00
brgphy0 at bge0 phy 1: BCM5714 10/100/1000baseT/SX PHY, rev. 0
bge1 at pci5 dev 4 function 1 Broadcom BCM5715 rev 0xa3, BCM5715 
A3 (0x9003): apic 8 int 17 (irq 11), address 18:a9:05:00:00:01
brgphy1 at bge1 phy 1: BCM5714 10/100/1000baseT/SX PHY, rev. 0
ppb5 at pci0 dev 28 function 4 Intel 82801JI PCIE rev 0x00
pci6 at ppb5 bus 4
uhci3 at pci0 dev 29 function 0 Intel 82801JI USB rev 0x00: apic 
8 int 20 (irq 5)
uhci4 at pci0 dev 29 function 1 Intel 82801JI USB rev 0x00: apic 
8 

Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-22 Thread Frédéric URBAN

Le 18/06/2010 16:43, w...@wootsie.com a icrit :

The same issue here - with different hardware - Supermicro X8DTU and
it's built-in dual Intel 82576 nics.

Running 4.7-patch.

Fails to initialize most of the time at boot (always em1), now and
then it works (initializes and gets link after boot).  em0 rarely
fails to initialize, but also rarely negotiates the link.

Sounds similar to this bug report?
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301

   

First, Hello, I'm new here ;)

In this bug report, the card is detected as 82575 while it's a 82576 and 
the host is running OpenBSD 4.6 amd64


We've ordered some Dell R510 with plenty of card running with 82576 
chips (Some Intel ET DualPort Copper, ET QuadPort Copper and even a EF 
DualPort fiber). I'm pretty sure we'll have the same problem with thoses 
cards.
They are not delivered yet but the goal was to replace some old 
firewalls and with such a problem it's no gonna be funny ;( We are ready 
to help/test all patch you guys can deliver since we'll get almost the 
whole products using 82576 chips (Only the Quad Port Fiber EF will be 
missing)


Somebody knows if this problem only happends on Intel X58/5500/5600 
chipsets ? Did somebody tried the i386 version of OpenBSD 4.7 ?


Another question, I browsed source code of the freebsd project and it 
looks like they use a dedicated drivers for the 82575 and 82576 cards 
aka igb(4). Excuse my newbiness ;) but why is the driver for thoses card 
integrated inside em(4) in openbsd ?


Fred



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-18 Thread uhu
Sevan / Venture37 venture37 at gmail.com writes:

 
 On 4 June 2010 16:57, Joerg Streckfuss streckfuss at dfn-cert.de wrote:
  Okey, we tested the newest snapshot but the issue remains.
 
  Any other clue?
 
  Joerg
 
 fire up sendbug
 
 


Exactly the same problem here on 5 different HP machines with recent Intel
PRO/1000 dual and quad-port cards on OpenBSD 4.6 and 4.7.

Reassigning the interrupts in the BIOS-setup helps, but the error reappears
sporadically on reboot.

Is help needed with bug reporting? Is bugfixing already in progress?

Uwe



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-18 Thread wrh
The same issue here - with different hardware - Supermicro X8DTU and
it's built-in dual Intel 82576 nics.

Running 4.7-patch.

Fails to initialize most of the time at boot (always em1), now and
then it works (initializes and gets link after boot).  em0 rarely
fails to initialize, but also rarely negotiates the link.

Sounds similar to this bug report?
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yesnumbers=6301


Thanks,
-Bill

dmesg/pcidump:
OpenBSD 4.7-stable (GENERIC) #0: Wed Jun 16 12:05:23 CDT 2010
r...@sway.co.green-lake.wi.us:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 3211264000 (3062MB)
avail mem = 3118342144 (2973MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9e000 (81 entries)
bios0: vendor American Megatrends Inc. version 2.0 date 05/28/2010
bios0: Supermicro X8DTU
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC MCFG SLIT OEMB HPET SSDT EINJ BERT ERST HEST
acpi0: wakeup devices NPE1(S4) NPE2(S4) NPE3(S4) NPE4(S4) NPE5(S4)
NPE6(S4) NPE7(S4) NPE8(S4) NPE9(S4) NPEA(S4) P0P1(S4) USB0(S4)
USB1(S4) USB2(S4) USB5(S4) EUSB(S4) USB3(S4) USB4(S4) USB6(S4)
USBE(S4) GBE_(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) P0P8(S4)
P0P9(S4) SLPB(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 E5520 @ 2.27GHz, 2267.09 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,NXE,LONG
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: apic clock running at 133MHz
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
ioapic1 at mainbus0: apid 9 pa 0xfec8a000, version 20, 24 pins
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (NPE1)
acpiprt2 at acpi0: bus 2 (NPE3)
acpiprt3 at acpi0: bus -1 (NPE4)
acpiprt4 at acpi0: bus 3 (NPE5)
acpiprt5 at acpi0: bus -1 (NPE6)
acpiprt6 at acpi0: bus 4 (NPE7)
acpiprt7 at acpi0: bus -1 (NPE8)
acpiprt8 at acpi0: bus 5 (NPE9)
acpiprt9 at acpi0: bus -1 (NPEA)
acpiprt10 at acpi0: bus 6 (P0P1)
acpiprt11 at acpi0: bus -1 (P0P4)
acpiprt12 at acpi0: bus -1 (P0P5)
acpiprt13 at acpi0: bus -1 (P0P6)
acpiprt14 at acpi0: bus -1 (P0P7)
acpiprt15 at acpi0: bus -1 (P0P8)
acpiprt16 at acpi0: bus -1 (P0P9)
acpicpu0 at acpi0: C3, C3, C1, PSS
acpibtn0 at acpi0: SLPB
acpibtn1 at acpi0: PWRB
ipmi at mainbus0 not configured
cpu0: unknown i686 model 0x1a, can't get bus clock
cpu0: EST: PSS not yet available for this processor
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 5520 Host rev 0x22
ppb0 at pci0 dev 1 function 0 Intel X58 PCIE rev 0x22
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 Intel PRO/1000 (82576) rev 0x01: apic 9
int 4 (irq 15), address 00:25:90:02:f4:9c
em1 at pci1 dev 0 function 1 Intel PRO/1000 (82576) rev 0x01: apic 9
int 16 (irq 14)em1: Hardware Initialization Failedem1: Unable to
initialize the hardware
ppb1 at pci0 dev 3 function 0 Intel X58 PCIE rev 0x22
pci2 at ppb1 bus 2
ppb2 at pci0 dev 5 function 0 Intel X58 PCIE rev 0x22
pci3 at ppb2 bus 3
ppb3 at pci0 dev 7 function 0 Intel X58 PCIE rev 0x22
pci4 at ppb3 bus 4
mfi0 at pci4 dev 0 function 0 Symbios Logic SAS1078 rev 0x04: apic 9
int 6 (irq 15), SAS 8704ELP
mfi0: logical drives 1, version 11.0.1-0028, 128MB RAM
scsibus0 at mfi0: 1 targets
sd0 at scsibus0 targ 0 lun 0: LSI, MegaRAID 8704ELP, 1.40 SCSI3 0/direct fixed
sd0: 238418MB, 512 bytes/sec, 488280064 sec total
ppb4 at pci0 dev 9 function 0 Intel X58 PCIE rev 0x22
pci5 at ppb4 bus 5
Intel X58 IOxAPIC rev 0x22 at pci0 dev 19 function 0 not configured
Intel X58 Misc rev 0x22 at pci0 dev 20 function 0 not configured
Intel X58 GPIO rev 0x22 at pci0 dev 20 function 1 not configured
Intel X58 RAS rev 0x22 at pci0 dev 20 function 2 not configured
Intel X58 Throttle rev 0x22 at pci0 dev 20 function 3 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 0 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 1 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 2 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 3 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 4 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 5 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 6 not configured
Intel X58 QuickData rev 0x22 at pci0 dev 22 function 7 not configured
uhci0 at pci0 dev 26 function 0 Intel 82801JI USB rev 0x00: apic 8
int 16 (irq 15)
uhci1 at pci0 dev 26 function 1 Intel 82801JI USB rev 0x00: apic 8
int 21 (irq 7)
uhci2 at pci0 dev 26 function 2 Intel 82801JI USB rev 0x00: apic 8
int 19 (irq 11)
ehci0 at pci0 dev 26 function 7 Intel 82801JI USB 

Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-04 Thread Sevan / Venture37
Test a snapshot to see if the issue still exists


Sevan / Venture37



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-04 Thread Joerg Streckfuss
Am 04.06.2010 13:18, schrieb Sevan / Venture37:
 Test a snapshot to see if the issue still exists


 Sevan / Venture37
Okey, we tested the newest snapshot but the issue remains.

Any other clue?

Joerg

[demime 1.01d removed an attachment of type application/pkcs7-signature which 
had a name of smime.p7s]



Re: Intel PRO/1000 QP on Dell R610 and OpenBSD 4.7

2010-06-04 Thread Sevan / Venture37
On 4 June 2010 16:57, Joerg Streckfuss streckf...@dfn-cert.de wrote:
 Okey, we tested the newest snapshot but the issue remains.

 Any other clue?

 Joerg

fire up sendbug