Bug 43099
Summary: | touchpad lost with "i8042: Can't reactivate AUX port" after s2ram | ||
---|---|---|---|
Product: | Drivers | Reporter: | Mikko Vinni (mmvinni) |
Component: | PCI | Assignee: | drivers_pci (drivers_pci) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | rjw |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.4.0-rc2 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: |
dmesg with touchpad failing after 1st s2ram, working after 2nd and 3rd
dmesg of 3.4.0-rc2+ with 26f41062f28 reverted |
Description
Mikko Vinni
2012-04-13 09:28:31 UTC
Created attachment 72905 [details]
dmesg of 3.4.0-rc2+ with 26f41062f28 reverted
dmesg with the commit 26f41062f28de65e11d3cf353e52d0be73442be1
reverted, one s2ram, touchpad works
I should add that this machine suffers from https://bugzilla.kernel.org/show_bug.cgi?id=35452 ("Devices not available after resume from suspend to RAM") which explains a lot of the noise in the logs. Is the problem in comment #2 independent of whether or not the problematic commit is reverted? Yes, they are independent. (My part of) Bug #35452 was reported with 2.6.39-rc7, but that problem existed before and still does. Commit 26f41062f28de65e11d3cf353e52d0be73442be1 was merged in mainline for v3.4-rc1 on Fri Mar 23 14:02:12 2012 -0700. ---- I did some testing today removing pcie_aspm=force from kernel parameters. Without it I get this message: pci 0000:08:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force' Unfortunately, having/not having the parameter makes no difference to any of the problems. The touchpad seemed to survive without the pcie_aspm=force option and without X (in single user mode) a s2ram in one test run only, but it failed when I tried to confirm by testing again. I posted a patch to try to the lists: https://lkml.org/lkml/2012/4/14/214 Fixed by ebfc5b802fa76baeb4371311ff9fc27a2258d90d "PCI: Fix regression in pci_restore_state(), v3" and a6cb9ee7cabe68002c3f2ab07224ea27d2617cf1 "PCI: Retry BARs restoration for Type 0 headers only" around v3.4-rc3. Hopefully the OEM systems fixed by 26f41062f28d are still working, too. |