From: lizefan@huawei.com (Li Zefan)
To: linux-arm-kernel@lists.infradead.org
Subject: backport patches to 2.6.34 to remove __ARCH_WANT_INTERRUPTS_ON_CTXSW?
Date: Tue, 29 Jan 2013 17:16:51 +0800 [thread overview]
Message-ID: <51079383.60406@huawei.com> (raw)
In-Reply-To: <51077966.1060703@huawei.com>
On 2013/1/29 15:25, Li Zefan wrote:
> Hi Catalin,
>
> We got system crashes, and then we managed to trigger the bug within minutes,
> and we found this in upstream, which also backported to 2.6.34 stable:
>
> commit cb297a3e433dbdcf7ad81e0564e7b804c941ff0d
> Author: Chanho Min <chanho0207@gmail.com>
> Date: Thu Jan 5 20:00:19 2012 +0900
>
> sched/rt: Fix task stack corruption under __ARCH_WANT_INTERRUPTS_ON_CTXSW
>
> The bug described in this commit resembles to ours. Unfortunately After applying
> the fix, we still get crash in hours. We tried to bind each real-time task to a
> single cpu to make sure no cpu migration will happen, and it ran without any
> problem for ~20 hours.
>
> We're still investigating this issue. One thing I'm doing is backporting patches
> that removes __ARCH_WANT_INTERRUPTS_ON_CTXSW. With those patches, I can boot
> the kernel, but it hung up when the system automatically start nfs and later
> soft-lockup was reported. Things are fine if I disable nfs startup and start it
> manually.
>
I've confirmed it's the 1st patch that causes this lockup.
> So did I miss something when backporting, or is it infeasible to backport them
> to 2.6.34? We're using ARMv7. I've attached the patches I backported.
>
next prev parent reply other threads:[~2013-01-29 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 7:25 backport patches to 2.6.34 to remove __ARCH_WANT_INTERRUPTS_ON_CTXSW? Li Zefan
2013-01-29 9:16 ` Li Zefan [this message]
2013-02-02 9:19 ` Li Zefan
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=51079383.60406@huawei.com \
--to=lizefan@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).