From: Orion Poplawski <orion@cora.nwra.com>
To: linux-acpi@vger.kernel.org
Subject: ACPI Log messages level
Date: Mon, 29 Sep 2014 11:59:14 -0600 [thread overview]
Message-ID: <54299DF2.2070709@cora.nwra.com> (raw)
I'm trying to just look at just "warning" level messages and above with
"journalctl --priority 0..4", but am seeing the following which appear to be
informational only:
Sep 29 11:10:24 barry kernel: ACPI: RSDP 0x00000000000FEC30 000024 (v02 DELL )
Sep 29 11:10:24 barry kernel: ACPI: XSDT 0x00000000000FCCC7 000074 (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: FACP 0x00000000000FCDB7 0000F4 (v03 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: DSDT 0x00000000FFE9E952 004A74 (v01 DELL
dt_ex 00001000
Sep 29 11:10:24 barry kernel: ACPI: FACS 0x00000000DFDF9C00 000040
Sep 29 11:10:24 barry kernel: ACPI: SSDT 0x00000000FFEA33C6 000089 (v01 DELL
st_ex 00001000
Sep 29 11:10:24 barry kernel: ACPI: APIC 0x00000000000FCEAB 00015E (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: BOOT 0x00000000000FD009 000028 (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: ASF! 0x00000000000FD031 000096 (v32 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: MCFG 0x00000000000FD0C7 00003C (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: HPET 0x00000000000FD103 000038 (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: TCPA 0x00000000000FD35F 000032 (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: DMAR 0x00000000000FD391 0000B8 (v01 DELL
B10K 00000015
Sep 29 11:10:24 barry kernel: ACPI: SSDT 0x00000000DFE4DC00 002454 (v01 INTEL
PPM RCM 80000001
Sep 29 11:10:24 barry kernel: DMA [mem 0x00001000-0x00ffffff]
Sep 29 11:10:24 barry kernel: DMA32 [mem 0x01000000-0xffffffff]
Sep 29 11:10:24 barry kernel: Normal [mem 0x100000000-0x61fffffff]
Sep 29 11:10:24 barry kernel: ACPI: All ACPI Tables successfully acquired
Sep 29 11:10:24 barry kernel: ACPI: Enabled 3 GPEs in block 00 to 3F
I see this:
./drivers/acpi/acpica/tbxfload.c:
ACPI_INFO((AE_INFO, "All ACPI Tables successfully acquired"));
which would appear to be sending the message with INFO priority, so I don't
understand why this is appearing here. This is with kernel
3.16.3-200.fc20.x86_64.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion@nwra.com
Boulder, CO 80301 http://www.nwra.com
reply other threads:[~2014-09-29 18:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54299DF2.2070709@cora.nwra.com \
--to=orion@cora.nwra.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.