From: "Stefan Dösinger" <stefandoesinger-RbZlAiThDcE@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Subject: Re: S3 resume broken in 2.6.
Date: Tue, 22 Jun 2004 12:19:19 +0000 [thread overview]
Message-ID: <200406221219.20439.stefandoesinger@gmx.at> (raw)
In-Reply-To: <20040621141227.GD14607-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
> Which driver does your sound card drive? Better would be to give
> this driver an empty suspend/resume method that does nothing.
i810_audio or snd_intel8x0.
In my system, there's at least one other card which causes the same problem.
> > I attached a path which undoes the change described above and should make
> > S3 work again.
>
> Overall the pci config space save/restore fixes much more resume
> problems than it causes new one, so this sledgehammer is the wrong
> solution.
I agree. I'd prefer a solution for the pci_write config fix.
The strange thing is that I can fix the PCI configuration with setpci after
resume.
Disabling the default resume is a quick help for my system.
I can provide further information if necessary.
Stefan
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
prev parent reply other threads:[~2004-06-22 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 2:53 S3 resume broken in 2.6.7 Adrian Yee
[not found] ` <GMail.1087700004.208457790.35614235518-CDLCgzMZgTDYtjvyW6yDsg@public.gmane.org>
2004-06-21 15:39 ` Stefan Dösinger
[not found] ` <200406211539.48269.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-06-21 14:12 ` Andi Kleen
[not found] ` <20040621141227.GD14607-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-06-22 12:19 ` Stefan Dösinger [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=200406221219.20439.stefandoesinger@gmx.at \
--to=stefandoesinger-rbzlaithdce@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ak-l3A5Bk7waGM@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