From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 01:09:24 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09C37106567A for ; Sun, 13 Nov 2011 01:09:24 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (muon.cran.org.uk [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id AEC068FC14 for ; Sun, 13 Nov 2011 01:09:23 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id A2488E65D0 for ; Sun, 13 Nov 2011 01:09:22 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cran.org.uk; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; s=mail; bh=TU4Fz3SbTq1N9Ytnt/tZ8jbrX rc=; b=uS1Hv6m7J6PCYlGMKEh1NXDigj0LgTEmx6+kkgRNr+ydGuJZ+ssTRwAZE eCteQoKYiryx50qvMdPfVd4e3U/EvModEW48Voc+RL+FBZ7x8DHaLobv7Fo2mHBi Bl9ao3LQU7pEMtSVNETFEsjSY6BZhNkZIClgi2Ro67rEwDNgOY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=cran.org.uk; h=message-id :date:from:mime-version:to:subject:content-type :content-transfer-encoding; q=dns; s=mail; b=v3iMMjJRCT38CnN++7N Uv1GrE7rxGBeqED2TcUFypSPRd7USa7e97/jvNZTWzC6Xit1JGU/ByylDK32SjLh kPcdoQ7LsklkgDQXqKCmgVLNEOfpii/qxlyTLYO+ENuIhQv9L4oBKjghB7JDlQ2b KmBym1bYjE1wcjr44zuLJGQ4= Received: from [192.168.1.68] (188-220-36-32.zone11.bethere.co.uk [188.220.36.32]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 8A84FE6472 for ; Sun, 13 Nov 2011 01:09:22 +0000 (GMT) Message-ID: <4EBF18C2.3000909@cran.org.uk> Date: Sun, 13 Nov 2011 01:09:22 +0000 From: Bruce Cran User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: freebsd-acpi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 9.0-RC1 error AE_NO_MEMORY (max_tasks not high enough?) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 01:09:24 -0000 When booting 9.0-RC1 without setting debug.acpi.max_tasks, I get the error: AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable ACPI Error: Method parse/execution failed [\_SB_.PCI0.HEC2.HSCI] (Node 0xfffffe0003c9d5c0), AE_NO_MEMORY (20110527/psparse-560) ACPI Error: Method parse/execution failed [\_GPE._L06] (Node 0xfffffe0003c9d500), AE_NO_MEMORY (20110527/psparse-560) ACPI Exception: AE_NO_MEMORY, while evaluating GPE method [_L06] (20110527/evgpe-606) AcpiOsExecute: failed to enqueue task, consider increasing the debug.acpi.max_tasks tunable Overriding debug.acpi.max_tasks to 2048 causes it to go away though. -- Bruce Cran From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 08:10:11 2011 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0B9C1065673 for ; Sun, 13 Nov 2011 08:10:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 76A4C8FC0C for ; Sun, 13 Nov 2011 08:10:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pAD8ABnX036463 for ; Sun, 13 Nov 2011 08:10:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pAD8AB2T036462; Sun, 13 Nov 2011 08:10:11 GMT (envelope-from gnats) Date: Sun, 13 Nov 2011 08:10:11 GMT Message-Id: <201111130810.pAD8AB2T036462@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 08:10:11 -0000 The following reply was made to PR kern/162491; it has been noted by GNATS. From: Jaakko Heinonen To: Alexey Slynko Cc: bug-followup@FreeBSD.org, avg@FreeBSD.org Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading Date: Sun, 13 Nov 2011 09:49:40 +0200 On 2011-11-11, Alexey Slynko wrote: > My EliteBook 8540p panic on boot after upgrade to 9.0-RC1. I've tried > to unload all kernel modules and load it manually. It was crashed on > acpi_hp loading: > acpi_wmi0: on acpi0 > acpi_wmi1: on acpi0 > panic: make_dev_credv: bad si_name (error=17, si_name=wmistat) I don't really know much about acpi_wmi(4) but obviously it tries to create /dev/wmistat twice here. I am not sure if it's legitimate to have several wmistat device files but you could try this patch: %%% Index: sys/dev/acpi_support/acpi_wmi.c =================================================================== --- sys/dev/acpi_support/acpi_wmi.c (revision 227463) +++ sys/dev/acpi_support/acpi_wmi.c (working copy) @@ -265,7 +265,7 @@ acpi_wmi_attach(device_t dev) acpi_wmi_ec_handler); } else { sc->wmistat_dev_t = make_dev(&wmistat_cdevsw, 0, UID_ROOT, - GID_WHEEL, 0644, "wmistat"); + GID_WHEEL, 0644, "wmistat%d", device_get_unit(dev)); sc->wmistat_dev_t->si_drv1 = sc; sc->wmistat_open_pid = 0; sc->wmistat_bufptr = -1; Index: share/man/man4/acpi_wmi.4 =================================================================== --- share/man/man4/acpi_wmi.4 (revision 227463) +++ share/man/man4/acpi_wmi.4 (working copy) @@ -24,7 +24,7 @@ .\" .\" $FreeBSD$ .\" -.Dd February 8, 2010 +.Dd November 13, 2011 .Dt ACPI_WMI 4 .Os .Sh NAME @@ -49,16 +49,16 @@ The .Nm driver provides an interface for vendor specific WMI implementations (e.g. HP and Acer laptops). -It creates /dev/wmistat, which can be read to get +It creates /dev/wmistat%d, which can be read to get information about GUIDs found in the system. .Sh FILES -.Bl -tag -width /dev/wmistat -compact -.It Pa /dev/wmistat +.Bl -tag -width /dev/wmistat%d -compact +.It Pa /dev/wmistat%d WMI status device. .El .Sh EXAMPLES .Bd -literal -# cat /dev/wmistat +# cat /dev/wmistat0 GUID INST EXPE METH STR EVENT OID {5FB7F034-2C63-45E9-BE91-3D44E2C707E4} 1 NO WMAA NO NO AA {95F24279-4D7B-4334-9387-ACCDC67EF61C} 1 NO NO NO 0x80+ - %%% I have cc'd avg@. He might know something about acpi_wmi(4). -- Jaakko From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 09:40:08 2011 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BAD421065672 for ; Sun, 13 Nov 2011 09:40:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AAEEC8FC0A for ; Sun, 13 Nov 2011 09:40:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pAD9e84t022817 for ; Sun, 13 Nov 2011 09:40:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pAD9e84B022816; Sun, 13 Nov 2011 09:40:08 GMT (envelope-from gnats) Date: Sun, 13 Nov 2011 09:40:08 GMT Message-Id: <201111130940.pAD9e84B022816@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Andriy Gapon Cc: Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andriy Gapon List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 09:40:08 -0000 The following reply was made to PR kern/162491; it has been noted by GNATS. From: Andriy Gapon To: Jaakko Heinonen Cc: Alexey Slynko , bug-followup@FreeBSD.org Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading Date: Sun, 13 Nov 2011 11:35:19 +0200 on 13/11/2011 09:49 Jaakko Heinonen said the following: > On 2011-11-11, Alexey Slynko wrote: >> My EliteBook 8540p panic on boot after upgrade to 9.0-RC1. I've tried >> to unload all kernel modules and load it manually. It was crashed on >> acpi_hp loading: > >> acpi_wmi0: on acpi0 >> acpi_wmi1: on acpi0 >> panic: make_dev_credv: bad si_name (error=17, si_name=wmistat) > > I don't really know much about acpi_wmi(4) but obviously it tries to > create /dev/wmistat twice here. I am not sure if it's legitimate to have > several wmistat device files but you could try this patch: I think that this is the most appropriate patch, thank you! I don't know of any actual usage for /dev/wmistat devices in userland besides cat-ing them and staring in awe at a bunch of GUID strings :-) -- Andriy Gapon From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 09:48:13 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04BDE106566C; Sun, 13 Nov 2011 09:48:13 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 42F3D8FC12; Sun, 13 Nov 2011 09:48:12 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mail.0x20.net (Postfix) with ESMTP id 6BEC46A61CD; Sun, 13 Nov 2011 10:48:11 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.0x20.net Received: from mail.0x20.net ([217.69.76.211]) by mail.0x20.net (mail.0x20.net [217.69.76.211]) (amavisd-new, port 10024) with ESMTP id 3AKlb2JRGj5K; Sun, 13 Nov 2011 10:48:11 +0100 (CET) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 1D8476A6016; Sun, 13 Nov 2011 10:48:11 +0100 (CET) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.4/8.14.4) with ESMTP id pAD9mAln027044; Sun, 13 Nov 2011 10:48:10 +0100 (CET) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.4/8.14.4/Submit) id pAD9mAfV026672; Sun, 13 Nov 2011 10:48:10 +0100 (CET) (envelope-from lars) Date: Sun, 13 Nov 2011 10:48:10 +0100 From: Lars Engels To: rank1seeker@gmail.com Message-ID: <20111113094810.GC80782@e-new.0x20.net> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uXxzq0nDebZQVNAZ" Content-Disposition: inline In-Reply-To: <20111112.144149.725.1@DOMY-PC> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.2-RELEASE-p3 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: pyunyh@gmail.com, freebsd-acpi@freebsd.org, hackers@freebsd.org Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 09:48:13 -0000 --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 > 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: 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= =20 > usbus3 > > > kbd2 at ukbd0 > > > ums0: on= =20 > usbus3 > > > ums0: 16 buttons and [XYZT] coordinates ID=3D2 > > > uhid0: 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 metric 0 mtu 33152 > > > lo0: flags=3D8049 metric 0 mtu 16384 > > > options=3D3 > > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > > > inet6 ::1 prefixlen 128 > > > inet 127.0.0.1 netmask 0xff000000 > > > nd6 options=3D3 > > > cruiser# ifconfig > > > bge0: flags=3D8802 metric 0 mtu 1500 > > > =20 > options=3D8009b > > > 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 > > > ... ... ... > >=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-- From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 13:29:30 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3479106566C; Sun, 13 Nov 2011 13:29:30 +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 4241F8FC13; Sun, 13 Nov 2011 13:29:29 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so6841004bkb.13 for ; Sun, 13 Nov 2011 05:29:29 -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=0lEFaUOmpNGx1xmo6/bVKLS5afJjAmIFU+CAVAJ6pXI=; b=NT1VsPb9Vu1dqpx9I+X668uGTFYcJNc0dsrySOf6JAU0avomtBw6lOAD/xMtiA9kSR 8Ag25Wxm4Cs0cr+j2UASdO33rcIQL85UXNZDqL+xjqGQGU5OSjBTBpTrT6ziLK4Z7dj7 aTCqJKTwMC4I40QdS79dZDkgHWx7tFEk3fwis= Received: by 10.205.141.73 with SMTP id jd9mr4713639bkc.21.1321190968903; Sun, 13 Nov 2011 05:29:28 -0800 (PST) Received: from DOMYPC ([82.193.208.173]) by mx.google.com with ESMTPS id r12sm25211005bkw.5.2011.11.13.05.29.22 (version=SSLv3 cipher=OTHER); Sun, 13 Nov 2011 05:29:27 -0800 (PST) Message-ID: <20111113.132924.396.1@DOMY-PC> From: rank1seeker@gmail.com To: "Lars Engels" , pyunyh@gmail.com, hackers@freebsd.org, freebsd-acpi@freebsd.org Date: Sun, 13 Nov 2011 14:29:24 +0100 In-Reply-To: <20111113094810.GC80782@e-new.0x20.net> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> <20111113094810.GC80782@e-new.0x20.net> X-Mailer: POP Peeper (3.8.0.0) Cc: Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 13:29:31 -0000 ----- Original Message ----- From: Lars Engels To: rank1seeker@gmail.com Cc: pyunyh@gmail.com, hackers@freebsd.org, freebsd-acpi@freebsd.org Date: Sun, 13 Nov 2011 10:48:10 +0100 Subject: Re: Adventure into S3 state and back > On Sat, Nov 12, 2011 at 03:41:49PM +0100, rank1seeker@gmail.com wrote: > > ----- 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. > > stop moused in rc.suspend and start it in rc.resume. > Thanks, but it isn't that. Even with it, mouse works on random, after resume from S3. But what I did figured out, looking kernel msgs on console, just after resume, is that IF I see >1 of this: -- uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 -- Mouse won't work unless I unplug/plug it's USB receiver From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 16:40:11 2011 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6EA421065670 for ; Sun, 13 Nov 2011 16:40:11 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5F1C88FC12 for ; Sun, 13 Nov 2011 16:40:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pADGeB8G012347 for ; Sun, 13 Nov 2011 16:40:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pADGeB1q012346; Sun, 13 Nov 2011 16:40:11 GMT (envelope-from gnats) Date: Sun, 13 Nov 2011 16:40:11 GMT Message-Id: <201111131640.pADGeB1q012346@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Alexey Slynko Cc: Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexey Slynko List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 16:40:11 -0000 The following reply was made to PR kern/162491; it has been noted by GNATS. From: Alexey Slynko To: jh@FreeBSD.org Cc: bug-followup@FreeBSD.org, avg@FreeBSD.org Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading Date: Sun, 13 Nov 2011 20:18:08 +0400 (MSK) From: Jaakko Heinonen Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading Date: Sun, 13 Nov 2011 09:49:40 +0200 > I don't really know much about acpi_wmi(4) but obviously it tries to > create /dev/wmistat twice here. I am not sure if it's legitimate to have > several wmistat device files but you could try this patch: I have applied your patch, and acpi_wmi loaded sucessfully, but acpi_hp still doesn't work. acpi_wmi0: on acpi0 acpi_wmi1: on acpi0 acpi_wmi2: on acpi0 acpi_hp0: on acpi_wmi0 acpi_hp0: WMI device does not provide the HP BIOS GUID device_attach: acpi_hp0 attach returned 22 acpi_hp1: on acpi_wmi1 acpi_hp1: WMI device does not provide the HP BIOS GUID device_attach: acpi_hp1 attach returned 22 acpi_hp2: on acpi_wmi2 acpi_hp2: WMI device does not provide the HP BIOS GUID device_attach: acpi_hp2 attach returned 22 From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 20:10:25 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03D2C106566B; Sun, 13 Nov 2011 20:10:25 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id A5EB48FC14; Sun, 13 Nov 2011 20:10:24 +0000 (UTC) Received: by ywe9 with SMTP id 9so2687024ywe.13 for ; Sun, 13 Nov 2011 12:10:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=CGnGL2xXJmRmvRvFxwpSkCQ/Kn9v6E7s+4t/Q1F+UTM=; b=LejLfeWatbyvx8TmXvBY8oxzWRHVMn6RYnRlOos/heDu9vHFKvrj7zW8IRTwzP2+VS iBliy25ESn2ER4uT2nbmfu97ESxNSMkfhZL+ASqpC1ktVz8rzAn+MPM2YdNgEe7PhH9F 6/wLfjMOqt0J2cSaRQtwcQd70aV917cnK1Dvg= MIME-Version: 1.0 Received: by 10.182.12.66 with SMTP id w2mr1256326obb.7.1321213362402; Sun, 13 Nov 2011 11:42:42 -0800 (PST) Received: by 10.182.7.34 with HTTP; Sun, 13 Nov 2011 11:42:42 -0800 (PST) In-Reply-To: <20111113.132924.396.1@DOMY-PC> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> <20111113094810.GC80782@e-new.0x20.net> <20111113.132924.396.1@DOMY-PC> Date: Sun, 13 Nov 2011 11:42:42 -0800 Message-ID: From: Garrett Cooper To: rank1seeker@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: pyunyh@gmail.com, freebsd-acpi@freebsd.org, hackers@freebsd.org Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 20:10:25 -0000 On Sun, Nov 13, 2011 at 5:29 AM, wrote: > ----- Original Message ----- > From: Lars Engels > To: rank1seeker@gmail.com > Cc: pyunyh@gmail.com, hackers@freebsd.org, freebsd-acpi@freebsd.org > Date: Sun, 13 Nov 2011 10:48:10 +0100 > Subject: Re: Adventure into S3 state and back > >> On Sat, Nov 12, 2011 at 03:41:49PM +0100, rank1seeker@gmail.com wrote: >> > ----- 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 wrot= e: >> > > > 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) >> > > > =A0 =A0 =A0 =A0 media: Ethernet autoselect >> > > > =A0 =A0 =A0 =A0 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: o= n >> > usbus3 >> > > > ums0: 16 buttons and [XYZT] coordinates ID=3D2 >> > > > 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=3D141 metric 0 mtu 33152 >> > > > lo0: flags=3D8049 metric 0 mtu 1638= 4 >> > > > =A0 =A0 =A0 =A0 options=3D3 >> > > > =A0 =A0 =A0 =A0 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 >> > > > =A0 =A0 =A0 =A0 inet6 ::1 prefixlen 128 >> > > > =A0 =A0 =A0 =A0 inet 127.0.0.1 netmask 0xff000000 >> > > > =A0 =A0 =A0 =A0 nd6 options=3D3 >> > > > cruiser# ifconfig >> > > > bge0: flags=3D8802 metric 0 mtu 1500 >> > > > >> > > options=3D8009b >> > > > =A0 =A0 =A0 =A0 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 devic= e >> > 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 >> > > > =A0 =A0 didn't help >> > > > >> > > > I've also tried adding into loader.conf and nada: >> > > > --- >> > > > hint.psm.0.flags=3D"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. >> >> stop moused in rc.suspend and start it in rc.resume. >> > > Thanks, but it isn't that. > Even with it, mouse works on random, after resume from S3. > > But what I did figured out, looking kernel msgs on console, just after > resume, is that IF I see >1 of this: > -- > uhub_reattach_port: port 1 reset failed, error=3DUSB_ERR_TIMEOUT > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 > -- > > Mouse won't work unless I unplug/plug it's USB receiver You may need to kldunload and kldload ums(4) in order to get things to work (which suggests a driver bug in the newbus suspend and resume functions). FWIW I only need to do /etc/rc.d/moused restart in rc.resume to get things to work, but I'm using psm(4). The mouse pointer is kind of braindead for a second, but then it comes to life and does the right thing. So, bottom line is that there's something that gets out of sync with some mice drivers and moused, and mice driver bugs or bugs with moused might be involved. HTH, -Garrett From owner-freebsd-acpi@FreeBSD.ORG Sun Nov 13 20:42:48 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 12D6F106566B; Sun, 13 Nov 2011 20:42:48 +0000 (UTC) (envelope-from lars@e-new.0x20.net) Received: from mail.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) by mx1.freebsd.org (Postfix) with ESMTP id 964008FC08; Sun, 13 Nov 2011 20:42:47 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) by mail.0x20.net (Postfix) with ESMTP id 602666A61CD; Sun, 13 Nov 2011 21:42:46 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.0x20.net Received: from mail.0x20.net ([217.69.76.211]) by mail.0x20.net (mail.0x20.net [217.69.76.211]) (amavisd-new, port 10024) with ESMTP id A5Y-35dmK6Q9; Sun, 13 Nov 2011 21:42:46 +0100 (CET) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id 13E356A6016; Sun, 13 Nov 2011 21:42:46 +0100 (CET) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.4/8.14.4) with ESMTP id pADKgj7V061978; Sun, 13 Nov 2011 21:42:45 +0100 (CET) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.4/8.14.4/Submit) id pADKgjqJ060709; Sun, 13 Nov 2011 21:42:45 +0100 (CET) (envelope-from lars) Date: Sun, 13 Nov 2011 21:42:45 +0100 From: Lars Engels To: rank1seeker@gmail.com Message-ID: <20111113204245.GD80782@e-new.0x20.net> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> <20111113094810.GC80782@e-new.0x20.net> <20111113.132924.396.1@DOMY-PC> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OaZoDhBhXzo6bW1J" Content-Disposition: inline In-Reply-To: <20111113.132924.396.1@DOMY-PC> X-Editor: VIM - Vi IMproved 7.3 X-Operation-System: FreeBSD 8.2-RELEASE-p3 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: pyunyh@gmail.com, freebsd-acpi@freebsd.org, hackers@freebsd.org Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2011 20:42:48 -0000 --OaZoDhBhXzo6bW1J Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 13, 2011 at 02:29:24PM +0100, rank1seeker@gmail.com wrote: > ----- Original Message ----- > From: Lars Engels > To: rank1seeker@gmail.com > Cc: pyunyh@gmail.com, hackers@freebsd.org, freebsd-acpi@freebsd.org > Date: Sun, 13 Nov 2011 10:48:10 +0100 > Subject: Re: Adventure into S3 state and back > >=20 > > stop moused in rc.suspend and start it in rc.resume. > >=20 >=20 > Thanks, but it isn't that. > Even with it, mouse works on random, after resume from S3. >=20 > But what I did figured out, looking kernel msgs on console, just after=20 > resume, is that IF I see >1 of this: > -- > uhub_reattach_port: port 1 reset failed, error=3DUSB_ERR_TIMEOUT > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 > -- >=20 > Mouse won't work unless I unplug/plug it's USB receiver >=20 You might also build a trimmed down kernel without USB support compiled in and use USB modules. Before suspending, unload them and re-load them after waking up again. That used to work on my Thinkpad. --OaZoDhBhXzo6bW1J Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAk7AK8UACgkQKc512sD3afj6JgCgs7vgUcQHpqFym763TgdeaVuL or4An19noVLc2N3OvEEKPBosth4eYlw4 =YCD1 -----END PGP SIGNATURE----- --OaZoDhBhXzo6bW1J-- From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 02:16:17 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E51EE1065670; Mon, 14 Nov 2011 02:16:16 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8F39D8FC1B; Mon, 14 Nov 2011 02:16:16 +0000 (UTC) Received: by ywe9 with SMTP id 9so2880539ywe.13 for ; Sun, 13 Nov 2011 18:16:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=G0DCQS234YwcMFVXmKxTIEcE/yIJb4PL/JUvpgqnjX0=; b=r9dxXHMJnmTNQuIPOaX9vdlXQet8LUrvmUP8/0dP6rYpm/JtVchOe7Q0eKdyae9s1G hcEzZ04zHHL1Cne0z2L6rTgyifV4Lir1jM0b/+Mf9X8axv9DYDgOYOeWFctPhxx6f1Zp YGggUa1rlrdoXFgWAxzbHhV/fa797VS/R+LiA= Received: by 10.68.209.9 with SMTP id mi9mr5269967pbc.62.1321236975449; Sun, 13 Nov 2011 18:16:15 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id wf19sm52621432pbb.17.2011.11.13.18.16.12 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 13 Nov 2011 18:16:14 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sun, 13 Nov 2011 18:14:13 -0800 From: YongHyeon PYUN Date: Sun, 13 Nov 2011 18:14:13 -0800 To: rank1seeker@gmail.com Message-ID: <20111114021413.GA1709@michelle.cdnetworks.com> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20111112.144149.725.1@DOMY-PC> User-Agent: Mutt/1.4.2.3i Cc: freebsd-acpi@freebsd.org, hackers@freebsd.org Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 02:16:17 -0000 On Sat, Nov 12, 2011 at 03:41:49PM +0100, rank1seeker@gmail.com wrote: > ----- 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 Actually I spent a lot of time to address this but all attempts failed mainly because I have no access to such bge(4) controllers. Remote debugging does not work for suspend/resume issues so chances would be low to get it fixed in near future unless someone donate problematic hardwares to me. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 03:08:19 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9995B106567D for ; Mon, 14 Nov 2011 03:08:19 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id D3A148FC0C for ; Mon, 14 Nov 2011 03:08:18 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id pAE38FNO095057; Mon, 14 Nov 2011 14:08:16 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 14 Nov 2011 14:08:15 +1100 (EST) From: Ian Smith To: Garrett Cooper In-Reply-To: Message-ID: <20111114133503.T59637@sola.nimnet.asn.au> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> <20111113094810.GC80782@e-new.0x20.net> <20111113.132924.396.1@DOMY-PC> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1524783476-1321238492=:59637" Content-ID: <20111114134914.S59637@sola.nimnet.asn.au> Cc: rank1seeker@gmail.com, pyunyh@gmail.com, freebsd-acpi@freebsd.org Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 03:08:19 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1524783476-1321238492=:59637 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: <20111114134914.K59637@sola.nimnet.asn.au> Removing hackers@freebsd.org from ccs: On Sun, 13 Nov 2011, Garrett Cooper wrote: > On Sun, Nov 13, 2011 at 5:29 AM, wrote: > > ----- Original Message ----- > > From: Lars Engels > > To: rank1seeker@gmail.com [ chomp ] > >> > > > 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. > >> > >> stop moused in rc.suspend and start it in rc.resume. > >> > > > > Thanks, but it isn't that. > > Even with it, mouse works on random, after resume from S3. > > > > But what I did figured out, looking kernel msgs on console, just after > > resume, is that IF I see >1 of this: > > -- > > uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT > > uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 > > -- > > > > Mouse won't work unless I unplug/plug it's USB receiver > > You may need to kldunload and kldload ums(4) in order to get things to > work (which suggests a driver bug in the newbus suspend and resume > functions). > > FWIW I only need to do /etc/rc.d/moused restart in rc.resume to get > things to work, but I'm using psm(4). The mouse pointer is kind of > braindead for a second, but then it comes to life and does the right > thing. > > So, bottom line is that there's something that gets out of sync with > some mice drivers and moused, and mice driver bugs or bugs with moused > might be involved. I also used to restart moused in rc.resume, until this clue from jkim@ ======== psm(4): bit 13 HOOKRESUME The built-in PS/2 pointing device of some laptop computers is somehow not operable immediately after the system `resumes' from the power saving mode, though it will eventually become available. There are reports that stimulating the device by performing I/O will help waking up the device quickly. This flag will enable a piece of code in the psm driver to hook the `resume' event and exercise some harmless I/O operations on the device. bit 14 INITAFTERSUSPEND This flag adds more drastic action for the above problem. It will cause the psm driver to reset and re-initialize the pointing device after the `resume' event. It has no effect unless the HOOKRESUME flag is set as well. I always use hint.psm.0.flags="0x6000" in /boot/loader.conf, i.e., turn on both HOOKRESUME and INITAFTERSUSPEND, to work around similar problem on different laptop. ======= This works reliably for me on my Thinkpad: # 29/9/10 thanks Jung-uk Kim .. so can remove moused restart from rc.resume hint.psm.0.flags="0x6000" It's psm of course so I doubt it could help with ums(4), which appears to be a hint-free zone, but it should work for you, Garrett. cheers, Ian --0-1524783476-1321238492=:59637-- From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 11:07:02 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3225106566B for ; Mon, 14 Nov 2011 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C96568FC15 for ; Mon, 14 Nov 2011 11:07:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pAEB71Kv083435 for ; Mon, 14 Nov 2011 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pAEB71I6083433 for freebsd-acpi@FreeBSD.org; Mon, 14 Nov 2011 11:07:01 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 14 Nov 2011 11:07:01 GMT Message-Id: <201111141107.pAEB71I6083433@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-acpi@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-acpi@FreeBSD.org X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 11:07:02 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/162491 acpi [acpi_hp] [panic] EliteBook 8540p panic on acpi_hp mod o kern/161715 acpi [acpi] Dell E6520 doesn't resume after ACPI suspend o kern/161713 acpi [acpi] Suspend on Dell E6520 o kern/160838 acpi [acpi] ACPI Battery Monitor Non-Functional o kern/160419 acpi [acpi_thermal] acpi_thermal kernel thread high CPU usa o kern/158689 acpi [acpi] value of sysctl hw.acpi.thermal.polling_rate ne o kern/154955 acpi [acpi] Keyboard or ACPI doesn't work on Lenovo S10-3 o kern/152438 acpi [acpi]: patch to acpi_asus(4) to add extra sysctls for o kern/152098 acpi [acpi] Lenovo T61p does not resume o i386/146715 acpi [acpi] Suspend works, resume not on a HP Probook 4510s o kern/145306 acpi [acpi]: Can't change brightness on HP ProBook 4510s o i386/144045 acpi [acpi] [panic] kernel trap with acpi enabled o i386/143798 acpi [acpi] shutdown problem with SiS K7S5A o kern/143420 acpi [acpi] ACPI issues with Toshiba o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o kern/139088 acpi [acpi] ACPI Exception: AE_AML_INFINITE_LOOP error o amd64/138210 acpi [acpi] acer aspire 5536 ACPI problems (S3, brightness, o bin/137053 acpi [hang] FreeBSD 8.0 BETA2Compaq Mini 700 locks on boot o kern/137042 acpi [acpi] hp laptop's lcd not wakes up after suspend to r o i386/136008 acpi [acpi] Dell Vostro 1310 will not shutdown (Requires us o bin/135349 acpi [patch] teach acpidump(8) to disassemble arbitrary mem o kern/132602 acpi [acpi] ACPI Problem with Intel SS4200: System does not o kern/130683 acpi [ACPI] shutdown hangs after syncing disks - ACPI race? o i386/129953 acpi [acpi] ACPI timeout (CDROM) with Shuttle X27D p kern/128634 acpi [patch] fix acpi_asus(4) in asus a6f laptop o kern/124412 acpi [acpi] power off error on Toshiba M40 laptop o kern/123039 acpi [acpi] ACPI AML_BUFFER_LIMIT errors during boot a i386/122887 acpi [panic] [atkbdc] 7.0-RELEASE on IBM HS20 panics immed o kern/121504 acpi [patch] Correctly set hw.acpi.osname on certain machin f kern/119356 acpi [acpi]: i386 ACPI wakeup not work due resource exhaust o kern/119200 acpi [acpi] Lid close switch suspends CPU for 1 second on H o kern/116939 acpi [acpi] PCI-to-PCI misconfigured for bus three and can o bin/115947 acpi [hang] Dell poweredge 860 hangs when stressed and ACPI o i386/114562 acpi [acpi] cardbus is dead after s3 on Thinkpad T43 with a o kern/114165 acpi [acpi] Dell C810 - ACPI problem s kern/112544 acpi [acpi] [patch] Add High Precision Event Timer Driver f o kern/108695 acpi [acpi]: Fatal trap 9: general protection fault when in o kern/108488 acpi [acpi] ACPI-1304: *** Error: Method execution failed o kern/106924 acpi [acpi] ACPI resume returns g_vfs_done() errors and ker o kern/105537 acpi [acpi] problems in acpi on HP Compaq nc6320 o kern/102252 acpi acpi thermal does not work on Abit AW8D (intel 975) o kern/91594 acpi [acpi] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/ o i386/83018 acpi [install] Installer will not boot on Asus P4S8X BIOS 1 o kern/73823 acpi [request] acpi / power-on by timer support o i386/69750 acpi Boot without ACPI failed on ASUS L5 o kern/56024 acpi ACPI suspend drains battery while in S3 o i386/55661 acpi ACPI suspend/resume problem on ARMADA M700 47 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 15:18:43 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49E0A106566B for ; Mon, 14 Nov 2011 15:18:43 +0000 (UTC) (envelope-from John_Veit@DELL.com) Received: from aussmtpmrkps320.us.dell.com (aussmtpmrkps320.us.dell.com [143.166.224.254]) by mx1.freebsd.org (Postfix) with ESMTP id 1C2178FC08 for ; Mon, 14 Nov 2011 15:18:42 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.69,509,1315198800"; d="scan'208,217";a="511102103" Received: from mail.compellent.com ([64.238.244.148]) by aussmtpmrkps320.us.dell.com with ESMTP; 14 Nov 2011 08:50:16 -0600 From: John Veit To: "freebsd-acpi@FreeBSD.org" Date: Mon, 14 Nov 2011 08:50:14 -0600 Thread-Topic: Sandy Bridge Support for FBSD 8.1 Thread-Index: Acyi3LfazioSE87qTE6oCxMsdRTT0A== Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA03D08496A8@shandy.Beer.Town> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Don Croft Subject: Sandy Bridge Support for FBSD 8.1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 15:18:43 -0000 Motherboard: Dell R720 with 2 SandyBridge X6 CPU's I do not see some devices on the second CPU slot (e.g. the Integrated Memor= y Controller devices @ bus(127):slot(15):fn(0)). I do see the IMC devices o= n the first CPU Slot (bus(63):slot(15):fn(0)), however. Please advise. Thanks, John Veit jveit@dell.com From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 19:51:04 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B1BF106564A; Mon, 14 Nov 2011 19:51:04 +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 CA8CB8FC14; Mon, 14 Nov 2011 19:51:03 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so8687114bkb.13 for ; Mon, 14 Nov 2011 11:51:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:from:to:subject:date:content-type :content-transfer-encoding:in-reply-to:references:x-mailer; bh=+JQw/hwGWhqVxG4njFjFqLJUjTPYSJEeCI+5GqfHBII=; b=HR8+7Fa7lfxvK9Ijm75uLYnkJ500nQwlHeBTmcQZa2bpHpAclEw3uky+swt2Bfr967 uLRtwWFyCt7EsvVK2PyICWnUZ1XcbGBjgmnj520i2VHLAEKDeAL6lhEkrswMEjZOJQr4 t2rgBfv7NV7cqS9G1V3Bt2cwSBhe14sJ3JX1g= Received: by 10.204.129.70 with SMTP id n6mr20972312bks.0.1321300262524; Mon, 14 Nov 2011 11:51:02 -0800 (PST) Received: from DOMYPC ([82.193.208.173]) by mx.google.com with ESMTPS id a4sm24435431bkq.13.2011.11.14.11.50.57 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 11:51:00 -0800 (PST) Message-ID: <20111114.195057.675.1@DOMY-PC> From: rank1seeker@gmail.com To: "Garrett Cooper" , "Lars Engels" , "Ian Smith" , pyunyh@gmail.com, hackers@freebsd.org, freebsd-acpi@freebsd.org Date: Mon, 14 Nov 2011 20:50:57 +0100 Content-Type: text/plain; charset="Windows-1250" Content-Transfer-Encoding: quoted-printable In-Reply-To: <20111114021413.GA1709@michelle.cdnetworks.com> References: <20111110.182948.630.1@DOMY-PC> <20111112002727.GD17792@michelle.cdnetworks.com> <20111112.144149.725.1@DOMY-PC> <20111114021413.GA1709@michelle.cdnetworks.com> X-Mailer: POP Peeper (3.8.0.0) Cc: Subject: Re: Adventure into S3 state and back X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 19:51:04 -0000 ----- Original Message -----=0D=0AFrom: YongHyeon PYUN = =0D=0ATo: rank1seeker@gmail.com=0D=0ACc: = hackers@freebsd.org, freebsd-acpi@freebsd.org=0D=0ADate: Sun, 13 Nov 2011 = 18:14:13 -0800=0D=0ASubject: Re: Adventure into S3 state and = back=0D=0A=0D=0A> > > =0D=0A> > > Known issue. kern/136876.=0D=0A> > > = Mobile bge(4) controllers seem to have this issue.=0D=0A> > =0D=0A> > I = can see this has been reported, when 8.0-BETA1 was released.=0D=0A> > Now = is almost 8.3 out and problem is still present=0D=0A> =0D=0A> Actually I = spent a lot of time to address this but all attempts=0D=0A> failed mainly = because I have no access to such bge(4) controllers.=0D=0A> Remote = debugging does not work for suspend/resume issues so chances=0D=0A> would = be low to get it fixed in near future unless someone donate=0D=0A> = problematic hardwares to me.=0D=0A=0D=0A=0D=0AThen you have to = update:=0D=0Ahttp://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/136876=0D=0A=0D=0AAnd = post at the end, something like ...=0D=0A"All attempts to fix problem = failed, due to physicall unavailability of bge(4) controller.=0D=0ASTATUS = -> Waiting for donation of bge(4) hardware, in order to resume fixing a = problem"=0D=0A=0D=0A=0D=0A> > Mouse won't work unless I unplug/plug it's = USB receiver=0D=0A> =0D=0A> You may need to kldunload and kldload ums(4) = in order to get things to=0D=0A> work (which suggests a driver bug in the = newbus suspend and resume=0D=0A> functions).=0D=0A> =0D=0A> FWIW I only = need to do /etc/rc.d/moused restart in rc.resume to get=0D=0A> things to = work, but I'm using psm(4). The mouse pointer is kind of=0D=0A> braindead = for a second, but then it comes to life and does the right=0D=0A> = thing.=0D=0A> =0D=0A> So, bottom line is that there's something that gets = out of sync with=0D=0A> some mice drivers and moused, and mice driver = bugs or bugs with moused=0D=0A> might be involved.=0D=0A> =0D=0A> = HTH,=0D=0A> -Garrett=0D=0A>=0D=0A----- Original Message -----=0D=0AFrom: = Lars Engels =0D=0A> =0D=0A> You might also build a = trimmed down kernel without USB support compiled=0D=0A> in and use USB = modules. Before suspending, unload them and re-load them=0D=0A> after = waking up again. That used to work on my Thinkpad.=0D=0A> = =0D=0A=0D=0AFirst I tried to build kernel only without 'ums' and kldload = it.=0D=0A3 times in a row, to S3 and back worked, so I hopped it works, = until 4th and 5th time, resulted in error.=0D=0AI like things to 'WORK' = or 'NOT TO WORK'.=0D=0AThis is some borderline case, where IT does "this" = on random, so I was so pissed of, with need to test 10 times in a row = (slapping lid), to confirm not/working status!=0D=0A=0D=0AThen I tried = ums, uhid, ukbd drivers and recompiled kernel.=0D=0ASlapping lid around = again and nada!=0D=0A=0D=0AThen what really drained me, was point of = removing usb drivers 1 by 1, which caused many kernel builds to = fail.=0D=0AThen again build with 1 job, just to see what was missing, and = again ...=0D=0ADuh!=0D=0A=0D=0AFirst echi, then it was uhci, then umass = wasn't happy, then uhid ... Tsk tsk!=0D=0AAnyway now it DOES work: (after = ~16 kern builds!)=0D=0A=0D=0A# vi = /boot/loader.conf=0D=0A--=0D=0Aums_load=3D"YES"=0D=0Aehci_load=3D"YES"=0D=0Auhci_load=3D"YES"=0D=0Ausb_load=3D"YES"=0D=0Aumass_load=3D"YES"=0D=0Auhid_load=3D"YES"=0D=0Aukbd_load=3D"YES"=0D=0A--=0D=0A=0D=0AAnd = appropriate kld(un)load lines in /etc/rc.suspend and /etc/rc.resume, made = it work.=0D=0ANow upon resume, I see at least 8 times more kernel = output.=0D=0A=0D=0A=0D=0A=0D=0ADomagoj Smol=E8i=E6=0D=0A=0D=0A From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 19:59:28 2011 Return-Path: Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1412106566B for ; Mon, 14 Nov 2011 19:59:28 +0000 (UTC) (envelope-from geoffroy@vanelsuve.info) Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by mx1.freebsd.org (Postfix) with ESMTP id 90F668FC08 for ; Mon, 14 Nov 2011 19:59:28 +0000 (UTC) Received: by pzk33 with SMTP id 33so26884453pzk.3 for ; Mon, 14 Nov 2011 11:59:28 -0800 (PST) MIME-Version: 1.0 Received: by 10.68.47.4 with SMTP id z4mr52224817pbm.39.1321299045623; Mon, 14 Nov 2011 11:30:45 -0800 (PST) Received: by 10.143.165.1 with HTTP; Mon, 14 Nov 2011 11:30:45 -0800 (PST) Date: Mon, 14 Nov 2011 20:30:45 +0100 Message-ID: From: Geoffroy Van Elsuve To: freebsd-acpi@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Asus M51VA X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 19:59:28 -0000 Hi, I have issue when getting back from sleep when system resume. I have try lot of action from http://www.freebsd.org/doc/handbook/acpi-debug.html but without success. I have this error on boot, I am not sure this is important for suspend/resume action, if you think it is, i will rebuild the kernel on extanding in sys/kern/subr_firmware.c the #define FIRMWARE_MAX 30 firmware_register: cannot register image bwn_v4_lp_a0g0bsinitvals5, firmware table full! module_register_init: MOD_LOAD (bwn_v4_lp_ucode_fw, 0xffffffff818bf000, 0) error 6 Find in attachment my dmesg and on this url my asl. http://88.191.120.236/asus_m51va.asl I have recompile without error my ASL Thanks for your help. Geoffroy From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 21:06:54 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D2D1106564A for ; Mon, 14 Nov 2011 21:06:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 251458FC08 for ; Mon, 14 Nov 2011 21:06:54 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id CAA9A46B09; Mon, 14 Nov 2011 16:06:53 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 614F48A050; Mon, 14 Nov 2011 16:06:53 -0500 (EST) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 14 Nov 2011 16:06:52 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <975552A94CBC0F4DA60ED7B36C949CBA03D08496A8@shandy.Beer.Town> In-Reply-To: <975552A94CBC0F4DA60ED7B36C949CBA03D08496A8@shandy.Beer.Town> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111141606.52981.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 14 Nov 2011 16:06:53 -0500 (EST) Cc: John Veit , Don Croft Subject: Re: Sandy Bridge Support for FBSD 8.1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 21:06:54 -0000 On Monday, November 14, 2011 9:50:14 am John Veit wrote: > Motherboard: Dell R720 with 2 SandyBridge X6 CPU's > I do not see some devices on the second CPU slot (e.g. the Integrated Memory Controller devices @ bus(127):slot(15):fn(0)). I do see the IMC devices on the first CPU Slot (bus(63):slot(15):fn(0)), however. > > Please advise. > Thanks, John Veit > jveit@dell.com Eh. How are you seeing those devices in the first place? My understanding is that these devices showed up on busses starting with bus 255 on down. This is managed by the qpi driver in sys/x86/pci/qpi.c. Hmm, it doesn't see any devices on my SB desktop machine here. Ah. It does a CPU ID check that needs to be updated. However, are the buses defined to be 127 and 63 rather than 255 and 254 as they were on Nehalem/Westmere? Is there formal documentation you can point me at (from Intel perhaps?) that explains the official method for discovering these PCI buses? -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 21:35:36 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E75631065672 for ; Mon, 14 Nov 2011 21:35:36 +0000 (UTC) (envelope-from John_Veit@DELL.com) Received: from aussmtpmrkpc120.us.dell.com (aussmtpmrkpc120.us.dell.com [143.166.82.159]) by mx1.freebsd.org (Postfix) with ESMTP id BA36D8FC15 for ; Mon, 14 Nov 2011 21:35:36 +0000 (UTC) X-Loopcount0: from 64.238.244.148 X-IronPort-AV: E=Sophos;i="4.69,511,1315198800"; d="scan'208";a="483502039" Received: from mail.compellent.com ([64.238.244.148]) by aussmtpmrkpc120.us.dell.com with ESMTP; 14 Nov 2011 15:35:35 -0600 From: John Veit To: John Baldwin , "freebsd-acpi@freebsd.org" Date: Mon, 14 Nov 2011 15:35:33 -0600 Thread-Topic: Sandy Bridge Support for FBSD 8.1 Thread-Index: AcyjEVilJEApMQzlSXKRT8wZxUDpaQAAjEgw Message-ID: <975552A94CBC0F4DA60ED7B36C949CBA03D0849EB5@shandy.Beer.Town> References: <975552A94CBC0F4DA60ED7B36C949CBA03D08496A8@shandy.Beer.Town> <201111141606.52981.jhb@freebsd.org> In-Reply-To: <201111141606.52981.jhb@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: Don Croft Subject: RE: Sandy Bridge Support for FBSD 8.1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 21:35:37 -0000 The Intel SandyBridge_EDS volume 2 decribes how the CPUBUS0, CPUBUS1 values= are accessed for each physical CPU Slot. The BIOS loads these values at bo= ot time. For SandyBridge each physical CPU has multiple PCI segments for in= tegrated IO and CPU devices. Thus when 2 CPU's are present the following va= lues are set: CPU0BUS0=3D0 (IIO, PCH), CPU0BUS1=3D63 (IMC, DMA, etc),=20 CPU1BUS0=3D64, CPU1BUS1=3D127. Note: We are using amd64 build of FBSD 8.1. It looks like the qpi driver is= not supported for Sandy Bridge. =20 -----Original Message----- From: John Baldwin [mailto:jhb@freebsd.org]=20 Sent: Monday, November 14, 2011 3:07 PM To: freebsd-acpi@freebsd.org Cc: John Veit; Don Croft Subject: Re: Sandy Bridge Support for FBSD 8.1 On Monday, November 14, 2011 9:50:14 am John Veit wrote: > Motherboard: Dell R720 with 2 SandyBridge X6 CPU's I do not see some=20 > devices on the second CPU slot (e.g. the Integrated Memory Controller devices @ bus(127):slot(15):fn(0)). I do see the IMC devices on = the first CPU Slot (bus(63):slot(15):fn(0)), however. >=20 > Please advise. > Thanks, John Veit > jveit@dell.com Eh. How are you seeing those devices in the first place? My understanding= is that these devices showed up on busses starting with bus 255 on down. = This is managed by the qpi driver in sys/x86/pci/qpi.c. Hmm, it doesn't se= e any devices on my SB desktop machine here. Ah. It does a CPU ID check t= hat needs to be updated. However, are the buses defined to be 127 and 63 r= ather than 255 and 254 as they were on Nehalem/Westmere? Is there formal documentatio= n you can point me at (from Intel perhaps?) that explains the official meth= od for discovering these PCI buses? -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Mon Nov 14 22:30:17 2011 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E0031065670 for ; Mon, 14 Nov 2011 22:30:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 63B088FC15 for ; Mon, 14 Nov 2011 22:30:17 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 1AD6846B06; Mon, 14 Nov 2011 17:30:17 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B602E8A050; Mon, 14 Nov 2011 17:30:16 -0500 (EST) From: John Baldwin To: John Veit Date: Mon, 14 Nov 2011 17:30:15 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p8; KDE/4.5.5; amd64; ; ) References: <975552A94CBC0F4DA60ED7B36C949CBA03D08496A8@shandy.Beer.Town> <201111141606.52981.jhb@freebsd.org> <975552A94CBC0F4DA60ED7B36C949CBA03D0849EB5@shandy.Beer.Town> In-Reply-To: <975552A94CBC0F4DA60ED7B36C949CBA03D0849EB5@shandy.Beer.Town> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201111141730.15808.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 14 Nov 2011 17:30:16 -0500 (EST) Cc: Don Croft , "freebsd-acpi@freebsd.org" Subject: Re: Sandy Bridge Support for FBSD 8.1 X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2011 22:30:17 -0000 On Monday, November 14, 2011 4:35:33 pm John Veit wrote: > > The Intel SandyBridge_EDS volume 2 decribes how the CPUBUS0, CPUBUS1 values are accessed for each physical CPU Slot. The BIOS loads these values at boot time. For SandyBridge each physical CPU has multiple PCI segments for integrated IO and CPU devices. Thus when 2 CPU's are present the following values are set: > CPU0BUS0=0 (IIO, PCH), CPU0BUS1=63 (IMC, DMA, etc), > CPU1BUS0=64, CPU1BUS1=127. > > Note: We are using amd64 build of FBSD 8.1. It looks like the qpi driver is not supported for Sandy Bridge. Yeah, we'll have to fix qpi.c. Let me see if I can find that manual tomorrow and come up with a fix for qpi.c. I can test it on my desktop here which has SB. Hmm, I can't seem to find the relevant document on Intel's site. At least, this: http://www.intel.com/content/www/us/en/processors/core/2nd-gen-core-family- mobile-vol-2-datasheet.html Does not seem to mention CPU0BUS0 anywhere that I can see. Are these special MSRs or are they a config register in another PCI device? > -----Original Message----- > From: John Baldwin [mailto:jhb@freebsd.org] > Sent: Monday, November 14, 2011 3:07 PM > To: freebsd-acpi@freebsd.org > Cc: John Veit; Don Croft > Subject: Re: Sandy Bridge Support for FBSD 8.1 > > On Monday, November 14, 2011 9:50:14 am John Veit wrote: > > Motherboard: Dell R720 with 2 SandyBridge X6 CPU's I do not see some > > devices on the second CPU slot (e.g. the Integrated Memory > Controller devices @ bus(127):slot(15):fn(0)). I do see the IMC devices on the first CPU Slot (bus(63):slot(15):fn(0)), however. > > > > Please advise. > > Thanks, John Veit > > jveit@dell.com > > Eh. How are you seeing those devices in the first place? My understanding is that these devices showed up on busses starting with bus 255 on down. This is managed by the qpi driver in sys/x86/pci/qpi.c. Hmm, it doesn't see any devices on my SB desktop machine here. Ah. It does a CPU ID check that needs to be updated. However, are the buses defined to be 127 and 63 rather than > 255 and 254 as they were on Nehalem/Westmere? Is there formal documentation you can point me at (from Intel perhaps?) that explains the official method for discovering these PCI buses? > > -- > John Baldwin > -- John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Nov 15 17:10:07 2011 Return-Path: Delivered-To: freebsd-acpi@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33EB1106564A for ; Tue, 15 Nov 2011 17:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 23D408FC13 for ; Tue, 15 Nov 2011 17:10:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id pAFHA6Di089300 for ; Tue, 15 Nov 2011 17:10:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id pAFHA6iF089299; Tue, 15 Nov 2011 17:10:06 GMT (envelope-from gnats) Date: Tue, 15 Nov 2011 17:10:06 GMT Message-Id: <201111151710.pAFHA6iF089299@freefall.freebsd.org> To: freebsd-acpi@FreeBSD.org From: Jaakko Heinonen Cc: Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jaakko Heinonen List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2011 17:10:07 -0000 The following reply was made to PR kern/162491; it has been noted by GNATS. From: Jaakko Heinonen To: Alexey Slynko Cc: bug-followup@FreeBSD.org, avg@FreeBSD.org Subject: Re: kern/162491: EliteBook 8540p panic on acpi_hp module loading Date: Tue, 15 Nov 2011 19:00:36 +0200 On 2011-11-13, Alexey Slynko wrote: > I have applied your patch, and acpi_wmi loaded sucessfully, but > acpi_hp still doesn't work. Thanks for testing. Unfortunately, I don't know if there is much more that I can do to help you. However following information might be useful for solving the problem: - Did acpi_hp(4) work with previous FreeBSD versions? If it did, what is the exact working version? - verbose dmesg(8) output from working and non-working versions > acpi_wmi0: on acpi0 > acpi_wmi1: on acpi0 > acpi_wmi2: on acpi0 > acpi_hp0: on acpi_wmi0 > acpi_hp0: WMI device does not provide the HP BIOS GUID > device_attach: acpi_hp0 attach returned 22 > acpi_hp1: on acpi_wmi1 > acpi_hp1: WMI device does not provide the HP BIOS GUID > device_attach: acpi_hp1 attach returned 22 > acpi_hp2: on acpi_wmi2 > acpi_hp2: WMI device does not provide the HP BIOS GUID > device_attach: acpi_hp2 attach returned 22 -- Jaakko