Date: Sun, 13 Nov 2011 10:48:10 +0100 From: Lars Engels <lars.engels@0x20.net> To: rank1seeker@gmail.com Cc: pyunyh@gmail.com, freebsd-acpi@freebsd.org, hackers@freebsd.org Subject: Re: Adventure into S3 state and back Message-ID: <20111113094810.GC80782@e-new.0x20.net> In-Reply-To: <20111112.144149.725.1@DOMY-PC> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC>
next in thread | previous in thread | raw e-mail | index | archive | help
--uXxzq0nDebZQVNAZ Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 12, 2011 at 03:41:49PM +0100, rank1seeker@gmail.com wrote: > ----- Original Message ----- > From: YongHyeon PYUN <pyunyh@gmail.com> > 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 >=20 > > On Thu, Nov 10, 2011 at 07:29:48PM +0100, rank1seeker@gmail.com wrote: > > > 8.2-p4 RELEASE amd64 > > >=20 > > > I've built a custom kernel, only with drivers, that I need > > > After resuming from S3 ... > > >=20 > > > 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= =20 > usbus3 > > > kbd2 at ukbd0 > > > ums0: <Logitech USB Receiver, class 0/0, rev 2.00/12.01, addr 2> on= =20 > usbus3 > > > ums0: 16 buttons and [XYZT] coordinates ID=3D2 > > > uhid0: <Logitech USB Receiver, class 0/0, rev 2.00/12.01, addr 2> on= =20 > 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=3D141<UP,RUNNING,PROMISC> metric 0 mtu 33152 > > > lo0: flags=3D8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 > > > options=3D3<RXCSUM,TXCSUM> > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > > > inet6 ::1 prefixlen 128 > > > inet 127.0.0.1 netmask 0xff000000 > > > nd6 options=3D3<PERFORMNUD,ACCEPT_RTADV> > > > cruiser# ifconfig > > > bge0: flags=3D8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500 > > > =20 > options=3D8009b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,LINKSTA= TE> > > > 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) > > >=20 > > > ... ... ... <You get the point> > >=20 > > Known issue. kern/136876. > > Mobile bge(4) controllers seem to have this issue. >=20 > I can see this has been reported, when 8.0-BETA1 was released. > Now is almost 8.3 out and problem is still present >=20 > > > ---- > > >=20 > > > So, taking into account: > > > "A common problem with suspend/resume is that many device drivers do= =20 > not save, restore, or reinitialize their firmware, registers, or device= =20 > memory properly." > > >=20 > > > Next step was to get rid of 'bge' device from my KERNCONF and recompi= le=20 > it. > > > Voila! S3 works! > > >=20 > > > 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: > > >=20 > > > # camcontrol rescan all > > > didn't help > > >=20 > > > I've also tried adding into loader.conf and nada: > > > --- > > > hint.psm.0.flags=3D"0x3000" > > > --- > > > But i think it is PS/2 related > > >=20 > > > What works 100% for a mouse is to unplug and then plug back it's USB= =20 > receiver > > >=20 > > > This is Dell D830 laptop > > >=20 >=20 > How do I solve mouse issue? > It is annoying to unplug and then plug back it's USB receiver, each time. stop moused in rc.suspend and start it in rc.resume. --uXxzq0nDebZQVNAZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk6/kloACgkQKc512sD3afiP4ACfWQNbSYsSVJTm6vdOF2ymiGpd ftkAoLp+sFNEQ8IMx6zpQOz51Ofltiar =mGyx -----END PGP SIGNATURE----- --uXxzq0nDebZQVNAZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111113094810.GC80782>