From: Jean Delvare <jdelvare@suse.de>
To: Marius Hoch <mail@mariushoch.de>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450
Date: Mon, 19 Jun 2023 17:19:12 +0200 [thread overview]
Message-ID: <20230619171912.5407a7eb@endymion.delvare> (raw)
In-Reply-To: <967411b3-7013-619e-4fef-90644fa8d489@mariushoch.de>
On Sun, 18 Jun 2023 15:42:40 +0200, Marius Hoch wrote:
> I just booted with acpi=noirq, the PCI device no longer fails to be
> enabled and the device got assigned IRQ 19 now (according to lspci -v/
> proc/interrupts), while the freefall device remained at IRQ 18.
> Interestingly dmesg is full of spam from the freefall device (endlessly
> reporting that freefall got detected, probably indicating a problem in
> IRQ handling, yikes).
Unfortunately, while acpi=noirq can be useful for testing purposes and
bug investigation, there's no guarantee that a modern x86 system can
actually work properly without ACPI-based PCI routing.
> Booting without the smo8800 module results in:
> [root@fedora ~]# dmesg | grep -i smbus
> [ 20.042515] i801_smbus 0000:00:1f.3: PCI->APIC IRQ transform: INT C
> -> IRQ 19
> [ 20.042548] i801_smbus 0000:00:1f.3: SPD Write Disable is set
> [ 20.042574] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt
> [ 20.051270] i801_smbus 0000:00:1f.3: Accelerometer lis3lv02d is
> present on SMBus but its address is unknown, skipping registration
> [ 20.253942] i801_smbus 0000:00:1f.3: Transaction timeout
> [ 20.461962] i801_smbus 0000:00:1f.3: Transaction timeout
>
> The "Transaction timeout" messages might indicate that interrupt routing
> isn't actually working?
Indeed. This means the driver waited for an interrupt but was never
called back.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2023-06-19 15:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-14 10:36 [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450 Marius Hoch
2023-05-14 10:36 ` [PATCH 1/2] " Marius Hoch
2023-05-14 12:06 ` kernel test robot
2023-05-14 12:06 ` kernel test robot
2023-06-04 14:38 ` Jean Delvare
2023-06-18 13:08 ` Marius Hoch
2023-05-14 10:36 ` [PATCH 2/2] i2c: i801: Force no IRQ for further Dell Latitudes Marius Hoch
2023-05-23 18:03 ` [PATCH 0/2] i2c: i801: Force no IRQ for Dell Latitude E7450 Jean Delvare
2023-06-03 9:24 ` Marius Hoch
2023-06-04 14:01 ` Jean Delvare
2023-06-04 14:31 ` Jean Delvare
2023-06-04 20:41 ` Rudolf Marek
2023-06-18 12:52 ` Marius Hoch
2023-06-18 13:42 ` Marius Hoch
2023-06-19 15:19 ` Jean Delvare [this message]
2023-07-19 19:27 ` Pali Rohár
2023-10-29 17:17 ` Wolfram Sang
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=20230619171912.5407a7eb@endymion.delvare \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@mariushoch.de \
/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