Date: Fri, 11 Nov 2011 16:27:27 -0800 From: YongHyeon PYUN <pyunyh@gmail.com> To: rank1seeker@gmail.com Cc: freebsd-acpi@freebsd.org, hackers@freebsd.org Subject: Re: Adventure into S3 state and back Message-ID: <20111112002727.GD17792@michelle.cdnetworks.com> In-Reply-To: <20111110.182948.630.1@DOMY-PC> References: <20111110.182948.630.1@DOMY-PC>
next in thread | previous in thread | raw e-mail | index | archive | help
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: <Logitech> 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: <Logitech> at usbus3 > ukbd0: <Logitech USB Receiver, class 0/0, rev 2.00/12.01, addr 2> on usbus3 > kbd2 at ukbd0 > ums0: <Logitech USB Receiver, class 0/0, rev 2.00/12.01, addr 2> on usbus3 > ums0: 16 buttons and [XYZT] coordinates ID=2 > uhid0: <Logitech USB Receiver, class 0/0, rev 2.00/12.01, addr 2> 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<UP,RUNNING,PROMISC> metric 0 mtu 33152 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > options=3<RXCSUM,TXCSUM> > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=3<PERFORMNUD,ACCEPT_RTADV> > cruiser# ifconfig > bge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > options=8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTATE> > 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) > > ... ... ... <You get the point> Known issue. kern/136876. Mobile bge(4) controllers seem to have this issue. > ---- > > 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 > > > > Domagoj Smol?i? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111112002727.GD17792>