From: Hans de Goede <hdegoede@redhat.com>
To: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Maxime Ripard <maxime.ripard@free-electrons.com>,
Chen-Yu Tsai <wens@csie.org>
Subject: BUG?: kernel does not (re)set irq smp_affinity to reboot_cpu
Date: Sun, 26 Jun 2016 18:00:41 +0200 [thread overview]
Message-ID: <4dc8bd4c-8456-9f94-b7eb-c5d227ddc673@redhat.com> (raw)
Hi,
I've just spend most of my Sunday debugging a problem
where Allwinner ARM SoC based boards will not shutdown when
using a Fedora 24 userland, where as the exact same
kernel works fine with Fedora 22.
It turns out that irq-balanced is to blame. In Fedora 24
it pins the i2c controller, which talks to the pmic
which is needed for poweroff to cpu-id 1:
[root@localhost ~]# cat /proc/irq/49/smp_affinity
2
Where as the reboot_cpu is cpu-id 0 and with
cpu 1 disabled at poweroff time, the i2c transfer
never gets past its first step leading to an i2c
driver timeout + kernel panic due to machine_power_off()
returning.
As a workaround I can stop irq-balanced and do:
echo 3 > /proc/irq/49/smp_affinity
Before doing poweroff and then everything works as
expected again.
Now the question is how to fix this?
IMHO this is a kernel-bug, if we disable CPU-s then we
should unpin any irqs pinned to them before doing so.
If someone can write a fix for this I will be more then
happy to test it.
Although I'm mostly unfamiliar with the irq code I'm also
willing to try and write a fix myself, assuming that
people agree that this is the right thing to-do, and
that I can get some hints where to start.
Regards,
Hans
p.s.
I also noticed the following in the arm reboot code:
void machine_power_off(void)
{
local_irq_disable();
smp_send_stop();
if (pm_power_off)
pm_power_off();
}
And I cannot help but wonder what re-enables local-irqs ?
Clearly something does as they are needed for the i2c
communication done by the m_power_off() call.
next reply other threads:[~2016-06-26 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-26 16:00 Hans de Goede [this message]
2016-06-27 9:13 ` Marc Zyngier
2016-06-27 9:45 ` Russell King - ARM Linux
2016-06-27 10:55 ` Hans de Goede
2016-06-27 11:31 ` Russell King - ARM Linux
2016-06-27 11:46 ` Russell King - ARM Linux
2016-06-27 12:53 ` Hans de Goede
2016-06-27 13:57 ` Russell King - ARM Linux
2016-06-27 14:37 ` Hans de Goede
2016-06-27 14:54 ` Mark Rutland
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=4dc8bd4c-8456-9f94-b7eb-c5d227ddc673@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=tglx@linutronix.de \
--cc=wens@csie.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®