Re: em(4) on FreeBSD is sometimes annoying
I fought with this issue all day today, trying to root cause it, and while I don't have a solution I do have a better understanding of it. I was wrong about it being the interrupt handler, at least if there's any issue with it its not the primary cause. I actually found out using a Fedora Live CD that Linux seems to have the same issue, but its symptoms are slightly different due to driver architecture differences. If you boot Linux with no cable in, and then modprobe the e1000 driver you get no errors, however, when you follow that with an 'ifconfig eth0' it will fail saying that it cannot find the device!! Do the same with the cable in and it all works. The same 82573 NIC on a standalone adapter has NONE of these problems, it all works fine. So, right now my theory is the power system of the laptop is putting the phy into a sleep state due to having no link and neither our driver or the Linux driver has a way to bring it back out of that state. Until this gets worked out all I can tell you is "keep that cable IN" :) Jack On Thu, Aug 14, 2008 at 4:33 AM, Markus Vervier <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Jack Vogel wrote: > | I have reproduced the problem, you are correct. Thank you for > | persisting thru my doubts :) > Always persisting to help improving FreeBSD. Another odd thing I noticed > today: > When dual-booting Windows on the same machine and doing a warm-reboot from > Windows to FreeBSD, > you _do_ get a link with the procedure I described yesterday.. So there > seems to be some setting which is lost > after cold-boot or some EEPROM setting which is changed somehow. > > | OH, I should note that as long as you put in a cable before you > | ifconfig up its fine so > | its not that hard to work around the issue. > I completly forgot about the issue until now, after I noticed it some time > ago when being overworked. :-( > The situation just does not occur very often in times of wireless LAN / > Docking Stations. :-) > > - -- > Markus > > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.9 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkikGBMACgkQFhK2gHeM2QOLpACfdX4IyNSivy+TgAJBhKgZUwP2 > iiIAoNrPUTE0veViP7Zklm7jD25m7Aad > =DrBs > -END PGP SIGNATURE- > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jack Vogel wrote: | I have reproduced the problem, you are correct. Thank you for | persisting thru my doubts :) Always persisting to help improving FreeBSD. Another odd thing I noticed today: When dual-booting Windows on the same machine and doing a warm-reboot from Windows to FreeBSD, you _do_ get a link with the procedure I described yesterday.. So there seems to be some setting which is lost after cold-boot or some EEPROM setting which is changed somehow. | OH, I should note that as long as you put in a cable before you | ifconfig up its fine so | its not that hard to work around the issue. I completly forgot about the issue until now, after I noticed it some time ago when being overworked. :-( The situation just does not occur very often in times of wireless LAN / Docking Stations. :-) - -- Markus -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkikGBMACgkQFhK2gHeM2QOLpACfdX4IyNSivy+TgAJBhKgZUwP2 iiIAoNrPUTE0veViP7Zklm7jD25m7Aad =DrBs -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Wed, Aug 13, 2008 at 12:04:59PM +0200, Markus Vervier wrote: > Jack Vogel wrote: >> >> I didn't mean the NIC EEPROM, but the system BIOS, make sure you are >> running the version that Jeremy said he was, if that matches you might go >> look at settings in the BIOS that are about management. >> > I'm now running the latest BIOS for my X60 version 2.22 with the same > results. Jeremy runs version 1.15 but on a T60. >> I thought you told us that when you had a back to back connection that it >> worked, no?? > Sorry, it does not work when having a b2b connection, never said that. > But I noticed another thing: > > It is important that the device was up without a cable connected: > > 1. power off completely > 2. boot freebsd without a cable connected > 3. in a rootshell do ifconfig em0 up > 4. connect the cable > 5. no link This wasn't the procedure I was following when I did testing on my T60p widescreen -- I was booting with the cable connected. I'll have to try the above procedure tonight, although it may be wasted effort as Jack was able to repro it on an X60. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Wed, Aug 13, 2008 at 8:22 AM, Jack Vogel <[EMAIL PROTECTED]> wrote: > On Wed, Aug 13, 2008 at 3:04 AM, Markus Vervier <[EMAIL PROTECTED]> wrote: >> Jack Vogel wrote: >>> >>> I didn't mean the NIC EEPROM, but the system BIOS, make sure you are >>> running the version that Jeremy said he was, if that matches you might go >>> look at settings in the BIOS that are about management. >>> >> I'm now running the latest BIOS for my X60 version 2.22 with the same >> results. Jeremy runs version 1.15 but on a T60. >>> >>> I thought you told us that when you had a back to back connection that it >>> worked, no?? >> >> Sorry, it does not work when having a b2b connection, never said that. But I >> noticed another thing: >> >> It is important that the device was up without a cable connected: >> >> 1. power off completely >> 2. boot freebsd without a cable connected >> 3. in a rootshell do ifconfig em0 up >> 4. connect the cable >> 5. no link > > Hmmm, well let me see if I can get ahold of an X60. > > Jack > Markus, I have reproduced the problem, you are correct. Thank you for persisting thru my doubts :) There is a flip side to the problem, once the interface is up and active, if you remove the cable it never shows inactive :( It must be some interrupt handling/media status issue, I'll be looking into a fix this afternoon. OH, I should note that as long as you put in a cable before you ifconfig up its fine so its not that hard to work around the issue. Stay tuned Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Wed, Aug 13, 2008 at 3:04 AM, Markus Vervier <[EMAIL PROTECTED]> wrote: > Jack Vogel wrote: >> >> I didn't mean the NIC EEPROM, but the system BIOS, make sure you are >> running the version that Jeremy said he was, if that matches you might go >> look at settings in the BIOS that are about management. >> > I'm now running the latest BIOS for my X60 version 2.22 with the same > results. Jeremy runs version 1.15 but on a T60. >> >> I thought you told us that when you had a back to back connection that it >> worked, no?? > > Sorry, it does not work when having a b2b connection, never said that. But I > noticed another thing: > > It is important that the device was up without a cable connected: > > 1. power off completely > 2. boot freebsd without a cable connected > 3. in a rootshell do ifconfig em0 up > 4. connect the cable > 5. no link Hmmm, well let me see if I can get ahold of an X60. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel wrote: I didn't mean the NIC EEPROM, but the system BIOS, make sure you are running the version that Jeremy said he was, if that matches you might go look at settings in the BIOS that are about management. I'm now running the latest BIOS for my X60 version 2.22 with the same results. Jeremy runs version 1.15 but on a T60. I thought you told us that when you had a back to back connection that it worked, no?? Sorry, it does not work when having a b2b connection, never said that. But I noticed another thing: It is important that the device was up without a cable connected: 1. power off completely 2. boot freebsd without a cable connected 3. in a rootshell do ifconfig em0 up 4. connect the cable 5. no link -- Markus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
> For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386 > and neither install has this problem. I can cold boot it with the NIC > unplugged, plug in a cable, I get a link light and ifconfig em0 goes to > active, dhclient em0 gets an IP successfully. > Did you try to run /etc/rc.d/netif start after you've booted your laptop unplugged? Try to do that, THEN connect the cable. The problem appears ONLY in this situation. And it's quite common, because you often use your laptop with wireless network and suddenly you decide to connect it to wired network without having to switch the laptop off. My NIC is in such a state that I am forced to switch it off, or else I don't get link signal. I don't think it's a BIOS firmware problem (I have tried every update). I can remember that Linux had this issues, too a while ago. It works there now, but FreeBSD is still the same. Please read the steps how I cause this situation. It appears ONLY when you do it like I described it. I've seen that people first boot with plugged in cable and start to play with dhclient. Both is wrong. Correct steps to reproduce is: You have to start with unhooked interface AND the line ifconfig_re0="DHCP" in /etc/rc.conf. Then wait until you can login and try to attach the cable. -- Martin ___ EINE FÜR ALLE: die kostenlose WEB.DE-Plattform für Freunde und Deine Homepage mit eigenem Namen. Jetzt starten! http://unddu.de/[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 11, 2008 at 1:32 PM, Markus Vervier <[EMAIL PROTECTED]> wrote: > Jack Vogel wrote: >> >> Seems possibly a BIOS thing, if not that bad cable, bad link partner >> maybe?? >> > > I had the problem with all sorts of switches / cables. How can I dump my > EEPROM settings if that helps? I didn't mean the NIC EEPROM, but the system BIOS, make sure you are running the version that Jeremy said he was, if that matches you might go look at settings in the BIOS that are about management. I thought you told us that when you had a back to back connection that it worked, no?? Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel wrote: Seems possibly a BIOS thing, if not that bad cable, bad link partner maybe?? I had the problem with all sorts of switches / cables. How can I dump my EEPROM settings if that helps? -- Markus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 11, 2008 at 7:02 AM, Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Mon, Aug 11, 2008 at 08:19:46AM +, Josh Paetzel wrote: >> On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote: >> > OK, I just got access to a machine, am going to install and see if I >> > can repro this >> > this afternoon. >> > >> > Jack >> >> For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386 >> and neither install has this problem. I can cold boot it with the NIC >> unplugged, plug in a cable, I get a link light and ifconfig em0 goes to >> active, dhclient em0 gets an IP successfully. > > As promised, I tested said issue out on my T60p (widescreen) tonight, > using both FreeBSD 7.0-STABLE and 7.0-RELEASE. > > I wasn't able to reproduce the issue; so my experience was the same as > Josh. I can also boot it with the CAT5 inserted, dhclient fetch an IP, > no LED oddities -- then yank the cable (LED and link light go off), > re-insert the cable, and within a moment or so dhclient again gets an > IP. > > I'm left wondering if maybe there's an EEPROM setting that's doing this > (purely speculative on my part), or possibly some odd BIOS quirk. My > T60p (widescreen) is running BIOS 1.14. It's worth noting that the > non-widescreen T60p uses a different BIOS. Cool, it turned out that the laptop I was told I could use was an X61 and it had an ICH8 NIC rather than 82573 anyway, they were supposed to get me one today but given the two of you have already gone thru this verification I see little point in doing the same. Seems possibly a BIOS thing, if not that bad cable, bad link partner maybe?? Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 11, 2008 at 08:19:46AM +, Josh Paetzel wrote: > On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote: > > OK, I just got access to a machine, am going to install and see if I > > can repro this > > this afternoon. > > > > Jack > > For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386 > and neither install has this problem. I can cold boot it with the NIC > unplugged, plug in a cable, I get a link light and ifconfig em0 goes to > active, dhclient em0 gets an IP successfully. As promised, I tested said issue out on my T60p (widescreen) tonight, using both FreeBSD 7.0-STABLE and 7.0-RELEASE. I wasn't able to reproduce the issue; so my experience was the same as Josh. I can also boot it with the CAT5 inserted, dhclient fetch an IP, no LED oddities -- then yank the cable (LED and link light go off), re-insert the cable, and within a moment or so dhclient again gets an IP. I'm left wondering if maybe there's an EEPROM setting that's doing this (purely speculative on my part), or possibly some odd BIOS quirk. My T60p (widescreen) is running BIOS 1.14. It's worth noting that the non-widescreen T60p uses a different BIOS. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Friday 08 August 2008 06:31:24 pm Jack Vogel wrote: > OK, I just got access to a machine, am going to install and see if I > can repro this > this afternoon. > > Jack For what it's worth, I have a T60 that dual boots 6.3-R/amd64 and 7.0-R/i386 and neither install has this problem. I can cold boot it with the NIC unplugged, plug in a cable, I get a link light and ifconfig em0 goes to active, dhclient em0 gets an IP successfully. -- Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB signature.asc Description: This is a digitally signed message part.
Re: em(4) on FreeBSD is sometimes annoying
OK, I just got access to a machine, am going to install and see if I can repro this this afternoon. Jack On Fri, Aug 8, 2008 at 10:56 AM, Markus Vervier <[EMAIL PROTECTED]> wrote: > Jack Vogel schrieb: >> >> "me too" 's are of little help. Please elaborate on your "exact same", >> since >> each person's perception will be slightly different. >> >> > > Hi Jack, > > maybe read it like: Thinkpad X60 1706GMG affected too, so the problem is not > specific to Martins machine. > > I can write the same steps to reproduce the behaviour as Martin here: > > <--> > Once again, steps to reproduce this behavior: > 1) Power the laptop OFF. Really OFF, I mean. No reboots! > 2) Detach the cable from NIC. > 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0="DHCP") until > login appears. > 4) Attach the cable to the NIC. > 5) Voila... no link. > <--> > > My perception is that if the em driver gets loaded without a cable being > plugged in, no link can be established. > I can workaround the problem when em was not build into the kernel, by > unloading the em-kmod and reloading it > again with the cable plugged in. If the cable is not plugged in the > interface will always stay in state "no carrier". > The NIC works fine under Windows / Linux on the same machine. > > -- > Markus > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Mike Tancsa schrieb: If you manually type, dhclient em0 No, even if I type ifconfig em0 down && ifconfig em0 up it won´t work. The interface just gets no link until I reload the driver with a cable plugged. -- Markus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
At 01:56 PM 8/8/2008, Markus Vervier wrote: 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0="DHCP") until login appears. 4) Attach the cable to the NIC. 5) Voila... no link. <--> If you manually type, dhclient em0 does it work for you then ? ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel schrieb: "me too" 's are of little help. Please elaborate on your "exact same", since each person's perception will be slightly different. Hi Jack, maybe read it like: Thinkpad X60 1706GMG affected too, so the problem is not specific to Martins machine. I can write the same steps to reproduce the behaviour as Martin here: <--> Once again, steps to reproduce this behavior: 1) Power the laptop OFF. Really OFF, I mean. No reboots! 2) Detach the cable from NIC. 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0="DHCP") until login appears. 4) Attach the cable to the NIC. 5) Voila... no link. <--> My perception is that if the em driver gets loaded without a cable being plugged in, no link can be established. I can workaround the problem when em was not build into the kernel, by unloading the em-kmod and reloading it again with the cable plugged in. If the cable is not plugged in the interface will always stay in state "no carrier". The NIC works fine under Windows / Linux on the same machine. -- Markus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
"me too" 's are of little help. Please elaborate on your "exact same", since each person's perception will be slightly different. So far I have heard nothing that sounds like a driver issue. Jack On Fri, Aug 8, 2008 at 5:50 AM, Markus Vervier <[EMAIL PROTECTED]> wrote: > > Hi, > > I just stumbled upon this thread. I experience the exact same behaviour as > Martin on my Thinkpad X60: > > Thinkpad X60 Model: 1706GMG > BIOS-Version 2.15 (7BETD4WW) > FreeBSD 7.0 STABLE amd64 (from about two weeks ago) - same situtation on > 7.0-RELEASE i386 > > -- > Markus > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
em(4) on FreeBSD is sometimes annoying
Hi, I just stumbled upon this thread. I experience the exact same behaviour as Martin on my Thinkpad X60: Thinkpad X60 Model: 1706GMG BIOS-Version 2.15 (7BETD4WW) FreeBSD 7.0 STABLE amd64 (from about two weeks ago) - same situtation on 7.0-RELEASE i386 -- Markus ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Am Mon, 4 Aug 2008 12:12:24 -0700 schrieb "Jack Vogel" <[EMAIL PROTECTED]>: > OK, so your EEPROM is does not have the bug. As I was > saying before, I would like to see what back to back behavior is. > > And, BTW, back to back does NOT mean hook to the switch, > that's the very thing that is suspicious. It means NIC to NIC, > no DHCP, assigned addresses. And then see that you pass > traffic, and then unhook cable, see if link goes down, reconnect > and it should go up. With no /etc/rc.d/netif script involved during startup everything always works as expected. If I comment the line ifconfig_re0="DHCP" and start my laptop. I can assign the address. I can ping the other NIC. If can unhook the cable the LED goes off, link goes down, I can plug it in again, I can ping again. I have also no problems if I start without ifconfig_re0="DHCP" and run "dhclient em0" while ethernet cable is unplugged. If I plug it in again, everything works like above. But: If I startup with ifconfig_em0="DHCP" AND (binary and!) no cable nothing of this works correctly. There must be something ifconfig_em="DHCP" causes on startup that running dhclient does not cause and that provokes the dead state. > Oh, and exactly what kernel, and driver revision are you using. Kernel is FreeBSD-STABLE compile date Mon Aug 4 13:41:43 CEST 2008. It's GENERIC. The em(4) driver is the one used in this STABLE version of yesterday. I should perhaps mention that I have some other problems with this laptop. I cannot boot with a PCMCIA wireless card (atheros) already in the slot, or I get 100% load on cbb(4) and the system is not usable. If I boot without the Atheros card and I plug it in later, it mostly is detected. AND I get sometimes an NMI when Atheros card is in use AND (binary and again!) the laptop is on battery. This happens also on Linux. AND the laptop will almost never recognize the Atheros card, if I am using a text terminal with high resolution (set by vidcontrol MODE_280 with VESA support compiled in; cannot reproduce now, because I'm using GENERIC). I don't know if these things are related. I will get some other laptop in one or two months. I hope these things won't bother me anymore. -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 10:18:50AM -0700, Jack Vogel wrote: > The focus here on the laptop distracted me, but someone else at work > reminded me. Its very important that you run the EEPROM fix for > the 82573 that i posted a long while back, search in email archive > for it. Its a DOS executable that will patch your EEPROM. > > I am not sure if the Lenova's need it, but get it, run it, and then > see if your problem goes away. The tool Jack is referring to is below. I knew saving it for a rainy day would be worth it. :-) http://people.freebsd.org/~koitsu/em_82573_manc_fix.zip -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
OK, so your EEPROM is does not have the bug. As I was saying before, I would like to see what back to back behavior is. And, BTW, back to back does NOT mean hook to the switch, that's the very thing that is suspicious. It means NIC to NIC, no DHCP, assigned addresses. And then see that you pass traffic, and then unhook cable, see if link goes down, reconnect and it should go up. Oh, and exactly what kernel, and driver revision are you using. Jack On Mon, Aug 4, 2008 at 11:52 AM, Martin <[EMAIL PROTECTED]> wrote: > On Mon, 04 Aug 2008 09:35:21 -0800 > Royce Williams <[EMAIL PROTECTED]> wrote: > >> Jack Vogel wrote, on 8/4/2008 9:18 AM: >> > The focus here on the laptop distracted me, but someone else at work >> > reminded me. Its very important that you run the EEPROM fix for >> > the 82573 that i posted a long while back, search in email archive >> > for it. Its a DOS executable that will patch your EEPROM. >> > >> > I am not sure if the Lenova's need it, but get it, run it, and then >> > see if your problem goes away. >> >> Martin, there's also a link to it from Jeremy's "Commonly Reported >> Issues" page: >> >> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues >> >> Look for "DOS-based EEPROM". > > Hi Royce, > > thank you for the link. I've read this issue description and I'm not > sure if it helps. I don't have any "watchdog timeouts" and my EEPROM > data looks clean: > > Interface EEPROM Dump: > Offset > 0x > 0x0010 0053 0103 026b 2001 17aa 109a 8086 80df > 0x0020 2000 7e54 0014 00da 0004 2700 > 0x0030 6cc9 3150 073e 040b 298b f000 0f02 > > (I masked out the MAC address) > > -- > Martin > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, 04 Aug 2008 09:35:21 -0800 Royce Williams <[EMAIL PROTECTED]> wrote: > Jack Vogel wrote, on 8/4/2008 9:18 AM: > > The focus here on the laptop distracted me, but someone else at work > > reminded me. Its very important that you run the EEPROM fix for > > the 82573 that i posted a long while back, search in email archive > > for it. Its a DOS executable that will patch your EEPROM. > > > > I am not sure if the Lenova's need it, but get it, run it, and then > > see if your problem goes away. > > Martin, there's also a link to it from Jeremy's "Commonly Reported > Issues" page: > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > Look for "DOS-based EEPROM". Hi Royce, thank you for the link. I've read this issue description and I'm not sure if it helps. I don't have any "watchdog timeouts" and my EEPROM data looks clean: Interface EEPROM Dump: Offset 0x 0x0010 0053 0103 026b 2001 17aa 109a 8086 80df 0x0020 2000 7e54 0014 00da 0004 2700 0x0030 6cc9 3150 073e 040b 298b f000 0f02 (I masked out the MAC address) -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Right, the Linux driver implemented the ability to write as well as read the eeprom, I've always been hesitant to add that. But for some it will be easier to boot Linux and run the script. Thanks for adding the URL Royce. Jack On Mon, Aug 4, 2008 at 11:15 AM, Royce Williams <[EMAIL PROTECTED]> wrote: > Jack Vogel wrote, on 8/4/2008 9:54 AM: >> On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams <[EMAIL PROTECTED]> wrote: >>> Jack Vogel wrote, on 8/4/2008 9:18 AM: The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. >>> Martin, there's also a link to it from Jeremy's "Commonly Reported >>> Issues" page: >>> >>> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues >>> >>> Look for "DOS-based EEPROM". >>> >>> >>> Jack, is this issue the same one that is documented here? >>> >>> http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages >>> >>> >>> ... and addressed by this script? >>> >>> http://e1000.sourceforge.net/doku.php?id=tx_unit_hang >>> >>> >>> If so, the script could be used without booting from a DOS disk. If >>> this is unrelated or is an unsafe way to apply this fix, that would be >>> handy to know. > >> Thanks for the pointer Royce, and yes that's the issue, and if you >> want to boot Linux and use that instead of DOS then more power to >> you. > > Excellent! For some folks, booting from a Knoppix or Ubuntu CD > might be easier than trying to gen up a DOS-bootable USB key. I > think that recent Knoppix and Ubuntu include ethtool out of the box. > > Point of clarity: the script that I linked to above is to test/invoke > the problem, not to "address" it. Below is the script that calls > ethtool to change the actual bits: > > http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh > > > Royce > > > -- > Royce D. Williams - http://royce.ws/ > The only normal people are the ones you don't know very well. -A.Adler > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel wrote, on 8/4/2008 9:54 AM: > On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams <[EMAIL PROTECTED]> wrote: >> Jack Vogel wrote, on 8/4/2008 9:18 AM: >>> The focus here on the laptop distracted me, but someone else at work >>> reminded me. Its very important that you run the EEPROM fix for >>> the 82573 that i posted a long while back, search in email archive >>> for it. Its a DOS executable that will patch your EEPROM. >>> >>> I am not sure if the Lenova's need it, but get it, run it, and then >>> see if your problem goes away. >> Martin, there's also a link to it from Jeremy's "Commonly Reported >> Issues" page: >> >> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues >> >> Look for "DOS-based EEPROM". >> >> >> Jack, is this issue the same one that is documented here? >> >> http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages >> >> >> ... and addressed by this script? >> >> http://e1000.sourceforge.net/doku.php?id=tx_unit_hang >> >> >> If so, the script could be used without booting from a DOS disk. If >> this is unrelated or is an unsafe way to apply this fix, that would be >> handy to know. > Thanks for the pointer Royce, and yes that's the issue, and if you > want to boot Linux and use that instead of DOS then more power to > you. Excellent! For some folks, booting from a Knoppix or Ubuntu CD might be easier than trying to gen up a DOS-bootable USB key. I think that recent Knoppix and Ubuntu include ethtool out of the box. Point of clarity: the script that I linked to above is to test/invoke the problem, not to "address" it. Below is the script that calls ethtool to change the actual bits: http://e1000.sourceforge.net/files/fixeep-82573-dspd.sh Royce -- Royce D. Williams - http://royce.ws/ The only normal people are the ones you don't know very well. -A.Adler ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Thanks for the pointer Royce, and yes that's the issue, and if you want to boot Linux and use that instead of DOS then more power to you. Cheers, Jack On Mon, Aug 4, 2008 at 10:35 AM, Royce Williams <[EMAIL PROTECTED]> wrote: > Jack Vogel wrote, on 8/4/2008 9:18 AM: >> The focus here on the laptop distracted me, but someone else at work >> reminded me. Its very important that you run the EEPROM fix for >> the 82573 that i posted a long while back, search in email archive >> for it. Its a DOS executable that will patch your EEPROM. >> >> I am not sure if the Lenova's need it, but get it, run it, and then >> see if your problem goes away. > > Martin, there's also a link to it from Jeremy's "Commonly Reported > Issues" page: > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > Look for "DOS-based EEPROM". > > > Jack, is this issue the same one that is documented here? > > http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages > > > ... and addressed by this script? > > http://e1000.sourceforge.net/doku.php?id=tx_unit_hang > > > If so, the script could be used without booting from a DOS disk. If > this is unrelated or is an unsafe way to apply this fix, that would be > handy to know. > > > Royce > > -- > Royce D. Williams - http://royce.ws/ >A finished person is a boring person. - Anna Quindlen > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Jack Vogel wrote, on 8/4/2008 9:18 AM: > The focus here on the laptop distracted me, but someone else at work > reminded me. Its very important that you run the EEPROM fix for > the 82573 that i posted a long while back, search in email archive > for it. Its a DOS executable that will patch your EEPROM. > > I am not sure if the Lenova's need it, but get it, run it, and then > see if your problem goes away. Martin, there's also a link to it from Jeremy's "Commonly Reported Issues" page: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Look for "DOS-based EEPROM". Jack, is this issue the same one that is documented here? http://e1000.sourceforge.net/doku.php?id=known_issues#v_l_e_tx_unit_hang_messages ... and addressed by this script? http://e1000.sourceforge.net/doku.php?id=tx_unit_hang If so, the script could be used without booting from a DOS disk. If this is unrelated or is an unsafe way to apply this fix, that would be handy to know. Royce -- Royce D. Williams - http://royce.ws/ A finished person is a boring person. - Anna Quindlen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
The focus here on the laptop distracted me, but someone else at work reminded me. Its very important that you run the EEPROM fix for the 82573 that i posted a long while back, search in email archive for it. Its a DOS executable that will patch your EEPROM. I am not sure if the Lenova's need it, but get it, run it, and then see if your problem goes away. Jack On Mon, Aug 4, 2008 at 8:44 AM, Martin <[EMAIL PROTECTED]> wrote: > Am Mon, 4 Aug 2008 12:51:38 +0200 > schrieb Martin <[EMAIL PROTECTED]>: > >> I'm trying some other things here. Before you waste time on >> PEBKAC problems ;) (which I now suspect to be). Let me try to install >> the latest GENERIC on my laptop first. > > I've build fresh world and then kernel (GENERIC configuration), I also > removed everything from rc.conf except host name assignment, and > ifconfig_re0="DHCP". I have still same effect as described before. > > Booting without ethernet cable will prevent me to get link "status: > active" on em(4), when I try to use it later. > > GENERIC from FreeBSD 7.0 CD installation works fine. I checked it > again. I can boot without cable in my NIC, "try" to assign an IP using > DHCP and then plug the cable in and I have link. > > Is there a difference how /etc/rc.d/netif handles a NIC with DHCP and > how the installation CD is handling it? > > Once again, steps to reproduce this behavior: > > 1) Power the laptop OFF. Really OFF, I mean. No reboots! > 2) Detach the cable from NIC. > 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0="DHCP") until > login appears. > 4) Attach the cable to the NIC. > 5) Voila... no link. > > -- > Martin > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Am Mon, 4 Aug 2008 12:51:38 +0200 schrieb Martin <[EMAIL PROTECTED]>: > I'm trying some other things here. Before you waste time on > PEBKAC problems ;) (which I now suspect to be). Let me try to install > the latest GENERIC on my laptop first. I've build fresh world and then kernel (GENERIC configuration), I also removed everything from rc.conf except host name assignment, and ifconfig_re0="DHCP". I have still same effect as described before. Booting without ethernet cable will prevent me to get link "status: active" on em(4), when I try to use it later. GENERIC from FreeBSD 7.0 CD installation works fine. I checked it again. I can boot without cable in my NIC, "try" to assign an IP using DHCP and then plug the cable in and I have link. Is there a difference how /etc/rc.d/netif handles a NIC with DHCP and how the installation CD is handling it? Once again, steps to reproduce this behavior: 1) Power the laptop OFF. Really OFF, I mean. No reboots! 2) Detach the cable from NIC. 3) Boot FreeBSD. Let it pass the DHCP phase (ifconfig_em0="DHCP") until login appears. 4) Attach the cable to the NIC. 5) Voila... no link. -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
Am Mon, 4 Aug 2008 03:23:07 -0700 schrieb Jeremy Chadwick <[EMAIL PROTECTED]>: > When I return to work on Wednesday night, I'll try to reproduce what > you see (we have Juniper, Cisco, Extreme, and Netgear switches > there), then bring the laptop home and test against a D-Link switch, > as well as my ProCurve. Hi Jeremy, I'm trying some other things here. Before you waste time on PEBKAC problems ;) (which I now suspect to be). Let me try to install the latest GENERIC on my laptop first. I have made some modifications with polling and some other stuff like HZ and zero copy sockets. I tried several things now: Windows XP worked fine. Ubuntu also. FreeBSD 7.0R install CD works, too. Of course, there might be some other things from userland that cause the problem and that don't run during install (powerd?). I have to check it first to narrow down the problem. Thanks to all people here for helping me so far. I would not get that many ideas what to look at, if I hadn't asked. Sometimes, I expect too much to run flawlessly together, I think. I will tell more when I have checked the things I mentioned. -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
2008/8/4 Jeremy Chadwick <[EMAIL PROTECTED]>: > On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote: >> Martin <[EMAIL PROTECTED]> wrote: >> >> > On Sat, 02 Aug 2008 12:55:53 +0200 >> > Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: >> > >> >> Just to be sure: also if the first command you try on the interface is >> >> 'ifconfig up'? >> > >> > Hello Torfinn, >> > >> > good point, no. The problem appears when the first thing called on this >> > interface is dhclient (caused by ifconfig_em0="DHCP"). I could also >> > provoke this behavior after the interface was once up had an IP and was >> > working (ping). All I need to do is to disconnect the NIC from the >> > switch when I type "/etc/rc.d/netif restart". >> > >> > I have noticed further strange effects here. The behavior seems to >> > be even more complex. >> > >> > After I typed "/etc/rc.d/netif restart", I waited until I get "giving >> > up" message. Then I plugged the cable in. After about 30 seconds the >> > link LED was on. I noticed that at this point I couldn't get an address >> > using DHCP. >> > >> > So I disconnected physically the NIC (no cable) and link LED was >> > still on! ifconfig showed me "state: active" with no cable plugged in. >> > After further 30 seconds the LED went off. >> > >> > I attached the NIC again to the switch again and after 30 seconds >> > again I got some other effect. The link LED went on (status: active) >> > and the data LED was permanently blinking (about 2,5 times a second). I >> > pulled the cable again and now the link LED is still on and the data >> > LED still blinking (since about 10 minutes already). >> > >> > By the way... >> > Now I'm typing this E-Mail without an ethernet cable plugged in and the >> > link status LED is still on and the other data LED is blinking. >> > >> > -- >> > Martin >> > >> I may have misunderstood the purpose of this, but do you have the bpf >> compiled into your kernel? If you're having DHCP troubles, this could >> be a problem. > > I have never seen "device bpf" cause any sort of DHCP-related problems > on FreeBSD. > > Can you expand on this, and provide reference material confirming such? > > -- > | Jeremy Chadwickjdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > Sorry, I was referring to the possible absence of it. Ref: http://www.freebsd.org/doc/en/books/handbook/network-dhcp.html , section 27.5.4: "Make sure that the bpf device is compiled into your kernel. To do this, add device bpf to your kernel configuration file, and rebuild the kernel." Chris -- R< $&h ! > $- ! $+ $@ $2 < @ $1 .UUCP. > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 11:00:16AM +0100, Chris Rees wrote: > Martin <[EMAIL PROTECTED]> wrote: > > > On Sat, 02 Aug 2008 12:55:53 +0200 > > Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: > > > >> Just to be sure: also if the first command you try on the interface is > >> 'ifconfig up'? > > > > Hello Torfinn, > > > > good point, no. The problem appears when the first thing called on this > > interface is dhclient (caused by ifconfig_em0="DHCP"). I could also > > provoke this behavior after the interface was once up had an IP and was > > working (ping). All I need to do is to disconnect the NIC from the > > switch when I type "/etc/rc.d/netif restart". > > > > I have noticed further strange effects here. The behavior seems to > > be even more complex. > > > > After I typed "/etc/rc.d/netif restart", I waited until I get "giving > > up" message. Then I plugged the cable in. After about 30 seconds the > > link LED was on. I noticed that at this point I couldn't get an address > > using DHCP. > > > > So I disconnected physically the NIC (no cable) and link LED was > > still on! ifconfig showed me "state: active" with no cable plugged in. > > After further 30 seconds the LED went off. > > > > I attached the NIC again to the switch again and after 30 seconds > > again I got some other effect. The link LED went on (status: active) > > and the data LED was permanently blinking (about 2,5 times a second). I > > pulled the cable again and now the link LED is still on and the data > > LED still blinking (since about 10 minutes already). > > > > By the way... > > Now I'm typing this E-Mail without an ethernet cable plugged in and the > > link status LED is still on and the other data LED is blinking. > > > > -- > > Martin > > > I may have misunderstood the purpose of this, but do you have the bpf > compiled into your kernel? If you're having DHCP troubles, this could > be a problem. I have never seen "device bpf" cause any sort of DHCP-related problems on FreeBSD. Can you expand on this, and provide reference material confirming such? -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 11:34:48AM +0200, Martin wrote: > On Sat, 2 Aug 2008 10:34:47 -0700 > "Jack Vogel" <[EMAIL PROTECTED]> wrote: > > > 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. > > Hi Jack, > > this is a Lenovo Thinkpad T60p model 2007-93G. It's the standard > built-in NIC by Lenovo on the mainboard. I also have a T60p (though a different model/type number). Note that the BIOSes for the T60p have historically documented numerous changes to how the NIC is initialised and "fiddled with", **especially** if PXE booting is enabled (regardless if a PXE boot itself is performed or not). My employer sent a company-wide message to all owners of the T60p asking that they upgrade their BIOS solely to address link negotiation failures occasionally seen when PXE booting. Meaning: I would not be surprised if this issue proved to be something specific to Lenovo laptops, possibly this model. When I return to work on Wednesday night, I'll try to reproduce what you see (we have Juniper, Cisco, Extreme, and Netgear switches there), then bring the laptop home and test against a D-Link switch, as well as my ProCurve. I can tell you that I have absolutely no problems under Windows Vista when pulling the CAT5 cable out and reinserting it; and yes, DHCP is used. (I do this literally on a nightly basis, which is how/why I'm so sure.) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Martin <[EMAIL PROTECTED]> wrote: > On Sat, 02 Aug 2008 12:55:53 +0200 > Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: > >> Just to be sure: also if the first command you try on the interface is >> 'ifconfig up'? > > Hello Torfinn, > > good point, no. The problem appears when the first thing called on this > interface is dhclient (caused by ifconfig_em0="DHCP"). I could also > provoke this behavior after the interface was once up had an IP and was > working (ping). All I need to do is to disconnect the NIC from the > switch when I type "/etc/rc.d/netif restart". > > I have noticed further strange effects here. The behavior seems to > be even more complex. > > After I typed "/etc/rc.d/netif restart", I waited until I get "giving > up" message. Then I plugged the cable in. After about 30 seconds the > link LED was on. I noticed that at this point I couldn't get an address > using DHCP. > > So I disconnected physically the NIC (no cable) and link LED was > still on! ifconfig showed me "state: active" with no cable plugged in. > After further 30 seconds the LED went off. > > I attached the NIC again to the switch again and after 30 seconds > again I got some other effect. The link LED went on (status: active) > and the data LED was permanently blinking (about 2,5 times a second). I > pulled the cable again and now the link LED is still on and the data > LED still blinking (since about 10 minutes already). > > By the way... > Now I'm typing this E-Mail without an ethernet cable plugged in and the > link status LED is still on and the other data LED is blinking. > > -- > Martin > I may have misunderstood the purpose of this, but do you have the bpf compiled into your kernel? If you're having DHCP troubles, this could be a problem. Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Sat, 2 Aug 2008 10:34:47 -0700 "Jack Vogel" <[EMAIL PROTECTED]> wrote: > 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. Hi Jack, this is a Lenovo Thinkpad T60p model 2007-93G. It's the standard built-in NIC by Lenovo on the mainboard. > There should be NO need to specify full duplex, if you have to do > that then you have some problem with your switch. No, I don't have to specify full duplex. Earlier someone has asked me if it might be some problem with the autonegotiation. I don't think it is. > Are you loading the driver as a module, or is it static? 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?? Ok, I've done that. I connected my laptop directly to my home router. At the other side we have an xl(4) NIC, btw. Faulty variant: 1) Boot with cable disconnected. DHCP fails, of course, which is ok. 2) I plug in the cable where on the other side sits xl(4). ifconfig shows me "no carrier", all LEDs at the NIC are off. No way to get an IP. No way to get "status: active", by "ifconfig em0 up/down". Ok: 1) Boot with cable directly connected to xl(4) at the other side. 2) em0 gets instantly an IP from DHCP server running on xl(4). -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Mon, Aug 04, 2008 at 10:53:35AM +0200, Martin wrote: > Am Sat, 2 Aug 2008 16:01:35 -0700 > schrieb "Jack Vogel" <[EMAIL PROTECTED]>: > > > After I typed "/etc/rc.d/netif restart", I waited until I get > > > "giving up" message. Then I plugged the cable in. After about 30 > > > seconds the link LED was on. I noticed that at this point I > > > couldn't get an address using DHCP. > > > > Well DUH, the agent exited, thats why it said "giving up" :) > > That ain't complex behavior, its behaving as designed. > > I'm describing the circumstances WHEN everything happens. I was trying > to show you that even the cable is plugged in you cannot get an IP. The > NIC is in a kind of "dead" state. > > > Ya, so the update is slow, the fact that the LED is blinking means you > > have an autoneg failure, so again, its your switch not the NIC. > > I have this problem with every kind of switch. > > The switch at home is a 100Mbit switch made by Digitus (5-port). Can you try repeating the problem under Linux? It may be a bit much to ask, but I believe there's an Ubuntu Live CD you can download + burn + boot. You could try repeating the behaviour there. If it's identical, or at least "still broken", then it's less likely FreeBSD's fault. > > Let me guess, you have some 100Mb home router and you are trying > > to plug a gig nic into it and forcing the speed maybe? > > This is true except for the "forcing the speed" part. It's set to > "media: Ethernet autoselect". Which means it's using auto-neg, which Jack says (based on the information he has) may be failing upon link loss + reconnect. As described, auto-negotiation has to be properly implemented on both the NIC/PHY and on the switch, as well as handled properly in the NIC driver. I can tell you that in the case of the Intel 82573E and FreeBSD's em(4) driver (version 6.x.x), auto-neg is performed properly, including when link is lost/cable pulled. I've personally tested this on numerous consumer switches (D-Link, Linksys, and Hawking Technologies), as well as enterprise switches (specifically ProCurve and Cisco). I can tell you that I've seen odd speed negotiation failures with Netgear consumer switches (100mbit being chosen instead of gigE). In fact, this weekend in my home, I just migrated from a D-Link switch to an HP ProCurve switch. I powered off one switch, installed the new one, powered it on, and link came up. Took a couple minutes. But then I decided to re-organise some of my cabling, which caused another disconnect. Here's evidence: em0: port 0x4000-0x401f mem 0xe800-0xe801 irq 16 at device 0.0 on pci13 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: 00:30:48:97:25:40 [EMAIL PROTECTED]:13:0:0:class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = '82573E Intel Corporation 82573E Gigabit Ethernet Controller (Copper)' class = network subclass = ethernet icarus# bzgrep "kernel: em0" /var/log/all.log.3.bz2 Jul 31 06:28:23 icarus kernel: em0: link state changed to DOWN Jul 31 06:30:17 icarus kernel: em0: link state changed to UP Jul 31 06:32:36 icarus kernel: em0: link state changed to DOWN Jul 31 06:32:53 icarus kernel: em0: link state changed to UP And absolutely no problems: icarus# netstat -in -I em0 NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll em01500 00:30:48:97:25:40 32941661 0 34620277 0 0 em01500 192.168.1.0/2 192.168.1.51 32915748 - 35942133 - - icarus# ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=19b ether 00:30:48:97:25:40 inet 192.168.1.51 netmask 0xff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseTX ) status: active What I'm saying is "I don't know what to tell you". I'm not doubting your claims, but it would be worthwhile to test on Linux to see if it's a FreeBSD driver issue, something with the NIC/PHY, the way the NIC/PHY is implemented on the computer, or even the cable (yes really!). I'd start with the obvious: try replacing the cable, and go with a CAT5e cable that's pre-made (rather than self-rolled, if you're using such). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Am Sat, 02 Aug 2008 23:50:10 +0200 schrieb Torfinn Ingolfsen <[EMAIL PROTECTED]>: > On Sat, 02 Aug 2008 22:40:46 +0200 > Martin <[EMAIL PROTECTED]> wrote: > > > good point, no. The problem appears when the first thing called on > > this interface is dhclient (caused by ifconfig_em0="DHCP"). I could > > So, if you don't automatically configure the interface, but instead do > something like: > 'ifconfig em0 up' > and then the DHCP stuff > does the interface work then? Hi Torfinn, I've put "/sbin/ifconfig em0 up" into rc.local. Now the behavior is slightly different. Steps: 1) I switch laptop on with cable unplugged. Everything ok (DHCP failed, of course; this is normal). 2) I plug the cable in: "state: active". Yay! This is OK! 3) NIC does not get IP (one time it got the correct IP but the it lost it again, I could see by repeatedly typing "ifconfig em0"). 4) I kill the dhclient. 5) I manually start "dhclient em0". No response (DHCPREQUEST, DHCPDISCOVER, does not finish). 6) I start "ifconfig em0 down" and once again "dhclient em0" (this time without "ifconfig em0 up"!). 7) Got an IP, without delays (as it should be). -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
Am Sat, 2 Aug 2008 16:01:35 -0700 schrieb "Jack Vogel" <[EMAIL PROTECTED]>: Hi, > > After I typed "/etc/rc.d/netif restart", I waited until I get > > "giving up" message. Then I plugged the cable in. After about 30 > > seconds the link LED was on. I noticed that at this point I > > couldn't get an address using DHCP. > > Well DUH, the agent exited, thats why it said "giving up" :) > That ain't complex behavior, its behaving as designed. I'm describing the circumstances WHEN everything happens. I was trying to show you that even the cable is plugged in you cannot get an IP. The NIC is in a kind of "dead" state. > Ya, so the update is slow, the fact that the LED is blinking means you > have an autoneg failure, so again, its your switch not the NIC. I have this problem with every kind of switch. The switch at home is a 100Mbit switch made by Digitus (5-port). > Let me guess, you have some 100Mb home router and you are trying > to plug a gig nic into it and forcing the speed maybe? This is true except for the "forcing the speed" part. It's set to "media: Ethernet autoselect". > I asked for a hardware list, now that includes the switch. Digitus DN-5001C: http://www.amazon.de/Assmann-Digitus-DN-5001C-Switch-Fast/dp/B0009FHTWI -- Martin signature.asc Description: PGP signature
Re: em(4) on FreeBSD is sometimes annoying
On Sat, Aug 2, 2008 at 1:40 PM, Martin <[EMAIL PROTECTED]> wrote: > On Sat, 02 Aug 2008 12:55:53 +0200 > Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: > >> Just to be sure: also if the first command you try on the interface is >> 'ifconfig up'? > > Hello Torfinn, > > good point, no. The problem appears when the first thing called on this > interface is dhclient (caused by ifconfig_em0="DHCP"). I could also > provoke this behavior after the interface was once up had an IP and was > working (ping). All I need to do is to disconnect the NIC from the > switch when I type "/etc/rc.d/netif restart". > > I have noticed further strange effects here. The behavior seems to > be even more complex. > > After I typed "/etc/rc.d/netif restart", I waited until I get "giving > up" message. Then I plugged the cable in. After about 30 seconds the > link LED was on. I noticed that at this point I couldn't get an address > using DHCP. Well DUH, the agent exited, thats why it said "giving up" :) That ain't complex behavior, its behaving as designed. > So I disconnected physically the NIC (no cable) and link LED was > still on! ifconfig showed me "state: active" with no cable plugged in. > After further 30 seconds the LED went off. > > I attached the NIC again to the switch again and after 30 seconds > again I got some other effect. The link LED went on (status: active) > and the data LED was permanently blinking (about 2,5 times a second). I > pulled the cable again and now the link LED is still on and the data > LED still blinking (since about 10 minutes already). Ya, so the update is slow, the fact that the LED is blinking means you have an autoneg failure, so again, its your switch not the NIC. Let me guess, you have some 100Mb home router and you are trying to plug a gig nic into it and forcing the speed maybe? I asked for a hardware list, now that includes the switch. Jack ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Sat, 02 Aug 2008 22:40:46 +0200 Martin <[EMAIL PROTECTED]> wrote: > good point, no. The problem appears when the first thing called on > this interface is dhclient (caused by ifconfig_em0="DHCP"). I could So, if you don't automatically configure the interface, but instead do something like: 'ifconfig em0 up' and then the DHCP stuff does the interface work then? -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Sat, 02 Aug 2008 12:55:53 +0200 Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote: > Just to be sure: also if the first command you try on the interface is > 'ifconfig up'? Hello Torfinn, good point, no. The problem appears when the first thing called on this interface is dhclient (caused by ifconfig_em0="DHCP"). I could also provoke this behavior after the interface was once up had an IP and was working (ping). All I need to do is to disconnect the NIC from the switch when I type "/etc/rc.d/netif restart". I have noticed further strange effects here. The behavior seems to be even more complex. After I typed "/etc/rc.d/netif restart", I waited until I get "giving up" message. Then I plugged the cable in. After about 30 seconds the link LED was on. I noticed that at this point I couldn't get an address using DHCP. So I disconnected physically the NIC (no cable) and link LED was still on! ifconfig showed me "state: active" with no cable plugged in. After further 30 seconds the LED went off. I attached the NIC again to the switch again and after 30 seconds again I got some other effect. The link LED went on (status: active) and the data LED was permanently blinking (about 2,5 times a second). I pulled the cable again and now the link LED is still on and the data LED still blinking (since about 10 minutes already). By the way... Now I'm typing this E-Mail without an ethernet cable plugged in and the link status LED is still on and the other data LED is blinking. -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Fri, Aug 1, 2008 at 9:47 PM, Martin <[EMAIL PROTECTED]> wrote: > On Fri, 1 Aug 2008 09:24:53 -0700 > "Jack Vogel" <[EMAIL PROTECTED]> 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: > > [EMAIL PROTECTED]:2:0:0: class=0x02 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 metric 0 mtu > 1500 options=19b >ether xx:xx:xx:xx:xx:xx >media: Ethernet autoselect >status: no carrier > > All LEDs are off. > > Device was found on boot: > > em0: port 0x3000-0x301f > mem 0xee000 000-0xee01 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Sat, 02 Aug 2008 07:00:15 +0200 Martin <[EMAIL PROTECTED]> wrote: > Once again. I made a mistake describing the problem. I'm really sorry > for this. The interface actually appears in the ifconfig list, but I > cannot get it up. It always shows "no carrier". No matter what I try. Just to be sure: also if the first command you try on the interface is 'ifconfig up'? -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Fri, 1 Aug 2008 05:42:24 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote: Hi Jeremy, > Most commonly what you're reporting is the result of a switch upstream > which isn't fully compatible or properly doing 802.3u auto-neg. It is attached to a cheap switch here. Also at my office it is not coming up. And I have NEVER this problem when the laptop is already plugged in. > Rebooting the machine (thus tearing down link hard, and resetting the > entire chip) often works in this situation. You can also try setting > the speed and duplex (media and mediaopt) in your ifconfig_emX line in > rc.conf to see if that helps (on some switches it does). This is what I get, when I plug it in and try to configure something: # ifconfig em0 mediaopt full-duplex ifconfig: SIOCSIFMEDIA (media): Device not configured But it accepts up, down and even inet . LEDs are off and still "no carrier". > The behaviour you're reporting I've seen on old 3Com XL 509x cards with > Cisco switches, for example. I've heard of the autonegotiation problem, but it rather looks to my as if something is getting initialized during BIOS boot and FreeBSD is not doing it correctly. > I have a Thinkpad T60p. I'll try booting FreeBSD on it next week and > see if I can reproduce the behaviour. I'll also include what switch > brands/models are being plugged into. Once again. I made a mistake describing the problem. I'm really sorry for this. The interface actually appears in the ifconfig list, but I cannot get it up. It always shows "no carrier". No matter what I try. -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Fri, 1 Aug 2008 09:24:53 -0700 "Jack Vogel" <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]:2:0:0:class=0x02 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 metric 0 mtu 1500 options=19b ether xx:xx:xx:xx:xx:xx media: Ethernet autoselect status: no carrier All LEDs are off. Device was found on boot: em0: port 0x3000-0x301f mem 0xee000 000-0xee01 irq 16 at device 0.0 on pci2 em0: Using MSI interrupt em0: [FILTER] em0: Ethernet address: xx:xx:xx:xx:xx:xx -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
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. Jack On Fri, Aug 1, 2008 at 7:43 AM, Robert Watson <[EMAIL PROTECTED]> wrote: > > On Fri, 1 Aug 2008, Martin wrote: > >> I don't remember anymore when I reported it the first time. I think it was >> around 4.x or something like that. The em(4) bug is still there after years. >> >> Hasn't anyone really noticed yet that em(4) only appears when you boot >> FreeBSD with the interface physically attached to a switch for example? If >> you attach it later, after boot up, the interface won't power up and appear >> in the interface list (ifconfig)? > > The card range supported by the if_em driver is huge, so it wouldn't be > surprising if this is a hardware bug affecting a relatively narrow line of > parts. I've added Jack Vogel to the CC line, as he's the Intel developer > responsible for maintaining our if_em driver. I don't promise he can help > either, but it's worth a try :-). > > Robert > >> >> Steps to reproduce: >> 1) Switch your PC/laptop off. Really OFF, no reboot. >> 2) Disconnect the em(4) NIC from your switch. >> 3) Boot FreeBSD. >> 4) Plug in the ethernet cable. >> 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) >> unless you reboot your machine. >> >> Something is not being initialized properly on em(4) devices, it seems. >> >> I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's >> extremely annoying on Thinkpads, when you just want to plug in your >> laptop somewhere. >> >> -- >> Martin >> > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Fri, 1 Aug 2008, Martin wrote: I don't remember anymore when I reported it the first time. I think it was around 4.x or something like that. The em(4) bug is still there after years. Hasn't anyone really noticed yet that em(4) only appears when you boot FreeBSD with the interface physically attached to a switch for example? If you attach it later, after boot up, the interface won't power up and appear in the interface list (ifconfig)? The card range supported by the if_em driver is huge, so it wouldn't be surprising if this is a hardware bug affecting a relatively narrow line of parts. I've added Jack Vogel to the CC line, as he's the Intel developer responsible for maintaining our if_em driver. I don't promise he can help either, but it's worth a try :-). Robert Steps to reproduce: 1) Switch your PC/laptop off. Really OFF, no reboot. 2) Disconnect the em(4) NIC from your switch. 3) Boot FreeBSD. 4) Plug in the ethernet cable. 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) unless you reboot your machine. Something is not being initialized properly on em(4) devices, it seems. I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's extremely annoying on Thinkpads, when you just want to plug in your laptop somewhere. -- Martin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
Hi, On 1 Aug 2008, at 13:20, Martin wrote: Hello, I don't remember anymore when I reported it the first time. I think it was around 4.x or something like that. The em(4) bug is still there after years. Hasn't anyone really noticed yet that em(4) only appears when you boot FreeBSD with the interface physically attached to a switch for example? If you attach it later, after boot up, the interface won't power up and appear in the interface list (ifconfig)? Steps to reproduce: 1) Switch your PC/laptop off. Really OFF, no reboot. 2) Disconnect the em(4) NIC from your switch. 3) Boot FreeBSD. 4) Plug in the ethernet cable. 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) unless you reboot your machine. Something is not being initialized properly on em(4) devices, it seems. I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's extremely annoying on Thinkpads, when you just want to plug in your laptop somewhere. Well it's not a problem for my TP T41 (just tested with 5.0R and 7.0R), the NIC probes as: Version - 6.7.3> and I've never seen it on sundry other boxes with em. That doesn't mean it can't happen, of course. -- Martin -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED]fax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
On Fri, Aug 01, 2008 at 02:20:05PM +0200, Martin wrote: > I don't remember anymore when I reported it the first time. I think it > was around 4.x or something like that. The em(4) bug is still there > after years. > > Hasn't anyone really noticed yet that em(4) only appears when you boot > FreeBSD with the interface physically attached to a switch for example? > If you attach it later, after boot up, the interface won't power up and > appear in the interface list (ifconfig)? > > Steps to reproduce: > 1) Switch your PC/laptop off. Really OFF, no reboot. > 2) Disconnect the em(4) NIC from your switch. > 3) Boot FreeBSD. > 4) Plug in the ethernet cable. > 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) > unless you reboot your machine. > > Something is not being initialized properly on em(4) devices, it seems. Generally speaking (with my other NICs, specifically Pro/1000 NICs), I have not seen this behaviour. The em(4) driver behaves very well and does 802.3u auto-neg of speed/duplex properly. I have used many different revisions of Pro/1000 on FreeBSD and haven't seen this behaviour. Most commonly what you're reporting is the result of a switch upstream which isn't fully compatible or properly doing 802.3u auto-neg. Rebooting the machine (thus tearing down link hard, and resetting the entire chip) often works in this situation. You can also try setting the speed and duplex (media and mediaopt) in your ifconfig_emX line in rc.conf to see if that helps (on some switches it does). The behaviour you're reporting I've seen on old 3Com XL 509x cards with Cisco switches, for example. I gladly await more flame mails from people telling me "Yes, that is a known problem with Cisco switches in the past, but it does not happen any more", but even present-day Cisco switches we use at our workplace (alongside em(4) NICs) behave erroneously just like "in the past". *shrug* Everyone has a different experience. > I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's > extremely annoying on Thinkpads, when you just want to plug in your > laptop somewhere. I have a Thinkpad T60p. I'll try booting FreeBSD on it next week and see if I can reproduce the behaviour. I'll also include what switch brands/models are being plugged into. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: em(4) on FreeBSD is sometimes annoying
> Hasn't anyone really noticed yet that em(4) only appears when you boot > FreeBSD with the interface physically attached to a switch for example? > If you attach it later, after boot up, the interface won't power up and > appear in the interface list (ifconfig)? I'm afraid I don't see your problem at all. My em interfaces appear as they should, even if not connected to a switch. And when I connect an em interface to a switch, I get link and things work as expected. > Steps to reproduce: > 1) Switch your PC/laptop off. Really OFF, no reboot. > 2) Disconnect the em(4) NIC from your switch. > 3) Boot FreeBSD. > 4) Plug in the ethernet cable. > 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) > unless you reboot your machine. > > Something is not being initialized properly on em(4) devices, it seems. This may well be the case - but not that the em driver handles several different chip models. You may have a problem which is specific to one or a few chip models. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
em(4) on FreeBSD is sometimes annoying
Hello, I don't remember anymore when I reported it the first time. I think it was around 4.x or something like that. The em(4) bug is still there after years. Hasn't anyone really noticed yet that em(4) only appears when you boot FreeBSD with the interface physically attached to a switch for example? If you attach it later, after boot up, the interface won't power up and appear in the interface list (ifconfig)? Steps to reproduce: 1) Switch your PC/laptop off. Really OFF, no reboot. 2) Disconnect the em(4) NIC from your switch. 3) Boot FreeBSD. 4) Plug in the ethernet cable. 5) Tataa! All leds at the NIC stay off. You won't be able to use em(4) unless you reboot your machine. Something is not being initialized properly on em(4) devices, it seems. I have had 3 of 3 em(4) NICs so far, where this bug shows up. And it's extremely annoying on Thinkpads, when you just want to plug in your laptop somewhere. -- Martin signature.asc Description: PGP signature
