From owner-freebsd-current@FreeBSD.ORG Wed Jul 15 00:50:59 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC6211065673 for ; Wed, 15 Jul 2009 00:50:59 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 01DFB8FC15 for ; Wed, 15 Jul 2009 00:50:58 +0000 (UTC) (envelope-from adamk@voicenet.com) Received: from OMTA06.westchester.pa.mail.comcast.net ([76.96.62.51]) by QMTA08.westchester.pa.mail.comcast.net with comcast id G0eU1c00716LCl0580qzpd; Wed, 15 Jul 2009 00:50:59 +0000 Received: from sorrow.ashke.com ([68.45.151.98]) by OMTA06.westchester.pa.mail.comcast.net with comcast id G0qz1c00F27dlBY3S0qzRQ; Wed, 15 Jul 2009 00:50:59 +0000 Message-ID: <4A5D27F2.50208@voicenet.com> Date: Tue, 14 Jul 2009 20:50:58 -0400 From: Adam K Kirchhoff User-Agent: Thunderbird 2.0.0.22 (X11/20090714) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: bge problems when resuming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2009 00:51:00 -0000 Hello all, I have a Dell Latitude D610 laptop with 8.0-BETA1 installed. I hadn't tried suspend/resume for a while and decided to give it a shot. I was pleasantly surprised to see that I could suspend to ram, resume, and have a (relatively) working system (previously the display would never come back up and the serial console I had hooked up remained dead). Great job to everyone who helped make that possible. The only real issue that I seem to have now is that bge is completely unusable after resume. Another individual seems to have reported similar problems with bge and resume, but he also had other issues that apparently trumped his networking issues: http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009023.html Like him, resuming from suspend gives me: Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 0, val 32768) Jul 14 12:35:53 scroll kernel: bge0: PHY read timed out (phy 1, reg 0, val 0xffffffff) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 24, val 3072) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 23, val 10) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 21, val 12555) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 23, val 8223) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 21, val 38150) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 23, val 16415) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 21, val 5346) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 24, val 1024) Jul 14 12:35:53 scroll kernel: bge0: PHY write timed out (phy 1, reg 24, val 7) And so on and so forth. I thought that compiling if_bge as a module, unloading it before suspend, and reloading it after resume, might get this working. However, doing a "kldload if_bge" after the resume does nothing. Well, the module gets loaded, but the device doesn't show up. No errors from kldload, and there is nothing new in dmesg. Before the suspend, the device shows up as: bge0@pci0:2:0:0: class=0x020000 card=0x01821028 chip=0x167714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme Gigabit Ethernet PCI Express (BCM5750A1)' class = network subclass = ethernet After resuming, and reloading the module, it's: none1@pci0:2:0:0: class=0x020000 card=0x01821028 chip=0x167714e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'NetXtreme Gigabit Ethernet PCI Express (BCM5750A1)' class = network subclass = ethernet If there are no ideas, I'll go ahead and open up a pr. I assume this is just one bug, since both problems (the PHY issues and the inability to reload the driver) are both related to the network device. Adam