Date: Thu, 14 Aug 2008 20:02:16 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Markus Vervier" <markus@vervier.info> Cc: freebsd-stable@freebsd.org Subject: Re: em(4) on FreeBSD is sometimes annoying Message-ID: <2a41acea0808142002l44541708gf917e65901611231@mail.gmail.com> In-Reply-To: <48A41816.3040904@vervier.info> References: <489C4129.4090303@vervier.info> <200808110819.53914.josh@tcbug.org> <20080811140249.GA27379@eos.sc1.parodius.com> <2a41acea0808110928h10d54441o7d49b11a60406934@mail.gmail.com> <48A0A1D9.8030601@vervier.info> <2a41acea0808111340o7b506804u9e4c95f1af22b95c@mail.gmail.com> <48A2B1CB.7060303@vervier.info> <2a41acea0808130822i5f336b1ci15099f27a3a7c13d@mail.gmail.com> <2a41acea0808131210r6371b532i93f1ae6963d1f1b9@mail.gmail.com> <48A41816.3040904@vervier.info>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <markus@vervier.info> 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 "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0808142002l44541708gf917e65901611231>