Date: Thu, 9 Apr 2015 08:24:19 +0200 From: Dimitry Andric <dim@FreeBSD.org> To: Slawa Olhovchenkov <slw@zxy.spb.ru> Cc: svn-src-stable@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, svn-src-stable-10@freebsd.org Subject: Re: svn commit: r281075 - in stable/10: sys/conf sys/contrib/dev/acpica sys/contrib/dev/acpica/common sys/contrib/dev/acpica/compiler sys/contrib/dev/acpica/components/debugger sys/contrib/dev/acpica/c... Message-ID: <FA6847C9-C057-4822-816A-08162033063E@FreeBSD.org> In-Reply-To: <20150408232131.GB1394@zxy.spb.ru> References: <201504041017.t34AHr5R059717@svn.freebsd.org> <20150408232131.GB1394@zxy.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 09 Apr 2015, at 01:21, Slawa Olhovchenkov <slw@zxy.spb.ru> wrote: > > On Sat, Apr 04, 2015 at 10:17:53AM +0000, Dimitry Andric wrote: > >> Author: dim >> Date: Sat Apr 4 10:17:51 2015 >> New Revision: 281075 >> URL: https://svnweb.freebsd.org/changeset/base/281075 >> >> Log: >> MFC r272444 (by jkim): >> >> Merge ACPICA 20140926. >> >> MFC r278970 (by jkim): >> >> Merge ACPICA 20141107 and 20150204. >> >> Approved by: jkim >> Relnotes: yes >> > > Some time ago `acpidump -dt` was broken for me: > > # acpidump -dt > /* > RSD PTR: OEM=ALASKA, ACPI_Rev=2.0x (2) > XSDT=0x7f1e6080, length=36, cksum=95 > */ > /* > XSDT: Length=132, Revision=1, Checksum=106, > OEMID=ALASKA, OEM Table ID=A M I, OEM Revision=0x1072009, > Creator ID=AMI, Creator Revision=0x10013 > Assertion failed: (addr != 0), function acpi_print_rsdt, file /usr/src/usr.sbin/acpi/acpidump/acpi.c, line 1097. > Entries={ 0x7f1efe90, 0x7f1eff88, 0x7f1f0098, 0x7f1f00d8, 0x7f1f0448, 0x7f1f0478, 0x7f1f04b0, 0x7f1f0570, 0x7f1f05b0, 0x7f2606b8, 0x7f260708, Abort (core dumped) Hi Slawa, Is there a PR for this? And a core dump or (preferably) a reproduction scenario? From a quick look, it seems that your RSDT contains an entry with an address size which is neither 4 nor 8, and that leads to the assertion failure. I am unsure whether there is any upstream fix for it. -Dimitry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUmGx0ACgkQsF6jCi4glqMlgwCg/10j4wpjTR5LJZgtCfJOv8wf r/0AoPIXnLMXi3teaDRq6+cY0ehYmEaw =wGtn -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FA6847C9-C057-4822-816A-08162033063E>