Date: Tue, 14 Sep 2004 09:38:02 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: bms@spc.org Cc: freebsd-mobile@freebsd.org Subject: Re: 5.2.1 can't load xl0 driver Message-ID: <20040914.093802.107963883.imp@bsdimp.com> In-Reply-To: <20040914094326.GC809@empiric.icir.org> References: <1095064963.41455d831ff01@postoffice.tpg.com.au> <20040914094326.GC809@empiric.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040914094326.GC809@empiric.icir.org>
Bruce M Simpson <bms@spc.org> writes:
: On Mon, Sep 13, 2004 at 06:42:43PM +1000, adslvmlg@tpg.com.au wrote:
: > After I installed 5.2.1 on my IBM Thinkpad A21P, the system didn't recoganize my
: > 3Com network card during installation. After I reboot the system, the xl0 3Com
: > NIC showed up, and I ifconfig it, and my network is blocked, I can't ping any
: > computer within my network. And then I reboot the system again, the xl0
: > disappeared again. And the system keep doing this to me.
:
: This is a well known issue with the 3Com NIC chips, where they won't
: come out of a PCI D3 power state properly and lose their PCI configuration.
: It can happen across reboots. It often affected me when using an IBM
: ThinkPad T22. See xl(4) for more details.
But the current pci code saves and restores the standard pci
configuration registers because D3 -> D0 state transitions are defined
to reset the device, including things like the BARs in the pci
standard. Is that not sufficient?
Of course, this code went in AFTER 5.2 was branched.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040914.093802.107963883.imp>