From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mikko Vinni <mmvinni@yahoo.com>, Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Allen Kay <allen.m.kay@intel.com>,
Jean Guyader <jean.guyader@eu.citrix.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [linux-pm] "i8042: Can't reactivate AUX port" after s2ram on 3.4-rc2
Date: Fri, 13 Apr 2012 22:19:22 +0200 [thread overview]
Message-ID: <201204132219.23106.rjw@sisk.pl> (raw)
In-Reply-To: <1334346546.93033.YahooMailNeo@web161806.mail.bf1.yahoo.com>
On Friday, April 13, 2012, Mikko Vinni wrote:
> From: Rafael J. Wysocki:
>
> > On Friday, April 13, 2012, Mikko Vinni wrote:
> >> Bug report:
> >> https://bugzilla.kernel.org/show_bug.cgi?id=43099
> >>
> >> Briefly:
> >>
> >> After s2ram the touchpad on a HP dv5 laptop doesn't work anymore.
> >>
> >> dmesg contains this about the touchpad
> >> Apr 11 18:00:05 koni kernel: i8042: Can't write CTR while closing AUX
> > port
> >> Apr 11 18:00:08 koni kernel: i8042: Can't reactivate AUX port
> >>
> >>
> >> Full log in bugzilla with PCI and i8042 debug turned on.
> >>
> >> Bisected to:
> >>
> >> commit 26f41062f28de65e11d3cf353e52d0be73442be1
> >> Author: Kay, Allen M <allen.m.kay@intel.com>
> >> Date: Thu Jan 26 10:25:53 2012 -0800
> >>
> >> PCI: check for pci bar restore completion and retry
> >>
> >> On some OEM systems, pci_restore_state() is called while FLR has not
> > yet
> >> completed. As a result, PCI BAR register restore is not successful.
> > This fix
> >> reads back the restored value and compares it with saved value and
> > re-tries 10
> >> times before giving up.
> >
> > Does reverting the above commit on top of the current Linus' tree fix the
> > problem for you?
>
>
> It does (at least with the tree from yesterday, 4166fb64593514ad920b7dbd290e0a934b37d24a).
OK, thanks.
Please change that dev_dbg() in pci_restore_state() into dev_info()
and see how many times it gets printed with the commit applied (not reverted).
[Margin note: I think it would make more sense to read the value from
the register _after_ and not before the waiting and I'm not exactly sure why
msleep() is not used.]
Thanks,
Rafael
next prev parent reply other threads:[~2012-04-13 20:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1334310754.17013.YahooMailNeo@web161804.mail.bf1.yahoo.com>
2012-04-13 19:18 ` [linux-pm] "i8042: Can't reactivate AUX port" after s2ram on 3.4-rc2 Rafael J. Wysocki
2012-04-13 19:49 ` Mikko Vinni
2012-04-13 20:19 ` Rafael J. Wysocki [this message]
2012-04-13 20:47 ` Mikko Vinni
2012-04-14 22:11 ` Rafael J. Wysocki
2012-04-15 10:39 ` Mikko Vinni
2012-04-15 18:30 ` Rafael J. Wysocki
2012-04-15 19:52 ` Rafael J. Wysocki
2012-04-15 20:56 ` Rafael J. Wysocki
2012-04-16 7:23 ` Mikko Vinni
2012-04-16 16:17 ` Rafael J. Wysocki
2012-04-16 18:57 ` Mikko Vinni
2012-04-16 19:59 ` Rafael J. Wysocki
2012-04-16 20:35 ` [PATCH] PCI: Retry BARs restoration for Type 0 headers only Rafael J. Wysocki
2012-04-16 20:35 ` Linus Torvalds
2012-04-16 21:07 ` Rafael J. Wysocki
2012-04-16 5:15 ` [linux-pm] "i8042: Can't reactivate AUX port" after s2ram on 3.4-rc2 Mikko Vinni
2012-04-16 16:14 ` Rafael J. Wysocki
2012-04-15 18:32 ` [PATCH] PCI: Fix regression in pci_restore_state() Rafael J. Wysocki
2012-04-15 18:36 ` Linus Torvalds
2012-04-15 18:47 ` Rafael J. Wysocki
2012-04-15 18:59 ` Linus Torvalds
2012-04-15 19:40 ` Rafael J. Wysocki
2012-04-23 17:03 ` Bjorn Helgaas
2012-04-23 19:53 ` Rafael J. Wysocki
2012-04-23 20:07 ` Don Dutile
2012-04-23 22:33 ` Bjorn Helgaas
2012-04-24 16:03 ` Don Dutile
2012-04-24 17:01 ` Bjorn Helgaas
2012-04-24 17:35 ` Don Dutile
2012-04-27 22:20 ` Bjorn Helgaas
2012-04-15 8:12 ` [linux-pm] "i8042: Can't reactivate AUX port" after s2ram on 3.4-rc2 James Courtier-Dutton
2012-04-15 10:47 ` Mikko Vinni
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=201204132219.23106.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=allen.m.kay@intel.com \
--cc=bhelgaas@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jean.guyader@eu.citrix.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mmvinni@yahoo.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;
as well as URLs for NNTP newsgroup(s).