From: Len Brown <lenb@kernel.org>
To: jason hu <huzhijiang@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: acpi_osi Linux report and questions
Date: Thu, 13 Dec 2007 16:06:58 -0500 [thread overview]
Message-ID: <200712131606.58331.lenb@kernel.org> (raw)
In-Reply-To: <4760BDDC.60602@gmail.com>
On Thursday 13 December 2007 00:06, jason hu wrote:
> Hi All,
>
> With acpi_osi=Linux, which dmesg suggested, I got something changed in
> the dmesg output(I just listed out the most important things):
>
>
> diff !Linux Linux
> 79c80
> < Detected 1733.505 MHz processor.
> ---
> > Detected 1733.456 MHz processor.
> 95c96
> < Calibrating delay using timer specific routine.. 3470.37 BogoMIPS
> (lpj=1735185)
> ---
> > Calibrating delay using timer specific routine.. 3470.36 BogoMIPS
> (lpj=1735181)
> 121c122
> < Calibrating delay using timer specific routine.. 3466.35 BogoMIPS
> (lpj=1733178)
> ---
> > Calibrating delay using timer specific routine.. 3466.36 BogoMIPS
> (lpj=1733183)
These are not important.
> < PCI: Cannot allocate resource region 7 of bridge 0000:00:06.0
> < PCI: Cannot allocate resource region 8 of bridge 0000:00:06.0
> 207c206
> < MEM window: disabled.
> ---
> > MEM window: c0100000-c01fffff
These may be important.
> It seems with acpi_osi=Linux, it mainly made the two processors equals
> in BogoMIPS and made a PCI device window available.
>
> I am not so familiar with ACPI, so can you tell me what is
> acpi_osi=Linux used for, and why it made such changes above? Thank you!
The BIOS uses it to figure out if the OS is compatible with the
capabilities of Linux. Unfortunately, the capabilities of Linux
are changing over time, and mose BIOS detection of Linux leads
to worse behaviour rather than better...
Please file a bug report.
attach the output from acpidump, both dmesg, and the dmidecode output.
thanks,
-Len
next prev parent reply other threads:[~2007-12-13 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 5:06 acpi_osi Linux report and questions jason hu
2007-12-13 21:06 ` Len Brown [this message]
2007-12-15 19:05 ` jason hu
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=200712131606.58331.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=huzhijiang@gmail.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