From: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
To: Stefan D?singer <stefandoesinger-RbZlAiThDcE@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Adrian Yee
<brewt-acpi.sf.net-CDLCgzMZgTDYtjvyW6yDsg@public.gmane.org>,
arjanv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: S3 resume broken in 2.6.7
Date: Mon, 21 Jun 2004 16:12:27 +0200 [thread overview]
Message-ID: <20040621141227.GD14607@wotan.suse.de> (raw)
In-Reply-To: <200406211539.48269.stefandoesinger-RbZlAiThDcE@public.gmane.org>
On Mon, Jun 21, 2004 at 03:39:48PM +0000, Stefan D?singer wrote:
> Am Sonntag, 20. Juni 2004 02:53 schrieb Adrian Yee:
> > Hi,
> >
> > I've had S3 resume working with 2.6.5/6 (various mm and stock) and
> > 2.6.7-rc3-mm1, but after trying 2.6.7-rc3-mm2 and 2.6.7 kernels, S3 resume
> > has stopped working. I'd rather not go through the process of modularizing
> > all the drivers and figuring out what's causing the problem, so I wanted to
> > know if anyone knows what change could have caused the problem. Thanks.
> >
> On my notebook(Acer travelmate 803) I had the same problem. A look at the
> changelog showed me, that from 2.6.7-rc2 a default resume function restores
> the pci configuration of cards without a driver. On my system, any write to
> the soundcard's pci configuration done by a kernel driver after resume causes
> a crash.
Which driver does your sound card drive? Better would be to give
this driver an empty suspend/resume method that does nothing.
> 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.
-Andi
-------------------------------------------------------
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-21 14:12 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 [this message]
[not found] ` <20040621141227.GD14607-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-06-22 12:19 ` S3 resume broken in 2.6 Stefan Dösinger
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=20040621141227.GD14607@wotan.suse.de \
--to=ak-l3a5bk7wagm@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=arjanv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=brewt-acpi.sf.net-CDLCgzMZgTDYtjvyW6yDsg@public.gmane.org \
--cc=stefandoesinger-RbZlAiThDcE@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