From owner-freebsd-current@FreeBSD.ORG Fri Jul 17 22:09:24 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 9CDCF1065670 for ; Fri, 17 Jul 2009 22:09:24 +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 1A6948FC1D for ; Fri, 17 Jul 2009 22:09:23 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by bwz4 with SMTP id 4so881788bwz.43 for ; Fri, 17 Jul 2009 15:09:23 -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=jHYehJttAQI7HhddrVbG2ZoeVPANmri9aWX4ScLmFrg=; b=gcQKLIY+Gbmru7LrT2cOdAWQFhPs/IM77BTJ4U4gvZufTKf27OjpIg0g4Sfo/6TpYZ OG7gat+5nTuWNolhii5EqWwO+mmBrxSE6ELSpYimkMNSWE+4SjzPCOzdSC2STVfE23vV mExkkMPOL58T4k/72b8f9SZZyvJ2pNMn4p3IU= 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=GQj1pnDXYM81s6n3cQle5bDuMvaor42gBw+ni9aXqfqP8Bup35BW1LKHhRNZjJhvau Lcf/8NLxuBc8F80m63AYTw0ZNJBNM6jWpDxPEnj6Ag7qAMBZSe06y7gY3Eckwbprl8oy XrOXjDcSLR1wfydxAQvnNJSS3uWSDZ35MoP9Y= MIME-Version: 1.0 Received: by 10.204.59.73 with SMTP id k9mr1355787bkh.167.1247868562944; Fri, 17 Jul 2009 15:09:22 -0700 (PDT) In-Reply-To: <200907171743.11143.gnemmi@gmail.com> References: <4A5D27F2.50208@voicenet.com> <3a142e750907150020h712bfcecq89d5ccf3e00e302c@mail.gmail.com> <200907150713.47807.adamk@voicenet.com> <200907171743.11143.gnemmi@gmail.com> Date: Sat, 18 Jul 2009 00:09:22 +0200 Message-ID: <3a142e750907171509o62c999c5o446bcd7cd576b9a5@mail.gmail.com> From: "Paul B. Mahol" To: Gonzalo Nemmi Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Adam K Kirchhoff 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: Fri, 17 Jul 2009 22:09:24 -0000 On 7/17/09, Gonzalo Nemmi wrote: > On Wednesday 15 July 2009 8:13:47 am Adam K Kirchhoff wrote: >> On Wednesday 15 July 2009 03:20:45 Paul B. Mahol wrote: >> > 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/0090 >> > >23.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. >> >> Unfortunately, after doing this, reloading the if_bge driver causes >> the laptop to completely lock up... It gets as far as: >> >> bge0: > rev. 0xffff> >> mem 0xdfdf0000-0xdfdfffff irq 16 at device 0.0 on pci2 >> >> And then the entire machine hangs. I'm on ttyv0, so I'd see any >> kernel panic, but nothing like that happens. The screen stays on, >> but nothing else happens till I force a reboot. >> >> Adam > > Hi Adam, Paul ... > I'm the "another individual" from you OP. > I have the same problems you have regarding bge, but they weren't > trumped .. I just had an order of priorities ;) > > Anyways, I tried the solution Paul posted and, just as in your case, I > got a hard lock too ... > > I tried loading if_bge through /boot/loader.conf > Then issued a: > > kldunload if_bge coretemp coretemp is wrong module, it must be one of modules that attach to pci. > acpiconf -s 3 > > machine suspended > > As soon as I woke it up I got the following message followed by a hard > lock: > > fwohci0: Phy 1394a available S400, 1 ports. > fwohci0: Link S400, max_rec 2048 bytes. > fwohci0: Initiate bus reset > fwohci0: fwohci_intr_core: BUS reset > fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=1, > CYCLEMASTER mode > firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) > firewire0: bus manager 0 > fwohci0: unrecoverable error > bge0: 0xffff> mem 0xf69f0000-0xf69fffff irq 17 at device 0.0 on pci9 > > All this happens on a Dell 1318, FreeBSD 8.0-BETA1, i386, Intel(R) > Celeron(R) CPU 560@2.13GHz. > > bge0@pci0:9:0:0: class=0x020000 card=0x02861028 chip=0x171314e4 rev=0x02 > hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'Broadcom NetLink (TM) Fast Ethernet (BCM5906m)' > class = network > subclass = ethernet > bar [10] = type Memory, range 64, base 0xf69f0000, size 65536, > enabled > cap 01[48] = powerspec 3 supports D0 D3 current D0 > cap 03[50] = VPD > cap 09[58] = vendor (length 120) > cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) > > If somebody needs more info, just ask me for it and I'll try to answer > as soon as I can. > > Adam, if you do file a PR, please let me know so I can follow it. > > Best Regards > -- > Blessings > Gonzalo Nemmi > -- Paul