From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Regression in 6.8 from "ACPI: OSL: Use a threaded interrupt handler for SCI"
Date: Mon, 8 Jul 2024 10:07:56 +0200 [thread overview]
Message-ID: <205bd84a-fe8e-4963-968e-0763285f35ba@message-id.googlemail.com> (raw)
Hi all,
any kernels after 6.7 break my trusty old Toughbook CF-51 by rendering
many PCI devices unusable.
I did first notice that i915 did no longer work and filed
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11437, there I
was pointed to commit
commit 7a36b901a6eb0e9945341db71ed3c45c7721cfa9
Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Date: Mon Nov 27 20:57:43 2023 +0100
ACPI: OSL: Use a threaded interrupt handler for SCI
which I verified with a week-long bisecting from 6.7 to 6.8 (just for
fun :-)
Just reverting this commit top of 6.10-rc5 (sorry, this machine is not
very powerful so I did not try the latest git master) makes everything
work fine again.
I get these messages in dmesg when running the broken kernels:
[ T308] genirq: Flags mismatch irq 9. 00000080 (yenta) vs. 00002080 (acpi)
[ T305] genirq: Flags mismatch irq 9. 00000080 (uhci_hcd:usb1) vs.
00002080 (acpi)
[ T305] genirq: Flags mismatch irq 9. 00000080 (uhci_hcd:usb1) vs.
00002080 (acpi)
[ T46] genirq: Flags mismatch irq 9. 00000080 (ehci_hcd:usb1) vs.
00002080 (acpi)
[ T312] genirq: Flags mismatch irq 9. 00000080 (firewire_ohci) vs.
00002080 (acpi)
[ T305] genirq: Flags mismatch irq 9. 00000080 (uhci_hcd:usb1) vs.
00002080 (acpi)
[ T308] genirq: Flags mismatch irq 9. 00000080 (yenta) vs. 00002080 (acpi)
[ T592] genirq: Flags mismatch irq 9. 00000080 (snd_intel8x0) vs.
00002080 (acpi)
[ T581] genirq: Flags mismatch irq 9. 00000080 (i915) vs. 00002080 (acpi)
[ T874] genirq: Flags mismatch irq 9. 00000080 (enp2s1) vs. 00002080 (acpi)
These are not present with that commit reverted.
The machine has an old Pentium M (Dothan):
toughbook:~ # cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Pentium(R) M processor 1.60GHz
stepping : 6
microcode : 0x18
cpu MHz : 1600.000
cache size : 2048 KB
fdiv_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush
dts acpi mmx fxsr sse sse2 ss tm pbe bts cpuid est tm2
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
swapgs itlb_multihit mmio_unknown
bogomips : 3193.05
clflush size : 32
cache_alignment : 32
address sizes : 36 bits physical, 32 bits virtual
power management:
and is running an i686 pae kernel:
toughbook:~ # uname -a
Linux toughbook 6.10.0-rc5-pae-seife+ #17 PREEMPT_DYNAMIC Sat Jul 6
07:36:41 CEST 2024 i686 i686 i386 GNU/Linux
I can provide more information on request
Best regards
--
Stefan Seyfried
"For a successful technology, reality must take precedence over
public relations, for nature cannot be fooled." -- Richard Feynman
next reply other threads:[~2024-07-08 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-08 8:07 Stefan Seyfried [this message]
2024-07-08 13:50 ` Regression in 6.8 from "ACPI: OSL: Use a threaded interrupt handler for SCI" Wysocki, Rafael J
2024-07-10 13:13 ` Rafael J. Wysocki
2024-07-11 5:04 ` Stefan Seyfried
2024-07-11 10:21 ` Rafael J. Wysocki
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=205bd84a-fe8e-4963-968e-0763285f35ba@message-id.googlemail.com \
--to=stefan.seyfried@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
/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