From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 28 11:06:51 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 89DF0106564A for ; Mon, 28 Mar 2011 11:06:51 +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 5C0748FC20 for ; Mon, 28 Mar 2011 11:06:51 +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 p2SB6pXx026570 for ; Mon, 28 Mar 2011 11:06:51 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p2SB6o88026568 for freebsd-acpi@FreeBSD.org; Mon, 28 Mar 2011 11:06:50 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Mar 2011 11:06:50 GMT Message-Id: <201103281106.p2SB6o88026568@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, 28 Mar 2011 11:06:51 -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/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/142263 acpi [acpi] ACPI regression on Asus K8N7-E deluxe motherboa o kern/142009 acpi [acpi] [panic] Panic in AcpiNsGetAttachedObject o amd64/140751 acpi [acpi] BIOS resource allocation and FreeBSD ACPI in TO 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/135070 acpi [acpi] [patch] BIOS resource allocation and FreeBSD AC 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 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 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 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 41 problems total. From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 28 14:21: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 7C4BE106566C for ; Mon, 28 Mar 2011 14:21:02 +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 4E8E18FC15 for ; Mon, 28 Mar 2011 14:21:02 +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 07F4946B46; Mon, 28 Mar 2011 10:21:02 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 994EA8A01B; Mon, 28 Mar 2011 10:21:01 -0400 (EDT) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Mon, 28 Mar 2011 08:23:23 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110311; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201103280823.23502.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 28 Mar 2011 10:21:01 -0400 (EDT) Cc: =?utf-8?b?0JrRgdC10L3Qt9C+0LIg0JDQu9C10LrRgdC10Lk=?= Subject: Re: Atheros 9285 & Atheros AR8131 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, 28 Mar 2011 14:21:02 -0000 On Saturday, March 26, 2011 1:13:45 pm =D0=9A=D1=81=D0=B5=D0=BD=D0=B7=D0=BE= =D0=B2 =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9 wrote: > Network cards do not work. Tried on systems 8.0, 8.1, and 8.2. Notebook A= ser > Extenza 5635ZG. Tried to change Wi-Fi adapter on the other, but the > situation has not changed. In all kinds of windows and linux, works fine. >=20 > ath0: irq 19 at device 0.0 on pci7 > ath0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > ath0: cannot map register space > device_attach: ath0 attach returned 6 >=20 > alc0: irq 17 at device 0.0 on pci9 > alc0: 0x40000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > alc0: cannot allocate memory resources. > device_attach: alc0 attach returned 6 >=20 > Attached: dmesg, sysctl hw.acpi and acpidump -t -d This is probably due to a problem FreeBSD has with ACPI initialization=20 sometimes wiping out the state in PCI-PCI bridges for resource windows and = not=20 gracefully recovering from that. I have some early work in progress to=20 address this, but it will be a while before I have something ready for=20 testing. =2D-=20 John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 28 16:24: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 9E0C6106564A; Mon, 28 Mar 2011 16:24:43 +0000 (UTC) (envelope-from lenzi.sergio@gmail.com) Received: from mail-yi0-f54.google.com (mail-yi0-f54.google.com [209.85.218.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3F7BE8FC12; Mon, 28 Mar 2011 16:24:42 +0000 (UTC) Received: by yie12 with SMTP id 12so1395415yie.13 for ; Mon, 28 Mar 2011 09:24:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:subject:from:to:cc:in-reply-to:references :content-type:date:message-id:mime-version:x-mailer; bh=pUc1vdwaRwLubmT+xytbBuk4CymHVdLsr1nDkGPxROw=; b=qEnYAFxRooB2yNLtu6VV0dp4ce0+4AeX1JAY67DasSINZLLNmkOe1XfICW5o3hd+FA 1K+CDtD0b/fI32ZfPx37GlBGepzWsjBTeYqM/qv6edgtAYixu7Zwdly/3q7sQpFaqhdL S5mRkRjSKfHSP1YHpycLr1vpzphbdFTo53/00= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer; b=AckDl4nBdmCeMnXxTtI/eivAAai2Zmdn2Y6zz/XwFNXDyF7gWGr7cmLOZ04Fio8fdy Kl3VI8+c/VL8Um4wlyIx/pcZY4lavPnxjVYqgxb4lcz+pHgIIUrw7ulzuLFqYAGcKXP4 NUOHh+hfjcpbDpRA0s7ClQkm1DCf8PSnkV2dg= Received: by 10.91.160.15 with SMTP id m15mr3948602ago.181.1301328163149; Mon, 28 Mar 2011 09:02:43 -0700 (PDT) Received: from [192.168.6.230] ([201.21.166.97]) by mx.google.com with ESMTPS id m12sm1406659ybn.27.2011.03.28.09.02.40 (version=SSLv3 cipher=OTHER); Mon, 28 Mar 2011 09:02:42 -0700 (PDT) From: Sergio de Almeida Lenzi To: John Baldwin In-Reply-To: <201103280823.23502.jhb@freebsd.org> References: <201103280823.23502.jhb@freebsd.org> Date: Mon, 28 Mar 2011 13:02:39 -0300 Message-ID: <1301328159.12239.16.camel@z6000.lenzicasa> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-acpi@freebsd.org, =?UTF-8?Q?=D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9?= , =?UTF-8?Q?=D0=9A=D1=81=D0=B5=D0=BD=D0=B7=D0=BE=D0=B2_?= Subject: Re: Atheros 9285 & Atheros AR8131 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, 28 Mar 2011 16:24:43 -0000 > > This is probably due to a problem FreeBSD has with ACPI initialization > sometimes wiping out the state in PCI-PCI bridges for resource windows and not > gracefully recovering from that. I have some early work in progress to > address this, but it will be a while before I have something ready for > testing. > it is the acer bios that is does not follow acpi standard... I have the same problem in an old acer 5050 no solution still... I had to install linux in that notebook. My advice is not to buy acer... they are cheap any good... Well let's wait for the Baldwin fix.... From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 28 16:46:03 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 4566D1065675 for ; Mon, 28 Mar 2011 16:46:03 +0000 (UTC) (envelope-from aksenzov@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3C38FC1E for ; Mon, 28 Mar 2011 16:46:02 +0000 (UTC) Received: by iyj12 with SMTP id 12so4761283iyj.13 for ; Mon, 28 Mar 2011 09:46:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=QhFvPEHOQkOCpDJpE7UfBbvgA00+z8CqyptWkfHgRUc=; b=lOeeWk3tJlFatMGNg9lSlowvbl1LrIh9YkbTFiBPiUyDBWbffJa3iBC2EcNMAqrgu5 +x4+zFUzNy3e5FbFZxx28dyGxh+QBIZYTfBn8Ep//w+hfh0ZK37Pvz1VKv41F4pYWIiM uA7CnLuiJpdB102Hzm0VF8012tVf/A3azUsZ4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=kBuKl41qDkJErypXkVs7WZpB+2pz2XqRkdzj/pyRUyD9vctf2CaRBelm4M89ljHh41 JRUhMoMuyowSwVd738+oFzuqTd0UVSVjsbi7Eoo8RxOuHieq2ZXhtNru9Phy8J7ct+6V zpT+LuezKCBwHKxnAA41FKoy2Rgh0XOB3YBgk= MIME-Version: 1.0 Received: by 10.42.175.66 with SMTP id az2mr2188742icb.219.1301330762271; Mon, 28 Mar 2011 09:46:02 -0700 (PDT) Received: by 10.42.74.2 with HTTP; Mon, 28 Mar 2011 09:46:02 -0700 (PDT) In-Reply-To: <1301328159.12239.16.camel@z6000.lenzicasa> References: <201103280823.23502.jhb@freebsd.org> <1301328159.12239.16.camel@z6000.lenzicasa> Date: Tue, 29 Mar 2011 00:46:02 +0800 Message-ID: From: =?KOI8-R?B?69PFztrP1yDhzMXL08XK?= To: Sergio de Almeida Lenzi X-Mailman-Approved-At: Mon, 28 Mar 2011 16:48:07 +0000 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-acpi@freebsd.org Subject: Re: Atheros 9285 & Atheros AR8131 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, 28 Mar 2011 16:46:03 -0000 2011/3/29 Sergio de Almeida Lenzi > > This is probably due to a problem FreeBSD has with ACPI initialization > sometimes wiping out the state in PCI-PCI bridges for resource windows and not > gracefully recovering from that. I have some early work in progress to > address this, but it will be a while before I have something ready for > testing. > > > it is the acer bios that is does not follow acpi standard... I have the > same problem > in an old acer 5050 no solution still... I had to install linux in that > notebook. > > My advice is not to buy acer... they are cheap any good... > > Well let's wait for the Baldwin fix.... > > maybe this can be corrected by editing the ASL? From owner-freebsd-acpi@FreeBSD.ORG Mon Mar 28 18:06:29 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 950671065677 for ; Mon, 28 Mar 2011 18:06:29 +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 69C328FC1B for ; Mon, 28 Mar 2011 18:06:29 +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 B215446B9D; Mon, 28 Mar 2011 14:06:28 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id E136D8A01B; Mon, 28 Mar 2011 14:06:27 -0400 (EDT) From: John Baldwin To: =?utf-8?b?0JrRgdC10L3Qt9C+0LIg0JDQu9C10LrRgdC10Lk=?= Date: Mon, 28 Mar 2011 14:06:27 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110311; KDE/4.5.5; amd64; ; ) References: <1301328159.12239.16.camel@z6000.lenzicasa> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201103281406.27334.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 28 Mar 2011 14:06:28 -0400 (EDT) Cc: freebsd-acpi@freebsd.org Subject: Re: Atheros 9285 & Atheros AR8131 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, 28 Mar 2011 18:06:29 -0000 On Monday, March 28, 2011 12:46:02 pm =D0=9A=D1=81=D0=B5=D0=BD=D0=B7=D0=BE= =D0=B2 =D0=90=D0=BB=D0=B5=D0=BA=D1=81=D0=B5=D0=B9 wrote: > 2011/3/29 Sergio de Almeida Lenzi >=20 > > > > This is probably due to a problem FreeBSD has with ACPI initialization > > sometimes wiping out the state in PCI-PCI bridges for resource windows = and not > > gracefully recovering from that. I have some early work in progress to > > address this, but it will be a while before I have something ready for > > testing. > > > > > > it is the acer bios that is does not follow acpi standard... I have the > > same problem > > in an old acer 5050 no solution still... I had to install linux in th= at > > notebook. > > > > My advice is not to buy acer... they are cheap any good... > > > > Well let's wait for the Baldwin fix.... > > > > > maybe this can be corrected by editing the ASL? We've never figured out what is zeroing the registers in the PCI-PCI bridge= s. I suspect it is not something in the ASL, but is a side effect of some BIOS code that runs in SMM when ACPI is turned on. =2D-=20 John Baldwin From owner-freebsd-acpi@FreeBSD.ORG Tue Mar 29 04:32: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 6C21C106564A; Tue, 29 Mar 2011 04:32:04 +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 7DF198FC12; Tue, 29 Mar 2011 04:32:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id p2T45jqF040904; Tue, 29 Mar 2011 15:05:46 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Tue, 29 Mar 2011 15:05:45 +1100 (EST) From: Ian Smith To: John Baldwin In-Reply-To: <201103280823.23502.jhb@freebsd.org> Message-ID: <20110329143235.F33521@sola.nimnet.asn.au> References: <201103280823.23502.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-681787032-1301371545=:33521" Cc: freebsd-acpi@freebsd.org, aksenzov@gmail.com, Adrian Chadd Subject: Re: Atheros 9285 & Atheros AR8131 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: Tue, 29 Mar 2011 04:32:04 -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-681787032-1301371545=:33521 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Mon, 28 Mar 2011, John Baldwin wrote: > On Saturday, March 26, 2011 1:13:45 pm ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿ wrote: > > Network cards do not work. Tried on systems 8.0, 8.1, and 8.2. Notebook Aser > > Extenza 5635ZG. Tried to change Wi-Fi adapter on the other, but the > > situation has not changed. In all kinds of windows and linux, works fine. > > > > ath0: irq 19 at device 0.0 on pci7 > > ath0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > > ath0: cannot map register space > > device_attach: ath0 attach returned 6 > > > > alc0: irq 17 at device 0.0 on pci9 > > alc0: 0x40000 bytes of rid 0x10 res 3 failed (0, 0xffffffff). > > alc0: cannot allocate memory resources. > > device_attach: alc0 attach returned 6 > > > > Attached: dmesg, sysctl hw.acpi and acpidump -t -d > > This is probably due to a problem FreeBSD has with ACPI initialization > sometimes wiping out the state in PCI-PCI bridges for resource windows and not > gracefully recovering from that. I have some early work in progress to > address this, but it will be a while before I have something ready for > testing. I'd forwarded the original message to adrian@, who's been beavering away on ath recently. His take would seem to complement yours: > Date: Sun, 27 Mar 2011 15:39:03 +0800 > From: Adrian Chadd > To: Ian Smith > Subject: Re: Atheros 9285 & Atheros AR8131 (fwd) > > Hi, > > He's going to have crappy performance on the AR9285 on -8. I fixed a lot > (and I mean a lot!) of AR9285 related bugs. > > But this is likely an ACPI issue and/or general bus issue. He can't map > register space, that needs to be fixed. It's nothing to do with the driver > as far as I can tell; it's to do with the bus management stuff. > > Fix that, then we can work on his AR9285 issues. :) > > Adrian cheers, Ian --0-681787032-1301371545=:33521-- From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 2 15:30: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 4E4C81065672 for ; Sat, 2 Apr 2011 15:30:04 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by mx1.freebsd.org (Postfix) with ESMTP id B82FA8FC17 for ; Sat, 2 Apr 2011 15:30:03 +0000 (UTC) Received: from pool-141-154-217-103.bos.east.verizon.net ([141.154.217.103] helo=homobox.opal.com) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Q62m2-000Nj0-VT for freebsd-acpi@freebsd.org; Sat, 02 Apr 2011 15:30:03 +0000 Received: from opal.com (localhost [IPv6:::1]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id p32FU08W044366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 2 Apr 2011 11:30:01 -0400 (EDT) (envelope-from fbsd@opal.com) Received: from shibato.opal.com ([173.77.114.241] helo=shibato.opal.com) with IPv4:587 by opal.com; 2 Apr 2011 11:30:00 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 141.154.217.103 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX18tBN8oXSb7YjxIUd3k1+Ko Date: Sat, 2 Apr 2011 11:29:58 -0400 From: "J.R. Oldroyd" To: freebsd-acpi@freebsd.org Message-ID: <20110402112958.449d8624@shibato.opal.com> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: pci buses missing from suspend/resume powerstate 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: Sat, 02 Apr 2011 15:30:04 -0000 I've been looking at why some devices do not work after ACPI suspend/resume sequence on a laptop here, and have discovered that two of the system's four PCI buses are not being powered down and up again during the ACPI suspend/resume sequence. This is, I'm guessing, why the devices on those buses no longer work after the resume. Devices on the other PCI buses that are being powered down/up do work OK after the resume. Why would entire PCI buses be omitted from the: acpi_pci_set_powerstate_method power down/up sequence? Laptop has device tree: nexus0 ram0 cryptosoft0 apic0 acpi0 cpu0 hwpstate0 acpi_perf0 cpufreq0 cpu1 acpi_perf1 pcib0 pci0 hostb0 pcib1 pci1 vgapci0 vgapm0 scpm0 acpi_video0 drm0 hdac1 pcm2 pcib2 pci2 ath0 pcib3 pci3 re0 miibus0 rgephy0 If I instrument acpi_pci_set_powerstate_method, it is being called on the suspend/resume for pci0 and pci1 but NOT for pci2 or pci3. After the resume, devices ath0 and re0 no longer work. Any thoughts? Lots more info (devinfo, dmesg, dsdt, verbose boot, pciconf, etc) here: http://opal.com/jr/toshiba_l675d/ -jr From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 2 21:56:55 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 56A29106564A for ; Sat, 2 Apr 2011 21:56:55 +0000 (UTC) (envelope-from jr@opal.com) Received: from mho-01-ewr.mailhop.org (mho-01-ewr.mailhop.org [204.13.248.71]) by mx1.freebsd.org (Postfix) with ESMTP id 0A6818FC1B for ; Sat, 2 Apr 2011 21:56:54 +0000 (UTC) Received: from pool-141-154-217-103.bos.east.verizon.net ([141.154.217.103] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Q68AB-000A7Y-CV for freebsd-acpi@freebsd.org; Sat, 02 Apr 2011 21:15:19 +0000 Received: from opal.com (localhost [IPv6:::1]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id p32LYk8W047392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Apr 2011 17:34:47 -0400 (EDT) (envelope-from jr@opal.com) Received: from shibato.opal.com ([173.77.114.241] helo=shibato.opal.com) with IPv4:587 by opal.com; 2 Apr 2011 17:34:46 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 141.154.217.103 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+Pb11mcV+f3VTtkJEII90d Date: Sat, 2 Apr 2011 17:34:44 -0400 From: "J.R. Oldroyd" To: "J.R. Oldroyd" Message-ID: <20110402173444.6811f735@shibato.opal.com> In-Reply-To: <20110402112958.449d8624@shibato.opal.com> References: <20110402112958.449d8624@shibato.opal.com> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org Subject: Re: pci buses missing from suspend/resume powerstate 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: Sat, 02 Apr 2011 21:56:55 -0000 On Sat, 2 Apr 2011 11:29:58 -0400, "J.R. Oldroyd" wrote: > > [suspend/resume of network cards] > > pcib0 > pci0 > hostb0 > pcib1 > pci1 > vgapci0 > vgapm0 > scpm0 > acpi_video0 > drm0 > hdac1 > pcm2 > pcib2 > pci2 > ath0 > pcib3 > pci3 > re0 > miibus0 > rgephy0 > ... I had been working from this: on suspend: kernel: pci0:1:5:0: Transition from D0 to D3 # vgapci kernel: pci0:1:5:1: Transition from D0 to D3 # hdac1 kernel: pci0:2:0:0: Transition from D0 to D3 # ath0 kernel: pci0:3:0:0: Transition from D0 to D3 # re0 kernel: pci0:0:18:2: Transition from D0 to D3 # ohci0 kernel: pci0:0:19:2: Transition from D0 to D3 # ohci1 kernel: pci0:0:20:2: Transition from D0 to D3 # hdac0 but on resume, only: kernel: pci0:0:18:2: Transition from D3 to D0 kernel: pci0:0:19:2: Transition from D3 to D0 which had led me to think the buses were not being resumed. Looking further at this, two things come to light: - they ARE being suspended using set_powerstate to D3, but after the resume, their powerstate still shows as D0, so set_powerstate is not being re-invoked to actually set D0 again - the PCI-PCI bridges pcib1, pcib2, pcib3 have hdrtype==1 and so are also excluded from the set_powerstate (don't know if that's OK or not) But, overriding those checks and forcing set_powerstate D0 to be invoked for all devices still doesn't get ath0 or re0 working after the resume. I have an older but similar laptop model with the same configuration of ath0 and re0 also on secondary PCI buses pci2 and pci3 and that one does suspend/resume properly. But on the newer laptop: kernel: ath0: unable to reset hardware; hal status 3 kernel: re0: reset never completed! kernel: re0: PHY write failed last message repeated 4 times So this problem is specific to this newer hardware. Perhaps related to the PCI-PCI bridges? pcib2 and pcib3 are both devid=96xx1022... perhaps some odd quirk handling is needed here? -jr From owner-freebsd-acpi@FreeBSD.ORG Sat Apr 2 22:10:42 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 AB795106564A for ; Sat, 2 Apr 2011 22:10:42 +0000 (UTC) (envelope-from fbsd@opal.com) Received: from mho-01-ewr.mailhop.org (mho-01-ewr.mailhop.org [204.13.248.71]) by mx1.freebsd.org (Postfix) with ESMTP id 63A148FC08 for ; Sat, 2 Apr 2011 22:10:42 +0000 (UTC) Received: from pool-141-154-217-103.bos.east.verizon.net ([141.154.217.103] helo=homobox.opal.com) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1Q68is-000M2Z-U0 for freebsd-acpi@freebsd.org; Sat, 02 Apr 2011 21:51:11 +0000 Received: from opal.com (localhost [IPv6:::1]) (authenticated bits=0) by homobox.opal.com (8.14.4/8.14.4) with ESMTP id p32MAcQ4047688 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 2 Apr 2011 18:10:39 -0400 (EDT) (envelope-from fbsd@opal.com) Received: from shibato.opal.com ([173.77.114.241] helo=shibato.opal.com) with IPv4:587 by opal.com; 2 Apr 2011 18:10:38 -0400 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 141.154.217.103 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+n/AO/DRMDlSjOCvqsH1Hw Date: Sat, 2 Apr 2011 18:10:37 -0400 From: "J.R. Oldroyd" To: freebsd-acpi@freebsd.org Message-ID: <20110402181037.0eea27c1@shibato.opal.com> In-Reply-To: <20110402112958.449d8624@shibato.opal.com> References: <20110402112958.449d8624@shibato.opal.com> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: pci buses missing from suspend/resume powerstate 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: Sat, 02 Apr 2011 22:10:42 -0000 On Sat, 2 Apr 2011 11:29:58 -0400, "J.R. Oldroyd" wrote: > > [suspend/resume of network cards] > > pcib0 > pci0 > hostb0 > pcib1 > pci1 > vgapci0 > vgapm0 > scpm0 > acpi_video0 > drm0 > hdac1 > pcm2 > pcib2 > pci2 > ath0 > pcib3 > pci3 > re0 > miibus0 > rgephy0 > ... I had been working from this: on suspend: kernel: pci0:1:5:0: Transition from D0 to D3 # vgapci kernel: pci0:1:5:1: Transition from D0 to D3 # hdac1 kernel: pci0:2:0:0: Transition from D0 to D3 # ath0 kernel: pci0:3:0:0: Transition from D0 to D3 # re0 kernel: pci0:0:18:2: Transition from D0 to D3 # ohci0 kernel: pci0:0:19:2: Transition from D0 to D3 # ohci1 kernel: pci0:0:20:2: Transition from D0 to D3 # hdac0 but on resume, only: kernel: pci0:0:18:2: Transition from D3 to D0 kernel: pci0:0:19:2: Transition from D3 to D0 which had led me to think the buses were not being resumed. Looking further at this, two things come to light: - they ARE being suspended using set_powerstate to D3, but after the resume, their powerstate still shows as D0, so set_powerstate is not being re-invoked to actually set D0 again - the PCI-PCI bridges pcib1, pcib2, pcib3 have hdrtype==1 and so are also excluded from the set_powerstate (don't know if that's OK or not) But, overriding those checks and forcing set_powerstate D0 to be invoked for all devices still doesn't get ath0 or re0 working after the resume. I have an older but similar laptop model with the same configuration of ath0 and re0 also on secondary PCI buses pci2 and pci3 and that one does suspend/resume properly. But on the newer laptop: kernel: ath0: unable to reset hardware; hal status 3 kernel: re0: reset never completed! kernel: re0: PHY write failed last message repeated 4 times So this problem is specific to this newer hardware. Perhaps related to the PCI-PCI bridges? pcib2 and pcib3 are both devid=96xx1022... perhaps some odd quirk handling is needed here? -jr