Date: Thu, 27 Mar 2008 17:28:15 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: pyunyh@gmail.com Cc: freebsd-stable@freebsd.org, yongari@freebsd.org Subject: Re: 6.3 nfe: strange behavior after reset Message-ID: <47EBBD0F.8060207@icyb.net.ua> In-Reply-To: <20080226073633.GC47750@cdnetworks.co.kr> References: <47A3041D.5050402@icyb.net.ua> <20080201123603.GA14050@cdnetworks.co.kr> <47A321BB.1060708@icyb.net.ua> <47A32501.7080703@icyb.net.ua> <20080204035242.GA28554@cdnetworks.co.kr> <47C2BC50.5040702@icyb.net.ua> <47C2DBEF.301@icyb.net.ua> <20080226073633.GC47750@cdnetworks.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
on 26/02/2008 09:36 Pyun YongHyeon said the following: > > Nice catch! > The register name in nfe(4) for NvRegMIIMask is NFE_SETUP_R4. > According to Linux driver it's used for generating link state > change interrupt. So I guess nfe(4) may have to clear the > register in nfe_stop(). How about clearing the register as > attached patch? (Sorry I couldn't test this ATM...) Unfortunately, the latest patch didn't make any difference either. So the issue is where it was: do a reboot or a power off / power on cycle - nfe is good, press reset and boot - nfe is silently dead. There is even a stranger thing: in the problematic scenario, if I unload nfe.ko and load nve.ko then the NIC becomes alive, unload nve and re-load nfe NIC is still dead. Mystery. I'll try to do more local debugging later when I have a chance to hit the reset button. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47EBBD0F.8060207>