From: Murali Karicheri <m-karicheri2@ti.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: possible reason: unannotated irqs-off
Date: Mon, 21 Sep 2015 11:44:54 -0400 [thread overview]
Message-ID: <560025F6.6030700@ti.com> (raw)
In-Reply-To: <20150918170226.GK21084@n2100.arm.linux.org.uk>
Russell,
On 09/18/2015 01:02 PM, Russell King - ARM Linux wrote:
> On Fri, Sep 18, 2015 at 12:02:15PM -0400, Murali Karicheri wrote:
>> While chasing a fix for a deadlock in netcp driver with debug options
>> enabled, i bumped on another warning shown below.. Looks like I need to
>> enable CONFIG_IRQSOFF_TRACER as well to get rid of this. Have anyone seen
>> this? My google search showed me some connection with this option and I
>> enabled it as well and I don't see the warning anymore. Any idea if this is
>> a false alarm or a real bug? Looks like I need to enable
>> CONFIG_IRQSOFF_TRACER as well. If so, I can send a patch. Either way let me
>> know.
>
> Do you have this commit applied?
No. We are using v4.1.x.
>
> commit 3302caddf10ad50710dbb7a94ccbdb3ad5bf1412
> Author: Russell King <rmk+kernel@arm.linux.org.uk>
> Date: Thu Aug 20 16:13:37 2015 +0100
>
> ARM: entry: efficiency cleanups
>
I have cherry-picked this one, but ran into some conflicts which I have
fixed. Will try and let you know.
Thanks
--
Murali Karicheri
Linux Kernel, Keystone
next prev parent reply other threads:[~2015-09-21 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 16:02 possible reason: unannotated irqs-off Murali Karicheri
2015-09-18 17:02 ` Russell King - ARM Linux
2015-09-21 15:44 ` Murali Karicheri [this message]
2015-09-21 20:26 ` Murali Karicheri
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=560025F6.6030700@ti.com \
--to=m-karicheri2@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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