Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: "Benjamin S." <sbenni@xxxxxx>
- Date: Sun, 14 Jun 2009 14:59:10 +0200
On Sun, 14 Jun 2009 14:43:11 +0200 (CEST)
Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote:
On Sun, 14 Jun 2009, Benjamin S. wrote:
19: 0 17 IO-APIC-fasteoi ehci_hcd:usb4, HDA Intel
24: 4830 0 HPET_MSI-edge hpet2
This is probably the culprit. Try booting with hpet=disble and check
whether your resume works.
With this option set resume works.
Benjamin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Thomas Gleixner
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- References:
- 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Benjamin S.
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Rafael J. Wysocki
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Thomas Gleixner
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Rafael J. Wysocki
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Benjamin S.
- Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- From: Thomas Gleixner
- 2.6.30 enabling cpu1 on resume fails after suspend to memory
- Prev by Date: Re: [KVM PATCH v2 2/2] kvm: use POLLHUP to close an irqfd instead of an explicit ioctl
- Next by Date: Re: [PATCH 1/2] lib: Provide generic atomic64_t implementation
- Previous by thread: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- Next by thread: Re: 2.6.30 enabling cpu1 on resume fails after suspend to memory
- Index(es):
Relevant Pages
|
