Re: em(4) problems.
From: Roberto Nunnari (roberto.nunnari_at_supsi.ch)
Date: 05/06/04
- Previous message: Bruno Tavares: "Re: SATA Support gone bad?"
- In reply to: Stefan Bethke: "Re: em(4) problems."
- Next in thread: Søren Schmidt: "Re: em(4) problems."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 06 May 2004 19:57:56 +0200 To: Stefan Bethke <stb@lassitu.de>
I cannot boot the system with em0 after FreeBSD 5.2.1-RELEASE-p3..
it did work with 5.2-RELEASE-p1, though.
See: http://www.freebsd.org/cgi/query-pr.cgi?pr=65282
One month is over since I submitted the pr, but nobody has
looked at it yet.
Stefan Bethke wrote:
>
> Am 05.05.2004 um 13:31 schrieb Søren Schmidt:
>
>> Pawel Jakub Dawidek wrote:
>>
>>> On Wed, May 05, 2004 at 12:42:48PM +0200, Pawel Jakub Dawidek wrote:
>>> +> Hi.
>>> +> +> I've problems with em(4) and IPSEC/FAST_IPSEC and TCP_STREAM
>>> netperf test.
>>> +> While running netperf tests between two FreeBSD machines directly
>>> connected
>>> +> em0 goes down once every few minutes and I've no idea why.
>>> +> Without IPSEC everything works just fine, with IPSEC/FAST_IPSEC it
>>> also
>>> +> works fine but for other tests (UDP_STREAM, TCP_RR, UDP_RR).
>>
>>
>> For what its worth I have problems with one em based interface as
>> well, it locks the machine solid when used:
>
>
> me too:
> FreeBSD 5.2-CURRENT #0: Tue Apr 13 18:50:30 GMT 2004
> root@vergissnix:/usr/obj/usr/src/sys/VERGISSNIX
> em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port
> 0xc000-0xc01f
> mem 0xf2000000-0xf201ffff irq 12 at device 1.0 on pci2
> em0: Bus reserved 0x20000 bytes for rid 0x10 type 3 at 0xf2000000
> em0: Bus reserved 0x20 bytes for rid 0x18 type 4 at 0xc000
> em0: [GIANT-LOCKED]
> em0: Ethernet address: 00:e0:81:27:b6:12
> em0: Speed:N/A Duplex:N/A
> em1: <Intel(R) PRO/1000 Network Connection, Version - 1.7.25> port
> 0xd300-0xd33f
> mem 0xf1020000-0xf103ffff,0xf1000000-0xf101ffff irq 23 at device 2.0 on
> pci3
> em1: Bus reserved 0x20000 bytes for rid 0x10 type 3 at 0xf1000000
> em1: Bus reserved 0x40 bytes for rid 0x18 type 4 at 0xd300
> em1: [GIANT-LOCKED]
> em1: Ethernet address: 00:e0:81:27:b6:13
> em1: Speed:N/A Duplex:N/A
>
> em0@pci2:1:0: class=0x020000 card=0x10198086 chip=0x10198086 rev=0x00
> hdr=0x00
> em1@pci3:2:0: class=0x020000 card=0x10138086 chip=0x10138086 rev=0x00
> hdr=0x00
>
> # vmstat -ia
> irq12: em0 0 0
> stray irq12 0 0
> irq23: em1 3916723 3
> stray irq23 0 0
>
> em1 works; after bringing em0 up, machine locks solid after 2 to 5 minutes.
>
>
--
Roberto Nunnari -software engineer-
mailto:roberto.nunnari@supsi.ch
Scuola Universitaria Professionale della Svizzera Italiana
Dipartimento Tecnologie Innovative
http://www.dti.supsi.ch
SUPSI-DTI
Via Cantonale tel: +41-91-6108561
6928 Manno """ fax: +41-91-6108570
Switzerland (o o)
=======================oOO==(_)==OOo========================
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
- Previous message: Bruno Tavares: "Re: SATA Support gone bad?"
- In reply to: Stefan Bethke: "Re: em(4) problems."
- Next in thread: Søren Schmidt: "Re: em(4) problems."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
