xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Kevin Tian <kevin.tian@intel.com>,
	Fengzhe Zhang <fengzhe.zhang@intel.com>,
	mingo@redhat.com, hpa@zytor.com,
	Ian Campbell <Ian.Campbell@eu.citrix.com>,
	JBeulich@novell.com, xen-devel@lists.xensource.com,
	Lars Boegild Thomsen <lth@cow.dk>
Subject: [regression] Ideapad S10-3 does not wake up from suspend (Re: [PATCH v2 2/2] x86: don't unmask disabled irqs when migrating them)
Date: Sun, 28 Aug 2011 23:15:42 -0500	[thread overview]
Message-ID: <20110829041532.GA22087@elie.gateway.2wire.net> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1505C8ED7F7E3@shsmsx502.ccr.corp.intel.com>

Hi,

Lars Boegild Thomsen writes[1]:

> After update from 2.6 kernel to 3.0 my Idepad S10-3 will not wake up after 
> sleep.  Back to latest 2.6 kernel works fine.
[...]
> Upon wakeup, the power light go from slow flashing to on, the battery light 
> goes from off to on, the hdd light blink once and then everything is dead.  
> Nothing happens on the screen, all keys dead.  The fan/hdd switch on 
> physically (very hard to hear on this model or I am getting deaf).  
> Ctrl+alt+del or the alt+sysreq is non-responsive.  The only LED that show 
> keyboard status is CAPS lock and that is unresponsive too.  Only way I have 
> found to get it rebooted is holding down the power button a few secs until it 
> switch physically off and then switch it on again.
[...]
> Here's the result of the final bisect:
>
> 983bbf1af0664b78689612b247acb514300f62c7 is the first bad commit
[...]
> I also tried to go back to HEAD and manually change arch/x86/irq.c revert this 
> particular commit and it works.

For reference:

> commit 983bbf1af0664b78689612b247acb514300f62c7
> Author: Tian, Kevin <kevin.tian@intel.com>
> Date:   Fri May 6 14:43:56 2011 +0800
>
>    x86: Don't unmask disabled irqs when migrating them
>
>    It doesn't make sense to unconditionally unmask a disabled irq when
>    migrating it from offlined cpu to another. If the irq triggers then it
>    will be disabled in the interrupt handler anyway. So we can just avoid
>    unmasking it.
> 
>    [ tglx: Made masking unconditional again and fixed the changelog ]
> 
>    Signed-off-by: Fengzhe Zhang <fengzhe.zhang@intel.com>
>    Signed-off-by: Kevin Tian <kevin.tian@intel.com>
>    Cc: Ian Campbell <Ian.Campbell@citrix.com>
>    Cc: Jan Beulich <JBeulich@novell.com>
>    Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
>    Link: http://lkml.kernel.org/r/%3C625BA99ED14B2D499DC4E29D8138F1505C8ED7F7E3%40shsmsx502.ccr.corp.intel.com%3
>    Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
>
> diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
> index 544efe2741be..6c0802eb2f7f 100644
> --- a/arch/x86/kernel/irq.c
> +++ b/arch/x86/kernel/irq.c
> @@ -276,7 +276,8 @@ void fixup_irqs(void)
>  		else if (!(warned++))
>  			set_affinity = 0;
>  
> -		if (!irqd_can_move_in_process_context(data) && chip->irq_unmask)
> +		if (!irqd_can_move_in_process_context(data) &&
> +		    !irqd_irq_disabled(data) && chip->irq_unmask)
>  			chip->irq_unmask(data);
>  
>  		raw_spin_unlock(&desc->lock);

Known problem?  Ideas?

Regards,
Jonathan

[1] http://bugs.debian.org/635575

  parent reply	other threads:[~2011-08-29  4:15 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  6:43 [PATCH v2 2/2] x86: don't unmask disabled irqs when migrating them Tian, Kevin
2011-05-06  9:59 ` Thomas Gleixner
2011-05-06 12:54   ` Tian, Kevin
2011-05-06 13:14     ` [Xen-devel] " Tian, Kevin
2011-05-06 13:24     ` Thomas Gleixner
2011-05-06 14:04       ` Ian Campbell
2011-05-08  1:44         ` Jeremy Fitzhardinge
2011-05-09  0:44           ` Tian, Kevin
2011-05-09  1:45             ` Jeremy Fitzhardinge
2011-05-06 14:28     ` Stefano Stabellini
2011-05-06 21:43       ` Tian, Kevin
2011-05-09  2:11       ` Tian, Kevin
2011-05-09 12:02         ` Stefano Stabellini
2011-05-09 12:36           ` Thomas Gleixner
2011-05-10  3:24             ` Tian, Kevin
2011-05-18 23:49               ` Tian, Kevin
2011-05-19 12:08                 ` Stefano Stabellini
2011-05-19 16:18                   ` Konrad Rzeszutek Wilk
2011-08-29  4:15 ` Jonathan Nieder [this message]
2011-08-31  1:04   ` [regression] Ideapad S10-3 does not wake up from suspend (Re: [PATCH v2 2/2] x86: don't unmask disabled irqs when migrating them) Dave Hansen
2011-08-31  8:22     ` Jonathan Nieder
2011-09-02  3:01       ` Serge E. Hallyn
2011-09-01  6:24   ` Tian, Kevin
2012-05-12 23:13     ` [regression] Ideapad S10-3 does not wake up from suspend Jonathan Nieder
2012-05-13  1:22       ` Lars Boegild Thomsen
2012-07-15 23:24         ` Jonathan Nieder
2012-04-15 14:06   ` Jonathan Nieder
2012-04-16 18:05     ` Robert Scott
2012-04-17  2:04       ` Jonathan Nieder
2012-04-18 10:03         ` Lars Boegild Thomsen
2012-04-22 16:34           ` [Xen-devel] " Pasi Kärkkäinen
2012-04-21 13:14         ` Robert Scott
2012-05-06 12:44         ` Robert Scott

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=20110829041532.GA22087@elie.gateway.2wire.net \
    --to=jrnieder@gmail.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=JBeulich@novell.com \
    --cc=fengzhe.zhang@intel.com \
    --cc=hpa@zytor.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lth@cow.dk \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=xen-devel@lists.xensource.com \
    /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).