Date: Sat, 2 Aug 2008 10:34:47 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: Martin <nakal@web.de> Cc: jfv@freebsd.org, freebsd-stable@freebsd.org, Robert Watson <rwatson@freebsd.org> Subject: Re: em(4) on FreeBSD is sometimes annoying Message-ID: <2a41acea0808021034g588fdc77w50797f473e8809b0@mail.gmail.com> In-Reply-To: <20080802064727.042d5e3d@web.de> References: <20080801142005.473c17ca@zelda.local> <20080801154208.W6085@fledge.watson.org> <2a41acea0808010924u22603c61p10e47237fad5b6fb@mail.gmail.com> <20080802064727.042d5e3d@web.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 1, 2008 at 9:47 PM, Martin <nakal@web.de> wrote: > On Fri, 1 Aug 2008 09:24:53 -0700 > "Jack Vogel" <jfvogel@gmail.com> wrote: > >> If the poster gives me EXACT hardware list I will see about repro'ing the >> problem inhouse. We do not do much of anything with laptops but I >> will see. Oh and a pciconf would help too. > > Hi Jack, > > pciconf -lv gives me: > > em0@pci0:2:0:0: class=0x020000 card=0x200117aa chip=0x109a8086 > rev=0x00 hdr=0x00 vendor = 'Intel Corporation' > device = '82573L Intel PRO/1000 PL Network Adaptor' > class = network > subclass = ethernet > > > One thing, I have to add. I described the behavior wrong. The adapter > actually IS available in the interface list, but it gets "no carrier". > Sorry for that. > > This is what I get from ifconfig when the NIC is plugged in: > > em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > 1500 options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4> > ether xx:xx:xx:xx:xx:xx > media: Ethernet autoselect > status: no carrier > > All LEDs are off. > > Device was found on boot: > > em0: <Intel(R) PRO/1000 Network Connection 6.9.5> port 0x3000-0x301f > mem 0xee000 000-0xee01ffff irq 16 at device 0.0 on pci2 > em0: Using MSI interrupt > em0: [FILTER] > em0: Ethernet address: xx:xx:xx:xx:xx:xx > > -- > Martin > Telling me what kind of NIC it is isn't going to help, 82573's are working the world over :) What exactly is your laptop, what model, is the NIC a LOM (on the motherboard) or some addin. Some random thoughts: There should be NO need to specify full duplex, if you have to do that then you have some problem with your switch. Are you loading the driver as a module, or is it static? So, if you do this: get a cable and eliminate any switch, just a back to back connection between two machines, then if you load the driver and ifconfig address up... what happens?? Jack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0808021034g588fdc77w50797f473e8809b0>