From owner-freebsd-current@FreeBSD.ORG Wed Jul 15 07:20:47 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 07B941065694 for ; Wed, 15 Jul 2009 07:20:47 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-bw0-f208.google.com (mail-bw0-f208.google.com [209.85.218.208]) by mx1.freebsd.org (Postfix) with ESMTP id 76ECE8FC13 for ; Wed, 15 Jul 2009 07:20:46 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by bwz4 with SMTP id 4so679731bwz.43 for ; Wed, 15 Jul 2009 00:20:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Tfdlb91V+kg0N7vJuG0OTUmTwkGn/abIh8/ENNk6BM0=; b=uNwPCDfioZNDk3ZmYNyZhuuUxeHIPal2okTRwMp3uZmlCfO2oY7yMz7z/YzEKim94h oze7nz/WTvZWQL5F0l7PzDRZZ1/FpAqgvTD34RVNXcTSzvCsfiiqQd20ghYurS3MxNWk SvLHxa4VP2cp9wmDigLCqdJc6X8Zf9uFKD5Gg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=N32+u5gBPhdBaTK3m+ViV89DJ9cvmZaDMk0YhNVFRXkkrWwLVkhBL4jkPplAYvM/+8 Oko6IDRaOCeLC5zg4vrdSu2pX9OIut8MZT9SBPFVIEorQThmFrzUzBB5V3mrMPvTz54g Htqa/lIUEZouqjFj3PZYmma6IlLqfGfqt/yaQ= MIME-Version: 1.0 Received: by 10.204.54.198 with SMTP id r6mr7287262bkg.191.1247642445401; Wed, 15 Jul 2009 00:20:45 -0700 (PDT) In-Reply-To: <4A5D27F2.50208@voicenet.com> References: <4A5D27F2.50208@voicenet.com> Date: Wed, 15 Jul 2009 09:20:45 +0200 Message-ID: <3a142e750907150020h712bfcecq89d5ccf3e00e302c@mail.gmail.com> From: "Paul B. Mahol" To: Adam K Kirchhoff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 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 07:20:47 -0000 On 7/15/09, Adam K Kirchhoff wrote: > > 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. Put this lines into loader.conf and reboot. hw.pci.do_power_nodriver="3" hw.pci.do_power_resume="1" Now, before suspend, unload if_bge and some another driver (sound drivers are best candidate) and load sound driver again, suspend and resume. Now loading if_bge should make it succesfully attach. -- Paul