mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: "Brown, John M (WGBU R&D)" <john.brown3@hp.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] ACPI suspend: Blacklist HP xw4600 Workstation for old code ordering
Date: Thu, 16 Oct 2008 15:31:38 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0810161525450.3026@localhost.localdomain> (raw)
In-Reply-To: <C075D3D77BA5EF4FBB0939047B182ABF25C79ADA45@GVW1144EXB.americas.hpqcorp.net>

> 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@sisk.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
> 

  reply	other threads:[~2008-10-16 19:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 20:54 Rafael J. Wysocki
2008-10-15  8:58 ` Matthew Garrett
2008-10-15 14:05   ` Rafael J. Wysocki
2008-10-15 14:15     ` Matthew Garrett
2008-10-15 20:35       ` Brown, John M (WGBU R&D)
2008-10-15 21:49         ` Len Brown
2008-10-15 22:00           ` Rafael J. Wysocki
2008-10-16 17:01             ` Brown, John M (WGBU R&D)
2008-10-16 19:31               ` Len Brown [this message]
2008-10-15 21:20       ` Rafael J. Wysocki
2008-11-22 11:11         ` Carlos Corbacho
2008-11-22 12:56           ` Rafael J. Wysocki
2008-10-16  9:13   ` Pavel Machek
2008-10-16  9:12 ` Pavel Machek
     [not found] <fa./6DR3VeG3JltQZvwctIdnZpBOO8@ifi.uio.no>
     [not found] ` <fa.TMVI/3KJQDTBIWAfYmLw01GczF4@ifi.uio.no>
     [not found]   ` <fa./GCX/x0zwCB6BIEvtQehNpVDSVk@ifi.uio.no>
     [not found]     ` <fa.MkpTJy5Iw9ZR3PXWpugQeK5oN1o@ifi.uio.no>
2008-10-17  4:07       ` Robert Hancock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.1.10.0810161525450.3026@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=john.brown3@hp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®