From: Taku Izumi <izumi.taku@jp.fujitsu.com>
To: linux-acpi@vger.kernel.org
Subject: BIOS _OSI(Linux) query ignored on PRIMEQUEST
Date: Tue, 29 Apr 2008 19:34:33 +0900 [thread overview]
Message-ID: <4816F9B9.3090609@jp.fujitsu.com> (raw)
Hi all,
The following message is displayed on our server(PRIMEQUEST):
ACPI: bus type pci registered
ACPI: EC: Look up EC in DSDT
ACPI: BIOS _OSI(Linux) query ignored
ACPI: DMI System Vendor: <NULL>
ACPI: DMI Product Name: <NULL>
ACPI: DMI Product Version: <NULL>
ACPI: DMI Board Name: <NULL>
ACPI: DMI BIOS Vendor: FUJITSU LIMITED
ACPI: DMI BIOS Date: 1/17/2008
ACPI: Please send DMI info above to linux-acpi@vger.kernel.org
ACPI: If "acpi_osi=Linux" works better, please notify
linux-acpi@vger.kernel.org
Because "acpi_osi=Linux" boot option works well, so we want to
use _OSI(Linux) query on PRIMEQUEST without this boot option and
inihibit above message.
I thought the way to achive our goal was to add
the following entry to acpi_osi_dmi_table
(at drivers/acpi/blacklist.c),
{
.callback = dmi_enable_osi_linux,
.ident = "Fujitsu PRIMEQUEST",
.matches = {
DMI_MATCH(DMI_BIOS_VENDOR, "FUJITSU LIMITED"),
},
}
but unfortunately this table seems to be valid only for x86 machines.
Our server is ia64, but what is the best solution?
--
Regards,
Taku Izumi <izumi.taku@jp.fujitsu.com>
next reply other threads:[~2008-04-29 10:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 10:34 Taku Izumi [this message]
2008-05-23 6:36 ` [PATCH 0/2] ACPI: add "OSI(Linux) checking procedure" for ia64 machines Taku Izumi
2008-05-23 6:39 ` [PATCH 1/2] ACPI: add acpi_osi_dmi_table evaluation procedure " Taku Izumi
2008-05-23 6:43 ` [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST Taku Izumi
2008-05-25 11:43 ` Pavel Machek
2008-05-26 7:56 ` Taku Izumi
2008-05-26 8:06 ` Pavel Machek
2008-05-27 1:13 ` KAMEZAWA Hiroyuki
2008-05-27 2:05 ` Arjan van de Ven
2008-05-27 23:20 ` Andrew Morton
2008-05-27 23:41 ` Tony Luck
2008-05-27 23:50 ` Andrew Morton
2008-05-28 4:04 ` Luck, Tony
2008-05-28 0:09 ` KAMEZAWA Hiroyuki
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=4816F9B9.3090609@jp.fujitsu.com \
--to=izumi.taku@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
/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