From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] soc: ti: reset irq affinity before freeing irq
Date: Thu, 27 Aug 2015 17:43:47 -0400 [thread overview]
Message-ID: <55DF8493.7090307@ti.com> (raw)
In-Reply-To: <55DF58A0.8090105@oracle.com>
On 08/27/2015 02:36 PM, santosh.shilimkar at oracle.com wrote:
> On 8/27/15 11:34 AM, Nathan Lynch wrote:
>> On 08/27/2015 01:23 PM, Murali Karicheri wrote:
>>> On 08/27/2015 12:43 PM, Nathan Lynch wrote:
>>>> On 08/27/2015 10:51 AM, Murali Karicheri wrote:
>>>>> When using accumulator queue for rx side for network driver, following
>>>>> warning is seen when doing a reboot command from Linux console. This
>>>>> is because, affinity value is not reset before calling free_irq().
>>>>> This
>>>>> patch fixes this.
>>>>>
>>>>> Deconfiguring network interfaces...
>>>>> [ 55.176589] ------------[ cut here ]-----------
>>>>> [ 55.181232] WARNING: CPU: 0 PID: 2081 at kernel/irq/manage.c:1370
>>>>> __free_irq+0x208/0x214
>>>>
>>>> The full content of the warning should be included in the commit
>>>> message; __free_irq has several potential sources of warning messages,
>>>> and line 1370 doesn't correspond to any of them in 4.2-rc8.
>>>
>>> The log corresponds to 4.1.x kernel. Corresponding WARN_ONCE is
>>>
>>> #ifdef CONFIG_SMP
>>> /* make sure affinity_hint is cleaned up */
>>> if (WARN_ON_ONCE(desc->affinity_hint))
>>> desc->affinity_hint = NULL;
>>> #endif
>>>
>>> Which is line 1922. I can edit to make it 1922. Does that work?
>>
>> Eh, I guess I wasn't thinking clearly about this clearly when I wrote
>> that. (I somehow had the notion that WARN_ON... maybe printed more than
>> just the file and line number, but that is clearly mistaken.) I think
>> your message is fine as is, sorry for the noise.
>>
>> I don't think changing the line number will make it any easier on future
>> readers.
>>
> Right. Just leave the full call in the commit so that the context
> is captured.
>
>
Will do that and resend it
--
Murali Karicheri
Linux Kernel, Keystone
WARNING: multiple messages have this Message-ID (diff)
From: Murali Karicheri <m-karicheri2@ti.com>
To: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>,
Nathan Lynch <Nathan_Lynch@mentor.com>
Cc: <ssantosh@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] soc: ti: reset irq affinity before freeing irq
Date: Thu, 27 Aug 2015 17:43:47 -0400 [thread overview]
Message-ID: <55DF8493.7090307@ti.com> (raw)
In-Reply-To: <55DF58A0.8090105@oracle.com>
On 08/27/2015 02:36 PM, santosh.shilimkar@oracle.com wrote:
> On 8/27/15 11:34 AM, Nathan Lynch wrote:
>> On 08/27/2015 01:23 PM, Murali Karicheri wrote:
>>> On 08/27/2015 12:43 PM, Nathan Lynch wrote:
>>>> On 08/27/2015 10:51 AM, Murali Karicheri wrote:
>>>>> When using accumulator queue for rx side for network driver, following
>>>>> warning is seen when doing a reboot command from Linux console. This
>>>>> is because, affinity value is not reset before calling free_irq().
>>>>> This
>>>>> patch fixes this.
>>>>>
>>>>> Deconfiguring network interfaces...
>>>>> [ 55.176589] ------------[ cut here ]-----------
>>>>> [ 55.181232] WARNING: CPU: 0 PID: 2081 at kernel/irq/manage.c:1370
>>>>> __free_irq+0x208/0x214
>>>>
>>>> The full content of the warning should be included in the commit
>>>> message; __free_irq has several potential sources of warning messages,
>>>> and line 1370 doesn't correspond to any of them in 4.2-rc8.
>>>
>>> The log corresponds to 4.1.x kernel. Corresponding WARN_ONCE is
>>>
>>> #ifdef CONFIG_SMP
>>> /* make sure affinity_hint is cleaned up */
>>> if (WARN_ON_ONCE(desc->affinity_hint))
>>> desc->affinity_hint = NULL;
>>> #endif
>>>
>>> Which is line 1922. I can edit to make it 1922. Does that work?
>>
>> Eh, I guess I wasn't thinking clearly about this clearly when I wrote
>> that. (I somehow had the notion that WARN_ON... maybe printed more than
>> just the file and line number, but that is clearly mistaken.) I think
>> your message is fine as is, sorry for the noise.
>>
>> I don't think changing the line number will make it any easier on future
>> readers.
>>
> Right. Just leave the full call in the commit so that the context
> is captured.
>
>
Will do that and resend it
--
Murali Karicheri
Linux Kernel, Keystone
next prev parent reply other threads:[~2015-08-27 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 15:51 [PATCH] soc: ti: reset irq affinity before freeing irq Murali Karicheri
2015-08-27 15:51 ` Murali Karicheri
2015-08-27 16:39 ` santosh.shilimkar at oracle.com
2015-08-27 16:39 ` santosh.shilimkar
2015-08-27 16:43 ` Nathan Lynch
2015-08-27 16:43 ` Nathan Lynch
2015-08-27 18:23 ` Murali Karicheri
2015-08-27 18:23 ` Murali Karicheri
2015-08-27 18:34 ` Nathan Lynch
2015-08-27 18:34 ` Nathan Lynch
2015-08-27 18:36 ` santosh.shilimkar at oracle.com
2015-08-27 18:36 ` santosh.shilimkar
2015-08-27 21:43 ` Murali Karicheri [this message]
2015-08-27 21:43 ` 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=55DF8493.7090307@ti.com \
--to=m-karicheri2@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.