Message-ID: <487F3AFA.7090908@linux.intel.com>
Date: Thu, 17 Jul 2008 14:28:42 +0200
From: Andi Kleen <ak@linux.intel.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Jan Beulich <jbeulich@novell.com>
CC: robert.moore@intel.com, Andrew Paprocki <andrew@ishiboo.com>,
       Len Brown <lenb@kernel.org>, Andrew Morton <akpm@linux-foundation.org>,
       LKML <linux-kernel@vger.kernel.org>
Subject: Re: ACPI WARNING: at	drivers/acpi/tables/tbfadt.c:348	acpi_tb_create_local_fadt+0x147/0x2f4()
References: <76366b180807161929i4eb9462exc3d2255e0ec881e8@mail.gmail.com> <76366b180807162034y1e725b15t7658c331bb89b52@mail.gmail.com> <487F2629.76E4.0078.0@novell.com> <487F0B85.4030202@linux.intel.com> <487F29B2.76E4.0078.0@novell.com>
In-Reply-To: <487F29B2.76E4.0078.0@novell.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 879
Lines: 23

Jan Beulich wrote:
>> The question is just if the hardware is really 8 bits or if the table
>> is not just wrong. What does lspci say?
> 
> What would lspci have to do with this? 

When it's an chipset with available data sheets one could check that.

> /proc/acpi/fadt (from an older
> kernel if the new one fails to come up) would seem to help somewhat,
> as that would allow comparing the v1 (byte-width) and v2 (bit-width)
> values - if they're out of sync (and they likely are if the system worked
> flawlessly with previous kernels), I'd be certain the tables are wrong.

Ok, but we can just get that from a table dump.

-Andi

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/