From: Ben Hutchings <ben@decadent.org.uk>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: 1041484@bugs.debian.org, Al Ma <alma0@ro.ru>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel: hpet_acpi_add: no address or irqs in _CRS
Date: Sun, 22 Sep 2024 21:53:57 +0200 [thread overview]
Message-ID: <bb1ee774f6b5a00a3a735389b14e8cf86d5ca187.camel@decadent.org.uk> (raw)
In-Reply-To: <5183ae1168b9661a6c31a15b02802db6@mail.rambler.ru>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
On Wed, 2023-07-19 at 15:04 +0000, Al Ma wrote:
> Package: linux-image-6.1.0-10-amd64
> Version: 6.1.37-1
> In the journal of a laptop Lenovo ThinkPad T14s Gen1, connected to a docking station ThinkPad Thunderbolt 3 Dock Gen 2/Workstation Dock Gen 2 Type 40 AN (which is powered by a 135 W AC Adapter ADL135NCC3A) and to a monitor Philips 275B1 via a HMDI cable, we discovered the following warning (last line is yellow) generated at boot:
[...]
> Jul 19 16:20:34 AnonymizedLenovoThinkPadT14s kernel: hpet_acpi_add: no address or irqs in _CRS
[...]
This was also reported as appearing on Lenovo ThinkPad T14 gen 4
running Linux 6.10. I searched for the warning on lore.kernel.org and
found that it also appeared on:
- Dell XPS 13 9360/0596KF, Linux 6.9-6.11
- Intel NUC12WSHi7/NUC12WSBi7, Linux 6.11
- Lenovo IdeaPad 82MG, Linux 6.1
- Lenovo ThinkPad T480, Linux 6.10
- System76 Pangolin, Linux 6.11
Is this likely to be a bug in the driver, or in the firmware? If this
is a common case where the HPET isn't available and has an incomplete
description in the ACPI table, should the warning message be downgraded
to info level?
Ben.
--
Ben Hutchings
The two most common things in the universe are hydrogen and stupidity.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2024-09-22 19:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5183ae1168b9661a6c31a15b02802db6@mail.rambler.ru>]
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=bb1ee774f6b5a00a3a735389b14e8cf86d5ca187.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=1041484@bugs.debian.org \
--cc=alma0@ro.ru \
--cc=clemens@ladisch.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®