From owner-freebsd-stable@FreeBSD.ORG Tue Jun 24 20:24:44 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A8A02B9; Tue, 24 Jun 2014 20:24:44 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F0EA298F; Tue, 24 Jun 2014 20:24:44 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D83D1B953; Tue, 24 Jun 2014 16:24:42 -0400 (EDT) From: John Baldwin To: Hilko Meyer Subject: Re: powerd stopped working after update from 8.4 to 9.2 Date: Tue, 24 Jun 2014 16:23:39 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <201406241026.52678.jhb@freebsd.org> <6hcjq9540905oeibsjnf8ogee7sqfcdoej@4ax.com> In-Reply-To: <6hcjq9540905oeibsjnf8ogee7sqfcdoej@4ax.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Message-Id: <201406241623.39328.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 24 Jun 2014 16:24:42 -0400 (EDT) Cc: freebsd-acpi@freebsd.org, freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2014 20:24:44 -0000 On Tuesday, June 24, 2014 1:36:41 pm Hilko Meyer wrote: > On Tue, 24 Jun 2014 10:26:52 -0400, you wrote: > >On Monday, June 23, 2014 7:12:23 pm Hilko Meyer wrote: > >> John Baldwin wrote: > >> >On Sunday, June 22, 2014 9:27:08 pm Hilko Meyer wrote: > >> >>=20 > >> >> powerd doesn't work anymore after the update from 8.4 to 9.2. The s= ystem > >> >> has an old (more than 10 years) mainboard with Via KT133 chipset. > >> >>=20 > >> >> I made a verbose boot with both, 8.4 and 9.2: > >> >> 8.4: http://pastebin.com/iiZXRXgK > >> >> 9.2: http://pastebin.com/sHcd3MHv > >> >> The relevant part of the diff seem to be these parts: > >> >>=20 > >> >> viapropm0: SMBus I/O base at 0x5000 > >> >> viapropm0: SMBus I/O base at 0x5000 > >> >> viapropm0: port 0x5000-0x500= f at > >> >> device 7.4 on pci0 > >> >> -viapropm0: SMBus revision code 0x40 > >> >> -smbus0: on viapropm0 > >> >> -smb0: on smbus0 > >> >> +viapropm0: could not allocate bus space > >> >> +device_attach: viapropm0 attach returned 6 > >> >> [=85] > >> >> acpi_throttle0: on cpu0 > >> >> -acpi_throttle0: P_CNT from P_BLK 0x4010 > >> >> +acpi_throttle0: failed to attach P_CNT > >> >> +device_attach: acpi_throttle0 attach returned 6 > >> >>=20 > >> >> Any ideas what I can do? > >> > > >> >acpi_timer0 also failed to probe due to a resource issue. Can you get= the=20 > >> >output of 'devinfo -rv' and 'devinfo -u' from the both kernels? > >>=20 > >> Yes, no problem. > >> devinfo -rv: > >> 8.4: http://pastebin.com/6xm1tBrU > >> 9.2: http://pastebin.com/whXk32Ab > >>=20 > >> devinfo -u: > >> 8.4: http://pastebin.com/47U7HZb3 > >> 9.2: http://pastebin.com/U85HTw0C > >>=20 > >> thanks for your help, > >> Hilko > > > >Can you provide your acpidump? This box seems confusing. >=20 > Well, its quite old. An Epox 8kta3 from around 2002. I was not sure which= output > you need so I attached acpidump -d and acpidump -dt. Ok, try this: Index: sys/dev/acpica/acpi.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =2D-- acpi.c (revision 267784) +++ acpi.c (working copy) @@ -1196,15 +1196,24 @@ acpi_set_resource(device_t dev, device_t child, in return (0); =20 /* =2D * Ignore memory resources for PCI root bridges. Some BIOSes + * Ignore most resources for PCI root bridges. Some BIOSes * incorrectly enumerate the memory ranges they decode as plain =2D * memory resources instead of as a ResourceProducer range. + * memory resources instead of as ResourceProducer ranges. Other + * BIOSes incorrectly list system resource entries for I/O ranges + * under the PCI bridge. Do allow the one known-correct case on + * x86 of a PCI bridge claiming the I/O ports used for PCI config + * access. */ =2D if (type =3D=3D SYS_RES_MEMORY) { + if (type =3D=3D SYS_RES_MEMORY || type =3D=3D SYS_RES_IOPORT) { if (ACPI_SUCCESS(AcpiGetObjectInfo(ad->ad_handle, &devinfo))) { if ((devinfo->Flags & ACPI_PCI_ROOT_BRIDGE) !=3D 0) { =2D AcpiOsFree(devinfo); =2D return (0); +#if defined(__i386__) || defined(__amd64__) + if (!(type =3D=3D SYS_RES_IOPORT && start =3D=3D CONF1_ADDR_PORT)) +#endif + { + AcpiOsFree(devinfo); + return (0); + } } AcpiOsFree(devinfo); } =2D-=20 John Baldwin