Rafael J. Wysocki wrote: > On Tuesday 26 May 2009, Richard Atterer wrote: >> Hello, >> >> "Jerry" contacted me off-list with information about the root of the >> problem - many thanks indeed!!! >> >> It turns out that the e100 driver is responsible. (The motherboard actually >> has a r8169 chip, but I added an old Intel PCI ethernet card I own.) >> >> By rmmoding e100 before s2disk, the problem goes away. Jerry mentions that >> he once saw a message about e100 failing to load its microcode - I never >> saw such a message. >> >> The most recent e100 commit ac7c992 by Thadeu Lima de Souza Cascardo (Apr >> 28) made some changes to the behaviour in the case of shutdown vs. suspend, >> maybe the problem is there? (But note that during bisecting, I tested >> kernels older than that commit, and not all of them worked.) Before that, >> f902283 (Mar 3 2008) mentions suspend in the log message. > > OK, thanks for the information. I'll have a look at the e100 suspend-resume > code, but I really don't think commit ac7c992 is at fault here. adding Jeff Kirsher to the Cc, who currently maintains the e100 driver. Auke -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
