Date: Fri, 23 Oct 2009 13:03:23 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Erwan Velu <erwanaliasr1@gmail.com>, Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] dmi_check_system can generate Warnings when no DMI
	table is present
Message-ID: <20091023110323.GC10071@elte.hu>
References: <4AE178AF.3010804@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4AE178AF.3010804@gmail.com>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1071
Lines: 28


* Erwan Velu <erwanaliasr1@gmail.com> wrote:

> When running the Linux Kernel, on some systems that doesn't have any DMI  
> table (like a Xen domU), some dmi_* calls can generates Warnings like :
>
>> / WARNING: at /usr/src/linux-2.6.29.1/drivers/firmware/dmi_scan.c:425/
>> / dmi_matches+0x7e/0x80()/
>> / dmi check: not initialized yet/

Empty DMI tables are common. What is not common is to call dmi_matches() 
before the DMI strings code has initialized.

> Some users reported this error : 
> http://lists.xensource.com/archives/html/xen-users/2009-04/msg00128.html 
> https://qa.mandriva.com/show_bug.cgi?id=54775

Looks like a Xen bug. DMI matching functions should be called after that 
code has initialized. The warning was added to catch such early calls.

Your patch works around that bug and the warning.

	Ingo
--
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/