From: Len Brown <lenb@kernel.org>
To: Lexington Luthor <lexington.luthor@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: dmidecode - Dell Inspiron 1501
Date: Fri, 18 Jan 2008 22:55:28 -0500 [thread overview]
Message-ID: <200801182255.28510.lenb@kernel.org> (raw)
In-Reply-To: <fc8i45$fh4$1@sea.gmane.org>
On Wednesday 12 September 2007 07:20, Lexington Luthor wrote:
> Hi,
>
> Running vanilla 2.6.22.6 on a Dell Inspiron 1501 (w/ latest BIOS
> update), the kernel says:
> ...
> Sep 12 11:49:27 [kernel] ACPI: System BIOS is requesting _OSI(Linux)
> Sep 12 11:49:27 [kernel] ACPI: Please test with "acpi_osi=!Linux"
> Sep 12 11:49:27 [kernel] Please send dmidecode to linux-acpi@vger.kernel.org
> Sep 12 11:49:27 [kernel] ACPI: Interpreter enabled
> Sep 12 11:49:27 [kernel] ACPI: Using IOAPIC for interrupt routing
> ...
>
> The machine itself is stable under load (aside from wifi network drops,
> but thats a known bcm43xx tx power problem), aside from an occasional
> message in dmesg saying stuff like:
> Sep 12 07:21:45 [kernel] APIC error on CPU0: 00(40)
> Sep 12 07:21:48 [kernel] APIC error on CPU1: 00(40)
> Sep 12 07:28:27 [kernel] APIC error on CPU0: 40(40)
> Sep 12 07:28:46 [kernel] APIC error on CPU1: 40(40)
I think you can ignore them, just like you can ignore
strange engine noises from inexpensive autos:-)
System Information
Manufacturer: Dell Inc.
Product Name: Inspiron 1501
Version: Not Specified
Serial Number: HR9ZX2J
UUID: 44454C4C-5200-1039-805A-C8C04F58324A
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0003, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0UW744
Thanks for the dmidecode output.
Do you notice any functional difference when booting with
"acpi_osi=Linux" (default for 2.6.22 and earlier)
vs.
"acpi_osi=!Linux" (default for 2.6.23 and later)
Also, please send me the output from acpidump.
thanks,
-Len
ps
If you don't have acpidump, you can get it from pmtools here:
http://www.lesswatts.org/projects/acpi/utilities.php
prev parent reply other threads:[~2008-01-19 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 11:20 dmidecode Lexington Luthor
2008-01-19 3:55 ` 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=200801182255.28510.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=lexington.luthor@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.