sendbug submitted with 4.7-current.
http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=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=yes&numbers=6301
> <http://cvs.openbsd.org/cgi-bin/query-pr-wrapper?full=yes&numbers=6301>
>
> Can somebody report it with a dmesg on 4.7 ?
