From: David Miller <davem@davemloft.net>
To: grawity@gmail.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] jme: fix irq storm after suspend/resume
Date: Mon, 24 Oct 2011 02:58:22 -0400 (EDT) [thread overview]
Message-ID: <20111024.025822.548298031734112062.davem@davemloft.net> (raw)
In-Reply-To: <j7uqst$kpc$1@dough.gmane.org>
From: "Mantas M." <grawity@gmail.com>
Date: Sat, 22 Oct 2011 19:27:09 +0300
> On 22/10/11 15:56, Clemens Buchacher wrote:
>> If the device is down during suspend/resume, interrupts are enabled
>> without a registered interrupt handler, causing a storm of
>> unhandled interrupts until the IRQ is disabled because "nobody
>> cared".
>>
>> Instead, check that the device is up before touching it in the
>> suspend/resume code.
>>
>> Fixes https://bugzilla.kernel.org/show_bug.cgi?id=39112
>
> Just tested the patch, suspend/resume works well.
Applied, thanks.
prev parent reply other threads:[~2011-10-24 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 12:56 [PATCH] jme: fix irq storm after suspend/resume Clemens Buchacher
2011-10-22 13:09 ` Mohammed Shafi
2011-10-22 16:27 ` Mantas M.
2011-10-24 6:58 ` David Miller [this message]
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=20111024.025822.548298031734112062.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=grawity@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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).