From owner-freebsd-acpi@FreeBSD.ORG Fri Apr 26 19:01:18 2013 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A7612D01; Fri, 26 Apr 2013 19:01:18 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mx1.freebsd.org (Postfix) with ESMTP id 5BF5918A4; Fri, 26 Apr 2013 19:01:17 +0000 (UTC) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP; 26 Apr 2013 12:01:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,559,1363158000"; d="scan'208";a="324717176" Received: from fmsmsx104.amr.corp.intel.com ([10.19.9.35]) by fmsmga001.fm.intel.com with ESMTP; 26 Apr 2013 11:59:22 -0700 Received: from fmsmsx155.amr.corp.intel.com (10.18.116.71) by FMSMSX104.amr.corp.intel.com (10.19.9.35) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 26 Apr 2013 11:59:22 -0700 Received: from fmsmsx153.amr.corp.intel.com ([169.254.9.79]) by FMSMSX155.amr.corp.intel.com ([169.254.5.136]) with mapi id 14.01.0355.002; Fri, 26 Apr 2013 11:59:20 -0700 From: "Moore, Robert" To: Benjamin Lee Subject: RE: panic: acpi_pci_link_srs_from_crs: can't put non-ISA IRQ 20 in legacy IRQ resource type) Thread-Topic: panic: acpi_pci_link_srs_from_crs: can't put non-ISA IRQ 20 in legacy IRQ resource type) Thread-Index: AQHOPG391d2djyxEFEWgLAw8ZTDWIJjeIoGAgABQL4CAABLrgIAAD0UAgADpmYCAAeY2AIAE2ziAgAMXcQD//4+sMA== Date: Fri, 26 Apr 2013 18:59:20 +0000 Message-ID: <94F2FBAB4432B54E8AACC7DFDE6C92E36FE44F8D@FMSMSX153.amr.corp.intel.com> References: <20130418124940.47e3618a@b1c1l1.com> <201304191726.31089.jhb@freebsd.org> <20130419152110.213c7fbb@b1c1l1.com> <201304200817.15189.jhb@freebsd.org> <20130421101728.6fc33a96@b1c1l1.com> <94F2FBAB4432B54E8AACC7DFDE6C92E36FE43F55@FMSMSX153.amr.corp.intel.com> <20130426113948.10b5400e@b1c1l1.com> In-Reply-To: <20130426113948.10b5400e@b1c1l1.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "freebsd-acpi@freebsd.org" , "Guan, Chao" , "Zheng, Lv" X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Apr 2013 19:01:18 -0000 > -----Original Message----- > From: Benjamin Lee [mailto:ben@b1c1l1.com] > Sent: Friday, April 26, 2013 11:40 AM > To: Moore, Robert > Cc: John Baldwin; freebsd-acpi@freebsd.org; Zheng, Lv; Guan, Chao > Subject: Re: panic: acpi_pci_link_srs_from_crs: can't put non-ISA IRQ 20 > in legacy IRQ resource type) >=20 > On Thu, 25 Apr 2013 02:28:25 +0000, "Moore, Robert" > wrote: > > > Thank you! I backed out my hacks and with your 2 patches 10-CURRENT > > > boots successfully (with functional devices). Loading a custom ASL > > > is not necessary. > > > > Do you mean that the change of a WORD field to a BYTE field is no longe= r > necessary? > > > > If so, I would really like to see the buffer that is being sent to _SRS= . >=20 > Yes, the change of WORD to BYTE is not necessary with 10-CURRENT. >=20 > I don't understand ACPI well enough to answer your followup. All I know > is that there is some change in the ACPI parsing behavior between 9-STABL= E > (which triggers AE_AML_BUFFER_LIMIT in the broken _SRS method) and 10- > CURRENT (which used to panic but after jhb's fixes now boots correctly). > Could it be possible that _SRS is not being called at all with the new > ACPI code? >=20 _SRS is called from the driver software, so ACPICA is not involved. It may = be that the resource descriptor is now a little longer and the WORD access = no longer goes beyond the end of the buffer. Still, I'm a bit worried about it anyway. >=20 > -- > Benjamin Lee > http://www.b1c1l1.com/