From owner-cvs-src@FreeBSD.ORG Thu Apr 28 22:50:07 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27D2216A4CF; Thu, 28 Apr 2005 22:50:07 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB34043D2D; Thu, 28 Apr 2005 22:50:06 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j3SMo4bW077581; Thu, 28 Apr 2005 22:50:05 GMT (envelope-from davidxu@freebsd.org) Message-ID: <427168A7.3070702@freebsd.org> Date: Fri, 29 Apr 2005 06:50:15 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050402 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Paul References: <20050426024435.487E516A4CF@hub.freebsd.org> In-Reply-To: <20050426024435.487E516A4CF@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/vge if_vge.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2005 22:50:07 -0000 Bill Paul wrote: >>Bill Paul wrote: >> >> >> >>>>with this change, I got following error on my abit av8: >>>>vge0: port 0xb800-0xb8ff mem >>>>0xf8122000-0xf81220ff irq 22 at device 14.0 on pci0 >>>>vge0: MII read timed out >>>>vge0: failed to start MII autopoll >>>>vge0: MII without any phy! >>>>device_attach: vge0 attach returned 6 >>>> >>>> >>>> >>>> >>>Fine, I took the reload step out. This should fix it. (If reading >>>the RX filter registers instead of the EEPROM makes it mad, then >>>I'll scream.) >>> >>> >>> >>> >>> >>With your lastest change, I still get same error result. >> >> > >I don't believe you. There's no reason why not reading the EEPROM >would break it. Especially since it doesn't break my sample card. >Whatever your problem is, I'm not even going to try to fix it without >access to the hardware, so I guess you just lose. > > I think the reason is I didn't power off the machine after updating, the the chip was in weird state. Now it seems working fine. > > >>>It must not be that important to you since you never bothered to mention >>>this to anyone before. >>> >>>Given all the various things it's complaining about when it fails, >>>it looks like the driver is no longer able to communicate with the device >>>over the PCI bus. All register accesses are failing. This may not be a >>>problem with the driver per-se, but with the PCI bridge. It might be >>>the device has completely locked up, but if vge_reset() doesn't bring >>>it back to life, then I don't know what else to do. >>> >>> >>> >>> >>> >>Without recent change, I can kldunload and kldload it to bring it back >>to work. >> >> > >*sigh* Is there some reason you didn't feel like telling me this the >first time? Why can't people just give me all the information up front >instead of making me drag it out of them. Is it so hard? Do I fix the >bugs by checking in one line of code at a time? No. So why do people >only describe their problems one line at a time? > >-Bill > > > > I am lazy to report the problem since I have an alternative rl0 which works just fine. sorry. :) David Xu