On Monday 07 December 2009, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=14730 > > > > > > --- Comment #7 from Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> 2009-12-07 19:51:32 --- > (switched to email. Please respond via emailed reply-to-all, not via the > bugzilla web interface). > > On Fri, 4 Dec 2009 09:02:21 GMT > bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > > http://bugzilla.kernel.org/show_bug.cgi?id=14730 > > > > Summary: sky2 won't work after suspend/resume cycle > > Product: Power Management > > Version: 2.5 > > Platform: All > > OS/Version: Linux > > Tree: Mainline > > Status: NEW > > Severity: high > > Priority: P1 > > Component: Hibernation/Suspend > > AssignedTo: power-management_other@xxxxxxxxxxxxxxxxxxxx > > ReportedBy: mat@xxxxxxxxxx > > Regression: Yes > > > > > > I use sky2 network adapter in my Fujitsu Siemens Esprimo Mobile U9200. It > > worked fine up until 2.6.31-rc3 (or at least that's the last one I tried it > > works for me) and in all versions after that I tried it stops working after > > suspend/resume cycle (I use powersave daemon, but I also tried without it - > > effect is the same). > > > > After resume what I see in dmesg is this: > > > > sky2 driver version 1.23 > > sky2 0000:04:00.0: enabling device (0000 -> 0003) > > sky2 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > > sky2 0000:04:00.0: setting latency timer to 64 > > sky2 0000:04:00.0: unsupported chip type 0xff > > It looks like reads from the device are returning all-ones. > > > sky2 0000:04:00.0: PCI INT A disabled > > sky2: probe of 0000:04:00.0 failed with error -95 > > > > So it looks like something is probably not restored correctly after resume or > > some initializations are not executed. > > > > I use Gentoo sources, but I also tried it on vanilla kernels - 2.6.31 and > > 2.6.32-rc8 and it doesn't work in any version past 2.6.31-rc3. > > > > Help. Do we think this regression is likely to be a sky2 thing, an > ACPI thing, an x86 arch thing or...? Quite frankly, I have no idea. In principle that may be a result of a PCI PM core change, but nothing comes to mind immediately. It may be worth trying to revert commit 4b77b0a2ba27d64f58f16d8d4d48d8319dda36ff Author: Rafael J. Wysocki <rjw@xxxxxxx> Date: Wed Sep 9 23:49:59 2009 +0200 PCI: Clear saved_state after the state has been restored and retesting. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
