archive mirror
 help / color / mirror / Atom feed
Subject: [Bug 213977] New: Unable to lock HW IRQ 44 TigerLake
Date: Wed, 04 Aug 2021 19:52:54 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 213977
           Summary: Unable to lock HW IRQ 44 TigerLake
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.13.6-200
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Platform_x86
        Regression: No

Created attachment 298201
acpidump -o clevo-tables.dat


I was told to open another report with an acpi dump. I do not have anything
else custom in my kernel except for including the .patch file in the following
post. I added to the .patch file to the SOURCES dir and added in to the
kernel.spec and rebuilt the kernel package and installed it. Still getting the
below error. 


[  924.443744] tigerlake-pinctrl INT34C6:00: pin 57 cannot be used as IRQ
[  924.443746] genirq: Setting trigger mode 8 for irq 131 failed
[  924.448165] gpio gpiochip0: (INT34C6:00): gpiochip_lock_as_irq: cannot get
GPIO direction
[  924.448166] gpio gpiochip0: (INT34C6:00): unable to lock HW IRQ 44 for IRQ
[  924.448167] genirq: Failed to request resources for ELAN0412:01 (irq 131) on
irqchip INT34C6:00
[  924.448174] i2c_hid_acpi i2c-ELAN0412:01: Could not register for ELAN0412:01
interrupt, irq = 131, ret = -22
[  924.448201] i2c_hid_acpi: probe of i2c-ELAN0412:01 failed with error -22

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2021-08-04 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-04 19:52 bugzilla-daemon [this message]
2021-08-04 19:55 ` [Bug 213977] Unable to lock HW IRQ 44 :: TigerLake Proc :: Clevo NH58HPQ bugzilla-daemon
2021-08-04 20:53 ` bugzilla-daemon
2021-08-04 21:21 ` bugzilla-daemon
2021-08-05  8:40 ` bugzilla-daemon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).