From: Matthew Garrett <mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 problem: No PCI-interrupts after resume
Date: Sat, 19 Jun 2004 23:02:40 +0100 [thread overview]
Message-ID: <1087682560.19031.18.camel@tyrosine> (raw)
In-Reply-To: <200406192347.27053.cr7-IG//nw+yl+iQIjdd1DhZXWfrygkm6VTR@public.gmane.org>
On Sat, 2004-06-19 at 23:47 +0200, Carsten Rietzschel wrote:
> I'm trying to get S3 Suspend to RAM running on my KT333CF-Board.
> But after resuming: USB, soundcard, firewire + eth don't work (read as: no
> PCI-devices except IDE) . In proc/interrupts I saw no interrupts for these
> devices were incremented after resume.
> Kernel version is 2.6.7 with acpi update from len
> (acpi-20040326-2.6.7.diff.gz), but same for older versions of 2.6.x.
Do you have APIC support in your kernel? If so, try disabling it. I get
no interrupts if I use APIC support, but everything is fine otherwise.
What should be setting up the APIC on resume?
--
Matthew Garrett | mjg59-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
next prev parent reply other threads:[~2004-06-19 22:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 21:47 S3 problem: No PCI-interrupts after resume Carsten Rietzschel
[not found] ` <200406192347.27053.cr7-IG//nw+yl+iQIjdd1DhZXWfrygkm6VTR@public.gmane.org>
2004-06-19 22:02 ` Matthew Garrett [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-20 10:41 Carsten Rietzschel
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=1087682560.19031.18.camel@tyrosine \
--to=mjg59-1xo5oi07kqx4cg9nei1l7q@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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