mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	李朝明 <chaoming_li@realsil.com.cn>,
	"Linux PM list" <linux-pm@vger.kernel.org>,
	"Huang Ying" <ying.huang@intel.com>
Subject: Re: Question about failure in PCI power-state change
Date: Sat, 8 Sep 2012 22:29:01 +0200	[thread overview]
Message-ID: <201209082229.01465.rjw@sisk.pl> (raw)
In-Reply-To: <CAErSpo7GEkN1XLZ=UeXmDZrLnp_648mH-sLYa9hMgOqz7t+b7Q@mail.gmail.com>

On Saturday, September 08, 2012, Bjorn Helgaas wrote:
> +cc Rafael, Huang, linux-pm
> 
> On Fri, Sep 7, 2012 at 3:44 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote:
> > Hi,
> >
> > On occasion when I unload and reload driver rtl8192ce, I get the message
> >
> > "Refused to change power state, currently in D3"
> >
> > I added additional info to the printk and discovered that it was trying to
> > change to state D0. The problem seems to occur when I have made a
> > connection, unloaded the driver, and reloaded it. If I do not make a
> > connection before unloading, then the problem is a lot less likely.
> >
> > This is with kernel 3.6-rc4 from wireless-testing. A Google search shows
> > that the problem is usually due to suspend/resume difficulties, but this
> > machine has not been suspended.
> >
> > I would appreciate any help that you might give in solving this issue.

I think writing "on" to the /sys/devices/.../power/control attribute of the device
in question would help.

Thanks,
Rafael

  reply	other threads:[~2012-09-08 20:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-07 22:44 Larry Finger
2012-09-07 22:48 ` Bjorn Helgaas
2012-09-08 20:29   ` Rafael J. Wysocki [this message]
2012-09-08 21:50     ` Alan Stern
2012-09-08 22:01       ` Larry Finger
2012-09-10  0:24   ` Huang Ying
2012-09-10  3:56     ` Larry Finger

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=201209082229.01465.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bhelgaas@google.com \
    --cc=chaoming_li@realsil.com.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome