On czwartek 10 grudzień 2009, Rafael J. Wysocki wrote: > On Thursday 10 December 2009, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=14730 > > > > --- Comment #11 from Ilya Hegai <vyacheslavovich@xxxxxxxxx> 2009-12-10 > > 10:36:36 --- (In reply to comment #9) > > > > > On Monday 07 December 2009, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > > > http://bugzilla.kernel.org/show_bug.cgi?id=14730 > > ... > > > > 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. > > > > I'm not familiar with git, but I haven't found traces of that commit in > > 2.6.31.7 that I'm using (gentoo-sources) (and the problem exists there) > > but after I applied it (got it from git) - sky2 errors after > > hibernation/resume dissapeared > > And as I can see this patch has applied against 2.6.32, so I guess TS > > person is considered to upgrade to the latest kernel > > Hmm. The original report is against 2.6.32-rc8. > > So you're saying that the commit above, when applied against 2.6.31.7, > actually fixes a sky2 resume problem for you? > > Maciej, can you please check if 2.6.31.7 with the above commit applied > works for you? > Well... I've downloaded the patch from git. The working kernel - 2.6.31-rc3 does not have it aplied, but later versions do, so I tried to revert it on the latest gentoo sources (2.6.32) - it reverted fine, but it didn't really helped - after suspend/resume sky2 does not work. I'll try gentoo-sources-2.6.31-r7 right now and I'll let you know of the results. m. -- Maciej J. Woloszyk, <mat@xxxxxxxxxx> "Rejoice. For Very Bad tel. +48 501 033 410 Things are about to happen." JID:mat@xxxxxxxxxx Richard/Looking For Group -- 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
