lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.1.10.0810161525450.3026@localhost.localdomain>
Date:	Thu, 16 Oct 2008 15:31:38 -0400 (EDT)
From:	Len Brown <lenb@...nel.org>
To:	"Brown, John M (WGBU R&D)" <john.brown3@...com>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] ACPI suspend: Blacklist HP xw4600 Workstation for old code
 ordering

> I also noted that acpidump printed this message to stderr:
> Wrong checksum for FADT!

The RSDT has a pointer to an FACP at DEFC2014 (aka FADT),
and that FACP has a bad checksum.

But this system has an XSDT, which the OS prefers
over the RSDT.  The XSDT points to an FACP at DEFC2088
and its checksum is fine.

This difference is moot here,
because both FACP's point to the same DSDT at DEFC2647,
and it is the DSDT that has the AML related to ordering.

The reason you see this error message from acpidump
and not from Linux is that the kernel only uses the 'active' 
tables, while acpidump snags both the active and insactive tables
for debugging.

cheers,
-Len

> -----Original Message-----
> From: Rafael J. Wysocki [mailto:rjw@...k.pl]
> Sent: Wednesday, October 15, 2008 4:01 PM
> To: Len Brown
> Cc: Brown, John M (WGBU R&D); Matthew Garrett; ACPI Devel Maling List; Andrew Morton; LKML
> Subject: Re: [PATCH] ACPI suspend: Blacklist HP xw4600 Workstation for old code ordering
> 
> On Wednesday, 15 of October 2008, Len Brown wrote:
> > Matthew,
> > You are right, of course, we're not doing something right if a new
> > machine needs this workaround.
> 
> Isn't that possible, however, that the BIOS of this new machine is based on an older one that used to have this problem?
> 
> > However, we don't yet know what we're not doing right:-)
> 
> Well, John, can you please post the output of acpidump from this machine?
> 
> Thanks,
> Rafael
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ