From: Thomas Gleixner <tglx@linutronix.de>
To: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Cc: "js@sig21.net" <js@sig21.net>, Matthew Wilcox <matthew@wil.cx>,
Linux PCI <linux-pci@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"Benjamin S." <sbenni@gmx.de>, Ingo Molnar <mingo@elte.hu>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
Date: Sun, 14 Jun 2009 16:45:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0906141644190.2800__29049.2408829325$1244990780$gmane$org@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0906141548490.2800@localhost.localdomain>
Benjamin,
On Sun, 14 Jun 2009, Thomas Gleixner wrote:
> On Sun, 14 Jun 2009, Pallipadi, Venkatesh wrote:
> > >Benjamin just confirmed that. The logic in disable_device_interrupts()
> > >already skips interrupts marked with IRQF_TIMER, but I suspect that
> > >the hpet/MSI interupts are not marked that way.
> > >
> >
> > For percpu hpet at offline we will have
> > - clockevent shutdown which will disable the interrupt
> > - free_irq that will unregister on CPU DEAD
>
> Well, the interupt in question is on the boot cpu which is not going
> through CPU DEAD :)
can you please test the patch below.
Thanks,
tglx
------------>
diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c
index 81408b9..dedc2bd 100644
--- a/arch/x86/kernel/hpet.c
+++ b/arch/x86/kernel/hpet.c
@@ -510,7 +510,8 @@ static int hpet_setup_irq(struct hpet_dev *dev)
{
if (request_irq(dev->irq, hpet_interrupt_handler,
- IRQF_DISABLED|IRQF_NOBALANCING, dev->name, dev))
+ IRQF_TIMER | IRQF_DISABLED | IRQF_NOBALANCING,
+ dev->name, dev))
return -1;
disable_irq(dev->irq);
next prev parent reply other threads:[~2009-06-14 14:45 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 10:09 2.6.30 enabling cpu1 on resume fails after suspend to memory Benjamin S.
2009-06-14 10:35 ` Rafael J. Wysocki
2009-06-14 10:57 ` Benjamin S.
2009-06-14 11:19 ` Rafael J. Wysocki
2009-06-14 11:48 ` Benjamin S.
2009-06-14 12:00 ` Rafael J. Wysocki
2009-06-14 12:09 ` Thomas Gleixner
2009-06-14 12:09 ` Thomas Gleixner
2009-06-14 12:15 ` Rafael J. Wysocki
2009-06-14 12:15 ` Rafael J. Wysocki
2009-06-14 12:37 ` Benjamin S.
2009-06-14 12:37 ` Benjamin S.
2009-06-14 12:43 ` Thomas Gleixner
2009-06-14 12:43 ` Thomas Gleixner
2009-06-14 12:59 ` Benjamin S.
2009-06-14 13:05 ` Thomas Gleixner
2009-06-14 13:05 ` Thomas Gleixner
2009-06-14 13:35 ` Benjamin S.
2009-06-14 13:35 ` Benjamin S.
2009-06-14 12:59 ` Benjamin S.
2009-06-14 12:46 ` Thomas Gleixner
2009-06-14 12:46 ` Thomas Gleixner
2009-06-14 13:12 ` Pallipadi, Venkatesh
2009-06-14 13:17 ` Thomas Gleixner
2009-06-14 13:26 ` Pallipadi, Venkatesh
2009-06-14 13:49 ` Thomas Gleixner
2009-06-14 13:49 ` Thomas Gleixner
2009-06-14 14:45 ` Thomas Gleixner
2009-06-14 15:03 ` Benjamin S.
2009-06-14 15:03 ` Benjamin S.
2009-06-14 15:41 ` Thomas Gleixner
2009-06-14 15:41 ` Thomas Gleixner
2009-06-14 16:12 ` Greg KH
2009-06-14 16:12 ` Greg KH
2009-06-14 16:19 ` Thomas Gleixner
2009-06-14 16:19 ` Thomas Gleixner
2009-06-15 13:12 ` Johannes Stezenbach
2009-06-15 13:12 ` Johannes Stezenbach
2009-06-14 14:45 ` Thomas Gleixner [this message]
2009-06-14 13:17 ` Thomas Gleixner
2009-06-14 12:00 ` Rafael J. Wysocki
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='alpine.LFD.2.00.0906141644190.2800__29049.2408829325$1244990780$gmane$org@localhost.localdomain' \
--to=tglx@linutronix.de \
--cc=jbarnes@virtuousgeek.org \
--cc=js@sig21.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=sbenni@gmx.de \
--cc=venkatesh.pallipadi@intel.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 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.