Date: Thu, 25 Feb 2010 18:18:08 +0200 From: Andriy Gapon <avg@icyb.net.ua> To: John Baldwin <jhb@freebsd.org> Cc: kochetkov.andrew@gmail.com, Randy Chou <randychou@yahoo.com>, agh@coolrhaug.com, freebsd-hardware@freebsd.org Subject: Re: Intel DP45SG motherboard problem (amd64) Message-ID: <4B86A2C0.10502@icyb.net.ua> In-Reply-To: <201002250802.58434.jhb@freebsd.org> References: <201002212231.12018.agh@coolrhaug.com> <201002240946.29754.jhb@freebsd.org> <201002250732.21691.agh@coolrhaug.com> <201002250802.58434.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 25/02/2010 15:02 John Baldwin said the following: > Hmm, the checksum for the XSDT is bad. You can try hacking > src/usr.sbin/acpi/acpidump/acpi.c to disable the checksum check for the XSDT. > Just look for the 'XSDT is corrupted' string in that source file and comment > out the call to acpi_checksum(). Something like this: > > rsdp = (ACPI_TABLE_HEADER *)acpi_map_sdt(rp->XsdtPhysicalAddress); > if (memcmp(rsdp->Signature, "XSDT", 4) != 0 /* || > acpi_checksum(rsdp, rsdp->Length) != 0 */) > errx(1, "XSDT is corrupted"); > addr_size = sizeof(uint64_t); > > Then see if acpidump -d -t gets any further. I would also look for a BIOS > update perhaps, and/or complain to your motherboard vendor that their BIOS is > broken. BTW, I googled for 'DP45SG XSDT' and addition to this thread it turned up some linux boot logs with complaints about invalid XSDT checksums. But linux seems to be more forgiving, it's just a warning. E.g. see here (search for XSDT): http://bugs.gentoo.org/attachment.cgi?id=201949&action=view -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B86A2C0.10502>