From: Jim Bos <jim876@xs4all.nl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: jiang.liu@linux.intel.com, tglx@linutronix.de
Subject: ACPI events broken on non-SMP since 3.16
Date: Sun, 05 Apr 2015 16:43:25 +0200 [thread overview]
Message-ID: <55214A0D.9000404@xs4all.nl> (raw)
Hello,
Since around 3.16 ACPI events aren't working on a single processor
system, I found this on an old Dell laptop Pentium-M and on AMD geode board.
By ACPI events I mean, acpid (via netlink) and acpi_listen doesn't give
anything when pressing ACPI power button.
Simply 'nosmp' on recent kernel on modern 2-core Celeron system also
stops acpid from working.
Note that booting an SMP kernel with single core isn't enough to break
this, smp really needs to be disabled by 'nosmp' or running it on a
older motherboard without I/O apic ('smbboot: SMP disabled' in dmesg).
With some problems managed to bisect this using VirtualBox guest, which
allows to to specify number of CPU's and having yes/no an I/O Apic.
It bisects to this commit which unfortunately doesn't revert cleanly on
latest 4.0-rcX:
commit 16ee7b3dcc56be14b9a813612cff2cc2339cdced
Author: Jiang Liu <jiang.liu@linux.intel.com>
Date: Mon Jun 9 16:20:04 2014 +0800
x86, irq: Simplify the way to handle ISA IRQ
On startup, setup_IO_APIC_irqs() will program all IOAPIC pins for ISA
IRQs. Later when mp_map_pin_to_irq() is called, it just returns ISA IRQ
number without programming corresponding IOAPIC pin.
This patch consolidates the way to program IOAPIC pins for both ISA and
non-ISA IRQs into mp_map_pin_to_irq() as below:
1) For ISA IRQs, mp_irqs array is used to map IOAPIC pin to IRQ and
mp_irqdomain_map() is used to actually program the pin.
2) For non-ISA IRQs, irqdomain is used to map IOAPIC pin to IRQ, and
mp_irqdomain_map() is also used to actually program the pin.
Any ideas ?
_
Jim
next reply other threads:[~2015-04-05 14:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-05 14:43 Jim Bos [this message]
2015-04-07 14:34 ` [PATCH] x86/ACPI: Fix regression caused by 16ee7b3dcc56 Jiang Liu
2015-04-07 16:49 ` Jim Bos
2015-04-08 5:26 ` Jiang Liu
2015-04-08 15:51 ` Jim Bos
2015-04-09 10:15 ` Jiang Liu
2015-04-09 16:41 ` Jim Bos
2015-04-10 1:56 ` Jiang Liu
2015-04-10 6:19 ` Jim Bos
2015-04-11 15:08 ` [PATCH] x86/ACPI: Fix regression caused by 16ee7b3dcc56 & c50f13c672df7 Jim Bos
2015-04-11 16:57 ` Jiang Liu
2015-04-12 1:29 ` Rafael J. Wysocki
2015-04-12 9:03 ` Jim Bos
2015-04-12 23:30 ` Rafael J. Wysocki
2015-04-13 13:36 ` Rafael J. Wysocki
2015-04-13 14:54 ` Jim Bos
2015-04-13 19:46 ` 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=55214A0D.9000404@xs4all.nl \
--to=jim876@xs4all.nl \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).