From: Len Brown <lenb@kernel.org>
To: David Carlos Manuelda <stormbyte@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: A couple of things about ACPI
Date: Tue, 18 Sep 2007 11:12:14 -0400 [thread overview]
Message-ID: <200709181112.14834.lenb@kernel.org> (raw)
In-Reply-To: <200709181610.52771.StormByte@gmail.com>
On Tuesday 18 September 2007 10:10, David Carlos Manuelda wrote:
> I've seen in dmesg some things I wanted to comment to you.
>
> First of all, I've seen a message at boot:
>
> ACPI: System BIOS is requesting _OSI(Linux)
> ACPI: Please test with "acpi_osi=!Linux"
> Please send dmidecode to linux-acpi@vger.kernel.org
>
> I've tested with that boot option, and I see exactly same message (maybe a
> bug?)
thanks, i'll look at this.
i also need to simplify it so that it just prints out the dmi into
right in the dmesg instead of asking for dmidecode....
we can tell exactly what this does if you open up a bug report
and attach the output from acpidump.
So far, i've seen OSI(Linux) used only for video re-post on resume.
> dmidecode is attached.
> =========================
> I've seen:
> ACPI: BIOS bug: multiple APIC/MADT found, using 0
> ACPI: If "acpi_apic_instance=2" works better, notify
> linux-acpi@vger.kernel.org
> Testing with that option, I see no difference, except the message change, now
> says:
> ACPI: BIOS bug: multiple APIC/MADT found, using 2
> ACPI: If "acpi_apic_instance=0" works better, notify
> linux-acpi@vger.kernel.org
> =========================
> I don't know what it is exactly, but I mail you with information requested.
>
> Please let me know if it is useful, and if you need more info, just tell me.
again, the acpidump will tell us the two table contents and we can compare.
when they are very broken, usually an IRQ is mis-routed (could tell from
both /proc/interrupts) or not all the processors are enumerated.
> This is a Samsung R70 laptop, intel core2 duo 1800, 2GB ram 'Santa Rosa'.
>
> By the way, info of dmidecode is not 100% correct, I don't know why. This is
> what is not correct:
>
> extract of dmidecode.txt:
> ====================
> Handle 0x000B, DMI type 10, 6 bytes
> On Board Device Information
> Type: Sound
> Status: Disabled (***!!! Sound is enabled and fully functional)
> Description: HD-Audio
DMI info is generally typed in by hand, and it is common for it
to be full of errors.
thanks,
-Len
prev parent reply other threads:[~2007-09-18 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 14:10 A couple of things about ACPI David Carlos Manuelda
2007-09-18 15:12 ` Len Brown [this message]
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=200709181112.14834.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=stormbyte@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).