From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 12 14:41:56 2011 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41B5E106564A; Sat, 12 Nov 2011 14:41:56 +0000 (UTC) (envelope-from rank1seeker@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8C5B08FC17; Sat, 12 Nov 2011 14:41:55 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so5926123bkb.13 for ; Sat, 12 Nov 2011 06:41:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:in-reply-to:references:x-mailer; bh=h55dFzJP1qqQmJrMkhOEQ3d7DINNPTkq+QQ/DX0tW0o=; b=fiscKQ/eWSJu7+U3ETHlSZFOSHKzQZ3jYaCpRdqPoFCg8zaxqxHN2JInxfjNqdB70l qOpQzkJ7H9bNL0zLcNo24GhVshPNnlb8jKTeixghksMD0d/sYqUdc8CX4AsO5QuHWfJ0 by9KKU9NrZ7R1rxPoTuhuLhrXRAvJFciosVWg= Received: by 10.205.128.13 with SMTP id hc13mr4536673bkc.140.1321108914481; Sat, 12 Nov 2011 06:41:54 -0800 (PST) Received: from DOMYPC ([82.193.208.173]) by mx.google.com with ESMTPS id dq2sm17847929bkb.11.2011.11.12.06.41.07 (version=SSLv3 cipher=OTHER); Sat, 12 Nov 2011 06:41:52 -0800 (PST) Message-ID: <20111112.144149.725.1@DOMY-PC> From: rank1seeker@gmail.com To: pyunyh@gmail.com, hackers@freebsd.org, freebsd-acpi@freebsd.org Date: Sat, 12 Nov 2011 15:41:49 +0100 In-Reply-To: <20111112002727.GD17792@michelle.cdnetworks.com> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> X-Mailer: POP Peeper (3.8.0.0) Cc: Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Nov 2011 14:41:56 -0000 ----- Original Message ----- From: YongHyeon PYUN To: rank1seeker@gmail.com Cc: hackers@freebsd.org, freebsd-acpi@freebsd.org Date: Fri, 11 Nov 2011 16:27:27 -0800 Subject: Re: Adventure into S3 state and back > On Thu, Nov 10, 2011 at 07:29:48PM +0100, rank1seeker@gmail.com wrote: > > 8.2-p4 RELEASE amd64 > > > > I've built a custom kernel, only with drivers, that I need > > After resuming from S3 ... > > > > I hit: > > # ifconfig > > and all hells breaks loose: > > ---- > > bge0: PHY read timed out (phy 1, reg 5, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 10, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 25, val 0xffffffff) > > media: Ethernet autoselect > > status: no carrier > > bge0: PHY read timed out (phy 1, reg 1, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 1, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 0, val 0xffffffff) > > ugen3.2: at usbus3 (disconnected) > > ukbd0: at uhub3, port 1, addr 2 (disconnected) > > ums0: at uhub3, port 1, addr 2 (disconnected) > > uhid0: at uhub3, port 1, addr 2 (disconnected) > > bge0: PHY read timed out (phy 1, reg 4, val 0xffffffff) > > ugen3.2: at usbus3 > > ukbd0: on usbus3 > > kbd2 at ukbd0 > > ums0: on usbus3 > > ums0: 16 buttons and [XYZT] coordinates ID=2 > > uhid0: on usbus3 > > bge0: PHY read timed out (phy 1, reg 5, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 10, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 25, val 0xffffffff) > > pflog0: flags=141 metric 0 mtu 33152 > > lo0: flags=8049 metric 0 mtu 16384 > > options=3 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > > inet6 ::1 prefixlen 128 > > inet 127.0.0.1 netmask 0xff000000 > > nd6 options=3 > > cruiser# ifconfig > > bge0: flags=8802 metric 0 mtu 1500 > > options=8009b > > ether 00:21:70:70:01:df > > bge0: PHY read timed out (phy 1, reg 1, val 0xffffffff) > > bge0: PHY read timed out (phy 1, reg 1, val 0xffffffff) > > > > ... ... ... > > Known issue. kern/136876. > Mobile bge(4) controllers seem to have this issue. I can see this has been reported, when 8.0-BETA1 was released. Now is almost 8.3 out and problem is still present > > ---- > > > > So, taking into account: > > "A common problem with suspend/resume is that many device drivers do not save, restore, or reinitialize their firmware, registers, or device memory properly." > > > > Next step was to get rid of 'bge' device from my KERNCONF and recompile it. > > Voila! S3 works! > > > > But another, mouse problem, didn't go away! > > In 9 out of 10 cases, mouse doesn't resume. > > As it is USB mouse, I've did: > > > > # camcontrol rescan all > > didn't help > > > > I've also tried adding into loader.conf and nada: > > --- > > hint.psm.0.flags="0x3000" > > --- > > But i think it is PS/2 related > > > > What works 100% for a mouse is to unplug and then plug back it's USB receiver > > > > This is Dell D830 laptop > > How do I solve mouse issue? It is annoying to unplug and then plug back it's USB receiver, each time.